SOPs your team will actually open

The two versions of this problem

Version one: nothing is written. Everything lives in a few people's heads. New hires ask the same questions every week. When a key person is out, work stops or gets done differently.

Version two: SOPs exist and nobody uses them. Someone wrote 40 pages in a burst of energy two years ago. The documents sit in a shared drive. They are long, out of date and written by someone who does not do the job.

• The same task is done three different ways depending on who does it.
• New hires cannot find a procedure in under a minute.
• No SOP has a named owner or a last reviewed date.
• Your SOPs are longer than two pages.
• Training does not use the SOPs at all.

Why SOPs fail

SOPs fail for predictable reasons. They are written from memory instead of from watching the work. They try to cover every edge case and become too long to use. They live in a folder nobody opens. And they have no owner, so the first process change makes them wrong and nobody trusts them again.

The cost of "just ask someone" adds up. Atlassian research (State of Teams 2025) found teams spend about a quarter of the workweek searching for information. And Panopto (2018) found 42% of institutional knowledge is unique to one person. Without SOPs, that knowledge leaves when they do.

What it costs

No SOPs means rework, longer onboarding, uneven customer experience and a business that depends on specific people. It also caps what you can delegate. You cannot hand off a task you cannot describe. When it is time to sell, buyers look for documented processes because they show the business can run without the founder.

How to start without stalling

1. Pick the list. Choose the tasks that cause the most errors, the most questions or the most customer complaints. That is your first 15 to 25.
2. Watch, then write. Record or shadow the best person doing the task. Write the steps in their words.
3. Keep it short. One task per SOP, numbered steps, a photo or screenshot where it helps, under two pages.
4. Test it. Have someone who has never done the task follow the SOP. Fix wherever they get stuck.
5. Own it. Name an owner and set a review date for every SOP.

Score what you have with the free SOP Readiness Score, or grade one document with the SOP Audit Checklist.

What good looks like

In a company with working SOPs, a new hire can find how to do a task in under a minute, on their phone, in the place they already look. Each SOP is short, has a photo or screenshot where it helps, shows who owns it and when it was last checked. When the process changes, the owner updates the SOP that week. Training uses the same documents, so what people learn is what the SOP says.

How we fix it

Core SOP drafting is Month 2 of The Prelude. We shadow the roles, write modular SOPs, build a simple documentation architecture (where things live, how they are named, who owns them) and place the SOPs inside the tools your team already uses. Your successor is trained as the SOP owner so the documents stay current after the engagement ends.

The SOPs then become the backbone of onboarding and training, so the way people are taught matches the way the work is done.

Questions owners ask