The Process Map Everyone Signs Off On Is Usually Wrong
Ask any team how a process works, and they'll give you a clean answer: The order comes in, it gets reviewed, it gets approved, it moves to fulfillment. Simple, logical, matches whatever training document exists somewhere in a shared drive that nobody has opened in a year.
Now go sit next to someone while they do that work, start to finish, on a real order that came in that morning. You'll see a step that isn't in any documentation or an issue that arises that doesn’t have a documented fix in the standard operating procedure (SOP). You'll see an email exchange that exists because the system doesn't handle a specific exception well, so the fix is to just message someone directly and ask them to sort it out manually.
None of that shows up when you ask people to describe the process. Nobody is trying to mislead you; they genuinely believe they're following the documented steps, because the workarounds have become so routine they stopped registering as workarounds years ago.
Why This Gap Actually Matters
This is the part that trips up a lot of process improvement efforts before they even get started. A team gets the official description of how something works, maps it, finds the obvious inefficiencies, and redesigns around that map. The problem is they just spent real time and money improving a process that doesn't have all the “what-ifs”. The real process still includes the one with the manual invoice check and the side spreadsheet and the email workaround, keeps running underneath whatever gets redesigned on paper. And because nobody dug into why those workarounds existed in the first place or identifying the fixes, they end up reattaching themselves to the new process too.
Every workaround exists for a reason. Somebody built that side spreadsheet because the real system was too slow, too rigid, or missing a field they needed. Somebody added that manual check because skipping it once caused a real problem. Ignore the reason and you haven't fixed anything. You've just handed people a new set of official steps to work around all over again.
Go Watch the Work
The fix sounds almost too simple: go watch people do the work and ask better questions while you're there. Skip "what's the process," which just invites the polished answer. Ask "walk me through the last time you actually did this, start to finish," then ask what they do when something doesn't go the way it's supposed to. The exceptions are usually where the real process lives. The happy path is the version everyone describes first, and it's rarely the one carrying most of the workload.
This takes longer than sending out a survey or running a single workshop to map things on a whiteboard. It's also the only reliable way to find the workaround carrying more of the operation than anyone in leadership realizes.
The Workarounds Are Telling You Something
The instinct in a lot of process work is to treat these deviations as the problem or things to eliminate, so everyone finally falls in line with the "real" process. That instinct has it backwards. Those deviations are some of the best diagnostic information available, and they point directly at the exact spot where the documented process breaks down under real conditions. Redesign around the official map and you're solving a problem that doesn't exist. Redesign around the workarounds and you're solving the one that does.
Good process improvement rarely starts with a whiteboard session about how things should work. It starts earlier, with an honest, sometimes uncomfortable look at how things work right now, workarounds and all. Skip that step, and the result is a nicer looking description of a process that was never quite accurate to begin with. Real improvement starts with what's happening on the ground.