From ambition
to execution.

01 · Choice and work

Make the commitment executable.

Write the decision as an instruction that changes what happens next. Name the intended recipient of the benefit, the change that person should experience and the boundary of the first commitment. Avoid leaving a whole business ambition inside an approval for a single project.

Then connect the decision to the work. What needs to become possible? Which process, information, behavior or service must change? Who will accept that change into everyday operation? A delivered asset and a realized benefit may be separated by training, adoption, revised responsibilities and the retirement of previous work. Keep those steps in view.

NASA's decision-analysis guidance calls for a defined decision, evaluation criteria, alternatives and explicit treatment of assumptions and uncertainty. Its engineering context differs from a business initiative, but the discipline is useful when an attractive proposal has crowded out other credible choices.

Source: NASA - Systems Engineering Handbook, section 6.8: Decision Analysis

Compare at least the preferred commitment with a meaningfully different route. That could be a smaller scope, a different operating approach or waiting until a named dependency is resolved. State the consequence of each. A token alternative included only to make the preferred proposal look reasonable adds little.

Separate what is agreed from what is assumed. If a dependency is uncertain, do not hide it in the schedule. Say whether approval is conditional on resolving it, whether a limited investigation is authorized or whether leadership is deliberately accepting the uncertainty. This gives the delivery team a clear instruction without pretending that all questions are settled.

02 · Capacity

Reconcile capacity before the promise.

A sponsor can authorize an initiative without controlling the resources it depends on. Ask the managers who supply those resources to confirm the allocation in the same conversation. Include specialist time, operational cover, decision-making availability, training and support after the initial release.

Build a short view of the periods in which those demands collide. Use named people or defined skills where that detail changes the decision. Distinguish total effort from the window in which it is needed. A team may have enough hours over a quarter and still lack the right person during a critical transition.

The U.S. Government Accountability Office's Schedule Assessment Guide treats assigning resources to activities as a scheduling best practice. It explains how making resource availability visible can expose a plan that cannot be delivered as scheduled.

Source: U.S. Government Accountability Office - Schedule Assessment Guide: Best Practice 3, Assigning Resources to All Activities

Resolve a collision through a leadership choice: sequence the work, reduce scope, provide credible additional capacity or revise the promise. Record what changes in the displaced initiative and tell its owner. An allocation is incomplete if one plan receives the people while another quietly retains its original deadline.

Allow for ordinary operating demands and uncertainty using evidence from the organization. Do not import an arbitrary utilization target or add a universal percentage as contingency. Revisit the allocation when demand, absence or dependencies materially change. Extra capacity also takes time to recruit, prepare and integrate; adding names to a plan does not immediately create interchangeable capability.

03 · Authority

Give ownership decision rights.

The word owner can conceal several different jobs. One person may coordinate delivery, another control the people, and another accept the result into operation. Name those responsibilities separately and identify the executive who resolves a conflict among them.

For the decisions most likely to interrupt progress, specify who can decide, whose input is necessary and what boundary requires escalation. Useful boundaries include a change to the agreed outcome, a demand on another team's reserved capacity or a transition that the operating owner is not ready to accept. Match them to the initiative.

The UK Government's Project Delivery Functional Standard describes governance in terms that include authority limits, decision-making roles, autonomy and accountability. We use that distinction here to encourage explicit permission to act, rather than relying on an ownership label alone.

Source: UK Government Project Delivery - Government Functional Standard GovS 002: Project Delivery, sections 4.1.3 and 4.4

An escalation should arrive as a decision request. Describe what changed, what the team can still do, the options available and the consequence of waiting. Name the person who must decide and when an answer is needed. If that person is unavailable, a previously agreed alternate or escalation route keeps the request from circulating without resolution.

Use these arrangements to shorten ordinary decisions. Routine choices within the agreed boundary should stay with the people closest to the work. Reserve executive review for changes that alter the commitment or require authority the team does not hold. Record consequential decisions where the team already works, with the reason and the affected commitments.

04 · Evidence

Make review change the decision.

Start a review by naming the decision it should inform. Should leadership expand the release, maintain the current scope, change the approach or stop further commitment? The evidence needed for each question may differ. A status presentation can describe activity without resolving any of them.

Use a small set of measures that connect the work to its intended outcome. Include the conditions that must remain acceptable, such as accuracy, unresolved demand or the burden transferred to another team. Record the source, definition, reporting period and known limitations. A movement in a metric is not useful if the team cannot explain what was counted.

GOV.UK's Service Manual recommends combining performance measures with user research and drawing on multiple data sources. It distinguishes the measurement of a transaction from assessing a wider journey or strategic objective.

Source: GOV.UK Service Manual - Measuring the success of your service

Apply that distinction to the initiative. Review completed outcomes alongside a few unresolved cases and the experience of the people handling them. Examine whether demand, case mix or reporting practices changed. An encouraging before-and-after result can guide the next step without proving that the intervention caused the improvement.

Close the review by updating the commitment, resources and authority together. If evidence is insufficient, name the missing information and decide whether obtaining it is worth the delay. A review may reasonably confirm the existing course. It should still leave a clear reason, an owner for unresolved questions and a trigger for reconsideration.

05 · Worked example

A service promise becomes an operating decision.

A business equipment service company wants customers to receive a reliable appointment after requesting a repair. Its leadership initially describes the initiative as launching a scheduling portal. The operations director and digital lead discover that the portal depends on appointment capacity, current equipment information and a clear route for requests that cannot be booked automatically.

During the fictional trial, staff observe that requests for specialist equipment are reaching the wrong service category. The team has evidence of a classification problem, but has not established its prevalence. It does not yet have grounds to declare the whole approach successful or unsuccessful.

The digital lead can clarify the selection interface within the existing authority. Changing the service categories themselves requires the operating owner's decision. The sponsor keeps the trial bounded while the team checks how often the issue occurs and what information would prevent it. Expansion remains a separate decision.

The useful result of the framework is a more specific conversation. Leadership can see the outstanding uncertainty, the action already authorized and the additional evidence it needs. No completion percentage or general reassurance can substitute for those distinctions. The next review can revise the commitment without reopening every settled choice.