Open any company's documentation and you will find a clean diagram of how work flows. Spend a day with the people doing the work and you will find a different diagram entirely. The gap between the official process and the real one is where leverage lives, and the shadow process map is how you find it.
The gap is not a hygiene failure; it is information. Every workaround exists because the official process failed someone at a specific point, and they engineered around it, quietly, because proposing a process change is a meeting and a workaround is an afternoon. The shadow process is therefore a record of everywhere the design does not fit the work, written by the people who know best, in the only medium they were allowed: their own behaviour.
How to map it
Pick one end-to-end workflow that matters: onboarding, an approval, an incident response. Sit with three people who execute it, separately, and ask them to walk through what actually happens, step by step, including the workarounds. Compare to the documented process.
Interview craft decides what you get. Anchor every walkthrough in a specific recent instance ("walk me through the last one you did"), never the general case, because the general case triggers the official answer. Ask to see the artifacts as they narrate: the real spreadsheet, the side channel, the personal checklist taped to the monitor. And ask the two questions that surface the shadow reliably: "what do you do when this step fails?" and "what would break if you went on holiday for two weeks?" The separate-witnesses rule matters because divergence between the three accounts is itself a finding: where their stories differ is where the process exists only as improvisation.
What you will find
Steps that have been quietly skipped for months. Workarounds that became standard. Approvals that are theatre. Handoffs that route through one heroic person who is one quarter from burnout. The shadow process is the real one; the documented process is aspirational.
Grade what you find before acting on it, because not all shadow is bad. Some workarounds are improvements the official process should adopt (the team found a shorter path; promote it). Some are compensations for a real defect (the tool is too slow, so people batch outside it; fix the defect, not the people). And some are genuine risks wearing convenience's clothes: the skipped verification, the shared login, the compliance step that became a checkbox. The first category is free wins, the second is the real backlog, and only the third justifies tightening anything.
What to change
You have two choices for each gap: change the documented process to match reality (often the right call), or change reality to match the documented process (sometimes the right call, but it requires fixing the reason the workaround exists). Either way, the gap is the leverage point.
One rule protects the whole exercise: nobody gets punished for what the map reveals. The first mapping is a truth-finding amnesty, and it only works once word spreads that the person who admitted skipping the broken step got the step fixed, not a warning. Handle it punitively and every future map will show you the official process, beautifully performed for your visit. Re-map one critical workflow each quarter; the shadow always regrows, and its shape each time tells you what the organisation has been quietly routing around since you last looked.