Delivering What Works: A Model for Competent Government
Executive Summary
Government succeeds when it delivers. Yet in Britain, delivery has too often become the exception rather than the rule: policies are announced with ambition, but fade without follow-through. Delivering What Works sets out Renewal’s model for restoring competence to the heart of government.
Drawing on lessons from past reforms, from the Prime Minister’s Delivery Unit to the fragmentation that followed, the paper defines a practical alternative: fewer priorities, clearer ownership, disciplined planning, and transparent performance.
At its centre is the proposed Office for Delivery and Performance (ODP): a small, independent body reporting to Parliament, responsible for tracking progress against priority outcomes, supporting departments to manage delivery risk, and surfacing problems early rather than after failure.
The paper sets out how this national delivery backbone is reinforced by a clear departmental operating model: minister-chaired Delivery Boards, time-bounded delivery plans, hard stage-gates, and public dashboards that make performance visible and comparable. Delivery is treated as a professional discipline, with explicit accountability, continuity of leadership, and clear escalation when programmes fall off track.
Finally, the paper outlines a credible implementation roadmap, showing how this framework can be introduced within a single Parliament by consolidating existing functions, piloting in priority areas, and scaling what works.
Renewal’s aim is not to promise more, but to ensure that what government commits to is delivered consistently, transparently, and with clear accountability. Competence is treated as a basic requirement of government.
Contents
1. Introduction - The Problem of Delivery and The Case for Competence 3
3. The Renewal Framework for Competent Government 9
4. The Office for Delivery and Performance (ODP) 11
5. Departments That Deliver 15
6. Local Delivery and Shared Accountability 18
7. Technology, Data, and Transparency 22
8. From Announcements to Outcomes 26
10. Conclusion - The Competence Revolution 30
1. Introduction - The Problem of Delivery and The Case for Competence
1.1 Why Delivery Has Failed
Successive governments have promised transformation across public services - digital government, levelling up, decarbonisation, and productivity reform - but too few of those ambitions have translated into visible results. The underlying problem isn’t a lack of ideas or commitment; it’s that the system of government itself has become structurally bad at delivery.
Departments are organised around functions and announcements, not outcomes. Ministers cycle through briefs faster than projects can mature (average ministerial tenure in major departments is under 18 months). Each reshuffle brings new slogans and priorities, but not the operational continuity needed for reform to stick.
Accountability is diffuse: Permanent Secretaries are accountable for “stewardship,” ministers for “policy,” and agencies for “delivery” - yet no one owns the result. This fragmentation is compounded by constant reorganisations: machinery of government changes, new taskforces, and one-off delivery units that seldom survive a Parliament.
See for example, Institute for Government, Whitehall Monitor, on ministerial turnover and leadership stability across departments; and National Audit Office reports on cross-government programmes and accountability.
The result is that government repeatedly over-promises and under-delivers. Voters notice the gap, and trust erodes. This erosion risks becoming a structural feature of British public life.
1.2 What Renewal Means by Competence
Competence matters because it shapes whether people trust government to do what it says it will do. Renewal defines competence as the ability to set clear objectives, deliver them efficiently, learn from experience, and sustain outcomes over time.
In practice, this depends on four core conditions being present across the system:
Clarity – Fewer, better-defined priorities, understood by every level of the system.
Continuity – Stable leadership and institutional memory, so reform survives beyond one minister or spending round.
Execution – Capability to translate plans into operations: the right skills, teams, and tools.
Feedback – Mechanisms to measure, learn, and adapt (a concept notably absent in current UK policymaking).
Failure to deliver is often framed as a managerial problem. In reality, it is also a question of fairness and legitimacy. When governments announce policies that never materialise, from housing to healthcare to local transport, people lose not only services, but confidence that effort and contribution will be rewarded.
That loss of trust has tangible consequences: declining civic participation, rising cynicism, and growing disengagement from the state. In this sense, competence is a basic obligation of government to the people it serves.
In practice, competence means that delivery rather than announcement of intent becomes the test of success.
1.3 The Case for Change
The UK has a world-class civil service and deep institutional expertise, but both are constrained by an outdated operating model. The political system rewards announcements, not outcomes; Whitehall structures reinforce silos; and performance management is weak or reactive.
If Britain is to rebuild trust and effectiveness, the focus must shift from policy-making as persuasion to policy-making as performance. Delivery must be treated as a discipline - measurable, learnable, and accountable.
This is the foundation of Renewal’s work: to define what competent government looks like in practice, identify where the current system falls short, and propose a model that can deliver measurable improvement across departments and services.
2. Lessons from the Past
Each generation has rediscovered the need for competence, built machinery to deliver it, and then watched it decay once political attention moved on. The lesson is not that reform fails - it’s that good delivery systems need constant maintenance.
2.1 The Thatcher Era (1979 – 1990): Efficiency as Control
When Margaret Thatcher entered office, the British state was large, centralised, and financially strained. Her instinct was not to make government more competent but to make it smaller and cheaper. The creation of the Efficiency Unit under Sir Derek Rayner (1979) was the first modern attempt to bring private-sector disciplines into Whitehall - cost reviews, output targets, management by results.
It introduced a culture of measurement but also of control from the centre. Departments were told to do “more with less,” and success was defined by fiscal savings rather than by improved services. Thatcher proved that standards and data could change behaviour, but also that efficiency alone is not the same as delivery.
2.2 The Major Years (1990 – 1997): Citizen as Customer
John Major inherited a state fatigued by reform and sought to make government more user-focused. His Citizen’s Charter (1991) reframed public services around the rights of citizens rather than the authority of departments.
It established clear service standards - punctual trains, waiting-time targets, plain-language documents - and introduced public scorecards for agencies. In today’s language, Major’s reforms were an early version of delivery transparency.
However, the initiative lacked enforcement power and was viewed as bureaucratic window-dressing. Without data systems or accountability mechanisms, most Charters faded quietly. Still, Major’s era left one important legacy: it treated the public as users of a service, not merely subjects of administration - a mindset Renewal aims to recover.
2.3 The Blair Decade (1997 – 2007): Delivery Professionalised
Tony Blair’s government turned the rhetoric of delivery into machinery. The Prime Minister’s Delivery Unit (PMDU), created in 2001 under Sir Michael Barber, was a breakthrough: a small, analytical team reporting directly to No. 10, charged with tracking and unblocking progress on the government’s top priorities - health, education, crime, and transport.
The PMDU pioneered:
Regular stocktakes between the PM and departments;
Quantified Public Service Agreements (PSAs);
The use of data dashboards and delivery chains.
For the first time, there was a system linking policy intent to delivery outcomes. Performance improved in measurable areas - NHS waiting times fell, school results rose - though at the cost of some target gaming and bureaucratic overload.
The Blair years proved delivery can be managed - but only when the centre has authority, good data, and clarity of purpose. The weakness was sustainability: once political focus shifted, the system hollowed out.
2.4 Coalition and Cameron (2010 – 2016): Decentralisation and Drift
The 2010 Coalition inherited a state heavy on targets and light on flexibility. David Cameron abolished the PMDU and replaced it with the Implementation Unit in the Cabinet Office, alongside the Efficiency and Reform Group (ERG) under Francis Maude.
The ERG was associated with substantial fiscal savings over the course of the Parliament - by consolidating procurement, property, and IT contracts. But the delivery culture fractured: instead of one system linking priorities to outcomes, Whitehall had a patchwork of spreadsheets and dashboards.
Cameron’s political philosophy of “small government, big society” left reform energy with local bodies and charities, but without the data or capacity to sustain it. Delivery once again became fragmented: strong financial control, weak follow-through.
2.5 May, Johnson and Sunak (2016 – 2024): Instability and Overload
Theresa May attempted to restore central coordination with a Delivery Unit 2.0, but Brexit consumed all bandwidth. The civil service reverted to crisis management.
Under Boris Johnson, Levelling Up briefly acted as a unifying narrative, yet machinery lagged behind rhetoric. A new No. 10 Delivery Unit was announced in 2021, but never gained traction.
Rishi Sunak’s government created an online Performance Dashboard with departmental metrics - a nod to transparency but limited by poor data quality and no real accountability.
Across these years, the state oscillated between over-centralisation and drift. The talent was there, the intent often genuine, but the system lacked consistency - the very trait competence depends on.
2.6 What These Cycles Show
Across successive attempts at reform, a consistent pattern emerges. Governments repeatedly recognise the need for focus, feedback, and follow-through in delivery. They build new mechanisms to provide it, see early gains, and then allow those systems to weaken as attention shifts elsewhere. The problem is not a lack of insight or innovation, but an inability to sustain delivery capability over time.
The lesson is therefore not that reform is futile, or that earlier models were misguided. On the contrary, Britain has built the tools of competent government before. What has been missing is permanence: institutions that endure beyond political cycles, adapt to changing priorities, and remain visible to the public they serve.
The next phase of reform must focus less on novelty and more on durability: embedding delivery capability in transparent, citizen-facing institutions rather than relying on temporary units or individual leadership. That is the purpose of the proposed Office for Delivery and Performance (ODP).
3. The Renewal Framework for Competent Government
3.1 Clarity of Purpose
Government today is responsible for an expanding range of objectives, often without clear prioritisation or clarity. Every department is loaded with objectives - from strategy papers to manifesto pledges - yet few are prioritised or costed against delivery capacity. Renewal’s first principle is that clarity must precede action.
This means:
Setting fewer, measurable priorities, each with explicit ownership.
Publishing clear outcomes frameworks, not just policy inputs or spend lines.
Aligning departmental structures and budgets with those priorities.
More recent efforts to introduce mission-led approaches to government have reflected a recognition of these challenges, but have struggled in practice without stable metrics or clear lines of accountability.
Clarity matters because ambiguity weakens accountability. Without clear priorities, delivery becomes inconsistent and difficult to sustain.
3.2 Capability and Data
Competence depends on people, systems, and information - the machinery of delivery.
Over the past two decades, capability reform has oscillated between strong central control (as under the PMDU) and lighter-touch, department-led approaches (as under the Implementation Unit). Neither model succeeded in building a self-sustaining delivery profession within government.
Renewal’s framework calls for:
Core delivery skills, including project design, implementation planning, and data interpretation, treated as a coherent profession across government, with clear standards, progression, and accreditation linked to outcomes.
Performance data is collected and published in standardised form, allowing Parliament and the public to track results over time.
Institutional continuity is built into delivery roles and processes, ensuring that delivery knowledge is embedded in systems rather than depending on individual leaders.
Taken together, these elements form a basic competence backbone: the minimum infrastructure of data, skills, and feedback required for policy to be delivered effectively.
3.3 Consistency and Continuity
Reform fatigue has become a feature of British government. Each new Prime Minister reshapes departments, relaunches priorities, and rewrites delivery plans. The result is constant motion, little progress.
Renewal’s framework proposes stability by design, recognising that reform is sometimes necessary, but should be deliberate, infrequent, and justified by function rather than politics:
A presumption against frequent machinery of government changes, with restructuring undertaken only where there is a clear functional case.
Five-year rolling delivery plans, published and reviewed annually.
Public reporting cycles tied to outcomes, not election announcements.
Consistency builds trust. Citizens care less about ideology than reliability: that schools open, roads are fixed, promises are kept. Competence grows when the machinery of delivery survives beyond one political cycle.
3.4 Renewal’s Three Pillars - Summary Table
Pillar
What It Means
Why It Matters
Application
Clarity of Purpose
Fewer, better-defined priorities with explicit ownership and measurable outcomes.
Prevents overpromising and restores accountability.
Outcome frameworks, public delivery plans.
Capability and Data
Skilled delivery profession and robust performance systems.
Turns plans into measurable results and learning.
ODP analytical core, open dashboards.
Consistency and Continuity
Stable machinery, long-term delivery cycles, fewer reorganisations.
Preserves institutional memory and public trust.
5-year delivery plans, minimal structural churn.
Together these three pillars form the Renewal Framework for Competent Government - the operating philosophy underpinning the proposed Office for Delivery and Performance (ODP).
4. The Office for Delivery and Performance (ODP)
4.1 Purpose and Rationale
Delivery is the missing link in British government. For decades, the system has been strong on analysis and announcement but weak on follow-through. Each new administration has promised to “get things done,” yet too often delivery relies on short-term taskforces or ad-hoc reviews rather than sustained, institutional capacity.
The Office for Delivery and Performance (ODP) is designed to fix that gap. It would serve as the permanent backbone of a new delivery model - a small, expert body that tracks progress across government, supports departments in achieving results, and ensures that early warning replaces late-stage crisis management.
Unlike previous delivery bodies, the proposed Office for Delivery and Performance is not designed as a mechanism of political control or project assurance. Past models have tended to fall into one of two categories: prime ministerial delivery units, such as the PMDU and more recent mission-led arrangements, which concentrate authority at the centre to drive a limited set of priorities; and infrastructure-focused bodies like IPA/NISTA, which provide assurance and professional standards for major projects.
Both play an important role, but neither is designed to build enduring delivery capability across the whole of government. The ODP is intended to fill that gap, focusing on outcomes rather than projects, capability rather than control, and permanence rather than political cycle. Its purpose is not to direct departments, but to strengthen the systems through which delivery is planned, measured, and sustained.
4.2 Core Functions
The ODP would have three core functions, each designed to address a persistent weakness in how delivery is currently managed across government.
a. Track and publish performance dataThe ODP would maintain a single, transparent set of cross-government delivery dashboards - measuring progress against clear, outcome-based targets agreed with departments. Rather than relying on self-reported departmental updates, data would be independently verified and presented in a public, comprehensible format. Every year, the ODP would publish a delivery report to Parliament, showing where promises are being kept, delayed, or off track.
b. Support delivery planning and risk managementDepartments would be able to access early-stage delivery support from ODP specialists in programme design, risk analysis, and implementation planning. The aim is prevention, not correction: identifying delivery risks before they become crises, and building practical capability inside departments. The ODP would maintain a small “Delivery Support Pool” - secondees and analysts who can embed temporarily in high-risk programmes to stabilise delivery and rebuild capability.
c. Enable early warning and accountabilityThe ODP would act as the system’s early warning mechanism - identifying emerging delivery failures and escalating them before public trust is lost. It would brief ministers and select committees quarterly, using objective data rather than narrative reporting. This approach replaces the reactive post-mortems of traditional performance reviews with real-time, preventive oversight.
Taken together, these functions are intended to strengthen delivery capability without duplicating policy, finance, or project assurance roles elsewhere in government.
4.3 Operating Model
The ODP would be established outside the Cabinet Office, with a formal duty to report to Parliament. Ministerial accountability would sit with a designated senior minister, such as the Chancellor of the Duchy of Lancaster, while operational independence would be protected in statute.
The ODP would not replace existing analytical or assurance functions within departments. Instead, it would align and standardise delivery-related data, methodology, and performance assessment currently fragmented across the Treasury, IPA/NISTA, and Cabinet Office, providing a consistent, system-wide view of progress and risk.
Operationally, the ODP’s work would centre on three tools:
A Public Delivery Dashboard, accessible online, showing headline outcomes in major policy areas (health, education, infrastructure, safety, economy, etc.).
A Delivery Framework, standardising how departments plan, assess, and report major projects.
A Delivery Academy, offering training and professional standards for delivery roles within the civil service.
The ODP’s authority would rest on transparency rather than hierarchy. Departments would remain accountable for results, while the ODP would ensure that performance is consistently defined, measured, and visible to ministers, Parliament, and the public.
The delivery model described here assumes interoperable data systems and shared reporting standards across government, but does not prescribe specific technologies, platforms, or procurement models.
4.4 Independence and Oversight
To maintain credibility, the ODP must be independent of both ministers and departmental politics. It would be established through statute, with a small oversight board appointed by Parliament - including representation from the National Audit Office, Civil Service Commission, and external delivery experts. The head of the ODP would be appointed on a fixed, non-renewable five-year term.
Its reports and data would be published directly to Parliament, not filtered through ministerial press releases. That transparency is the ODP’s primary safeguard - the surest way to keep it lean, objective, and non-partisan.
4.5 Resourcing and Scale
The ODP should be small, agile, and analytical, not another bureaucracy. Its steady-state headcount would be modest (no more than around 150 staff), largely drawn from redeployed roles within the Treasury, Cabinet Office, and existing project and performance functions such as IPA/NISTA.
Funding would primarily come from consolidating existing performance, assurance, and reporting budgets. While limited transitional investment would be required to establish common systems and data infrastructure, the ODP would add capability rather than cost over time.
Technology and data-sharing agreements would underpin efficiency, replacing multiple disconnected reporting systems with a single, secure cross-government delivery data pipeline over time.
4.6 Expected Impact
If implemented, the ODP would make delivery a visible and systematic discipline, comparable to fiscal management or legal compliance. Departments would gain consistent tools for planning and monitoring delivery; ministers would gain clearer sight of progress and risk; and Parliament and the public would be better able to see where commitments are being met, delayed, or falling short.
Many past delivery failures, including in areas such as infrastructure programmes and large-scale digital change, did not arise from a lack of intent, but from weak feedback, limited visibility, and delayed intervention. Problems were often identified too late, after costs had escalated or confidence had already been lost. By standardising how delivery is measured and reported, the ODP would help close this gap, allowing emerging risks to be surfaced earlier and addressed more effectively.
The impact of the ODP should therefore be understood in system-wide terms. It would not replace ministerial responsibility or departmental ownership, but strengthen the conditions under which delivery can succeed. Over time, this would support more reliable implementation, greater institutional learning, and increased confidence that government commitments are backed by the capability to deliver them.
4.7 Safeguards and Culture
For the ODP to be effective, it must remain lean, neutral, and focused on its core purpose. Clear safeguards are therefore essential, both to prevent mission creep and to ensure that the organisation strengthens delivery without displacing responsibility.
The ODP would operate within the following constraints:
No policy remit. The ODP would not recommend policy choices. Its role would be limited to reporting delivery performance, risk, and evidence.
No programme ownership. Departments would remain fully accountable for results. The ODP may provide short, time-limited delivery support, but line responsibility would not transfer.
Fixed size ceiling. Headcount would be capped at around 150 staff, with a rolling secondment model from departments to maintain practical expertise and avoid centre expansion.
Statutory transparency. Methods, metrics, and dashboards would be published by default. Any exceptions would require written, time-limited justification.
Clear conflict rules. Board members and senior staff would publish interests, with cooling-off periods applied where appropriate.
Stage-gate discipline. The ODP would assess readiness at key delivery stages, but would not block programmes. Where concerns are ignored, it would escalate evidence to ministers and Parliament.
Regular self-review. The ODP’s own remit and functions would be subject to periodic external review to prevent drift or duplication.
Alongside these formal safeguards, the ODP would operate to a clear cultural code: early warning rather than blame; support before escalation; and public data presented in plain language. This combination of constraint and culture is intended to ensure that the ODP remains a durable part of the state’s delivery infrastructure, rather than another short-lived reform initiative.
5. Departments That Deliver
Competent government is not delivered by the centre alone. However strong national oversight becomes, outcomes ultimately depend on how departments organise themselves, make decisions, and manage delivery in practice.
The Office for Delivery and Performance (ODP) does not replace departmental responsibility, but provides the standards, assurance, and escalation mechanisms that support its operation in practice.
In practice today, departmental boards are overloaded, accountability is blurred, and delivery is often treated as a reporting exercise rather than an operating discipline. Problems surface late, ownership is unclear, and learning is weak. The result is a familiar pattern: over-ambitious announcements followed by quiet slippage and eventual reset.
This section sets out a practical model for departments that deliver, not by adding new layers of bureaucracy, but by clarifying ownership, structuring decision-making around outcomes, and making delivery performance visible at every level.
While many of the mechanisms described below exist formally within government, this model differs by making them mandatory, time-bounded, decision-forcing, and enforced through explicit progression and stop decisions.
5.1 Governance: Clear Ownership and Visible Accountability
Delivery improves when responsibility is explicit, forums are decision-focused, and accountability is unambiguous. In practice, much of government delivery today is overseen through diffuse boards, crowded agendas, and reporting cycles that surface problems too late to resolve them. This model tightens governance around a small number of priority outcomes and makes ownership visible at every stage.
Each priority outcome is overseen by a minister-chaired Delivery Board with a formal mandate to take and record binding decisions. Boards meet monthly and are limited to three to five priority outcomes. Their purpose is not progress reporting but active management: resolving trade-offs, addressing delivery risks, and agreeing changes to scope, sequencing, or funding, including decisions to pause or stop activity where evidence requires it. Attendance is fixed and tightly defined, typically including the Secretary of State, Permanent Secretary, a Director-General for Delivery, relevant Senior Responsible Owners (SROs), and finance and data leads.
Accountability is structured and explicit. Ministers are accountable for outcomes and the political trade-offs they entail, including where delivery depends on external partners or complex delivery chains. Accounting Officers retain responsibility for feasibility, value for money, and propriety. SROs are accountable for the delivery of defined programmes within an agreed scope and timeframe. For each priority outcome, departments publish a short accountability statement setting out who owns what decisions, on what basis, and within what constraints.
At the start of every major programme or reform, departments undertake a mandatory 90-day delivery readiness review. This is a time-limited mobilisation phase, not an open-ended strategy exercise. It confirms the problem being addressed, the intended outcomes, the delivery chain, principal risks, dependencies, and an outline timeline with defined stage-gates. No programme proceeds beyond this phase without an agreed Delivery Plan, published in plain English and focused on execution rather than aspiration. The Delivery Readiness Review constitutes the first formal stage-gate for major programmes under this model.
5.2 Planning Discipline: From Intent to Operations
Government has formal planning frameworks, but in practice many programmes move too quickly from intent to commitment, with key uncertainties unresolved. This model tightens planning discipline by limiting progression, hardening decision points, and making evidence, not narrative, the basis for moving forward.
Major programmes progress through a small number of mandatory stage-gates: initiation, outline case, full case, build and scale, and steady-state operation. Movement between stages is conditional. Each gate requires explicit evidence on user need, delivery approach, cost and schedule risk, and a clear recommendation to proceed, adapt, or stop. Progression is a decision, not an assumption.
Risk is treated as a quantified management issue, not a traffic-light exercise. Departments maintain standardised risk registers with cost and schedule ranges, named risk owners, and defined mitigations. For complex or novel programmes, formal pre-mortems are required at early stages, along with agreed mechanisms for reset where assumptions no longer hold. Programmes are required to surface material risks and delivery failures at the earliest stage rather than absorb them informally.
Commercial and supplier strategy is addressed before delivery is locked in. Departments are required to test markets early, favour modular and incremental contracting where feasible, and avoid “big bang” delivery models that concentrate risk and reduce adaptability. Large-scale commitments without a credible commercial strategy are not permitted to proceed.
5.3 Data and Transparency: Comparable, Public, Useful
Delivery cannot be managed without reliable information. Each department is required to publish and maintain a live Delivery Dashboard, aligned to the ODP’s cross-government view and limited to a small number of outcome measures, performance against an agreed trajectory, material risks, and upcoming milestones. Dashboard data is the primary evidence used in Delivery Board discussions and stage-gate decisions.
Data is collected and published using a shared model agreed with the ODP, allowing Parliament and the public to compare performance across departments. For each metric, departments are required to publish definitions, data sources, update frequency, and known limitations. This enables independent scrutiny, reduces scope for selective reporting, and supports consistent interpretation over time.
Where performance deviates materially from plan, departments are required to record and publish the variance, the underlying causes, and the corrective action agreed. Disclosure is linked to problem-solving, not blame, and is expected to occur early enough to inform corrective decisions.
5.4 Capability and Skills: Fit for Delivery
Delivery outcomes depend on whether departments have the right mix of skills, roles, and experience to manage complex programmes. In the current system, delivery capability is uneven, key roles are frequently rotated, and accountability is weakened by short tenures and unclear expectations. This model treats delivery capability as an explicit operational requirement.
For each major priority outcome, departments are required to designate a stable delivery leadership team, including an SRO with relevant experience and sufficient tenure to see the programme through critical phases. This includes a designated Director-General for Delivery at board level in departments with significant delivery portfolios, responsible for delivery standards, stage-gates, and delivery capability across the department. Minimum tenure expectations apply to senior delivery roles, with changes requiring formal justification and handover arrangements. Continuity is treated as a delivery risk, not a staffing preference.
Departments are required to maintain an explicit capability plan for priority outcomes, setting out the skills required, gaps identified, and how these will be addressed through recruitment, development, or external support. Use of consultants or delivery partners must be justified against capability needs and knowledge transfer requirements, not treated as a default substitute for internal capacity.
The ODP supports this model by setting common expectations for delivery roles, supporting capability assessment at key stages, and identifying systemic skill gaps across government. Responsibility for building and sustaining delivery capability remains with departments.
Delivery roles are treated as part of a recognised professional pathway within the civil service, with common standards and progression based on demonstrated delivery outcomes rather than tenure alone.
Delivery performance against agreed outcomes, milestones, and risk management expectations is reflected in appraisal, progression, and future role allocation for senior delivery leaders and SROs. This reinforces the expectation that delivery roles carry sustained responsibility for results, decision quality, and corrective action, not just formal accountability.
5.5 Learning, Evaluation, and Reset: Building Institutional Memory
Government delivery is weakened by poor institutional learning. Lessons are often captured late, in isolation, or after programmes have failed, with limited impact on future decisions. This model embeds learning as a routine part of delivery management.
For major programmes, departments are required to conduct proportionate, timely evaluations at defined points, linked to stage-gates and significant delivery decisions. Evaluation focuses on what is working, what is not, and what needs to change, rather than retrospective justification.
Where evidence shows that assumptions are no longer valid, departments are required to initiate a formal reset process. This may involve revising scope, timetable, delivery approach, or where necessary recommending termination. Reset decisions are recorded, published where appropriate, and reviewed through Delivery Boards and ODP assurance processes.
The ODP supports cross-government learning by identifying recurring delivery risks, common failure modes, and effective mitigation strategies, and by feeding these back into standards, guidance, and capability development. Learning is treated as an operational input, not a post hoc exercise.
5.6 Escalation, Intervention, and Stop Decisions: Dealing with Failure Early
A credible delivery system must be able to intervene when programmes go off track and to stop activity that no longer represents a viable use of public resources. In the current system, escalation is often informal, late, or avoided altogether, leading to prolonged underperformance and higher eventual costs.
Under this model, material delivery risks, repeated stage-gate failures, or sustained deviation from agreed trajectories trigger formal escalation. Escalation routes are defined in advance, with clear thresholds and decision rights.
Where necessary, intervention may include additional assurance, changes to leadership or delivery approach, or the imposition of tighter controls. In cases where problems cannot be credibly resolved, departments are required to bring forward options to pause, materially rescope, or stop programmes altogether.
Stopping a programme is treated as a legitimate delivery outcome where evidence warrants it. It is recorded transparently, with clear explanation of the rationale and lessons learned. The objective is to limit harm, protect public value, and redeploy effort to activities with a higher likelihood of success.
6. Local Delivery: Principles and Next Steps
Competent government does not stop at Whitehall. Many of the outcomes that matter most to citizens, from health and skills to safety and housing, are delivered locally, through councils, combined authorities, and local public services.
Renewal’s delivery model is designed to operate across this system, applying the same principles of clarity, evidence, and accountability to local delivery as to departments at the centre. This includes earned autonomy based on demonstrated capability, shared outcome frameworks, and transparent performance data by place.
The detailed implications for local government, including funding, capability, and centre–local relationships, are set out in a separate forthcoming Renewal paper. This paper focuses on the core delivery architecture required at the national and departmental level.
7. Implementation Roadmap
Renewal’s delivery framework is designed to be implemented within a single Parliament. The objective is not wholesale reorganisation, but to embed delivery discipline progressively into the machinery of government, starting small, proving value, and then scaling what works.
Phase 1: Year 1 – Establish the Foundation
The first year focuses on credibility, clarity, and institutional setup.
The Office for Delivery and Performance (ODP) is established as a small, independent body reporting to Parliament, with an initial analytical core drawn from existing performance, assurance, and delivery functions across government. Its early focus is consolidation rather than expansion: aligning fragmented reporting, clarifying outcome definitions, and establishing a single cross-government view of delivery performance.
In parallel, ministers agree a limited set of priority outcomes (around 20), covering the core responsibilities of government. These outcomes are defined in clear, measurable terms and linked to existing data where possible, avoiding the creation of new reporting burdens.
Two to three pilot areas are selected to test the delivery model in practice. These should be cross-cutting, operationally complex, and politically salient, for example NHS waiting times, school attendance, or housing delivery. Departments involved establish Delivery Boards and Delivery Plans in line with the framework set out in this paper, with quarterly evidence-based reviews supported by the ODP.
During this phase, existing internal reporting units and duplicated assurance processes are reviewed, with the aim of reducing overlap and freeing capacity rather than adding new layers.
Phase 2: Years 2–3 – Embed and Scale
Once the model has demonstrated value, the focus shifts from pilots to routine operation.
The ODP’s remit expands to cover all departments responsible for agreed priority outcomes. Standardised Delivery Dashboards are published, presenting progress, risks, and milestones in a consistent format accessible to ministers, Parliament, and the public.
Departmental Delivery Boards become standard practice for major spending and reform areas. Each board maintains a concise Delivery Plan, setting out outcomes, metrics, key risks, and mitigation actions. These plans are reviewed periodically using common evidence standards, with escalation where delivery risks persist.
During this phase, delivery capability is strengthened by refocusing existing training and professional development for senior officials and SROs around the delivery framework, including planning discipline, risk management, and use of performance data. The emphasis is on practical competence, not new qualifications or institutions.
Evaluation and learning are embedded into decision-making. Evidence from delivery reviews and programme evaluations is used to inform corrective action and, where appropriate, budgetary and policy decisions.
Phase 3: Years 4–5 – Normalise and Report
By the fourth year, delivery discipline should be routine rather than exceptional.
The ODP publishes an annual delivery report to Parliament, consolidating progress across priority outcomes and highlighting areas of sustained success, emerging risk, and underperformance. This replaces fragmented departmental performance statements with a single, coherent account of delivery across government.
Targeted outcome-focused reviews are undertaken in selected policy areas to identify lessons, compare delivery approaches, and inform future priorities. These reviews are explicitly linked to Spending Reviews, ensuring that funding decisions reflect delivery performance as well as policy intent.
By the end of the Parliament, the delivery framework should be embedded across departments: with consistent planning discipline, visible accountability, and transparent performance reporting forming part of normal government practice.
Beyond the First Parliament
Delivery reform is not a one-off intervention. The framework set out here is intended to endure beyond political cycles, providing a stable operating model that successive administrations can adapt to their priorities without dismantling the underlying system.
The test of success is straightforward: fewer late-stage failures, earlier intervention when problems arise, and a higher proportion of government commitments delivered on time and to standard.
8. Conclusion – Competence as a Public Obligation
The starting point for reform is not a new ideology, but a renewed expectation that government does what it says it will do. For too long, success has been measured by the volume of announcements, budgets, and legislation rather than by whether outcomes are delivered in practice. That gap between promise and performance has become a defining weakness of the system.
Competence is not a technical detail. It is the foundation of trust, fairness, and legitimacy in public life. When government delivers reliably, it earns the authority to lead. When it does not, even well-intentioned policies lose credibility and public consent erodes.
The reforms set out in this paper are therefore deliberately practical. They focus on how priorities are chosen, how delivery is managed, how performance is measured, and how problems are addressed early rather than explained away later. The Office for Delivery and Performance, clearer departmental accountability, disciplined planning, and transparent reporting are not ends in themselves. They are the basic infrastructure required for government to perform consistently over time.
This is not a call for more ambition, but for fewer promises kept better. A competent state is defined not by its size or ideology, but by its ability to translate intent into results cleanly, fairly, and transparently. Each missed target, failed programme, or broken commitment carries a real cost, both to public resources and to public trust.
Restoring competence is therefore an obligation of government, not just a managerial concern. It is how government sustains credibility in the exercise of public authority. Renewal’s case is simple: when delivery becomes the measure of success, trust can be earned again not through rhetoric, but through results.