Most firm owners know they should have documented processes. Fewer have any. And the gap between knowing and doing comes down to one thing: they are not sure where to start.
This post is the practical answer to that question. By the end of it, you will have a clear method for mapping any process in your business, with no special software and no consultant required. Just a clear head, a document open on your screen, and an hour you have set aside to do it.
Before you start: pick the process
Not all processes are equal candidates for your first map. Picking the wrong one, something too complex, too much of an edge case, or too low-impact, makes the exercise harder than it needs to be and less likely to give you a result you can use.
A strong first process to document has most of these qualities:
It happens regularly, at least weekly or with each new client.
It currently depends on you, or on one specific team member, to run correctly.
When it goes wrong, the impact is noticeable: a client experience suffers, time is lost, or something falls through the cracks.
You could imagine handing it to someone else if they just knew the steps.
Common starting points for service businesses include client onboarding, new enquiry handling, invoice and payment follow-up, weekly reporting, or the process for delivering a core service. Any of these will give you a solid first map with immediate, practical value.
Step 1: Do a brain dump, and don't edit yet
Open a blank document. Set a timer for fifteen minutes. Write down everything that happens in this process, in whatever order it comes to you.
Do not worry about sequence yet. Do not worry about whether it is correct or complete. Just get it out of your head and onto the page.
Write it in plain language, as if you were explaining it to someone capable but new. "Client sends enquiry via website form. I get an email notification. I check the enquiry within 24 hours. I look at their website if they have one before responding..."
The goal here is to externalise it. The process lives in your head as a set of habits and instincts, not a neat sequence. This step makes it visible before you organise it.
Step 2: Sequence it
Once you have the brain dump, read back through it and number the steps in order. You will find things that are out of sequence, steps you forgot to include, and moments where a decision affects what comes next.
Add those in. Do not delete anything yet. Even if a step seems obvious or redundant, leave it in for now.
At this point you are looking for three types of content:
Actions: something that gets done. "Send the welcome email." "Create the client folder." "Book the kickoff call."
Decisions: a point where the path could go one of two ways. "If the client has confirmed payment, proceed to onboarding. If not, follow up."
Waiting points: moments where the process pauses while something external happens. "Wait for the signed agreement to be returned."
Telling these three apart matters later. For now, just flag them as you sequence.
Step 3: Add the detail that lives in your head
This is the step most people skip, and it is the most important one.
Go back through your sequenced list and, for each step, ask yourself:
What information do I need to complete this step, and where does it come from?
Is there a template, a tool or a system involved? Which one?
What does "done correctly" look like for this step?
What goes wrong here most often, and what do I do when it does?
The answers are the institutional knowledge that makes this process work: the things experienced team members carry in their heads and new people can never quite work out on their own.
Write it down next to each step. Even rough notes are valuable. "Client sometimes sends the brief in a Google Doc instead of using the form. If so, copy the key information into the standard template before proceeding" is exactly the kind of detail that prevents mistakes and saves time in a handover.
Step 4: Test it against reality
Read the map back as if you have never done this before. Follow each step literally. Ask yourself:
Would I know what to do at each stage with only this document in front of me?
Are there any steps that assume knowledge I haven't written down?
Are there any gaps, moments where the document goes silent and I'd have to guess?
If you can, walk a team member through it and watch where they hesitate or ask questions. Those hesitations are the gaps in your documentation. Fill them.
The aim of the first pass is a useful document: something another capable person could follow without needing you in the room. Perfect can wait.
Step 5: Give it a home
A process map that lives on someone's desktop or in an email thread will be ignored and forgotten.
Put it somewhere your team can find it. A shared Drive folder, a Notion workspace, a simple intranet: the tool matters less than the team knowing where to look and the document being easy to update.
Name it clearly. "Client onboarding process, as of November 2026" beats "onboarding v3 FINAL". Include a date so everyone knows whether they are looking at the current version.
Then communicate clearly that it exists. The best process document in the world is worthless if nobody knows about it.
What to do next
Once you have one process mapped, the second is easier, and the third easier still. The skill of getting what lives in your head onto a page improves quickly with practice.
A realistic goal for a service business is to have its five to ten most critical processes documented within three months. Not perfectly, and not with flowchart software. Clearly enough that someone else could follow them, and that you could take a week off without everything depending on your phone being on.
That is what documentation buys: a week off with the phone switched off.