From chaos to SOPs: systemising a 10-person team

Ten people is the size where informality stops working.

At three, everyone hears everything. At ten, information travels through relationships, quality depends on who happened to do the work, and the founder becomes the integration layer between functions that no longer talk. Nothing dramatic breaks. Things just take longer, cost more, and vary more than they should.

The fix isn't more management. It's converting knowledge that lives in people into systems that live in the business.

The symptoms worth taking seriously

• The same question is answered repeatedly, differently each time
• Quality depends on who did it
• One person going on leave slows a whole function
• New hires take months to become useful
• The founder is consulted on decisions that shouldn't reach them
• Mistakes recur, get discussed, and recur again

If three or more are true, the problem is systems, not effort.

Step 1: Map before you document

Spend a week observing rather than writing.

List every recurring process in the business. Don't describe them yet — just name them. Most ten-person companies land on 30–50 processes, and they cluster: winning work, delivering work, getting paid, supporting customers, hiring and onboarding, internal admin.

Then score each on three questions:

1. 1How often does it happen?
2. 2What does it cost when it goes wrong?
3. 3How many different people perform it?

High on all three means document first. This scoring is what separates a systemisation effort that changes the business from one that produces a folder nobody opens.

Step 2: Document the top ten only

Ten processes. Resist the urge to be comprehensive — comprehensive projects stall around week three and are abandoned.

A workable SOP format:

• Purpose: one sentence on what this achieves and why it matters
• Trigger: what starts it
• Owner: the role accountable for the outcome
• Steps: numbered, in order, each starting with a verb
• Decision rules: what to do when the common exceptions occur
• Definition of done: how you know it's finished and correct
• Last reviewed: a date

Write for competence, not ignorance. "Send the onboarding pack" is fine for a trained person; "Click the blue button" is condescending and ages badly.

The fastest way to produce these is to have the person who does the work best record themselves doing it while talking through decisions. Transcribe, edit into steps, then have a different person follow it and mark every point of confusion. That second pass is where the real SOP is written.

Step 3: Assign ownership properly

Every process gets one owner. Not a team — a person, by role.

Ownership means three things: the outcome is theirs, they decide how the process works, and they're responsible for updating it when reality changes. Shared ownership is unowned.

Separate this from execution. Several people may run a process; one person owns whether it works. And be explicit about decision rights — what the owner decides alone, what needs a second opinion, what genuinely needs the founder. Most escalation happens because nobody wrote this down, not because the decision was hard.

Step 4: Train against the document

Systems fail at the handover, not the writing.

Use a simple progression: the owner demonstrates once, the learner does it with the SOP open and the owner watching, the learner does it alone and their output is reviewed, then they're signed off. Four repetitions and one document beats a two-hour induction session.

Onboarding should be a sequence of SOPs plus a checklist, not a tour. It turns the first two weeks from ambient absorption into structured capability.

Step 5: Quality control that isn't surveillance

Define what "good" looks like for each critical output — a checklist, an example, or a small number of standards. Then check samples, not everything.

Review the first three outputs of anyone new to a process, then move to spot checks. When something is wrong, ask whether the SOP was unclear, unfollowed, or wrong. Most defects trace back to the first or third, which means the fix is a document change rather than a conversation about performance.

Hold one short weekly operations review: what broke, what's recurring, what one process gets improved this week. Fifteen minutes, standing agenda.

Step 6: Automate only what's already stable

Never automate a process you haven't documented and run cleanly for a month. Automating a messy process just makes it fail faster and more expensively.

Once stable, the best automation candidates are handoffs, reminders, status updates and record creation — the connective tissue between human steps. Keep judgment, exceptions and relationships manual.

Step 7: Keep the system alive

Documentation dies quietly. Three habits prevent it:

1. 1Change the SOP in the same week the process changes, by whoever changed it.
2. 2Quarterly review — each owner re-reads their processes and updates the date. Anything untouched for six months is treated as suspect.
3. 3Answer with links. When someone asks how something works, send the SOP. Missing? Write it, then send it. This is how a document set becomes a habit.

How to avoid bureaucracy

The fear is legitimate. Bureaucracy is what happens when process outgrows purpose. Four rules keep it in check:

• Document to remove decisions, not to add them. If an SOP creates a new approval step, justify it or drop it.
• Shorter is better. One page beats five. Nobody reads five.
• Standardise outcomes, not personalities. Define what "done" looks like; let people reach it their own way where it doesn't matter.
• Delete aggressively. Retire any process that exists only because it always has.

A good system reduces the number of things people have to think about. If yours increases that number, it's not a system — it's overhead.

A realistic timeline

• Weeks 1–2: map and score processes; pick the top ten
• Weeks 3–6: document two or three per week, tested by a second person
• Weeks 7–8: assign owners, define decision rights, train
• Week 9 onward: weekly review, quarterly refresh, automate what's stable

Two months of deliberate work, mostly done by the people already doing the jobs.

What changes

The founder stops being the routing layer. New hires become productive in weeks rather than months. Quality stops depending on who picked up the task. And the business becomes something that can be handed over, scaled, or stepped back from — which is the difference between owning a company and owning a job.