01. The one-liner
A process map is just a drawing of how something really works, step by step, on a piece of paper. You will almost always be surprised by what you find out.
02. Where it came from
The short history
The first process maps were drawn by Frank and Lillian Gilbreth in the early 1900s. They were industrial engineers (and also, as it happens, the parents in the book Cheaper by the Dozen). The Gilbreths were obsessed with one thing: most workers' hands were moving more than they needed to, and nobody was noticing because nobody had actually drawn the work. They invented the flow process chart, with little symbols for each kind of action. Transport. Inspect. Operate. Delay. Store. Once the work was on paper, it could be shrunk. They famously cut a bricklayer's motions from 18 per brick down to 5, and changed an entire trade.
The technique has shape-shifted since then. Toyota built value stream mapping in the 80s to draw whole factories at once. Consultants packaged SIPOC (Supplier, Input, Process, Output, Customer) as a one-page snapshot for boardroom audiences. Software teams draw swim lanes to show who is responsible for which step. None of these are complicated, and none of them require software. They're all the same idea wearing different clothes. Get the work out of people's heads. Draw it. Look at what you actually drew. Then improve it. The pen is the whole tool.
03. How it works at work
The Belt textbook version
Pick something your team does regularly. The way a support ticket travels. How a weekly report gets produced. Your hiring process. Find a real piece of paper. Draw the process from start to end, in pen, exactly as it happens. Not how you wish it happened.
Supplier
Who or what feeds the work in? In a hiring process, that's the recruiter, the candidate, the hiring manager, the interview panel. Write each of them down the left edge of the page. Be specific. 'The team' is not a supplier. Marie and Devon and a freelance recruiter are.
Input
What does each supplier hand in? Resumes. Calendar slots. Interview rubrics. Feedback forms. Write the input next to each supplier. If you can't name the input cleanly, that's usually a sign the work is fuzzy, which is useful information on its own.
Process
Now the middle. Each real step, in order, in boxes with arrows. Recruiter screens. Phone interview. Take-home task. Onsite. Debrief. Offer. Be specific. Don't write 'candidate is processed.' That's not a step, it's a euphemism for not knowing what happens. Write the five or six things that actually take time, in the actual order they happen.
Output
What comes out of each step? An updated ATS record. A scheduled onsite. A rejection email. A signed offer. List them next to the step that produced them. Outputs are usually where the leaks are. A step that produces nothing visible is almost certainly waste.
Customer
Who needs the output? The hiring manager. The candidate. Finance. The team. Everyone in the chain. When you finish the page, look at the drawing for two full minutes. You will find at least one step that nobody really owns, one step that exists but doesn't matter, and one handoff where time is leaking out. Every team finds these in their first map. They were always there. You just couldn't see them before you drew them.
04. How it works in real life
The secret self-help version
Same five letters. Different problem. Pick something domestic that keeps going wrong. Getting the family out the door on Saturday mornings, say. Or how money moves through your household.
Supplier
Who is in the morning, and what 'feeds in' to it? You. Your partner. The kids. Last night's preparation (or lack of it). Bags packed or not packed. The plan for the day, which currently lives only in one person's head.
Input
List honestly. Cereal. Coffee. Three pairs of shoes. Two backpacks. A vague sense of where everyone is supposed to be by 9 AM. A plan that nobody wrote down. If the inputs include 'the schedule, in my head only,' that's a finding before you've even drawn the process.
Process
Walk through the actual morning, step by step, in order, in boxes. Wake up. Coffee. Wake the kids. Breakfast (three different requests, two of which weren't agreed to the night before). Get dressed. Find shoes. Find the other shoe. Find a coat for the second kid. Pack bags. Leave. Notice that 'find shoes' is its own step. It belongs on the page. Most household friction is invisible until you write the boring steps down.
Output
Two fed, dressed, equipped humans heading out the door. A medium-stressed pair of adults. A kitchen that needs cleaning when you get back. Write that down too. The kitchen is real, even if you try not to think about it until 3 PM.
Customer
Who needs the output? The kid going to soccer. The kid going to a birthday party. Future-you who will deal with the kitchen at 3 PM. Now look at the page. The pattern shows up immediately. Three of the five steps involved hunting for things. The coat conversation could have happened the night before. The breakfast disagreement could have been a five-minute talk on Friday. You don't need a process consultant. You needed to see what you were already doing. That's the whole point of drawing it.
05. The assignment
Time
25 minutes
What you need
A sheet of A4 paper. A pen. Maybe a pencil for second-guessing yourself. Nothing else. No app.
The exercise
Pick one process you live with every week. A meeting. A morning. A monthly task. A handoff between you and someone else. Don't pick the worst one in your life. Pick a normal one, because the normal ones are where the surprises hide. Draw it. Boxes for each step. Arrows for the flow. Names of the people next to the steps they're responsible for. Use the whole sheet. Don't be neat. Neat maps lie. Messy maps are honest.
Then
When you finish, set the pen down and sit with the page for two full minutes. Two minutes is longer than it sounds, which is part of the exercise. Almost every first-time map reveals three things on its own: a step that doesn't add anything, a handoff where time or information slips, and a step where the wrong person is doing the work. You don't have to fix any of them yet. The drawing is the work. The fixing comes much later, and is much easier, once you can see.
06. The honesty check
Explain it to a 12-year-old
If you want to understand how something works, draw it. Boxes for the things. Arrows for the way they connect. Then look at your drawing instead of arguing about what's in your head. You'll see things you couldn't see before, because pictures are honest in a way memories aren't.
If you can't say it this way, you don't quite have it yet. That's one of the rules of this site.
Coming next
Variation and the average that lies
Why 'on average we're fine' is the most dangerous sentence in any business, and how control charts let you see what's actually happening.
Not yet published. Get it in your inbox the day it goes live.
