Free worksheet · about 20 minutes · no email required
Trace one thing.
Almost every business that feels disorganised is actually well organised — around five systems that don't talk. You can find most of what that costs you in twenty minutes, without hiring anyone, by following a single piece of information all the way through.
This is the first thing I do in a paid map. It works perfectly well on your own. Print it, or copy the tables into a notebook.
Step 1
Pick one real thing that already happened.
Not the process in general — one specific instance, preferably the most recent one. "How does it normally work" gives you the org chart. "Walk me through the last one" gives you the truth, and they are almost never the same.
Good candidates:
- The last new customer or client you took on
- The last order, job, or booking you fulfilled
- The last invoice you sent and got paid
- The last time somebody asked you a question you couldn't answer quickly
The thing I'm tracing:
Step 2
Write down every place it stopped.
Start at the moment it first entered your world — a phone call, a form, an email, someone walking in — and end when it was completely finished. One row per stop. Include the sticky note, the text message, and the thing that lives in one person's head.
| # | What happened | Where it lived | Who did it | Type |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 | ||||
| 5 | ||||
| 6 | ||||
| 7 | ||||
| 8 | ||||
| 9 | ||||
| 10 |
Most people expect four or five rows and end up with eleven. That gap is the whole point of the exercise.
Step 3
Mark each row with one of these.
A row can be more than one. MANUAL and RISK together is the combination worth circling — that's where a person is doing machine work and a mistake is invisible.
Step 4
Count.
Step 5
Now the two questions that matter.
How many times a week does this happen?
Multiply that by the manual stops. That's how many times a week
someone in your business is doing something a computer would do for
nothing.
Who is the only person who can do one of these steps?
Whatever you wrote there is your single point of failure, and it's
usually a person rather than a system. This is the risk most owners
can name instantly and have never written down.
Times per week:
Single point of failure:
What your numbers probably mean
Rough, and it holds up more often than it doesn't.
Your systems are in decent shape. Whatever's frustrating you is likely one specific gap rather than a structural problem — worth fixing, not worth rebuilding around. Don't let anyone sell you a platform.
Normal, and the most common place to be. Usually two or three of these can be closed by connecting tools you already pay for, which is far cheaper than new software. Start with whichever one you do most often.
Someone in your business has a full-time job that consists of moving information between systems, and it probably isn't in their job description. This is where a real structural fix pays for itself, usually faster than people expect.
Fix this before the efficiency ones, whatever the counts say. Silent failures cost more than slow ones because you find out from a customer.
If you want the whole picture instead of one thread
That's the map — this exercise done properly across the whole business, with you or with your team, and you get a written map of every flow, a ranked list of what's actually costing you, what to fix in what order, and which parts you can fix yourself without hiring anyone.
It starts with a free twenty-minute call. You keep the map either way, and it names what you can fix yourself.
Book a call See a finished map first
And if you did the worksheet and found nothing much, that's a real answer. Not every business needs software built.