What Processes Should You Document First? A Prioritization Framework

Key Takeaway

Document the simplest revenue-generating process that takes too much of your time and is eligible to be delegated quickly. Score every candidate against three questions: Does it produce revenue? How complex is it? How much time does it consume? The processes that score "yes / simple / time-heavy" go first. Everything else lines up behind them.

In This Article

1. Where to Start When Everything Feels Important
2. A Simple Three-Question Scoring System for Documentation Priority
3. Most Complex or Most Frequent: Which Wins?
4. Client-Facing vs. Internal: Which Comes First?
5. The Risk Lens: Which Undocumented Processes Are Most Dangerous?
6. How to Handle "We've Always Just Known How to Do It" Processes
7. What a Realistic 90-Day Documentation Plan Looks Like
8. The Order, in One Sentence

Where to Start When Everything Feels Important

When every process in your business feels equally critical, the right place to start is the process that hits all four of these:

• It generates revenue.
• It's relatively simple.
• It takes up too much of your time.
• It's eligible to be delegated quickly.

Find one process that meets all four. That's where you start. You can afford to delegate that work much sooner than almost anything else in the business, and the cost of bringing in help is easy to justify because the process directly produces revenue. If you want a ready-made shortlist of candidates, our guide to the first 5 SOPs every small business should write covers the usual suspects.

Either way, you absolutely need to start with the processes that bring in the money. It doesn't matter how good your payroll process is if there's no revenue to fund payroll. Once you have picked the first process, our guide to how to document business processes covers the actual capture, step by step.

There is real urgency to picking right. Most owners assume their business is mostly documented and that only a few edges are missing. The data says the opposite. Across 16 small businesses we gap-analyzed in depth, the average process area came back only 27 percent documented, and half of all role areas had zero documentation at all. For most businesses the question is not whether you have gaps. It is which gap to close first.

A Simple Three-Question Scoring System for Documentation Priority

You don't need a 30-row spreadsheet to rank your workflows. Three questions handle it.

How to Read the Score

Anything that scores yes / 1 / 3 (generates revenue, is simple, and consumes a lot of weekly time) moves to the top. That's your first process to document.

Everything else falls into different shades after that. The worst-case combination, and the last thing you should ever document, is no / 3 / 1: doesn't generate revenue, is very complicated, and barely takes any time. That's a process you may not even need to do at all. Definitely don't document it any time soon.

Two Quick Sample Scores

"New customer onboarding kickoff call" → Yes / 1 / 3 (revenue, simple, time-heavy). Document this first.

"Annual office supplier renegotiation" → No / 3 / 1 (no revenue, complex, almost no time). Park indefinitely.

Most Complex or Most Frequent: Which Wins?

If you're choosing between two processes that score similarly, go with the most frequent one, not the most complex.

This is the Pareto principle in action. A process you run daily that you make 10% better produces more total value than a complex process you run twice a year that you make 20% better. The math isn't even close. We go deeper on this in the 80/20 of process documentation, where a small slice of your processes carries most of the operational load.

Frequency creates leverage. The processes you do most often are the ones with the highest ROI on improvement. Start with those, hand them off to someone else, and then turn your attention to the more complex but less frequent work, now that you have time back to think about it properly.

Client-Facing vs. Internal: Which Comes First?

As a general rule, client-facing processes produce revenue. Internal processes don't.

Start with the client-facing work to make sure money keeps coming in the door. Then, and only then, turn to the internal processes like hiring, onboarding, payroll, and promotions.

This is the offense-before-defense rule. You need to make sure your offense can score before you worry about how good your defense looks. A business with beautifully documented internal HR but a broken sales process doesn't survive long.

The Risk Lens: Which Undocumented Processes Are Most Dangerous?

The most dangerous undocumented process is the one only one person knows. It's a single point of failure for the business.

If that person leaves the company, takes a long vacation, gets sick, or just has a bad week, the process is gone. Or worse, it survives but in a degraded form, with someone else trying to reverse-engineer it under deadline pressure. This is the exact trap we break down in the one-person problem, where a single key employee quietly becomes a liability the business cannot afford to lose.

Especially dangerous: a revenue-generating process that only one person knows. That combination, high importance plus single owner, is the riskiest spot in any business. If you have one of those, it should jump the queue regardless of how it scores on the time and complexity grid.

The Single-Owner Risk Test

Walk through your business and ask: "If [one person] disappeared tomorrow, what would actually break?" Anything on that list is a risk. Anything on that list that also generates revenue is a five-alarm fire. Document those processes first, even if they don't score highest on the framework above.

