Where to Start: How to Pick the First Process to Document in Your Business

The Decision That Stalls Everyone

You’ve already recognized the problem. Maybe you’ve hit the classic breaking points that signal your business needs written processes — the same mistakes repeating, key staff becoming irreplaceable, onboarding that takes forever — and you’ve decided to do something about it.

Then comes the question that stops most owners cold: Where do I even start?

If you’re running a 10- to 50-person business, you probably have 30 to 80 processes that could be documented. Some are critical and messy. Some are trivial and already consistent. Most fall somewhere in between. Trying to document everything at once produces nothing finished. Picking randomly produces something finished that doesn’t matter.

What you need is a simple way to rank your candidates and pick one with confidence.

Why Your First Process Choice Matters More Than You Think

The first SOP you finish sets the tone for everything that follows. If it’s too simple — documenting how to restock the supply closet — you’ll get it done but nobody will care, and the effort won’t justify the time. If it’s too complex — documenting your custom quoting workflow that involves three software platforms and three people — you’ll bog down, the draft will sit unfinished, and the whole initiative stalls.

The right first process is one where:

1. The documentation effort is bounded (you can finish a solid draft in a few hours)
2. The payoff is immediately visible to your team
3. You’re fixing something that actually causes pain right now

(Applying StoryBrand: the goal isn’t to produce documentation — it’s to remove a source of friction that’s hurting your business and your people.)

The Four-Factor Scoring Method

Score each candidate process on four dimensions, 1–5 per dimension (5 = highest). Add the scores. The highest total is your starting point.

Factor 1: Frequency (1–5)

How often does this process run?

• 1 — Once a year or less (annual review, year-end close)
• 2 — Monthly
• 3 — Weekly
• 4 — Multiple times a week
• 5 — Daily or multiple times per day

Why it matters: A high-frequency process that’s slightly wrong creates compounding damage. A low-frequency process that’s slightly wrong creates one problem, once. Document high-frequency processes first — the return on time invested is much higher.

Factor 2: Variability (1–5)

Do different people do this process differently, or does the same person do it differently each time?

• 1 — Everyone follows the same sequence, consistently
• 2 — Minor variations; results are mostly the same
• 3 — Noticeable variation; you can tell who did it
• 4 — Significant variation; outcomes differ meaningfully
• 5 — Every rep does it their own way; results are all over the place

Why it matters: High variability is where quality problems live. If everyone’s doing it the same way already, documentation is useful but not urgent. If you can tell who handled a case by how it looks, documentation is overdue.

Factor 3: Consequence (1–5)

What breaks if this process is done wrong?

• 1 — Minor inconvenience; easy to catch and fix
• 2 — Customer friction or internal rework; recoverable
• 3 — Revenue impact, compliance exposure, or a frustrated customer who might not come back
• 4 — Significant financial or legal risk
• 5 — Regulatory violation, patient/client safety issue, or direct business liability

Why it matters: High-consequence processes are where errors are most expensive. You don’t need to document everything to protect yourself — you need to document the things where getting it wrong costs real money or trust.

Factor 4: Trainability Gap (1–5)

How much pain does this process cause during onboarding or when someone is out sick?

• 1 — Any new hire can figure it out in 20 minutes
• 2 — Takes a day of shadowing; manageable
• 3 — Takes a week to learn; you lose productivity every time someone new starts
• 4 — Only one or two people really know how to do it; everyone else gets it wrong without supervision
• 5 — It lives entirely in one person’s head; if they leave, you have a real problem

Why it matters: This dimension captures how fragile your operation is. A process that only one person can do correctly is a single point of failure — and single points of failure in small businesses tend to become crises.

A Worked Example: 12-Person Dental Practice

Let’s put this to work. Meet a dental practice manager — 12 staff, two dentists, running a busy general practice. She knows documentation is long overdue. She pulls together eight candidate processes and scores them.

Process	Frequency	Variability	Consequence	Trainability Gap	Total
Insurance verification	5	5	4	5	19
Patient check-in	5	3	3	3	14
End-of-day close	5	4	3	3	15
New patient intake call	4	4	3	4	15
OSHA sterilization log	3	2	5	2	12
Treatment plan presentation	3	4	3	3	13
Appointment recall process	3	4	3	4	14
Supply ordering	2	2	2	2	8

Insurance verification wins at 19 — and it’s not close.

Here’s why those scores make sense:

• Frequency (5): Insurance is verified for almost every patient, every day. At 30–40 appointments per day, this process runs constantly.
• Variability (5): Every front desk staff member has developed their own habits — who they call, what they verify, what they skip. Results vary widely, and the dentists rarely see it happening.
• Consequence (4): When insurance verification is wrong or skipped, the practice eats the claim. A single missed verification on a complex procedure can mean $800–$2,000 written off. Do that five times and you’ve lost a month’s supply budget.
• Trainability gap (5): The person who does this best has 12 years of experience and has never written down how. When she was out for two weeks last year, the billing headaches lasted three months.

The practice manager doesn’t need to think hard about this. Insurance verification is the answer. She documents that one first, gets it done, and then returns to the matrix.

What didn’t make the cut: Supply ordering scored 8. It’s low frequency, low variability, low consequence — someone would have to be actively trying to break it. That gets documented eventually. Not today.

Common Mistakes When Picking the First Process

Defaulting to whatever’s top of mind. The most recent fire is rarely the most important process to document. A crisis is recent; it’s not necessarily chronic. Score dispassionately.

Picking based on what’s easiest to write. Simple processes are satisfying to document but create little organizational value. The matrix deliberately weights difficulty by consequence.

Picking a process the owner doesn’t understand well. If you’re going to write the first SOP yourself, pick a process you can actually describe. You’ll extract the expert’s knowledge in the next step — but for your very first document, choose something where at least one person (including you) can walk you through it start to finish.

Trying to document a meta-process. “How we onboard employees” is not one process — it’s ten. If your top-scoring candidate is itself a cluster of processes, break it down and score the components separately.

What “Good Enough to Start” Looks Like

Your first process doesn’t need to be perfect. It needs to be:

• Written down in sequence. Someone who has never done this should be able to follow it and produce an acceptable result.
• Reviewed by one person who does the work. They catch the three things you missed.
• Accessible. Not in a shared drive folder nobody knows about.

That’s it. Version 1 is not the final version. It’s the version that replaces tribal knowledge with something repeatable.

If you’re using What’s the Process For, the format does the heavy lifting — you write the steps, attach the notes and links, and the structure is already there. But even a Google Doc that lives somewhere everyone can find it is infinitely better than nothing.

Score Your Processes Now, Before You Move On

The scoring matrix works best as a team exercise. Pull your five or six most likely candidates. Give each person on your leadership team five minutes to score independently, then average the results. Disagreements on scores are useful — they surface assumptions (“I thought this was low variability” / “Really? We do it four different ways”).

You don’t need to score 30 processes. Score six to eight strong candidates and pick the highest. The rest will still be there next month.

Once you’ve picked your process, the work shifts from choosing to capturing. The biggest challenge at that stage is that the people who actually do the work best have never been asked to explain it — and most of what they know, they don’t realize they know. That’s where the next step in this series comes in: how to extract tribal knowledge from your team.

---

This is post 2 in a 10-part series on building a fully documented business — from recognizing you need SOPs to maintaining them. If you’re at the beginning of this journey, start with the signs your business needs documented processes.