Every founder eventually has the same conversation with themselves: "This place falls apart when I leave." The fix is SOPs. The problem with SOPs is that most attempts to write them collapse under their own ambition — three weeks in, the doc is half-finished, the team has stopped reading it, and the founder quietly gives up.
The 5-day playbook is built around one rule: document only what breaks when you're gone.
Day 1 — The "if I disappeared" inventory
Set a 90-minute timer. Write down every task that, if you vanished for two weeks, would cause one of:
- A customer to notice
- A vendor to chase you
- A team member to be blocked
- A number on a report to be wrong
That's your list. Everything else is noise.
Most founders' lists are 15–25 items. If yours is 60, you're listing tasks you do — not tasks that break without you. Cut it.
Day 2 — Rank by blast radius
For each item on the list, ask: "if this isn't done correctly, how long until someone notices, and how bad is it?"
Three buckets:
- Red — customer-facing or money-moving (invoicing, payroll, customer escalations)
- Yellow — internal coordination (weekly review, hiring pipeline, vendor renewals)
- Green — supporting work (research, internal reports, prep work)
You will write SOPs for Red first, then Yellow. Most Green tasks should be deleted or absorbed, not documented.
Day 3 — Write the Red SOPs (one page each)
The SOP template is one page. Anything longer is unreadable and won't be followed. The format:
- Trigger — what starts this work
- Input — what you need before you start
- Steps — numbered, 5–9 of them
- Output — what "done" looks like
- Edge cases — three known ways this goes wrong
If a Red task can't fit on one page, the task itself is too big. Split it before you document it.
Day 4 — Hand off, don't write more
Pick one person per Red SOP. Hand it to them. Watch them attempt the work with the SOP in front of them. Edit the SOP based on what they had to ask. Repeat once.
This is the day SOP projects usually fail. Founders skip it because it feels slow. Skipping it means you have a document, not a working SOP.
Day 5 — Set the cadence
Three commitments before you stop:
- Quarterly review — the SOP owner re-runs the work against the doc; if reality has drifted, the doc gets updated, not the work
- New-hire test — every SOP must be runnable by someone in their first 30 days
- One-page rule — any SOP that grows past one page gets split, not extended
That's it. You stop on day 5. You don't write the Yellow SOPs yet. You let the Red ones marinate for a month and prove they're actually used.
Why this works
It works because the constraint — Red only, one page, hand off and watch — is the entire point. SOP projects don't fail from lack of effort. They fail from too much ambition spread across documents nobody reads.
Five days. Five to twelve Red SOPs. That's the unsexy answer to "how do I make this run without me?" And it's the answer that actually ships.
Related reading:
- The first 10 SOPs every growing business needs (with examples)
- When you need an operations consultant — and when you're just avoiding a hard conversation
- How to hire a virtual assistant team in 2026: costs, contracts, and the mistakes that sink the rollout
When the writing is the bottleneck, our Business Operations Consulting team runs the 5-day cycle alongside your operator.
