The Executive Operating Model · Part 6 of 6
The Strategic Execution Operating Model: A Complete System for Executive Follow-Through
A complete system for closing the gap between strategy and what an executive team delivers: five layers tied by a traceability chain, with the monthly outcome commitment as its atomic unit.
Executive Summary
The Strategic Execution Operating Model is a system for closing the distance between an executive team’s strategy and the outcomes it actually delivers. It starts from a premise argued at length elsewhere in this series and documented across four decades of management research: strategy fails far more often in execution than in conception. The response is an architecture rather than another planning ritual layered onto the calendar.
The model organizes executive work into five interconnected layers: Direction, Portfolio, Execution, Measurement, and Learning. An unbroken traceability chain holds them together, running from mission down to individual work items under one rule, that no work should exist without upward traceability to strategy. Execution moves through a single atomic unit, the monthly outcome commitment, a time-bound strategic move that one executive owns and the model can sequence, measure, and roll forward.
The remaining layers keep the system honest. Execution health is read from a compact set of signals interpreted together rather than one metric at a time. Three standing registers and a graded escalation path keep decisions, assumptions, and risk visible and route blockers to the right altitude. A lean ritual set carries the cadence, coordinated by a facilitator who owns process quality rather than the commitments themselves. The whole system is installed in phases and matured over years rather than stood up once.
This paper specifies the whole system in one place so that an executive team can evaluate it, locate its own organization on the maturity ladder, and begin installing it. Two conventions hold throughout. First, the model is technology-agnostic; it concerns how executives commit and follow through, and it does not depend on any particular tool or platform. Second, every number in it is either a structural constant that defines the shape of the system or starting guidance to be tuned against an organization’s own baselines. None of the figures is an external benchmark, and the worked example used to illustrate the measurement loop is hypothetical.
The Execution Problem
Most executive teams that miss their strategy respond by re-examining the strategy. The instinct is understandable, but the evidence points elsewhere. In a multi-year study of large organizations, Sull, Homkes, and Sull found that between two-thirds and three-quarters of large organizations struggle with execution, and that the problem is concentrated not in strategic alignment but in coordinating across units and adapting as conditions change on the ground.1 The earlier and foundational work of Kaplan and Norton reached a compatible conclusion from a different direction: organizations lose their strategies in the gap between formulation and action because they lack a system to translate, communicate, and track strategy through to delivery, a shortfall commonly summarized in the estimate that the large majority of strategies are never executed successfully.2
The practical reading of this body of work is that the strategy an executive team writes is usually sound enough, and the failure occurs in the long, under-instrumented distance between the plan and the work. Delivery organizations closed a version of this gap years ago. They run on an operating model that converts intent into shipped outcomes on a cadence, with committed work, tracked progress, and a disciplined way to absorb change. The executive team that sets the direction typically holds itself to no equivalent standard. It plans in annual and quarterly rituals, meets on a calendar, and treats its own follow-through as informal. The Strategic Execution Operating Model exists to give the executive team the same execution discipline it already expects of the teams delivering beneath it, adapted to leadership work and kept deliberately lightweight so that leaders operate it rather than route around it.
The model is an original framework. It adapts proven elements of Restricted Agile, a delivery framework I developed for professional-services teams working under statements of work, timelines, and budgets, into a focused executive execution rhythm. The remainder of this paper specifies that framework as a complete system.
The Model in One View: Principles and Five Layers
Before the mechanics, the model is governed by a small set of design principles. They are worth stating first because they explain why every later mechanic takes the shape it does.
- Strategy should constrain execution rather than only inspire it.
- Executive capacity is the organization’s scarcest resource.
- Every recurring meeting should either create decisions or remove uncertainty.
- Work should enter the operating system intentionally rather than accumulate on its own.
- Progress should be measured through strategic movement rather than activity.
- Transparency should eliminate surprises rather than add reporting overhead.
- The operating model itself should evolve through retrospectives.
These principles are also the answer to the objection that a complete system means heavy process. The model stays light because each of its parts must earn its place against these tests. A ritual that produces no decision, a metric that measures activity, or a register no one reads is removed rather than tolerated.
Presented as one system, the model resolves into five interconnected layers. Each owns a different kind of work at a different cadence, and each feeds the layer above and constrains the layer below.
| Layer | Owns | Cadence | Purpose |
|---|---|---|---|
| Direction | Mission, vision, values, three-year strategy, strategic pillars | Multi-year | Set long-term direction |
| Portfolio | Annual priorities, major initiatives, strategic capabilities, sponsorship, funding | Annual | Invest executive attention in the highest-value work |
| Execution | Quarterly rebase, monthly executive sprints, weekly synchronization, executive outcomes | Quarterly to weekly | Convert strategic intent into measurable leadership action |
| Measurement | Sprint metrics, annual plan advancement, drift, portfolio health, KPI trends | Continuous | Determine whether execution is producing strategic progress |
| Learning | Retrospectives, drift analysis, quarterly lessons, annual strategy refinement | Quarterly to annual | Improve both strategy and execution capability over time |
The layers are the spine of the paper. The sections that follow specify each of them: the traceability chain and horizons that make Direction and Portfolio operational, the outcome commitment that carries Execution, the measurement loop, and the governance and learning instruments that keep the system honest and let it mature.
The Traceability Chain and Planning Horizons
The connective tissue of the model is a single traceability chain. Every level of work descends from the level above it, and no item exists without a path back up to strategy.
Mission → three-year strategy → strategic pillars → annual priorities → quarterly themes → monthly outcomes → work items.
The governing rule is that no work should exist without upward traceability. A monthly outcome that traces to no pillar is either mislabeled strategic work or work that does not belong on the executive team’s plate. The chain is what lets the model answer, for any activity consuming executive time, the question of which part of the strategy it advances.
The chain is operated through nested planning horizons, each of which owns a distinct decision at a distinct resolution. The three-year strategy sets the pillars and the phased arc of how the organization intends to scale, mature, and differentiate. Annual planning translates the pillars into the year’s priorities and capability-level objectives, creating a shared contract between executives, delivery teams, and cross-functional partners, and defining the strategic themes that shape the monthly sprints. Between annual planning and monthly execution sit quarterly themes, a lightweight device that names the emphasis of each quarter, for example foundation, scale, optimization, and expansion, and helps executives weigh competing priorities when several pillars compete for the same scarce attention. The monthly executive sprint is where specific commitments are actually made. The property that matters across all of this is that each horizon constrains and feeds its neighbors. A horizon that neither constrains the one below it nor feeds the one above it is decoration, and collapsing the horizons, so that strategy debates leak into execution meetings or execution status crowds out direction, is a recurring way the model fails.
The horizon that carries the most weight is the quarterly rebase. Every quarter, the executive team steps back from monthly execution to recalibrate. The purpose is to validate progress against the annual plan, re-sequence upcoming priorities against what has been learned, and set the scope for the next two to three monthly sprints. The distinction that makes this work is between a rebase and a replan. A rebase recalibrates direction on a fixed cadence while the strategy holds; the destination stays stable and the route is adjusted. A replan rewrites direction reactively whenever pressure arrives. Rebasing protects momentum because the team runs long enough against its commitments to deliver them; constant replanning destroys momentum because nothing is ever carried to completion. Agility in this model is a property of a reliable cadence rather than of continuous change. The rebase is the joint where strategy meets reality on a predictable schedule, and it is also where the assumption register, discussed later, is reviewed, because strategies fail when the assumptions beneath them quietly change.
The Outcome Commitment
An operating model is only as disciplined as its smallest unit of work, and for the executive team that unit is the monthly outcome commitment. Each executive commits to advancing one to three outcomes per monthly sprint, each a strategic move such as a decision made, a capability unlocked, or a critical dependency resolved, each linked to a strategic pillar and tracked. The unit is chosen deliberately. Because it is an outcome that one person owns, the model can sequence it, measure it, and roll it forward. A model built on tasks, deliverables, or status updates has nothing durable to operate on, and it slides back into confusing a full calendar with strategic progress.
The reason the unit is defined so tightly is that most executive work fails at the distinction between activity and progress. A leader can be fully occupied, moving deliverables and attending reviews, while advancing no strategic outcome at all. The commitment forces a sharper question: what will be true at the end of the month that is not true now. That question replaces the passive strategy deck and the recurring list of vague “big rocks” with a specific, ownable done state.
A valid executive sprint outcome must meet four criteria. It must be strategic, tied to a three-year pillar, an annual priority, or a defined capability objective. It must be executive-level, involving decision-making, cross-functional alignment, or the removal of blockers rather than task execution that belongs to a delivery team. It must be time-bound, achievable within the sprint with realistic scope and clear ownership. And it must be outcome-oriented, defined by a concrete done state such as a finalized decision, a launched pilot, a completed framework, or an unblocked initiative. An outcome that fails any of the four should be revised, delegated, or deferred rather than committed. Applying this test at the moment of commitment is what keeps the sprint from filling with work that looks like leadership.
Producing a strong outcome is a matter of refining a broad intent down a progression: idea, to initiative, to executive outcome, to sprint commitment. The method has six steps. Identify the strategic intent, naming which pillar the work advances and why it matters now. Find the executive lever that actually unlocks progress, which is usually a single leadership action: making a decision, creating alignment, approving funding, defining a strategy, resolving ownership, removing a blocker, selecting an option, or establishing governance. Define the done state precisely enough that its completion is observable. Test the outcome against a simple standard of objectivity, that someone outside the owner’s department can determine whether it is complete; if they cannot, the outcome is rewritten until they can. Ensure singular ownership, so that although many people contribute, exactly one executive owns delivery. And validate that the outcome fits a four-week sprint, splitting it, narrowing it, or elevating it into an initiative containing several sprint outcomes if it does not.
The language of an outcome signals its quality. Activity verbs mark weak outcomes and should be replaced with verbs that denote a completed executive action.
| Weak outcome | Strong outcome |
|---|---|
| Support PMO improvements | Finalize and approve a new PMO structure, roles, and governance model |
| Explore client issues | Lead root-cause analysis for two recurring client escalations and approve a resolution standard |
| Work on partner strategy | Define the criteria and select a shortlist of strategic partners for a new go-to-market initiative |
| Improve visibility into sales | Approve and implement an executive sales dashboard for tier-one accounts |
| Review the delivery process | Run a cross-functional retrospective on quarterly delivery gaps and approve three process changes |
A reliable template captures the pattern: a completed-action verb, plus the strategic deliverable, plus an observable done state, plus the strategic purpose. “Finalize the enterprise governance model to enable cross-functional ownership of customer implementations” is well formed because someone outside the owner’s function could confirm whether the governance model exists, and the purpose ties it to strategy. Verbs such as approve, finalize, define, decide, select, launch, publish, resolve, establish, and authorize belong at this altitude. Verbs such as work on, continue, support, explore, and review describe activity and signal an outcome that is not yet ready to commit.
The discipline that makes a commitment mean something is borrowed from delivery work. Restricted Agile exists because professional-services teams deliver under statements of work, timelines, and budgets, in an environment where clients want flexibility and predictability at the same time. It holds two truths together. Starting a sprint is a commitment to deliver the planned work when conditions remain stable. And change will occur and must be managed deliberately, transparently, and collaboratively rather than through informal drift. In practice this means commitment is enforced inside the sprint while change is absorbed outside it: once a sprint begins the work is locked, and if conditions hold the team delivers exactly what was planned, while new information is handled through defined mechanisms.
The executive operating model applies the same rule one level up. Once a leader commits an outcome for the month, that commitment holds unless new information forces a transparent rebase. This is the executive analogue of the delivery-team change mechanism, and it is why the quarterly rebase matters so much: the rebase is the defined, transparent channel through which strategic change enters the system, which keeps monthly commitments stable between rebases instead of eroding under whatever pressure arrived that week.
The commitment lives inside a four-week sprint that gives it a container. Week 1 is planning and commitment, where each executive defines the outcomes they will personally advance and links each to a pillar. Weeks 2 and 3 are execution, where leaders continue their normal roles with focused intent, hold a short weekly check-in to surface progress and blockers, and escalate early rather than late. Week 4 is review and retrospective, where the team examines what was completed, what was delayed, and what it contributed to strategic momentum, then carries the lessons into the next sprint. The cadence is minimal by design: its job is to give every commitment a defined start, a protected middle, and an honest close, without becoming project management.
Measuring Execution Health
Without measurement, an executive team learns whether it executed only at year-end, as a vague sense of overload rather than as evidence. The model instruments execution with a compact set of signals so that friction surfaces early enough to correct at the quarterly rebase. The signals fall into two families. Execution-health metrics describe whether committed work is landing. Executive-focus signals describe whether leadership attention is being spent where the strategy needs it.
Each metric carries a target band so the numbers drive action rather than merely describe. Green is healthy, watch warrants a conversation, and investigate signals that the model needs correction. The bands below are starting guidance, drawn from the framework’s own proposed defaults. They are not empirical benchmarks or validated thresholds, and every organization should tune them against its own baselines once it has a few sprints of history.
Execution-health metrics
| Metric | Definition | Target band (starting guidance) |
|---|---|---|
| Commitment accuracy | Committed items completed / total committed | ≥ 80% green · 70 to 79% watch · < 70% investigate |
| Roll-forward rate | Share of committed work moved to the next sprint | ≤ 15% green · 16 to 25% watch · > 25% investigate |
| Initiative age (median) | Median sprints an active initiative has been open | ≤ 3 green · 4 watch · > 4 investigate |
| Time to strategic outcome | Start-to-done elapsed time on pillar-aligned items | Trend down over time |
| Percent of annual plan advanced | Share of annual priorities advanced this sprint | ≥ 8% green · 5 to 7% watch · < 5% investigate |
Executive-focus signals
| Signal | Definition | Target band (starting guidance) |
|---|---|---|
| Exec pulse (1 to 5) | Self-rating of “I felt focused and impactful this sprint” | ≥ 4.0 green · 3.5 to 3.9 watch · < 3.5 investigate |
| Priority churn rate | Share of sprint items added mid-sprint that were not in the plan | ≤ 10% green · 11 to 15% watch · > 15% investigate |
| Dependency resolution rate | Share of known dependencies unblocked during the sprint | ≥ 85% green · 75 to 84% watch · < 75% investigate |
| Strategic drift time | Share of executive time consumed by unplanned or misaligned work | ≤ 15% green · 16 to 20% watch · > 20% investigate |
The last signal is sourced from a specific instrument, the Strategic Drift Log, which captures work that falls outside planned commitments and strategic priorities. Its purpose is to make visible how leadership time is actually spent, especially when urgent, unplanned, or misaligned activity consumes capacity. The log is self-reported during standups or retrospectives and reviewed monthly in the sprint review. It is a way to protect focus rather than a way to police individuals: by tracking drift entries and, more importantly, the patterns across them, the team exposes structural gaps such as unclear ownership, staffing shortfalls, or reactive demand, and it can respond with process changes, reallocation, or new commitments. Each entry records when the drift occurred, who did the work, what it was, the estimated time, the cause, the impact, any strategic pillar it touched, and the action taken.
The decisive move in measurement is that the signals are read as a set. No single metric tells the story; a converging pattern does. Consider an illustrative, hypothetical quarter across three monthly sprints. This example is constructed to show the reading, not to report a real outcome.
| Signal | Sprint 1 | Sprint 2 | Sprint 3 |
|---|---|---|---|
| Commitment accuracy | 90% | 83% | 65% |
| Exec pulse (average) | 4.2 | 3.9 | 2.9 |
| Strategic drift time | 15% | 23% | 28% |
| Priority churn rate | 8% | 12% | 18% |
| Dependency resolution rate | 95% | 88% | 91% |
Read one at a time, each figure invites a local explanation. Read together, the pattern is unambiguous. Commitment accuracy falls into the investigate band, exec pulse drops sharply, strategic drift time nearly doubles, and priority churn climbs alongside them, while dependency resolution stays strong throughout. The story is that unplanned work is crowding out committed work, executives feel it, and follow-through is eroding as a result, and because dependency resolution holds up, the problem is focus and capacity rather than coordination. The value of the model is that this appears as evidence during the quarter rather than as a vague sense of overload discovered at year-end. A rising-drift, falling-pulse, declining-accuracy signature is the model working as designed, and it is exactly the trigger the quarterly rebase exists to act on.
Two further instruments round out how status is read. Initiative health is assessed on more than a single red, yellow, or green: it separates delivery health (on track, at risk, off track), strategic health (high value, medium value, re-evaluate), and leadership attention (monitor, executive intervention required, escalate), because an initiative can be delivering well while losing strategic value, or holding strategic value while falling behind. And because executive overload is usually invisible, the model measures how executive capacity is allocated across categories such as strategic execution, operational leadership, customer engagement, people leadership, internal administration, firefighting, and innovation, and trends those percentages quarterly. At maturity, these feed an executive dashboard that combines four perspectives: strategic (annual plan progress, pillar advancement, initiative completion), execution (commitment accuracy, roll-forward, initiative age, dependency resolution), organizational (employee engagement, leadership capacity, hiring progress), and business (revenue, margin, customer retention, and cash flow).
Governance Instruments
The model governs itself with a small number of standing instruments. Their purpose is to keep decisions, assumptions, and risk visible and to route problems to the right altitude, without adding reporting for its own sake.
The executive team manages a portfolio rather than a set of independent initiatives. Each initiative is assigned exactly one primary category, drawn from a fixed set: growth, operational excellence, capability building, technology modernization, customer experience, risk reduction, talent, or innovation. And each is defined with a consistent set of fields: executive sponsor, business owner, strategic pillar, annual priority, desired business outcome, success metrics, major risks, dependencies, expected completion, current health, and investment level. Defining initiatives this way is what makes portfolio-level trade-offs possible, because it forces every initiative to declare its sponsorship, its strategic linkage, and its cost of attention.
Three standing registers preserve the reasoning the organization would otherwise lose.
- The Executive Decision Register is a permanent log of executive decisions, each recording the date, the decision, its owner, the context, the alternatives considered, the expected outcome, a review date, and the eventual result. It builds institutional memory and reduces the tax of re-litigating decisions the team has already made.
- The Executive Assumption Register tracks the strategic assumptions a plan rests on, for example market demand, hiring capacity, client retention, or competitive response. Because strategies fail when their assumptions change, the register is reviewed at every quarterly rebase.
- The Strategic Risk Register tracks strategic risks separately from operational ones, each with a probability, impact, owner, mitigation, trigger, and contingency, and is reviewed monthly.
Blockers are routed through a graded escalation framework so that not every obstacle consumes executive attention.
| Level | Resolution altitude |
|---|---|
| Level 1 | The department resolves it |
| Level 2 | Cross-functional leaders resolve it |
| Level 3 | The executive owner intervenes |
| Level 4 | The executive team decides |
| Level 5 | Board-level discussion |
Finally, the model tracks strategic debt explicitly, in the same spirit as technical debt. Delayed platform investments, deferred organizational redesign, legacy operating processes, outdated governance, and repeated temporary workarounds accumulate a cost that is rarely visible on any single initiative’s status. Naming and tracking that debt keeps it from silently compounding until it constrains the strategy itself.
The Operating Rhythm
The system runs on a defined meeting architecture, and every meeting in it has a decision purpose. A meeting that neither produces a decision nor removes uncertainty does not belong in the rhythm.
| Cadence | Ritual | Decision purpose |
|---|---|---|
| Weekly | Executive sprint standup | Surface status movement and blockers; escalate early |
| Monthly | Sprint review and retrospective | Walk through outcomes and measurement; capture lessons |
| Quarterly | Rebase | Confirm direction, re-sequence priorities, review assumptions |
| Semi-annual | Strategic health review | Assess whether the strategy itself still holds |
| Annual | Strategic planning | Set the year’s priorities and capability objectives |
The rhythm is coordinated by a facilitator, a role typically held by a chief of staff or a PMO lead. The facilitator keeps the cadence running and maintains the historical execution record, but does not own the strategic commitments; those belong to the executives. The remit is broader than scheduling. The facilitator protects executive focus, challenges unclear outcomes before they are committed, surfaces cross-functional risks, monitors portfolio health, prepares decision materials, and coaches executives on outcome quality. The facilitator owns process quality; the executives own delivery. Keeping that line clean is what prevents the operating model from decaying into a status meeting owned by no one.
A system like this ultimately depends on how leaders behave inside it. The model asks executives to commit realistically, to finish work before starting new work, to escalate early, to avoid hidden work, to share blockers openly, to protect strategic capacity, to make decisions quickly once the trade-offs are understood, and to revisit assumptions regularly. None of these behaviors is exotic, but each is a behavior the surrounding structure is designed to make easier and the absence of which the measurement loop is designed to expose.
Installing and Sustaining the Model
The model is adopted and evolved rather than installed once. It is a repeatable system that is re-earned each cycle as organizational capability matures and business complexity grows, and it should be introduced in phases rather than in a single reorganization.
A workable adoption path runs in four phases. Establish puts the foundations in place: the three-year strategy, the annual priorities, and the monthly sprint cadence. Standardize raises the quality of what the foundations produce: outcome quality, the metric set, the dashboard, and the ritual set. Optimize adds the governance depth: portfolio governance, capacity management, strategic-debt tracking, and assumption tracking. Scale cascades the model outward: to business units, to department-level operating models, to portfolio integration, and to enterprise dashboards. Each phase presupposes the one before it, and an organization gains little from portfolio optimization before it can reliably run a sprint.
Adoption maps onto a maturity ladder that describes where an organization actually operates, which is often behind where it believes it operates.
| Level | Stage | Characteristics |
|---|---|---|
| 1 | Reactive | Annual planning only, limited accountability, activity reporting |
| 2 | Structured | Executive sprints, quarterly rebase, strategic visibility |
| 3 | Aligned | Strategy traceability, portfolio governance, reliable metrics |
| 4 | Adaptive | Predictive planning, capacity optimization, continuous prioritization |
| 5 | Learning organization | Strategy evolves continuously, decisions are evidence-based, the operating model is continuously improved |
Sustaining the model requires an honest account of how it fails, because the common failure modes are predictable. Executive operating models break when teams commit to too many outcomes, when outcomes are really tasks in disguise, when outcomes carry weak strategic linkage, when no single executive owns an outcome, when capacity is never protected, when the quarterly rebase quietly becomes an annual replan, when reporting metastasizes, when there is no visible decision log, when strategic debt is ignored, and when the organization measures activity instead of outcomes. Every instrument in this paper is a response to one of those failure modes, and a team installing the model should treat the list as a standing set of checks rather than a one-time warning.
The counterpart to the failure modes is a recognizable signature of the model working. Execution is healthy when executives consistently complete the outcomes they commit to, when quarterly priorities rarely surprise the organization, when executive meetings become shorter and more decision-focused, when cross-functional blockers resolve quickly, when strategic drift decreases over time, when annual priorities visibly advance each month, when teams understand why initiatives exist, and when strategy discussions increasingly turn toward future opportunities rather than execution failures. That last shift is the clearest sign of maturity: an executive team that no longer spends its time explaining why the strategy did not happen.
Conclusion
The Strategic Execution Operating Model treats executive execution as a discipline with its own operating system, built to the same standard of rigor that leaders already expect of their delivery teams. Its architecture is a set of five layers tied together by an unbroken traceability chain, its atomic unit is a monthly outcome commitment that one executive owns, its feedback comes from a compact set of signals read together, and its governance and rhythm are kept deliberately lightweight so that leaders operate the system rather than route around it. Assembled as one artifact, it is meant to be installed, measured, and matured rather than admired.
The model does not promise that strategy will stop being hard. It changes where the difficulty lives. Instead of discovering at year-end that a sound strategy quietly failed in execution, an executive team running this model sees follow-through as it happens, corrects on a predictable cadence, and holds itself accountable for strategic movement in the same terms it uses for everyone else. The organizations that install an operating model for their own execution will close the strategy-to-execution gap that the rest continue to rediscover a year at a time.
Sources
The framework described in this paper, including the Strategic Execution Operating Model, its five layers, planning horizons, outcome-commitment discipline, measurement set and target bands, governance registers, escalation framework, maturity ladder, and adoption path, together with the Restricted Agile delivery framework it carries up, is the author’s own original work. The target bands are proposed starting guidance to be tuned against an organization’s own baselines, and the measurement example is illustrative and hypothetical.
Footnotes
-
Donald Sull, Rebecca Homkes, and Charles Sull, “Why Strategy Execution Unravels,” Harvard Business Review, March 2015. Cited only to establish the framing premise that large organizations struggle in execution rather than in strategic alignment; the study reports that two-thirds to three-quarters of large organizations struggle with execution and that the difficulty concentrates in coordination and adaptation. Not used to validate this model’s mechanics, metrics, or bands. ↩
-
Robert S. Kaplan and David P. Norton, The Balanced Scorecard: Translating Strategy into Action (Harvard Business School Press, 1996). Cited only for the framing premise that most organizations fail to translate strategy into execution for lack of a system to communicate and track it; the commonly cited estimate that up to roughly 90 percent of strategies are not executed successfully is widely attributed to this line of work and is presented here as a commonly cited estimate rather than a precise measured constant. ↩