The moment your strategy gets approved is the worst time to find out the conditions aren't ready. It's also the only time you can still do something about it.
Start with a 2-minute assessment
The hardest moment to question a strategy is right after it gets approved.
The energy is high. The budget is committed. The team is mobilized. Nobody wants to hear that the conditions for delivery haven't been designed yet.
That's exactly when it matters most to ask. Delivery Design comes in at the moment of maximum enthusiasm and asks the uncomfortable questions before momentum makes them expensive to answer. It's willing to recommend slowing down when the conditions aren't ready.
How decisions get made when the original plan doesn't cover reality.
How meaning survives handoffs between teams.
How learning happens early enough to matter.
How progress becomes visible to the people actually doing the work.
Not change management. Not agile coaching. Not another framework to implement.
Not a prescription for how to run your organization.
Diagnosis. Honest, specific, and designed to give you a clear picture of what to fix and in what order.
Five structural conditions determine whether change holds under pressure. Most stalled transformations are missing at least two of them — and the absence is rarely obvious until you look for it directly.
Every engagement starts with diagnosis. What happens after depends on what we find.
A 2.5-hour working session, run as a webinar or in-person in Toronto, bringing together senior leaders from a small number of organizations facing similar delivery pressure. Each participant examines a real outcome they're personally accountable for against the five delivery conditions. The format is deliberately cross-organizational: hearing peers from different sectors name the same stalls in real time is more clarifying than any case study. All four outcomes are valid: proceed, pause and design, re-sequence, or stop. Honest diagnosis is the point.
If the diagnostic reveals conditions that need to be built, this phase designs them explicitly: decision boundaries, handoff protocols, learning loops, and progress visibility mechanisms. Not theoretical documents. Operating agreements your teams can actually use when facing real trade-offs under pressure.
Support for keeping the conditions intact as organizational reality pushes back. Spotting early degradation before it becomes a crisis. The goal isn't dependence on facilitation, it's building your organization's capability to recognize and design delivery conditions independently.
A large public utility invested in an employee innovation platform. Ideas accumulated.
Almost nothing moved.
The problem wasn't the ideas. It was the conditions. No decision boundaries around which ideas could advance. No teams with authority and time to execute. No clarity on what the organization actually needed versus what was simply popular. The platform rewarded crowdsourcing, not delivery.
Through iterative redesign, specific campaigns around identified organizational needs, teams with real timelines and explicit decision authority, and roles that carried accountability, the platform became something genuinely different. A system with the structure to turn ideas into actual change.
"We stopped asking people to vote for their favourite ideas and started building the conditions for the best ones to actually land."
Between 2011 and 2019, Boeing used MCAS software to compensate for engine placement changes while avoiding additional pilot training. The competitive logic was sound. The delivery conditions were not.
Engineers optimized for "no additional training." Safety teams optimized for "prevent stalls." The conflict was never resolved, just hidden.
Engineers who raised safety concerns had no authority to stop or slow development. Schedule pressure removed their ability to adapt.
MCAS wasn't disclosed to the FAA during certification. A risk analysis predicting additional crashes was never escalated after the first one.
After 189 deaths in the first crash, Boeing didn't ground the fleet. Financial commitment made course correction feel too expensive.
Leadership saw certification achieved and costs controlled. Pilots saw an undocumented system and confusing emergencies.
A delivery conditions check in 2015, when stall problems first emerged, would have surfaced these fragilities. Any legitimate outcome, pause, redesign, extend timeline, would have been cheaper than $87 billion in losses and 346 lives.
"The conditions matter more than the talent. World-class engineering organizations produce catastrophic failures when delivery conditions are broken."
I've spent my career at the intersection of strategy and execution, at Accenture, Ontario Power Generation, and across a range of organizations navigating complex transformation. The pattern I kept seeing was the same: smart people, sound strategies, and transformations that quietly fell apart between approval and reality.
This work applies equally across sectors. Delivery conditions break in engineering firms, non-profits, public agencies, and healthcare systems for exactly the same structural reasons.
Delivery Design is my attempt to name that gap precisely and fix it systematically. I work with senior leaders who are accountable for outcomes that matter and willing to look honestly at whether their conditions are designed to support them.
This practice is currently operating through invitation-only diagnostic sessions. If your situation sounds like a fit, the best first step is a short conversation.
Five questions. Two minutes. A clear picture of which conditions are strongest and which need attention. Then we'll talk about what comes next.
Take the assessment kate@deliverydesign.ca · Toronto, Canada