Your processes aren’t designed. They’re accumulated. Every workaround your organization has ever invented to deal with a dysfunction is now embedded in how you operate — and nobody remembers what the original dysfunction was. The process map doesn’t reflect deliberate design. It reflects years of adaptation to failure. Layers of scar tissue from problems that may no longer exist, solving for conditions that may have changed three reorgs ago. Your organization has been shaped more by its failures than by its intentions. And the most dangerous part: these adapted processes feel normal. They’re “how we do things.” The workaround became invisible the moment it became routine.
What it looks like
There’s a process for everything, and most of them have steps that nobody can explain the purpose of. “We’ve always done it this way” is the actual answer when someone asks why. New hires notice the inefficiency immediately — then stop noticing it within three months as they adapt to the adaptation. The official process and the actual process are different, and everyone knows it. There’s an informal way things really get done, usually involving specific people who know how to work around the formal system. Some of these people are organizational heroes — they make things work despite the process, not because of it. If you mapped the actual workflow from initiation to completion on any significant deliverable, the path would be twice as long as it needs to be, with detours, approval loops, and handoffs that exist because something went wrong once, years ago. The organization runs slowly and everyone assumes that’s just how complex the work is. It isn’t. The work is simple. The accumulated adaptation to historical dysfunction is what’s complex.
The mechanism
Organizations adapt. That’s not the problem. The problem is that adaptation accumulates without curation. A customer escalation reveals a gap in the handoff between sales and delivery — so someone adds a review step. A miscommunication causes a production issue — so someone adds a sign-off. A key person leaves and takes context with them — so someone adds documentation requirements. Each adaptation is rational in isolation. But nobody ever removes an adaptation when the underlying condition changes. The review step stays after the handoff is redesigned. The sign-off stays after the production process is automated. The documentation requirement stays after the knowledge is embedded in the system. Over time, the process becomes a geological record of every failure the organization has experienced, each layer preserved in procedure. The current process isn’t optimized for current conditions. It’s optimized for every historical condition simultaneously — which means it’s optimized for nothing. And every time someone adds a new step without removing an old one, the process gets heavier. The adaptation compounds. What started as a lean operation carrying ten kilos of process scar tissue is now carrying fifty, and nobody can identify which kilos are load-bearing.
Why it persists
Three dynamics make the adaptation trap self-reinforcing. Removing a process step feels riskier than keeping it — nobody knows what that step prevents anymore, so removing it might reintroduce a failure mode nobody remembers. The safe choice is always to leave it. Meanwhile, the people who navigate the adapted process successfully have built expertise in workaround navigation. That expertise is real and valuable — to them. Simplifying the process devalues their navigational skill, which creates resistance from the people who are most competent within the current system. And underneath both of these, the adaptation trap is invisible because it looks like normalcy. The adapted process is “how we do things.” Questioning it requires the cognitive effort of distinguishing between deliberate design and accumulated adaptation — and from inside the system, they feel identical.
What changes
The diagnostic move is simple but uncomfortable: map the actual process, not the official one. Follow a real piece of work from initiation to completion. Document every step, every handoff, every approval, every wait state. Then ask, for each one: does this step exist because of a current operational requirement, or because of a historical failure that may no longer be relevant? The gap between the official process and the actual process is the diagnostic signal. A large gap means the organization has been adapting around its own dysfunction for a long time. The fix isn’t another process redesign — those tend to produce a new official process that the organization immediately begins adapting around. The fix is building the discipline of process archaeology: regularly excavating the layers of accumulated adaptation and deliberately choosing which ones to keep, which to remove, and which to replace with something designed for current conditions.
What I see
I’ve mapped actual versus official processes in climate tech companies where the gap was so wide that the official process was essentially fiction. The real work happened through a network of workarounds, personal relationships, and tribal knowledge invisible to anyone reading the documentation. The most striking pattern: the people who were best at navigating the adapted process were the most resistant to simplifying it — because their navigational expertise was genuine organisational value within the current system. Stripping the adaptation trap means temporarily devaluing the people who’ve been keeping the company alive despite its own processes. That’s why it requires structural redesign, not just process cleanup — you have to build a system where the people who were heroes under the old regime can be effective without needing heroics.
Where this shows up
The adaptation trap accumulates fastest in sectors with long sales cycles and regulatory complexity, where workarounds have more time to calcify. Climate adaptation companies develop elaborate processes for selling into fragmented municipal buyers — processes that become obstacles when they try to scale to enterprise. Built environment companies adapt around the partially-custom nature of every project until the adaptations become more complex than the work itself. Sustainable agriculture companies build seasonal workarounds that become permanent infrastructure. For investors looking at portfolio underperformance, the adaptation trap is often the invisible variable: the company isn’t slow because the team is bad, it’s slow because the accumulated process weight makes speed structurally impossible. Post-investment support that maps actual vs. official process is where the diagnosis starts.
The weight your organisation carries isn’t the work. It’s the accumulated history of every failure nobody cleaned up. Let’s map what’s load-bearing and what isn’t.