You Can't Skip the Map | Why Every Process Improvement Project Starts With a Map

If you work in process improvement (or lead any kind of transformative project) you cannot escape process maps. Just about every engagement I work on requires one, and they can easily make or break how a project turns out.

I used to treat them as a formality, a box-checking exercise before the "real" work started. I don't anymore. Here's why, and how I actually use them.

The Power of Zooming Out

When a process breaks, our natural instinct is to zero in on the one step that's frustrating and try to fix it right away. But that instinct is usually the wrong starting point. If you zoom into the one issue, you could be missing a larger operational shortfall.

Building a process map forces you to zoom out and see the entire flow end-to-end. Instead of staring at a single flagged defect, you see exactly how that step connects to everything upstream and downstream. It fundamentally changes what you notice.

How to Map What is Really Happening

Once a team agrees on what isn't working, we walk through the process together from the very first trigger to the final output. The goal is to build a map that reflects what really happens, not what's supposed to happen.

It is incredibly tempting to map the workflow exactly as it's written in the training manual or the SOP.

!!!DO NOT DO THAT!!!

Going over how things should work won't solve anything. You need to capture how things actually work in practice. Those little hidden workarounds and deviations can hide where the real problems live.

Keep It Low-Tech, Bring the Right People

Build the map early, right after the initial conversation about the problem and before anyone starts pitching solutions.

Early process maps should be low-tech on purpose: a whiteboard, sticky notes, or a simple flowchart tool. The format doesn't matter, the people in the room do. You need the people who actually do the work, not a manager describing the process secondhand. Managers can describe the impact of a problem, but the boots on the ground experience the bad process and will give you a much better description of what's going on.

Keep the first draft rough and expect to redraw it two or three times. Each pass surfaces a step someone forgot, a handoff nobody owns, or a "wait, we still do that?" moment. You're not done until the people in the room stop correcting you

Wrapping it all up

Process maps often get dismissed as a box-checking formality, but they're actually one of the most powerful tools in process improvement work. Rather than fixing the first frustrating step you spot, mapping the full end-to-end flow forces you to zoom out and see how that issue connects to everything around it. The key is capturing how work actually happens, not how it's supposed to happen. To get there, build the map early with a low-tech format (whiteboard, sticky notes, whatever's easiest), and make sure the room includes the people who actually do the work, not managers describing it secondhand. Expect to redraw it a few times; you're done only when the people in the room stop correcting you.

Have fun mapping!