How to Handle "We've Always Just Known How to Do It" Processes

Processes that everyone "just knows" how to do are actually some of the easiest to document. In most cases, easier than anything else.

Here's why: if everyone already knows how to do it, the as-is version is right there in their heads. Documenting the current state is mostly a matter of writing it down. That's the easy part.

The valuable part comes after. Once the process is laid out visually, usually in a process map, you can evaluate it honestly: have we always done it this way because it works really well, or is there room for improvement? Most "we've always done it this way" processes have at least one place where they could be sharpened.

These are great workflows to start with because they build momentum. Everyone agrees on what's happening, the documentation goes fast, and the team gets a quick win to point at before you tackle the more complex work.

What a Realistic 90-Day Documentation Plan Looks Like

If You're Doing It Yourself

In 90 days, working on this consistently in addition to your normal job, here's what a focused in-house process mapping effort can achieve:

1. All your core (revenue-generating) processes documented in high-level process maps.
2. KPIs identified and implemented from each of those process maps. You should be able to tell, in real time, whether each process is performing.
3. At least one full SOP built for the single most important process in the business, one your team could actually use to do the work.

That's a real outcome from 90 days of focused, sustained effort. Not glamorous, but solid foundation work.

If You Want to Move Faster

Two ways to expedite the timeline:

• Dedicate someone to documentation full-time. Pull a person off other work and make process documentation their job for the quarter. Progress accelerates dramatically.
• Bring in outside help. A team that does this work all day, every day can move through your business much faster, handling the tedious back-end work, interviewing each team member, and producing maps and SOPs at a pace your internal team typically can't match.

Either path gets you further than 90 days of solo effort. But even if you only do it yourself, even if you only do it in your spare hours, you can still come out the other end of three months with documented core processes, working KPIs, and one functional SOP. That's enough to start delegating, start measuring, and start getting your time back. For the full multi-quarter sequence beyond the first 90 days, see our systemization roadmap.

The Order, in One Sentence

Document the simplest revenue-generating process you spend too much time on, then the processes only one person knows, then the rest of your client-facing work, then your internal operations, always favoring frequency over complexity when in doubt.

Frequently Asked Questions

What process should I document first?

Document the simplest revenue-generating process that takes too much of your time and is eligible to be delegated quickly. Revenue-first matters because the strongest payroll process in the world doesn't help if there's no money coming in to fund it.

Should I start with the most complex or most frequent processes?

Start with the most frequent. The Pareto principle wins here: a 10% improvement to a process you run daily is worth more than a 20% improvement to one you run twice a year. Frequency creates leverage, because every gain compounds across every repetition.

Are client-facing processes higher priority than internal ones?

Yes. Client-facing processes are usually the ones generating revenue. Document those first to keep money flowing in the door before you turn to internal processes like hiring, payroll, or onboarding. Offense before defense.

What undocumented process is the most dangerous?

The process only one person knows. It becomes a single point of failure. If that person leaves, gets sick, or goes on vacation, the work stops. A revenue-generating process that lives in only one person's head is the riskiest of all, and it should jump the queue regardless of how it scores on time or complexity.

What does a realistic 90-day documentation plan look like?

Doing it yourself in 90 days, you can document all core revenue-generating processes in process maps, identify and implement KPIs from each map, and build at least one functional SOP for your most important process. With a dedicated person or an outside partner, you can move significantly faster across the rest of the business.

How many processes does a small business actually need to document?

Far fewer than most owners fear. You do not need to document every task in the business. Start with the handful of core processes that produce revenue and consume your time, usually somewhere between five and ten. In our research across 16 gap-analyzed small businesses, the average process area was only 27% documented and half of all role areas had zero documentation, so getting your top ten written down already puts you ahead of most companies your size.

Should I document a process before or after I improve it?

Document it first, then improve it. You cannot improve a process you cannot see. Capturing the current state in a process map exposes the redundant steps, the handoffs that stall, and the bottlenecks that all run through you. Improvement is the second pass, and it is much easier once the as-is version is on paper in front of the whole team.

What is the biggest mistake owners make when deciding what to document first?

They start with the most complex or most painful process instead of the highest-leverage one. Complex processes feel urgent, but they are slow to document and hard to delegate, so the project stalls before it produces a win. Start with a simple, frequent, revenue-generating process you can hand off quickly. The early win builds momentum that carries the harder work.