The operations manual nobody ever writes. And which costs a fortune not to have.

Every functioning digital team has a secret that almost nobody names explicitly: somewhere — in the leader's head, in scattered messages, in unnamed files on Google Drive — there exists a body of operational knowledge that keeps everything running. The question is not whether that knowledge exists. It is whether it exists only in your head or outside of you, where anyone can access it.

I built my first team operations system not because I was far-sighted. I built it because I got ill for a week and discovered, on my return, that at least five important things had not been done — not from negligence, but because nobody knew how to do them without me. That week cost me far more than a few lost work days. It showed me exactly how much of my system existed only in my head — and how fragile, as a result, everything I had built was.

What an operations manual is — and what it is not

An operations manual for a digital team is not a formal corporate document full of bureaucratic procedures nobody reads. It is something much simpler and more useful: the written, organised answer to the question "how do we do this?". Not how it should be done in theory — how it is actually done, with the concrete steps, specific tools, decisions to make, mistakes to avoid.

It does not need to be perfect. It does not need to be complete from day one. It needs to exist — and be updated every time the method evolves.

The difference between a team with a manual and one without is not visible in day-to-day operations. It becomes devastating at critical moments: when someone new joins, when the leader is absent, when something goes wrong and needs resolving quickly, when the team must scale faster than expected.

What goes in the manual — in the right order

First section: onboarding. The first seven days of every new member. What to know, what to do, what to avoid. The order in which to receive information. The questions they will certainly ask and the answers already prepared. This is the document with the highest return on investment in the entire manual — because it is used every time someone new joins.

Second section: recurring processes. The things the team does regularly. How to manage a lead from first contact to onboarding. How to run a team call. How to handle a collaborator who is slowing down. Every recurring process has an optimal variant — writing it down is how you replicate it.

Third section: decisions already made. Every team faces the same situations multiple times. Decisions made once with calm are worth far more than starting from zero each time under pressure.

Fourth section: tools and how they are used. Which tools the team uses, why, how to access them, who manages what. Not a complete tutorial — just enough to allow someone to step in without discovering everything from scratch.

The format that actually works

The most useful operations manual combines short videos (3-7 minutes) for processes with nuances difficult to describe in words, checklists for sequential processes so nothing gets skipped under pressure, and written documents for decisions and policies that require understanding the reasoning, not just executing the steps.

The manual as a living tool

Every time you answer a question not in the manual, add the answer. Every time you find a better way of doing something, update the process. Every time you onboard someone new and notice something is missing, write it before moving on.

It is not a project to complete. It is a practice to maintain. And that practice — the constant care of the team's operational knowledge — is one of the things that distinguishes teams that scale from those that remain permanently dependent on their leader's physical and cognitive presence.

With Squad.Win, this operational knowledge finally has a place to live — not dispersed across messages, folders and individual memories, but centralised, accessible, updatable. Not as a dead archive, but as a living system that accompanies every new member from day one.