Testing What a System Can Absorb
Real appetite. An operating model from a different era.
A province had big ambitions to transform its government into a more human-centred and impactful organization. The diagnostic had already been made public: the operating model was built for a different era, and people were working hard inside a system that no longer compounded their effort.
Real authorization. Real executive appetite. An open question about whether the system itself could hold the work long enough for the work to change it.
All workThe situation.
Section · what we walked intoThe ambition was to close the gap between mandate-letter intent and how the system actually made decisions, allocated resources, and delivered services. Political backing was real. Executive engagement was real. So was the appetite across the public service to change the way the work got done.
What hadn't been worked out was what the system could currently absorb. The transformation method was sound on paper. The question was whether the operating system underneath it could protect the work long enough for the work to mature into a new operating system.
The shift.
Section · what we changedWe treated the foundational year as a stress test of the receiving system. Every major activity ran as a structured experiment:
- A governance model that evolved from a Steering Committee to a Ministerial Committee as the work revealed where decision rights actually sat and what it took to move from alignment to action.
- A Triple Helix framework that named the three strands transformation must move in parallel: governance, operations, and delivery. The insight underneath it: progress holds or snaps back at the overlaps.
- A set of practical assets built to outlive the engagement: a Good Services assessment method for citizen experience, cross-functional workshops across policy, finance, digital, and HR, mission-style accelerators, and a prequalified vendor pathway designed as a capability flywheel rather than a contractor bench.
The reframe underneath all of it: transformation is an operating system change. The year was a deliberate test of what the system could absorb.
The flow.
Section · what travelsWhat the year produced was a clear-eyed answer to the question the work was designed to test. Appetite for change was stronger than the system's ability to hold it. The Good Services framework, the workshop methods, the accelerator learnings, the Triple Helix, and the prequalified vendor pathway remain as practical assets that departments can use, and several continue to.
The sharper legacy is the diagnosis itself, documented publicly: that cutting the status quo without investing in a defined future state produces weaker versions of today's results, and that learning does not scale unless it has a home. The work now functions as a reference case for the next attempt, in this jurisdiction and others.
Portable: When appetite outruns the system, the diagnosis is the legacy.
If this sounds like the system you're inside,
Start · discovery · next caseTell us what your receiving system is up against.
Half an hour. We'll reflect what we're hearing and name the receiving-system shapes we've seen in organizations like yours. If there's a fit, we talk about a lab or a sprint. If there isn't, you leave with a clearer read on the work in front of you.