The Operating Edge Capstone: The Final Word on Thriving in Disruption
Thirty percent of a strategy’s available value never arrives. That figure describes high performers, and McKinsey puts the shortfall on the operating model rather than on the strategy or on the teams delivering it.
Read that as a description of competent organizations. The strategy was sound. The programs delivered. The operations team produced what it was given. The value went missing in the connective tissue between them.
Connective tissue belongs to whoever designs the operating model, which means somebody can design it differently.
That design has a shape. A continuous chain of accountability from strategic direction through execution to performance feedback, six stages, each one with an owner, a forum, and a cadence. Underneath it, a culture that determines whether what reaches those forums is real or whether it is what leadership wanted to hear.
This capstone assembles a year of the series into that structure.
Disruption arrives as a continuous operating condition. The organizations that convert it into advantage built the structure before they needed it.
Disruption arrives as a continuous operating condition. The organizations that convert it into advantage built the structure before they needed it.
Sarah Marshall | Founder and CEO, Operations Architect
The Operating Edge. Capstone.
We are in an era of escalating ecosystem uncertainty, where disruption is continuous rather than episodic. Your strategy meets a changed world before the plan year ends. Your competitors meet the same world. What separates the organizations that compound from the ones that absorb shock after shock is not the quality of the response. It is whether the structure existed before the shock arrived.
This series has spent a year on the various aspects of the framework for thriving in disruption. This capstone assembles them into a final version.
What the organizations that win actually do
Four things, and each one depends on the others.
They maintain tight alignment to their strategic objectives, as both the objectives and the work keep moving. They build a culture of responsive flexibility, so the right behaviors stay easier than the wrong ones. They deliver high value to those objectives through all of their efforts, not only through the programs somebody is watching. And they embed disruption shock absorbers into the operating system itself, so recovery is a cadence instead of a mobilization.
McKinsey put a number on what the absence costs. Even among high performers, about 30 percent of a strategy’s available value never arrives, and McKinsey attributes the shortfall to the operating model. Read that as a description of competent organizations. The strategy was sound, the programs delivered, the operations team produced what it was given. The value went missing in the connective tissue, and connective tissue belongs to whoever designs the operating model.
Which means somebody can design it differently.
The Operating Edge Framework Create an Organizational System
Three foundations. Three integrating capabilities. One operating system.
The foundations are what you build. Adaptive Culture is the human operating system that determines whether every other investment survives contact with the organization. Actionable Strategy keeps strategic direction current, specific enough to act on, and connected to delivery. Orchestrated Execution connects strategic priorities to the actual work, and surfaces misalignment before it compounds.
The capabilities are what those three produce when they operate together as a system. Anticipation senses what is coming and prepares before it arrives, so the organization never starts from zero. Coherence maintains tight alignment between strategy and execution as both evolve. Adaptability reaches a new operating normal at speed, as a practiced discipline rather than a heroic effort.
None of the three capabilities gets built directly, which is the part most organizations miss when they go looking for a resilience program to buy. You build the foundations, you connect them, and the capabilities emerge from the connection. Underneath all six is operational clarity: every person able to see what the organization is trying to do and how today’s work serves it.
This series has built those six pieces one at a time. What follows assembles them.
Culture is the constraint, and it comes first
Every mechanism below this paragraph consumes information. Adaptive Culture is the human operating system that determines whether each of those mechanisms tells you what is real or quietly produces what leadership wants to hear.
March and Simon described the failure mode sixty years before anyone called it a dashboard problem. They called it uncertainty absorption: somebody draws an inference from evidence, and the inference moves onward while the evidence stays behind. By the time a status reaches an executive forum it is a judgment about a judgment about a number nobody has opened in six weeks. No governance design survives that, because governance is only as good as what reaches it.
So culture is the binding constraint on information quality, and it gets addressed structurally. Five behaviors matter most: transparency in surfacing what is real, accountability in owning what happens, curiosity as the default response to the unexpected, collaboration across boundaries rather than within them, and continuous improvement as a practiced discipline. Integrity underlies all five.
Culture reveals itself in three moments that repeat every week in your organization. What happens when somebody surfaces a problem. What happens when somebody misses a commitment. What happens when somebody disagrees with a priority call.
You already know how those three go where you work. That answer is your starting condition, and a values statement will not change it. Redesign one governance mechanism so the right behavior becomes the easy one, then expand from the evidence that produces.
The spine: one chain, direction through to performance
The Value Delivery Spine is the continuous chain of accountability from strategic direction through execution to performance feedback. Six stages across two phases.
The planning phase settles what and why. Actionable Strategy states direction a delivery team member can test their own work against. Business and Operations Model Refresh adjusts the operating model to deliver that direction, before any program is scoped. Strategic Commitments establishes the work we are doing today towards the strategic objectives, and puts what the organization has already promised in one place, scored against the strategy.
The execution phase settles how and whether. Proposed Solutions evaluates new work against the priorities and refreshed model rather than against last year’s. Solution Delivery Programs executes with the value sought still attached to the work. New State Performance measures what the business actually produces against what the strategy asked for, and feeds that back into strategy. Continuous coupling.
Every stage gets an owner, a forum, and a cadence. That is what makes it a system rather than a diagram. The forums are where the calls get made: Strategy Validation for options and debate, QBRs and MBRs for decision rhythm, Portfolio Rationalization to prioritize, fund and kill, and the Ops Review for performance assessment.
Get Sarah Marshall’s stories in your inbox
Join Medium for free to get updates from this writer.
Kaplan and Norton got to part of this first, and the debt is worth stating. Their strategy map links objectives, measures and initiatives across four perspectives, financial, customer, internal process, and learning and growth, into a single picture of how a strategy is meant to produce value. It remains the clearest published account of strategy as a connected system. The spine does the adjacent job: a map describes the logic, and the spine assigns the accountability and the cadence that keep the logic current. Draw the map once and it describes an intention. Operate the spine and it reports a condition.
The shock absorbers
A chain that only looks backward reports the damage after it is done. Two capabilities make the structure absorb disruption rather than record it.
Anticipation senses what is coming and prepares before it arrives, so the organization never starts from zero. The Living Uncertainty Registry is the instrument: a continuously updated record of the assumptions you are acting on, ranked by consequence and confidence, with assigned owners and defined escalation triggers. Three sensing failures recur. Perfectionism waits for certainty before acting on a weak signal. Political filtering surfaces the signal and then reads it through the commitments already made. Structural absence leaves nowhere for a signal to become a decision.
Adaptability shortens the distance between a disruption arriving and the organization operating effectively again. Governance is what makes it structural, by giving the response a time, a place, and decision rights before anyone needs them.
The pairing matters more than either half. Sensing without coherence produces awareness that does not move the organization. Coherence without sensing produces alignment to a strategy that may already be obsolete.
One design requirement belongs here, and it is the one most organizations leave to good intentions. Diane Vaughan’s study of the Challenger launch decision gave us normalization of deviance: a practice nobody would have accepted at the start becomes acceptable through repetition without consequence, over a long incubation, with warning signs available throughout. The people closest to a variance are the least able to see it as one, because they watched it become normal. So an external check belongs in the structure as a stage with a cadence, performed by somebody outside the chain. Asking for candor instead asks people to notice what their own experience has made invisible.
The Decision Making Stack Drives the System
A structure produces value only where decisions get made inside it. The coherence arc built the mechanism for that, piece by piece: a decision making stack designed to produce fast, high quality decisions that keep strategy and execution coherent while both keep moving.
The stack has four parts. A goal, meaning the decision the organization actually needs, stated at the altitude where it belongs. An architecture: agreement on what matters, alignment of the work to it, and the structure that keeps both current as they change. Inputs and outputs, the seams where work crosses between teams and where integration and coordination either happen or quietly fail. And decision rights, meaning who can act without asking permission.
Decision rights are the last brick. Without them the first three produce a very well-informed observer: someone who can see the misalignment, convene a meeting, escalate once, and document the problem with increasing precision every quarter. Under RACI, accountable and authority are one assignment with two names, so an accountable party without decision rights is a broken assignment rather than a hard job.
Four decisions make a horizontal assignment real, and each is narrow enough to write on one line. Stop a program that no longer serves a current objective. Reallocate capacity between programs inside a bounded envelope. Change a commitment between two teams at the seam, without routing through either chain. Escalate with a deadline attached, where silence past the date resolves in a stated direction.
This is what connects the stack to the spine. Every stage of the spine has an owner, a forum, and a cadence. The stack is what has to be true inside that forum for the cadence to produce a decision rather than a status update.
How it gets built
Nobody stands up the whole framework at once, and the attempt is how this becomes another initiative that produces one answer and ends.
Five moves, in order. Diagnose the friction, scoped or systemic, and baseline the health. Stabilize by clearing the fires and setting the operating cadence and decision rights. Configure the spine and the minimum build for the capability under the most pressure. Activate by operating the reviews, sensing what is coming, and rehearsing the response. Sustain with exit criteria, a scaled cadence, and off-ramps.
Minimum Viable Configuration governs the Configure move, and it applies to one capability at a time. Actionable Strategy at minimum is a simple strategy build using the intelligence you already have. Coherence at minimum is OKRs with no portfolio layer, built on later. Each cut above the minimum adds methodology that improves it. The discipline of producing a current answer on a schedule is the capability; the artifact is the evidence that you have it.
Build outward from your biggest pain point. Light enough to operate part-time.
What the series was about
Three foundations make an organization capable of this work: an Adaptive Culture, an Actionable Strategy, and Orchestrated Execution. Three integrating capabilities emerge when those foundations function as a system: Anticipation, Coherence, and Adaptability. One center underneath all of it: operational clarity.
Two promises come out the other side. Strategy and execution stay continuously aligned as both evolve. Strategic change becomes a continuous operating condition your organization processes, rather than a periodic crisis it survives.
The volatility is not going to stop. With the structure standing, leaders sense change early, respond with clarity, and convert disruption into sustained strategic opportunity. Without it, every shock costs the same as the last one and teaches the organization nothing.
You have the strategy. You have the operations. Build the chain between them, give every link an owner and a cadence, and put the culture underneath that makes the information real.
The rest of it you have been doing all along.
About this series
This piece closes The Operating Edge, a series on building organizations that thrive in continuous disruption. The series established the three foundations, worked through the cost of strategy and execution drift, examined coherence as a structural capability, and then asked what adaptability requires of a system and of the people inside it. This capstone assembles them around the Value Delivery Spine.
About the author
Sarah Marshall is the founder and CEO of Operations Architect and the author of The Operating Edge: Building an Organization that Thrives in Disruption. She has spent more than 30 years in strategy and operations across software, hardware, consumer electronics, biotech, and chemicals, leading functional and business operations at organizations ranging from Fortune 10 enterprises to startups, including executive roles at Google and Logitech. She has a BS in chemical engineering and an MBA, and she brings that systems training to one problem: the structural gap between the strategy leaders set and the work their organizations deliver. Through Operations Architect she works with founders, CEOs, and operations leaders on executive advisory, transformation programs, and fractional COO engagements.
Contact and next steps
Assess your readiness. A short self-assessment across the three foundations and three integrating capabilities. operations-architect.com/free-self-assessments/
Schedule a free consultation. One hour on the specific friction in front of you. calendly.com/sarah-marshall-operations-architect/60-minute-initial-consultation
Read the series. The Operating Edge on Medium. medium.com/@sarah.l.p.marshall
Operations Architect. operations-architect.com
References
McKinsey & Company. A new operating model for a new world. McKinsey Quarterly, June 18, 2025. Krivkovich, Di Lodovico, Weddle, Maor, Mahadevan, Steele.
March, James G., and Herbert A. Simon. Organizations. 1958. Uncertainty absorption.
Vaughan, Diane. The Challenger Launch Decision: Risky Technology, Culture, and Deviance at NASA. University of Chicago Press, 1996.
Kaplan, Robert S., and David P. Norton. “Having Trouble with Your Strategy? Then Map It.” Harvard Business Review 78, no. 5, September to October 2000, 167 to 176. See also Strategy Maps: Converting Intangible Assets into Tangible Outcomes. Harvard Business Press, 2004.
Hashtags
#TheOperatingEdge #OperationsArchitect #OperatingModel #StrategyExecution #AdaptiveCulture #OperationsLeadership
