The Strongly-Typed Organization

Six months into my military service, a new intake of recruits was arriving and I was made the sergeant responsible for running their first week. Before they showed up I gathered the other sergeants and gave them one instruction: do not befriend anyone. Do not talk about your hobbies. Do not tell them what car you drive. Be as antisocial as you can stand, even when it feels bad.

This sounds cruel. Bear with me.

The protocol

Finland has mandatory conscription so like most Finnish men I spent a year in the army. Everyone warned me it would be the worst year of my life. I'll get back to that.

The army is the only strongly-typed organization I have ever worked in. Everyone's status is printed on their collar. Every interaction has a defined interface: you address a captain as "herra kapteeni", there is a correct way to enter a room, a correct way to ask a question, a correct way to leave. You never have to infer how to treat someone. You read their collar and the protocol resolves the rest.

Every workplace has the same hierarchy. The difference is that at work, you have to reverse-engineer it.

The wall

Back to my antisocial instruction.

A sergeant is barely above a recruit. One step. The recruits see you all day: tired, annoyed, occasionally wrong. You are visibly a nineteen-year-old. The formal system says "obey him," but the evidence says "he is basically me." Authority over that small distance is fragile, and the army knows it. That's what the rituals are actually for. Prefixes, postures, standing up when a superior enters. Formality is a tool for manufacturing distance where natural distance doesn't exist.

Every intake, some outgoing sergeant ignores this. He's friendly, he chats with the recruits about cars during the first week. And you can watch his authority crack in real time. Once they've seen the human, his commands stop being commands. They become requests from a guy they know, and requests are negotiable. For a command to work, it has to feel like it comes from the system, not from a person.

Software has a name for this: Hyrum's Law. With enough users, people will depend on your observable behavior, not your contract. The recruits stopped programming against the sergeant's interface and started programming against his implementation.

The same failure mode exists at work. The new team lead who becomes best friends with everyone and then physically cannot deliver hard feedback is the car sergeant. He leaked his implementation.

The general benches 500 kg

The highest rank around was a brigadier general. Recruits had insane stories about him. That he fought in a war. That he has confirmed kills. That he benches 500 kg. Nobody had ever spoken to him. That is exactly why the stories existed.

With the sergeant, the problem is too much information. With the general, it's zero. And people do not leave an empty slot empty. They fill it, and not randomly, because there is exactly one observable data point about the general: how the people you already fear behave around him. To a recruit, a captain is superhuman. Everyone lowers to him, he is visibly excellent at everything, the whole system bends toward him. Then you watch that same captain straighten up and lower himself to the general. You never measure the general directly. You measure him in units of captains. The myth compounds all the way up the chain, which is why the stories are never "he is a competent administrator." They are confirmed kills and a 500 kg bench.

Nobody ever dereferences the general. Everyone just holds a pointer to him and writes whatever they want into that memory.

If this sounds absurd, think about how people talk about their CEO. You have never seen the CEO's actual work. What you have seen is your skip-level getting nervous before presenting to them. Companies don't observe their CEO. They co-author him.

Both ends of the machine

Here is the part I only understood later. While the recruits below me were building the general's myth, I was one floor up, deliberately manufacturing a miniature version of the same distance. Ordering sergeants to hide their hobbies is pedestal construction. I wasn't observing the mechanism. I was operating it.

Distance is just information, and rank is the schema for it. Too much information and authority collapses. Too little and it inflates into legend. The army's entire social design is the management of that curve.

Why I loved it

So, worst year of my life? I loved it, and it's worth being honest about why.

I have a tendency to treat social systems as problems to solve. In normal life that is a tax. You are constantly inferring rules that nobody wrote down and everyone else seems to just know. The army was the one environment where the rules were written down. Address forms, postures, procedures, all documented, all learnable, all executable. I min-maxed it. Correct prefix, correct form, every single time. People hate the army because it is rigid. I loved it because it was legible. A legible system is a playable game.

Which is why I find the modern workplace funny. The flat startup deletes the titles, the prefixes, the corner office, and declares hierarchy solved. But a flat organization is just a duck-typed organization. The distance between you and the CEO still exists. You just can't read it anymore, and you discover the boundaries at runtime.

People say the army is dehumanizing because everything is explicit. I think they have it backwards. Every organization runs this exact machine: the fragile close authority, the mythologized far authority, the careful management of who gets to be seen as human. The army is just the only one honest enough to print it on your collar.