When Process Maps Lie
Pretty diagrams can hide the exceptions that break real systems. Here is how we train analysts to pressure-test a map before it becomes policy.
A clean swimlane chart often describes the happy path that managers wish were true. Operators know the workarounds: the shared spreadsheet, the WhatsApp approval, the overnight batch that fails twice a month.
In our Systems Analysis Foundations cohort, every map must include an exceptions strip. Students interview at least one person who performs the work and one person who receives the output. Discrepancies become first-class documentation.
The goal is not a more decorative diagram. It is a map that predicts where automation will fail and where human judgment still matters—especially useful when Vietnamese operations teams sit between regional HQ tools and local regulations.
If your current map has no exception notes, treat it as a draft, not a source of truth.