Context
I've run this test at two companies now: a B2B/B2G technology company and a multi-brand education company. Both were, by conventional standards, unusually well documented. One had a COO who maintained detailed flowcharts for everything. This case is about what the flowcharts couldn't show.
What Looked Broken
Nothing. That's the point. By every process-maturity signal — documentation coverage, flowchart detail, leadership fluency in their own processes — these organizations looked healthy. Nobody commissioned this diagnosis. I went looking because answers to my questions kept not quite matching the questions.
What I Noticed
The flowcharts described steps the way you might write "put the peanut butter on the bread": accurate, and missing everything that matters. Open the jar. Get a knife. The steps between the steps, where the actual work lives, existed in nobody's documentation.
So I started asking people what specific documented steps meant in practice. One onboarding step — effectively "prepare the customer for onboarding" — I asked five people about.
What the Evidence Showed
Five completely different answers. Five sets of actions. Five definitions of done. Five different onboarding experiences, all running simultaneously under a single box on the official chart. One interpretation, and I am reporting this rather than inventing it, effectively involved a sword.
Nobody was wrong. Leadership was right that a process existed. Each person was right about their honest reading of it. The official story had one step where operational reality had five, and nobody had ever stood where all five were visible at once.
Interpretation 1
A different set of actions and a different definition of done.
Interpretation 2
A different set of actions and a different definition of done.
Interpretation 3
A different set of actions and a different definition of done.
Interpretation 4
A different set of actions and a different definition of done.
Interpretation 5
A different set of actions and a different definition of done.
One box wasn't one process. It was five.
The Actual Constraint
Documentation had created false confidence in shared meaning. The company possessed process documentation without process alignment. Visibility isn't the existence of information; it's the existence of shared, trustworthy meaning. And you cannot build systems — CRM stages, automation, reporting — on top of steps that mean five different things, because the system will encode exactly one of them and silently break the other four.
My Hypothesis
If we surfaced the interpretations side by side, without blaming anyone for having one, the organization could converge on a single defined process before encoding anything into software.
What I Architected
A simple, repeatable diagnostic: take a documented step, ask the people who touch it what it means, and map the answers next to the official version. Same table, same hour, leadership's version and the team's versions. The reaction is never anger. It's surprise — both sides discovering the other side's company exists.
What I Personally Built / Did
I conducted the interviews, mapped the interpretations, and presented the gap to leadership at both companies. At the technology company, I carried the reconciled definitions into the CRM transformation we were running at the time, so the system encoded the process as agreed rather than as assumed.
What Happened
At the technology company: the COO re-engaged with process definition. Honestly, it overcorrected at times — the instinct to control returned faster than the instinct to align, and what got closely managed wasn't always what most needed it. But shared definitions started existing, and leadership kept me close to exactly this kind of work afterward; the COO described me as the hire he couldn't replicate.
At the education company: leadership validated the findings and the method.
What Became Possible
Process conversations could reference a shared object instead of five private ones. And the CRM build had something real to encode.
What I Learned
The most dangerous process isn't the undocumented one. It's the documented one nobody has verified, because documentation ends the conversation that would have revealed the gap. Never eliminate or automate a step until you know what it actually means to the people performing it.
Evidence / Artifacts
Underlying materials are confidential at both companies. The interactive diagram on this page is a recreated, generalized illustration of the finding. Yes, the sword was real. No, I can't show it to you.
Related Work
The CRM transformation this fed: The Build Wasn't the Problem. The Gap Was. The pattern underneath: Shadow Systems. The human version: Every Company Has a Susan. Usually Several.