Remote Work and the Socio-Sexual Hierarchy II

Managing the different SSH ranks remotely

Yesterday’s post was written from the perspective of each rank operating within a remote environment. But the men doing the work are only half the equation. The other half lies with the man or woman responsible for getting productive output from men whose behavioral patterns he may not share and whose instincts in a remote-working environment will diverge from his own in ways that are entirely predictable by the SSH but invisible to anyone operating on the standard corpocratic assumption that all men are equal and all employees are interchangeable.

What follows is a manager's field guide, rank by rank, beginning today with the most important three.

Managing the Bravo Remotely

Managing a Bravo remotely is the easiest management task in the SSH, provided you understand one thing: the Bravo does not need to be managed. He needs to be directed. This is not a semantic distinction. Managing implies oversight, correction, and the monitoring of performance. Directing implies providing objectives, granting authority, and trusting execution. The Bravo who is managed will tolerate it, because Bravos are disciplined and loyal, but his performance will be suboptimal, because the time he should be spending on maintaining organizational cohesion will be partially wasted by the unnecessary friction of reporting in regularly to a superior who is incapable of adding any value to his activities.

The Bravo’s value in a remote environment is as a force multiplier for the Alpha’s authority and as the connective tissue that holds the distributed organization together. Your job as his manager is to ensure he has the information, the authority, and the access he needs to perform that function. This means including him in strategic conversations he might not have been part of in office environments, because the Bravo’s awareness of externalities depends on having access to information that flows naturally in a physical office but must be deliberately shared in a remote one. If you are filtering employee-related information before it reaches your Bravo, then you are reducing the effectiveness of the one man in your organization whose value proposition relies upon seeing the full operational picture.

The mistake most managers make with remote Bravos is treating them as senior individual contributors rather than as organizational leaders. They assign them the hardest tasks, the most complex projects, the work that requires the most skill, and then wonder why the team is falling apart. The Bravo can do that work, and do it well, but that is not his primary function. His function is to keep the team aligned, productive, and cohesive while the Alpha is focused on strategy and the Deltas are focused on execution. If your Bravo is spending eighty percent of his time on individual contribution and twenty percent on team leadership, the ratio is exactly backwards. Flip it. Give the hard technical work to your best Delta and free the Bravo to do what only a Bravo can do: hold the distributed organization together by sheer force of awareness, will, and loyalty.

Managing the Delta Remotely

Managing Deltas remotely is the most important management task in any organization, for the simple reason that Deltas are fifty to sixty percent of your male workforce and their collective output is the foundation upon which everything else rests. It is also the task that most remote managers get catastrophically wrong, because the Delta’s failure mode in a remote environment is silent. The Alpha who is dissatisfied makes demands. The Bravo who is underutilized makes suggestions. The Gamma who is frustrated makes noise. The Delta who is struggling simply produces less, says nothing, and hopes someone will notice before he give sup. No one notices, because Deltas are, by definition, the men whom no one notices until they are gone.

The Delta needs three things from his remote manager, and they are the same three things he needed in the office, except that in the office they were partially provided by the environment itself. First, he needs clarity. What is the task? What is the standard? When is it due? The Delta who receives clear instructions will execute them with a reliability that borders on the mechanical, and that reliability is worth more to your organization than any amount of Alpha charisma or Sigma brilliance, because it is the thing that keeps the lights on every single day. Second, he needs confirmation that his work matters and that the organization has a direction. The Delta’s motivation is craft-based, and craft requires a context. A man who builds beautiful furniture needs to know that someone wants the furniture. A Delta who writes excellent code needs to know that the code is going into a product that has a future. Remove that context and the craft loses its meaning.

Third, and this is the one that virtually every remote manager misses: the Delta needs peer contact. Not social contact in the HR sense, not virtual happy hours and forced team-building, but contact with other competent men who share his commitment to doing good work. The Delta’s identity is not individual. It is communal. He is part of the Brotherhood of Competence, and he draws his professional satisfaction not from individual achievement but from being part of a team of skilled men producing something worthwhile. Remote work severs that connection unless the manager deliberately maintains it. Try to pair your Deltas on projects. Create channels where they discuss technical problems and solve them together. Let them build the relationships that the office used to build automatically. The Delta who feels connected to his peers will be productive. The Delta who feels isolated will eventually quit and leave without ever telling you why.

Managing the Gamma Remotely

Managing a Gamma remotely is an exercise in containment, and the manager who approaches it as anything else is going to learn some expensive lessons about the difference between managing a difficult employee and managing a difficult personality disorder. Managing a Gamma requires a specific set of techniques that are almost exactly opposite to the techniques that work with every other rank, and that the manager who applies standard management practices to a Gamma will find that his instinctive responses tend to make the problem worse rather than better.

The core principle is this: the Gamma’s dysfunction is driven by the gap between his self-image and reality, and remote work widens that gap by removing the environmental feedback that partially constrains it. Your job as his manager is to substitute artificial constraints for the natural ones that the office provided. This means concrete, measurable deliverables with short deadlines. Not “work on the architecture document” but “deliver sections one through three by Thursday at noon.” Not “coordinate with the team” but “send your status update to these three specific people by 4 PM daily.” Then hold him ruthlessly and relentlessly accountable to your requirements. The Gamma will instinctively resist this, because the Gamma experiences structure and external boundaries imposed upon him as a personal insult. He will explain, at length, why the deadlines are arbitrary, why the format is wrong, why the real problem is something else entirely. Do not engage with him. Ignore his feedback, restate the directions, and hold him accountable

The second principle is information control. The Gamma in a remote environment will instinctively position himself as an information bottleneck, because information asymmetry is the only form of power available to a man who has no natural dominance, no organizational loyalty, and no competence sufficient to command respect on its merits. He will become the man who knows how the system works, the man whose documentation is indispensable, the man whom you have to go through to get anything done. This is not being helpful. It is a territorial strategy, and it is the single most dangerous thing a Gamma can do to a remote organization, because it creates a single point of failure that is also a single point of sabotage. The required countermeasure is redundancy. Ensure that every piece of institutional knowledge the Gamma possesses has to be documented, shared with, and accessible to at least two other people. Do not let him own any process exclusively. And when he objects, which he will absolutely do, do not explain your reasoning, because explaining your reasoning to a Gamma is an invitation to a debate that you cannot afford to have.