Remote Work and the Socio-Sexual Hierarchy III

Managing the different SSH ranks remotely

Managing the Alpha Remotely

The first thing to understand about managing an Alpha remotely is that you probably aren’t. If you are in a position to manage an Alpha, one of two things is true: either you are a higher-ranking Alpha and he is a situational Alpha within your organization, or you are operating under the pleasant delusion that your title gives you authority over a man who has never in his life happily accepted second place. In the first case, the remote environment requires you to maintain dominance through decisiveness and results rather than presence, because the situational Alpha who no longer sees you exercising authority in person will begin, perhaps unconsciously, to test the boundaries of your authority digitally. He will start making decisions without consulting you. He will begin to treat his team as his organization rather than as a subdivision of yours. This is not disloyalty. It is the Alpha’s nature reasserting itself in the absence of the physical cues that reminded him of his place in the larger hierarchy.

The correct management approach is to tighten the strategic communication loop while loosening the operational one. Give the Alpha clear strategic objectives and defined authority within his domain, and then let him run. Do not ask him for daily updates. Do not put him in status meetings with men who are not his peers. Do not, under any circumstances, CC him on emails that imply he is one of several direct reports receiving the same instructions, because the Alpha reads organizational signals the way a wolf reads the wind, and being grouped with the pack tells him you don’t understand what he is. Your communication with the Alpha should be peer-to-peer in tone, even if it is not peer-to-peer in structure. Call him. Ask his assessment. Make your decision. Move on.

The single most destructive thing you can do to an Alpha in a remote environment is to impose your process on him. The Alpha does not do your processes. Process is his domain. The moment you require an Alpha to fill out timesheets, attend stand-ups, or submit work through a project management tool designed for Deltas, you have communicated to him that you do not understand the difference between a man who sets direction and a man who follows it. He will not complain. He will simply begin looking for an organization that understands what he has to offer, and worse, he will take his Bravos with him when he goes.

Managing the Sigma Remotely

Managing a Sigma remotely requires you to accept, at the deepest level of your managerial soul, that the word “managing” does not mean what you think it means when the object of the verb is a Sigma. You are not managing him. You are negotiating a temporary alliance with an independent operator who has consented to exchange his output for your money, and who will terminate that arrangement the instant the terms become sufficiently irritating. Do not mistake this for arrogance or disloyalty. It is simply the fundamental operating condition of a man who exists outside the hierarchy and who does not experience organizational membership as a source of identity, security, or belonging. To him, it is a transaction. You, too, need to treat it like one.

The practical implications are straightforward. Define the deliverable. Define the deadline. Define the quality standard. Then disappear. Do not check in. Do not ask for progress reports. Do not invite him to team meetings unless his specific expertise is required for a specific agenda item, and even then, make his attendance optional and keep the meeting short. The Sigma will deliver, or he will tell you he can’t deliver, and either way you will know where you stand. What he will not do is perform the theater of productivity that remote management culture has substituted for actual productivity: the Slack status updates, the Jira ticket shuffling, the performative busyness that exists solely to reassure managers who have confused visibility with value.

The single greatest risk in managing a Sigma remotely is losing him to his own projects. The Sigma who is left entirely alone will eventually redirect his obsessive focus from your priorities to his own, not because he is disloyal but because the Sigma’s loyalty is to the mission, and if your mission stops being interesting, he will create more interesting ones. The way to prevent this is by ensuring that the challenges you assign him are worthy of his capabilities. The bored Sigma is soon the departed Sigma. Keep him challenged, keep the problems genuinely hard, and you will keep his attention. Bore him with routine work that any competent Delta could handle, and he will ghost you so smoothly you won’t even realize he’s gone until two weeks later.

Managing the Omega Remotely

Managing the Omega remotely is, paradoxically, both the simplest and the most delicate management task in the SSH. It is the simplest because the Omega’s needs are minimal and his behavioral patterns are the most predictable of any rank. He wants to be left alone. He wants clear tasks. He wants to be invisible. Give him these three things and he will produce competent, reliable, detail-oriented work with almost no managerial overhead. It is the most delicate because the Omega’s failure mode is not underperformance but disappearance—not the dramatic exit of an unhappy Alpha or the passive-aggressive sabotage of a frustrated Gamma, but the quiet, total withdrawal of a man who has concluded that even the minimal social demands of remote work are more than he can bear.

The manager’s task is to maintain contact without creating pressure. This is harder than it sounds, because virtually every management technique that exists was designed for men who operate within the hierarchy, and the Omega does not. One-on-ones, even brief ones, may be the most stressful thirty minutes of his week. Status updates, even written ones, require him to perform a social function—representing himself and his work to another person—that consumes far more of his cognitive resources than it would consume for a Delta or a Bravo doing the same thing. The manager who schedules a daily fifteen-minute check-in with his Delta and his Omega is applying the same technique to two entirely different organisms. The Delta finds the check-in reassuring. The Omega finds it exhausting. Scale accordingly. A weekly written update, submitted asynchronously, with the explicit understanding that no response means satisfactory performance, is worth more than ten video calls.

The final and most important principle: do not try to develop the Omega. Do not put him on a growth plan. Do not send him to communication workshops. Do not assign him a mentor. The Omega is not a broken Delta who can be fixed with the right training. He is a man who lacks the neurological equipment for social hierarchy, and no amount of professional development will install what nature did not provide. Your job is not to transform him. Your job is to create the conditions under which his actual capabilities can be utilized without the crippling overhead of social performance. The organization that figures out how to do this will discover that it has employees whose productivity-to-management-cost ratio is the best in the company. The organization that insists on treating the Omega as a socialization project will at best discover that it has an empty desk and a resignation letter.

And for the worst case scenario, see Office Space.