The Organisational Fork
Stop trying to transform your legacy business from the inside. Build the new one beside it. Choose a path for your workflow and see the outcomes diverge.
Why Transformation Fails
Kodak invented the digital camera. Nokia had smartphone prototypes years before the iPhone. Blockbuster turned down buying Netflix for $50 million. They didn't lack the technology. They tried to transform the core from within. The core won. It always does.
What the Fork is NOT
- • Not a skunkworks or innovation lab
- • Not a "Centre of Excellence"
- • Not a spin-off or separate company
- • Not a pilot programme that reports to the old structure
What the Fork IS
- • Real work — actual business processes
- • Real metrics — same KPIs as legacy
- • Its own governance — agent-speed, not committee-speed
- • Ring-fenced budget — not competing with legacy
- • A defined absorption trajectory — designed to grow
The funding reframe: The Fork isn't asking for new money. It's asking you to spend the same money differently.
Organisational Fork Simulator
Choose a path for your highest-friction workflow. Then see the outcomes at Month 3, Month 6, and Month 12.
Path A: Transform
Evolve the existing process step by step
Add AI copilots, modernise gradually, keep existing approvals and governance. Minimal disruption, consensus-driven rollout.
Path B: Fork
Build an AI-native version from scratch
Small team, ring-fenced budget, agent-speed governance. Runs in parallel. Real work, real metrics, designed to absorb the legacy version.
Outcome Comparison at Month 12
Beachhead Readiness Scorer
Score your workflow against five criteria to determine if it's an ideal first fork, a second-wave candidate, or better left patched.
The Courage Equation
The courage required to fork today is significantly less than the courage required to fork in three years — because in three years the gap is wider, the talent is scarcer, and the competitor who forked today is three years ahead.