Delivery
Turn project updates into decisions.
A useful status update names the decision, owner, deadline and consequence of waiting.
Consider a hypothetical project update: the status is amber, twelve actions are in progress and the meeting lasts an hour. A week later, the same unresolved choice appears again. Activity has been reported, but the decision needed to move the work forward is still hidden inside the detail.
Separate progress from the decision queue
A progress update should still explain what has changed, what is complete and what is at risk. Give decisions their own short section so they cannot be mistaken for another action or discussion point.
Write each decision as a question that one accountable person can answer. “Discuss integration” is an activity. “Do we use the existing integration or fund the proposed replacement?” describes a choice. If the question is not ready to answer, state which evidence is missing and who will provide it.
Give the decision enough structure
The decision owner should not have to reconstruct the issue from a long document or a crowded meeting. Prepare a compact decision note with the information needed to make a judgement, while linking to deeper material for anyone who needs it.
- The decision required, in one sentence.
- The realistic options, including doing nothing or waiting.
- A recommendation and the reasons for it.
- The evidence available and material uncertainty that remains.
- The decision owner, latest useful date and consequence of delay.
Discuss choices before general updates
Put time-sensitive decisions near the start of the meeting, after any genuinely urgent operational issue. State the recommendation, invite challenge and record the outcome. A decision can be approved, rejected, changed or deferred for specific evidence. “We talked about it” is not a usable status.
Where several people contribute advice, keep the final owner clear. Consensus can be valuable, but an unclear decision path often sends the work back into another round of circulation. If a decision changes later, keep the earlier record and note what new evidence or constraint led to the change.
Close the loop into delivery
Translate the decision into the next action, owner and review point. Update the plan, supplier brief or acceptance criteria that the choice affects. Tell the people doing the work what has changed; a decision that stays in meeting notes has not yet altered delivery.
Review the decision queue regularly. Remove completed items, escalate those approaching their useful date and challenge repeated deferrals. The aim is not to create a large governance log. It is to make the small number of choices currently constraining delivery visible and actionable.
Rethink’s ongoing support can provide regular senior advice, delivery challenge and follow-through under an agreed scope. A practical starting point is to rewrite one recurring project issue as the decision it actually needs.