Document Your SME's First 20 Processes (Without Creating a Wiki Nobody Reads)

Every SME has tried to document its processes. Most attempts die in the same way. Someone buys Notion. Three enthusiastic afternoons later there's a "Company Wiki" with a table of contents. Two months later, the wiki is stale. Six months later, nobody remembers the password.

This isn't because documentation is hard. It's because the approach is wrong. Founders try to document an entire company in one push. They write for an imaginary reader ("a new employee") rather than the real one ("Marko, who does invoicing on Fridays"). They choose the wrong tool before they have the habit. They over-format.

Here's the version that works. It's boring, it's unsexy, and it compounds.

The wiki-nobody-reads trap

Three patterns kill most documentation efforts:

1. The "comprehensive" trap — trying to document 100 processes at once. Burns out whoever's doing it; none get finished.
2. The "for a theoretical reader" trap — writing in abstract corporate voice for an imaginary new hire instead of the real person doing the work today.
3. The "tool-first" trap — buying fancy documentation software before the habit of documenting exists. Becomes a different shape of shelfware.

The fix for all three: radically narrow the scope. Twenty processes. One page each. Written for the specific person who owns each one. Stored anywhere (shared folder, Google Docs, Notion — doesn't matter yet).

The four clusters

Every SME's processes fall into one of four buckets. Document five in each.

Revenue cluster (how you make money):

1. Lead qualification
2. Sales handoff (from sales to delivery)
3. Proposal / quote creation
4. Pricing decisions (when non-standard)
5. Customer onboarding

Delivery cluster (how you serve customers):

6. Project kickoff
7. Weekly customer check-in
8. Escalation handling
9. Customer offboarding / renewal
10. Incident response

People cluster (how you run the team):

11. Hiring (from requisition to offer)
12. First 30 days of a new employee
13. Weekly one-on-one
14. Performance review
15. Termination

Finance cluster (how the money moves):

16. Monthly financial close
17. Invoice approval
18. Expense reimbursement
19. Supplier payment
20. Budget / forecast cycle

This is the boring list. It's also the list that, if done, covers ~85% of what an SME actually does operationally. The flashy strategic stuff can wait.

The one-page template

Every process document is the same five sections. No more.

1. Trigger — what starts this process? (a signed contract, a date, a threshold crossed, a request)
2. Steps — numbered list, each step naming the person or role who does it
3. Output — what's the deliverable, and who gets it?
4. Failure modes — the two or three things that typically go wrong, and what to do when they do
5. Owner and review date — who maintains this document, and when will they next revise it?

That's it. No flowcharts unless they genuinely help. No screenshots unless the tool isn't obvious. No "purpose" or "scope" sections — the trigger is the scope.

Most process docs bloat because people treat them as compliance artefacts (things to satisfy an auditor) rather than operational artefacts (things a human uses to do the work). Compliance documents describe the process; operational documents enable the process. Target the second.

Who writes them

The person who currently does the work writes the first draft. Not the founder. Not a consultant. Not an intern.

This is the part that feels backwards. The person doing the invoicing isn't a writer, doesn't want to write, and thinks their process is "obvious". But they're the only one who actually knows how it works. Anyone else writing it will produce fiction.

The founder's job is to make it safe and fast for them to write:

• One page, not ten
• 30 minutes during work hours, not on top of their job
• Template is filled in, not blank
• First draft is good enough; we'll iterate

A senior operator then reviews each draft with three questions:

1. If this person went on holiday, could someone use this to do the process?
2. Are the failure modes honest? (Most first drafts skip the real failures.)
3. What's missing that only shows up under stress?

The cadence that works

• Five processes per quarter. Not five per week. The habit is more important than the pace.
• One person owns each document and has it in their calendar to review every six months.
• Weekly leadership meeting includes "process changes" as a standing item — 5 minutes max, but it keeps the documents alive.

By the end of year one, you have 20 one-page documents. By month 18 they're being read and revised. By month 24, you have a library that newly-joined people read on day one.

What tool to use

The right answer for the first 20 processes is whatever your team already uses. Google Docs. Notion. A shared SharePoint folder. The tool matters much less than the habit.

Upgrade tools only when you hit real friction — usually around 40+ documents, when search becomes a problem. At that point, Notion or a dedicated wiki (Guru, Slab, Tettra) are fine. Don't buy an enterprise SOP management platform. That's over-engineered for an SME and always will be.

What to do next

1. This week: pick five processes from cluster 1 or cluster 2 (whichever is more painful right now). Write the names on a whiteboard. Assign owners.
2. Next two weeks: each owner spends 30 minutes drafting. Use the template above.
3. Week 4: senior operator reviews the five drafts. Revises with the three questions.
4. Month 2: start cluster 2. Then 3. Then 4.

By end of year one, 20 documents. By end of year two, a living system.

If you want help structuring the rollout, Business Build is the part of BusinessPulse OS that installs this kind of operational structure without the usual SME consulting overhead.

Frequently asked questions