The Executive Sprint

Ask a leadership team what it is working on and the answer usually arrives as a list. There are the annual goals, the objectives and key results, the themes from the last offsite, and the handful of big rocks each executive has agreed to move this year. The list is real, and the people holding it are genuinely busy. What the list does not contain is a unit an operating model can actually run. A goal is a direction, a theme is a category, and a big rock is an intention with no defined edge. None of them says what a specific leader will make true by a specific date, which is the smallest thing a model needs before it can sequence work, check on it, or tell whether it landed.

The first piece in this series argued that strategy fails at execution rather than at conception, and that the executive team needs its own operating model rather than another planning cycle. The second built the frame: a set of nested planning horizons that carry a three-year strategy down through annual priorities and a quarterly rebase to the monthly sprint, where individual executives commit to the outcomes they will personally advance. That piece named the monthly sprint as the horizon where commitments live and then deliberately left the commitment itself unspecified. This piece specifies it. 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. Everything else in the model, the cadence above it and the measurement around it, exists to protect and read those commitments.

The unit is an outcome a leader owns

A monthly outcome commitment is a discrete move on the plan that one executive owns and will advance to a defined state within the sprint. The useful examples are concrete: a decision that has to be made, a capability that has to be funded and unlocked, a dependency that only a leader can clear. Each executive takes one to three of these in a month, and each one traces up to a pillar of the strategy so that the reason it is worth a leader’s attention is explicit rather than assumed. The number is deliberately small. Holding three real commitments and following them through is harder and more valuable than listing ten priorities and hoping the important ones survive contact with the calendar.

Choosing an outcome as the unit is what makes the rest of the model coherent. Because a commitment names a state a person will bring about, it can be sequenced against other commitments, checked partway through, tracked to completion, and rolled forward honestly when it does not finish. A model built on tasks or status updates has none of this. Tasks describe activity, and activity alone does not move the plan. A leader can fill every hour of the month, clear a full inbox, and attend every review on the calendar while advancing no committed outcome at all. The commitment discipline exists to catch exactly that gap. It forces a single question at the start of the month, which is what will be true at the end of it that is not true now, and it answers that question with a specific, owned result rather than a promise of effort.

The value of the unit depends entirely on the quality of what gets committed, so the model applies a test at the moment of commitment. Most commitments start as something broader, an initiative or a standing priority, and become sprint-ready only by being narrowed to the single outcome a leader will finish this month. A valid executive outcome has to satisfy four conditions, and an outcome that fails any of them is revised, delegated, or deferred rather than carried into the sprint.

An outcome earns its place only if it is genuinely strategic, tied to a pillar, an annual priority, or a defined capability objective, so that advancing it moves the plan rather than merely clearing the desk. It also has to be executive-level, turning on a lever only a leader can pull: a decision made, alignment created, funding approved, ownership resolved, a blocker removed. Task execution that a capable team could carry does not belong on an executive’s commitment list, and putting it there is one of the quieter ways a leadership team fills its month with motion while the work only a leader can do waits.

The other two conditions govern the shape of the outcome rather than its substance. It has to be time-bound, scoped to be achievable within the sprint under a single executive owner even when many people contribute, which keeps the commitment from becoming a standing aspiration that reappears every month. And it has to be defined by a concrete done state, a finalized decision, a launched pilot, a completed framework, an unblocked initiative, something a person can look at and agree is finished.

That last condition, the concrete done state, is where most weak outcomes are exposed, and the language an executive reaches for usually gives them away. Commitments that begin with work on, support, explore, or review describe activity and rarely resolve to anything anyone can point at as finished. The ones that hold begin with a verb of completed action, approve, finalize, decide, select, publish, and then name the thing that will exist because of it. A reliable shape is a verb of completed action, the deliverable it produces, the state that marks it done, and the pillar it serves, so that improve reporting becomes approve the executive dashboard and publish the first monthly report against it. The check that settles a borderline case is whether someone outside the owning executive’s function could look at the result at the end of the month and agree it is done. If they could not, the outcome is not yet defined well enough to commit.

Applied honestly, the test does most of the work of the model before the sprint even begins. A vague priority meets none of the four conditions, and forcing it through them either sharpens it into a real commitment or exposes that it was never executive work in the first place. This is where a leadership team decides what it is actually going to advance this month, and it is the point at which the difference between running a strategy and describing one becomes visible.

The discipline is carried up from delivery

The idea that starting a period of work is a genuine commitment did not originate at the executive level. It comes from Restricted Agile, a delivery framework I built for professional-services teams working under statements of work, timelines, and budgets, where clients expect flexibility and predictability from the same engagement. Restricted Agile holds two truths together. Starting a sprint is a commitment to deliver the planned work when conditions hold steady, and change is inevitable and has to be managed deliberately and transparently rather than absorbed as informal drift. In practice that means commitment is enforced inside the sprint while change is handled outside it, through a defined mechanism, so that the team runs long enough against a plan to actually finish it and new information is routed into the next planning decision instead of quietly dissolving the current one.

The executive operating model carries that same rule up one level. Once a leader commits an outcome for the month, the commitment holds through the sprint unless new information is significant enough to force a transparent rebase. This is the executive analogue of the delivery-team change mechanism, and it connects directly to the quarterly rebase the previous piece established. Change is allowed, but it is routed to the rebase rather than absorbed silently inside the sprint. Within the sprint, the commitment is protected so the outcome has a chance to land. When conditions genuinely shift, the team re-sequences openly at the rebase rather than letting each executive quietly drop a commitment when the week gets loud. What the delivery organization does for work under a statement of work, the executive team does for the moves the strategy is waiting on, and holding itself to that standard is precisely the discipline it already expects of everyone below it.

A commitment needs a container, and the monthly executive sprint is a deliberately simple one: a four-week cycle with a defined start, a protected middle, and an honest close. Week one is planning and commitment, where each executive sets the one to three outcomes they will own and runs them through the four conditions. Weeks two and three are execution, carried by a short weekly check-in that surfaces blockers early enough to act on them rather than discovering them at the end. Week four is review and retrospective, where the team looks at what was committed against what was delivered and carries the lessons into the next sprint.

The cadence is intentionally light, and that is a design requirement rather than a convenience. The moment an executive operating model starts to feel like project management, leaders route around it, and the discipline decays into another status meeting. The sprint earns its place by doing two things and nothing more: it gives every commitment a fixed rhythm so follow-through is expected rather than optional, and it creates a regular, low-ceremony moment where drift becomes visible while there is still a sprint left to correct it. Keeping it that lean is a subject in its own right, and it is one the later pieces in this series take up directly.

Built this way, the executive team finally has an atomic unit it can operate. A strategy expressed as pillars now reaches down to specific, owned outcomes that are committed on a cadence, tested for whether they are worth an executive’s time, and protected long enough to be delivered. What remains is to know whether the commitments are actually landing, sprint over sprint, and whether the pattern of follow-through is improving or quietly eroding. Commitment accuracy and roll-forward are the beginning of that answer, but reading them well means measuring the executive team’s own execution health rather than trusting a year-end impression of how the work went. That measurement loop is what the next piece builds.