Mapping a Process in One Afternoon: A Facilitator’s Guide
You do not need weeks of interviews to see how a process really works. With the right people and a tight agenda, one afternoon produces a map worth acting on.

It is two o’clock on a Sunday at a group of outpatient clinics in Amman, and six people are standing around a wall covered in brown paper. By six o’clock they will have mapped how a patient referral moves from the front desk to a specialist appointment, and they will have found four places where it waits for no good reason. That is what a well-run process mapping afternoon can do, and most organisations never try it because they assume mapping is a long consulting exercise.
This guide is for the manager or internal facilitator who wants to run one. It assumes no special software and no prior training, only a willingness to keep the room honest.
Choose a process with clear edges
The most common reason a mapping session fails is scope. “Procurement” is too big for an afternoon. “From a site engineer requesting materials to the purchase order being sent to the supplier” is about right. A good process for a first session has a clear trigger, a clear end point and somewhere between three and six people or teams involved.
Before the day, write one sentence on a card: “This process starts when … and ends when …”. Read it out at the start. Every time the discussion drifts into another process, point at the card.
Invite the people who do the work
A map drawn by managers shows how the process is supposed to work. A map drawn by the people who do it shows how it actually works. You need the second one. Invite one person from each step, preferably someone who handles the work daily, plus one manager who can make decisions about what you find.
Keep the group between five and eight. Fewer than five and you miss steps. More than eight and the quiet people stop talking. If a senior person tends to dominate, ask them to arrive for the last hour, when decisions are needed, rather than the first.
The afternoon, hour by hour
Four hours is enough if you protect the time. A simple running order looks like this:
| Time | Activity | Output |
|---|---|---|
| First 20 minutes | Agree the start and end points, explain the rules, pick one real recent example to follow | Scope card and a real case on the wall |
| Next 80 minutes | Map the current process step by step, using the real case, one sticky note per step | Current-state map |
| Short break | Facilitator tidies the wall and notes open questions | Clean map |
| Next 60 minutes | Mark waits, rework loops, handovers and missing information on the map | Problem markers |
| Final 60 minutes | Pick the three problems worth fixing first, assign an owner and a next step to each | Short action list |
Following one real recent case is the single most useful technique. Instead of asking “what happens next?”, ask “what happened next with this request from last Tuesday?”. People stop describing the official procedure and start describing reality.
How to run the room
Materials
Use a long roll of paper on a wall, sticky notes in three colours and thick markers. Yellow for steps, pink for problems, blue for questions nobody can answer. Avoid laptops and projectors for the mapping itself. When one person controls the screen, everyone else becomes an audience.
Rules worth stating out loud
- One step per note, written as verb and object. “Check stock”, “Approve request”, “Email supplier”. This keeps notes small enough to move around and stops vague notes like “processing”.
- Map what happens, not what should happen. If the official step is skipped three times out of four, the map shows it being skipped.
- No blame. The aim is to find weak points in the process, not someone to hold responsible. Say this at the start and repeat it when someone gets defensive.
- Questions go on blue notes, not into long debates. If nobody knows how long the finance check takes, write it down and move on. Someone can find out next week.
What to look for in the second half
Once the steps are on the wall, walk the map with the group and mark four things in pink. Waits: the request sits in an inbox or a tray. Rework: something goes back a step because information was missing. Handovers: work moves between people or departments. Duplicates: the same data is typed twice into different places. In the clinic example, the biggest finding was that referral letters were scanned at reception and then printed again by the specialist’s assistant because the two systems did not share files.
Turning the wall into action
A photographed wall of sticky notes is not an outcome. Before people leave, agree on three problems at most, and for each one write a named owner, the first concrete step and the date it will be done. Small fixes are welcome. A form that collects the missing information at the start often removes a whole rework loop.
Within two working days, the facilitator should redraw the map cleanly, in a tool as simple as PowerPoint or Visio, and send it with the action list to everyone who attended. Ask them to correct anything that looks wrong. That second pass usually catches a few missing steps and builds ownership of the result.
Then schedule a 30-minute follow-up two or three weeks later. Without it, the actions fade into everyone’s normal workload. With it, the group sees that the afternoon led somewhere, which makes the next mapping session much easier to fill.
From one afternoon to a clear operating picture
A single afternoon will not redesign your whole operation, but it gives you something many organisations lack: a shared, honest picture of one process, drawn by the people who run it. This follows the Know and Map stages of the KEMLAT Method: understand reality first, make it visible, and only then decide what to change or which system to buy.
When the processes are larger, cross several departments or need redesign rather than quick fixes, our Operations Transformation service runs this work in a structured way, from operational audit and process mapping through to redesigned processes, clear ownership and standard operating procedures (SOPs) that teams can follow without asking.



