2023 operational guide — Establish decision governance in four weeks

Four weeks to make a decision executable

This guide starts with a concrete problem: a proposal circulates, advice accumulates and the team still does not know which option to implement. The four-week sequence makes one decision family manageable from preparation to checking its effect. The deliverable is a tested mandate, a completed decision brief and a route people understand. It is not a promise that an entire organisation can change in four weeks.

This is a retrospective on 2023 written in 2026. Every case, threshold, budget and timing is a fictional teaching example, not a CYTIZEN engagement. The forty-five-minute format concerns a prepared choice. It cannot substitute for discovering a complex problem during the meeting. A question lacking authority or minimum evidence leaves this format and receives a specific preparation action.

Week one: frame the question and check authority

In a fictional service business, team leads propose moving appointments into different time slots. Sales anticipates better availability; operations anticipates additional staffing costs. Define the question as authorising or refusing a trial involving one team and two slots. Avoid broad wording such as “improve the organisation”. A bounded question identifies the affected people, the resources involved and the effect that can be checked.

The sponsor names someone able to commit resources and accept the customer consequence. Specify scope, spending limit, non-negotiable constraints and reversal conditions. The preparer interviews staff about real exceptions. The facilitator checks existing commitments. If authority is split between two directors, name an arbiter before the session. Shared chairing without a tie-breaking rule simply creates another unresolved dependency.

A completed minimum brief

These numbers demonstrate the brief rather than recommend universal limits. Record data sources and dates. The expected benefit remains a hypothesis until observed. Including a maintain option makes the cost of doing nothing explicit; otherwise, the meeting compares proposals without comparing their usefulness to the current situation.

Week two: prepare disagreement before the session

The preparer gathers minimum evidence and consults essential contributors. Ask what would change their view: a confirmed volume, omitted workload, authorisation or technical constraint. Separate established facts, assumptions and preferences. Document disagreement and its possible consequence instead of editing it out to produce an apparently unanimous brief. Unresolved issues hidden during preparation reappear during execution when they are harder to address.

Send a stable version two days before the meeting. Contributors receive a clear question and a deadline for identifying blocking gaps. Check four entry conditions: comparable options, authorised decision maker, dated evidence, and explicit boundaries and reversibility. If one is missing, replace the session with a fifteen-minute preparation check or reschedule with an owner and deadline. Eight participants should not spend forty-five minutes collectively discovering that the same information is absent.

Assign roles deliberately

The decision maker concludes. The preparer explains options. The business describes operating consequences. Experts examine constraints within their competence. The facilitator maintains pace, records wording and checks understanding. Some roles can be combined where necessary examination remains credible, but identify the combination. People who only need information receive the conclusion. A small meeting without authority is no more effective than a crowded one.

Week three: use forty-five minutes to conclude

1. Minutes 0–5: confirm question, authority, necessary participants and mandate boundaries.
2. Minutes 5–15: present options, decisive evidence and untested assumptions, including maintaining the current situation.
3. Minutes 15–25: examine objections and displaced consequences; classify each as risk, condition, missing evidence or advice.
4. Minutes 25–35: authorise, refuse or defer for named evidence. State the accepted consequence and reasoning.
5. Minutes 35–45: read back the conclusion, name the executor, date the action and specify verification and recipients.

The clock protects time to conclude but cannot require an unsafe choice. A new constraint invalidating the options justifies stopping. Name the missing evidence, its owner and the next decision opportunity. “Review later” is insufficient. In the example, unconfirmed staffing leads to deferral until coverage is established, rather than a show of hands committing absent teams.

Choose the decision method in advance. A managerial arbitration ends with the accountable manager's choice after consultation. Consent can suit people with comparable authority if objections describe concrete risks and a recourse rule exists. Voting can rank preferences but cannot transfer statutory responsibility. The guide therefore requires an announced method and a way to resolve persistent disagreement rather than prescribing one universal method.

Week four: verify execution and improve the route

The team lead confirms the schedule changed inside the approved boundary. The customer lead checks existing commitments. Operations distinguishes ordinary absence from trial-related incidents. A circulated record does not close the action. Close it when the expected change occurs or an obstacle receives an explicit new decision. Keep conclusion and execution as separate states in the register.

Use three measures initially. Complete decisions divided by all conclusions gives the completeness rate; completeness requires action, owner, date and verification. Implementation lead time equals the date of the first verified effect minus the decision date. Track preparation-related deferrals separately from genuinely new information. In a fictional sample of eight files, two deferrals for missing authority require better participant selection, not longer meetings.

Stop the trial at the agreed customer-impact limit, when workload evidence becomes unreliable or when the mandate is exceeded. Correct the process if conclusions are repeatedly misunderstood. Expand it only when staff can prepare and implement the brief without constant dependence on its original facilitator. Reducing meetings while concentrating invisible preparation work on one person does not demonstrate sustainable improvement.

Adapt the session to its consequences

In healthcare, changed slots can affect qualified staffing and continuity of care; competent expertise becomes an entry condition. In manufacturing, respect safety, maintenance and shift constraints; reversal may follow a production cycle rather than a day. Public administrations must preserve service duties and access for people unable to use digital channels.

A delegated local decision can use the same brief asynchronously. Exceptional or irreversible commitments may need separate analysis and additional assurance. Match preparation, participants and method to the consequences. The four weeks establish a usable discipline; they do not replace legal authority or applicable contractual procedures.

Sources and methodological scope

Official sources checked in October 2026. Meeting durations, roles and thresholds are teaching proposals specific to this guide.

• GOV.UK, Governance principles for agile service delivery, 2016: available in 2023, covering explicit authority and decisions at the appropriate level.
• GOV.UK, Measuring the success of your service, first published in 2018: an outcome-measurement reference consulted in 2026. The meeting format above is not attributed to this source.