You Haven't Fixed Anything. You've Just Given the Mess a QR Code.
Somewhere in a glass-walled meeting room right now, a slide deck is being presented that describes the act of taking a broken process and encoding it into software as "digital transformation." The slide has a curved arrow on it. The arrow is teal. Everyone in the room nods, because the arrow is very convincing.
This is the foundational myth of an entire industry: that the problem with broken workflows is that they are insufficiently digital. That chaos, given a dashboard and a helpdesk ticket category, becomes something other than chaos. That if you move fast enough through the wreckage, the wreckage counts as progress.
It does not.
The Load-Bearing Workaround
Here is something that transformation programmes are structurally incentivised to ignore: most analog processes are analog for a reason. They were built by actual humans solving actual problems in real time, patching the gaps with institutional knowledge, judgment calls, and the kind of contextual wisdom that does not survive a requirements workshop.
Someone on the team knew that the Friday purchase orders needed a second look. Someone else knew that submitting the complaint form before the second-stage sign-off meant it vanished until the quarterly review. These are not inefficiencies. They are load-bearing workarounds. The operational ceiling of the organisation has been quietly resting on them for years.
Then the consulting firm arrives, interviews seventeen people across four departments, and produces a current-state process map that is technically accurate in the same way a photograph of a burning building is technically accurate. It shows you what something looks like. It tells you nothing about why it is on fire, or who is still inside.
The Scanner and the Unopened Post
You know that stack of post that has been building up behind your front door for eight months? Bank statements. Pizza leaflets. A jury summons you have almost certainly missed. A letter from the council with a red border that you slid under the pizza leaflets so you would not have to think about it.
You decide, finally, to do something about it. So you buy a very good scanner. You scan every item. You create folders. The jury summons is now a high-resolution PDF filed under "Urgent Legal." The council letter is indexed and searchable. You have, technically, digitized your analog pile of post.
You have also, technically, still not opened any of it.
This is not a fringe outcome. It is the standard outcome of transformation programmes that begin with the technology and reverse-engineer the people in afterwards. The digital system becomes the destination rather than the vehicle. Success gets quietly redefined from "has the problem been solved" to "has the problem been uploaded." And because the upload happened — because the dashboards are populated and the completion rate reads ninety-three percent — the programme gets closed, the consultants get thanked, and the lessons-learned document gets filed in the SharePoint folder that nobody has permissions to access.
The People Who Actually Paid for This
The cost of this cycle is not primarily financial, though the financial cost is considerable and almost always underreported because the business case assumed the workarounds would disappear on their own, like embarrassing houseguests.
The real cost is human. The frontline employees handed a new system without adequate training, without genuine involvement in its design, without any acknowledgment that their contextual knowledge was the actual asset being replaced — they are the ones who absorb all of the friction. They build the new workarounds. They carry the cognitive weight of operating a system that does not reflect their reality while the programme communications team sends them emails with the subject line: Exciting news about your digital journey!
And here is the compounding damage that rarely makes it into a board report. Every time this cycle completes — the chaos preserved, repackaged, and relaunched — a small but measurable quantity of institutional trust evaporates. Staff become incrementally less likely to engage honestly with the next initiative. They have learned, quite rationally, that engagement is effortful and that the system will be built around what the vendor already built, not around the architecture of their actual work. So they comply at the surface, answer the survey in whatever way ends it fastest, and wait for the whole thing to blow over.
The Organisations That Actually Get This Right
They do exist. They rarely headline conferences because their story lacks the dramatic arc that conference organisers require. There is no teal arrow slide. There is no "we moved at the speed of light" soundbite.
What they did instead was unglamorous. They fixed the process first. They talked to the people doing the work. They treated workarounds not as evidence of employee non-compliance but as evidence of organisational problem-solving — forensic clues about where the real friction lived. They built the digital layer on top of something that actually functioned, which meant the technology could finally do what it is genuinely good at: removing friction, surfacing better information, and giving people the space to make better decisions.
They did not scan the pile of unopened post. They opened it first.
Speed Is Not the Solution. It Is the Problem.
The pressure to show progress — to demonstrate "digital maturity," to have something credible in the board report by Q3 — consistently overrides the slower, less photogenic work of actually fixing what is broken. The transformation roadmap becomes more important than the transformation. The milestone becomes more important than the meaning.
A broken workflow digitized at the speed of light is still a broken workflow. It has simply failed more efficiently, at greater expense, and you now have an audit trail and a sans-serif error message to prove it.
The jury summons is still in the folder. The council letter still has a red border. You have simply given them both a very organised home.