A priority becomes deliverable when the organisations involved understand what they must contribute and how unresolved choices will be settled.
A public commitment may be clear in ambition and still leave substantial implementation choices open. Improving access, simplifying a service or coordinating support across agencies requires more than assigning a programme name and reporting date.
The people responsible for delivery need a workable mandate: the outcome sought, the boundaries of their authority, the contributions expected from others and the decisions that remain with senior leaders. Without that clarity, a programme can accumulate activity while leaving the citizen's experience largely unchanged.
The OECD's public governance framework connects effective implementation with coordination, delivery capability and monitoring. The following approach applies that perspective to the practical work of converting a priority into a set of deliverable commitments. OECD: Toward sound policy implementation.
Translate the mandate into an observable outcome
Start by asking what should be different for the people or organisations using the service. Avoid defining success solely as a new policy, platform, office or committee. These may be necessary outputs, but they do not explain the intended public benefit.
For illustration, a programme intended to simplify an application process could distinguish between publishing a common form and reducing the number of times applicants must provide the same information. The first is a deliverable. The second describes an experience that can be examined.
Document the people affected, the present difficulty, the intended improvement and the limits of the programme. Be explicit about exclusions. A delivery team should not have to discover through escalation that stakeholders expect different populations, services or locations to be included.
Separate settled choices from open questions
A mandate can contain firm commitments alongside matters still requiring evidence or authority. Treating both as settled makes a plan appear more certain than it is.
Create a short decision record that distinguishes:
- What has been approved and by whom
- What remains a working assumption
- What requires advice or consultation
- What must return for a formal decision
- When an unresolved choice begins to affect delivery
This is particularly useful when policy, funding and operational design move on different timetables. A team may be able to investigate an option without being authorised to implement it. The plan should make that distinction visible.
Map the institutional commitments
Cross-agency work requires more precision than a list of stakeholders. For each organisation, identify the contribution required, the accountable executive and the authority needed to make that contribution.
A commitment might involve providing a service, assigning staff, changing an operational process, supplying approved information or confirming an implementation dependency. Record how the contribution will be accepted and what happens if it is late or cannot be provided.
Check each commitment against the organisation's actual remit. A programme sponsor should not assume that another body's responsibilities or constraints can be changed through project governance alone. Matters outside delegated authority need a clear route to the appropriate decision-maker.
Plan around capacity and dependencies
A deadline is useful only when the work required to meet it is understood. Ask delivery organisations to identify the operational preparation, specialist input, approvals and external dependencies on which the plan relies.
Make competing demands visible. The same staff may be expected to maintain current services and implement several reforms. An implementation plan that omits that conflict passes a resource decision down to people who may lack authority to make it.
Sequence work around readiness. Some activities can proceed while others wait for a decision; some would create expensive rework if started early. Explain those choices to sponsors so that apparent inactivity is not confused with avoidable delay, and visible activity is not mistaken for progress.
Give the centre and delivery organisations distinct roles
A central programme team can maintain the integrated plan, expose dependencies and bring unresolved decisions to the right authority. Delivery organisations remain responsible for the work within their remit.
Agree the minimum reporting needed to support that relationship. A useful review asks what has changed, which commitment is at risk, what evidence supports the assessment and what decision or assistance is required.
Avoid asking multiple bodies to recreate the same information in different formats. Where reporting needs differ, identify the shared underlying facts and adapt the executive interpretation. This preserves local accountability while creating a coherent view of the overall programme.
Make room for service-user and frontline evidence
Implementation should test whether the proposed change works for the people who use and deliver the service. Include those perspectives early enough to affect the design, rather than only to validate a finished proposal.
Use a mix of service observations, structured feedback and operational data. Consider who might be missing from the evidence, including people who do not complete the process or cannot access the intended channel.
For the illustrative application programme, an improved online completion rate would not by itself establish that the service had become easier for everyone. Leaders would also need to understand incomplete journeys, assisted access and the work transferred to staff or applicants.
Establish an honest review and adaptation cycle
Agree how the programme will distinguish delivery progress from evidence of benefit. Reporting can show whether an agreed action happened; evaluating the outcome requires a separate question about what changed and why.
Specify when assumptions will be reviewed, who can approve adjustments and which changes require renewed sponsorship. Keep a record of the reason for each material revision. This helps a new leader or team understand the current direction without reconstructing the programme from old presentations.
When performance falls short, first identify the nature of the problem. The policy design, implementation capacity, institutional agreement or original diagnosis may need attention. Escalating pressure without clarifying the constraint can produce more reporting without a better response.
A practical mobilisation brief
Before moving into detailed scheduling, bring the essentials together in a concise brief:
- The public outcome and the people it should serve
- The scope, boundaries and decisions already authorised
- Named institutional contributions and their dependencies
- The capacity and readiness needed for implementation
- The evidence, review points and escalation arrangements
Use the brief to expose disagreement, not simply to record consensus. A programme is better prepared when competing interpretations are resolved before they become delivery failures.
Executive questions
- Can every participating organisation describe its commitment in the same terms?
- Which assumption could change the scope or timing most significantly?
- What are delivery teams being asked to do without the necessary authority or capacity?
- How will we know whether the service has improved for the people it is intended to support?
JP Associates supports public-sector leaders in clarifying mandates, aligning institutional responsibilities and building a practical management rhythm for complex change.