← Back to writing

Team Ideology: Why Write Down What "Everyone Already Knows"

A playbook turns N private interpretations into one shared contract

“What happens if I go to my manager and say I’m just tired?”

People ask themselves that question silently. They assemble the answer out of past experience, rumours, and whatever they saw happen yesterday when someone else made a mistake. On my teams, the answer is written down. Literally: there is a chapter in the playbook that says — if you are tired, say so; details are optional, "I need a couple of days" is enough. Staying silent is the one thing that is not an option, because managers cannot read minds.

I deliberately call it ideology, not "team values". Values are a poster on the wall. Ideology is the set of shared interpretations a team actually lives by and cites in arguments.

The problem of N interpretations

What my teams put in their ideology is nothing exotic: autonomy, ownership, trust, mistakes, initiative. Everyone deals with these. The difference is that in most places they form spontaneously and get passed on by word of mouth, like a family saying handed down through generations — losing meaning at every step.

Over a career, every engineer builds a private interpretation of "how the world works". What happens when you break something. When you can take initiative and when it is safer to keep your head down. Whether you can admit you are behind schedule. Until this is written down, a manager is not working with a team — they are working with N different interpretations and reactions, where N is the number of people reporting to them.

I sat down to write the playbook for a mundane reason: people kept coming to me with questions that were, underneath, the same question in different wording. Why spend an hour explaining it every time, when you can describe it once and let the developers send each other the link?

But it turned out the win was not only time. People calm down once they know there will be no mood swings from management, no punishing the innocent and no rewarding the uninvolved. Ideology is not a mood; it has no "one thing today, another tomorrow".

What it looks like in practice

My teams' playbook has ten chapters: a developer's purpose, autonomy, trust credit, the marathon, initiative instead of heroics, mistakes, ownership, teamwork, legacy and tech debt, wellbeing. Here are three mechanics, so it is clear these are not declarations.

Trust credit. Every engineer starts with maximum credit: take tasks in any order, no lead breathing down your neck, the decisions inside a task are yours. Credit drops for specific things: missing a deadline without warning, asking what the documentation already answers, repeating the same mistakes. Credit down means tighter control and simpler tasks. And crucially: a drop is not a verdict — the way back is spelled out just as explicitly as the way down.

Ownership. The passive voice is banned. Not "the task did not get done", "time ran out", "nobody told me", but "I got the estimate wrong", "I did not check the artifacts before starting". We all make mistakes, and admitting it is maturity, not weakness: we optimise for the fix, not for the punishment. Having the wording fixed in writing means that in an incident review I cite a chapter, not my own irritation.

Wellbeing. The chapter about being tired. Exhaustion, anxiety, trouble in your life — all normal; staying silent until you break is not. A few days of recovery is cheaper than losing a person for good.

A case: the person who stayed silent

I once had a developer who — presumably from past experience — could not deliver bad news. Problems, "I am stuck", "I will not make it" — all of it piled up in silence. He would show up once the deadline had already passed and he had burned himself down to near-zero output.

Instead of a post-mortem, I explained a simple thing: my job in front of my own management is to deliver value on time. When the mechanism breaks, we do not shout at the mechanism — we repair it. We agreed on this: temporarily, a regular status ping — on important features up to twice a day, at the start and at the end. And we spelled out the exit condition: once he understood that making mistakes is not the scary part, staying silent is, and once I saw the rules had landed, we would go back to standard reporting.

That is trust credit in action: not humiliating surveillance, but a clear mechanic with an explicit way back. He knew why the control tightened and what it would take to loosen it.

What changed once it was written down

Before the playbook, situations like that took weeks to resolve — explaining, spelling it out step by step, and then starting over a month later with a different person. After: send the link, they read it, they ask questions, I say the substance out loud once and mean it. As a rule, the problem did not come back. Some people looked for the catch at first: "why is this so simple?" Because once you have tested it yourself, you see that what is written matches what happens.

Same story with the wellbeing chapter: people came in with "my life is on fire" — and no catastrophe followed. Processes did not stall without them, the person calmly dealt with their personal problem, and afterwards their loyalty grew. Not because they were "given an exception", but because the system worked exactly as written.

"If everyone thinks the same way, there is no creativity"

A common objection. In practice it works the other way round. Ideology does not standardise thinking — it standardises interpretations of fairness and the predictability of the system's reactions. People keep arguing about architecture, patterns and priorities — but nobody burns energy figuring out "what will this cost me".

That is exactly what a creative person needs. Initiative requires safety: until someone knows how "I found a problem in someone else's code" ends, they will not find it. We have a separate chapter for this — initiative instead of heroics: find it, assess the impact, align, fix it. Creativity does not live where there are no rules; it lives where the rules are known and stable.

Nature abhors a vacuum

If a manager does not shape an explicit culture, the culture will form anyway — spontaneously, and without them. It gets written by the toxic old-timer, by smoking-room rumours, and by somebody's past traumatic experience ("at a normal company you get fired for that"). The question is not whether the team will have an ideology. The question is whether you write it openly or it assembles itself out of random debris.

And "you write it" does not mean "handed down from above". My playbook was filtered through the teams end to end: people read it, argued, edited the wording. They are the ones who have to live by these rules, so they get to edit them. The document is alive: processes change, and it changes with them.

The full playbook — ten chapters — is open: kozhanov.space/playbook. And for how this ideology meets a new person on day one, see the article on onboarding.

EK
Egor Kozhanov· Head of Videoconferencing Solutions Development Group, Moscow

Head of Videoconferencing Solutions Development Group at IVA Technologies — ~40 people across the cycle, 12 frontend direct. I codified how we work in a ten-chapter team playbook.

Let's talk.

For roles, advice, or the occasional essay digest.