The Patching Fallacy
Adding AI to a broken process makes the fast parts faster — the slow parts don't change. Model two futures for your workflow and watch the gap compound.
The $50 Million Lesson
A company spent $50 million deploying AI across every department. Marketing drafted in minutes. Legal reviewed 40% faster. But the approval chain was unchanged. The cycle time barely moved. They had built the world's best engine and bolted it to a horse and cart.
$15M invested. Net cycle-time improvement: ~15%. Employee satisfaction declined. Lost two senior hires. Payback not achieved at month 12.
$3M invested. Net cycle-time improvement: ~99%. Employee satisfaction improved. Attracted three new hires. Payback in 7 months.
Patching Fallacy Simulator
Model two scenarios for your workflow. Adjust the sliders and watch the gap between patching and rebuilding compound over five years.
Scenario A: Patch
Keep existing process, add AI copilots to accelerate parts of it.
Scenario B: Rebuild
Remove human handoffs from execution layer. Build the new process natively.
The Compounding Gap
Patch It or Fork It?
Answer four questions about your workflow. If all four are yes — fork it.
What Comes Next
You've diagnosed the friction, calculated the cost, and seen why patching won't close the gap. In Module 2, you'll learn the alternative: the Organisational Fork — how to build the new alongside the old, without blowing up what's working today.