EnleashedEnleashed
Mission #2Delivery plan

Fix the government delivery machine

Modernise public-sector delivery through digital systems, incentives, and accountability.

We know what needs to change (see the Challenge investigation). This page maps how that change actually gets made.

2

Status quo

What exactly exists today — legally, institutionally, technically and operationally — that the desired system needs to change?

Law

Not yet documented.

Regulation

Not yet documented.

Institutions

Not yet documented.

Markets & mechanisms

Not yet documented.

Funding

Not yet documented.

Technology

Not yet documented.

Data

Not yet documented.

Operations

Not yet documented.

The status quo hasn't been documented for this mission yet.
3

The change map

Every concrete change required to move from the status quo to the desired system, with who has authority, the legal mechanism, and current status.

No changes have been mapped for this mission yet.
4

Who can act?

Decision makers, delivery bodies, influencers, beneficiaries, potential opponents, experts, the public and funders — transparent democratic advocacy, not tactics.

No stakeholders have been mapped for this mission yet.
5

Pathways to change

Not every change happens the same way. These are the generic routes this mission's changes can take — highlighted where a change item actually uses them.

Legislative

Change requires new primary or secondary legislation from Parliament.

Drafting → Parliament → Bill → Act → Implementation

Regulatory

Change requires a regulator (e.g. Ofgem) to run a decision or licence-modification process.

Case for change → Regulator consultation → Decision → Licence / rule change → Implementation

Industry code

Change is delivered through an industry code's own governance process (e.g. BSC, CUSC, Grid Code).

Modification proposal → Workgroup → Impact assessment → Panel / authority decision → Implementation

Government policy

Change requires a government department to adopt a policy position and commit to it.

Evidence → Department engagement → Ministerial support → Policy decision

Institutional

Change is a decision an institution (e.g. NESO, a network operator) can make about its own responsibilities or operations.

Proposal → Board / leadership decision → Organisational reform

Procurement

Change is delivered by specifying and procuring a system, service or pilot.

Specification → Funding → Procurement → Deployment

Voluntary market adoption

Change spreads through the market without a mandate — early adopters demonstrate it, then it scales.

Demonstration → Early adopters → Scaling

Technology

Change depends on building and proving working software or infrastructure first.

Research → Prototype → Pilot → Production → Integration

Public / political

Change depends on public understanding and political will, not only technical or regulatory steps.

Evidence → Communication → Coalition → Public support → Political commitment

Funding

Change is blocked on securing the money to do the work, not on a decision or a mechanism.

Case → Funder → Commitment → Deployment

6

Change agents

What forces could actually make this change happen?

No change agents have been flagged as relevant to this mission yet.
7

Coalition / buy-in

What legitimate concerns must be resolved to build a coalition capable of delivering change?

No coalition positions recorded yet.
8

Evidence needed for change

Different decision makers require different evidence. Connects back to the Challenge investigation's evidence where it already exists.

No evidence requirements recorded yet.
9

Fund the mission

Funding as a first-class delivery workstream — required, secured and the gap, by workstream.

Required

Not yet costed

Secured

£0

Gap

No funding lines have been costed for this mission yet.
Fund this mission →
10

Campaign / communication

Public understanding and political support this mission needs, and what each piece of communication is trying to achieve.

No campaign or communications activity recorded yet.
11

Build

Technology is one delivery workstream among many — shown here only where it's required to deliver the agreed solution.

No technical build work has been scoped for this mission yet.
12

Roadmap

Milestones from every workstream, together — not a generic month-by-month calendar.

No milestones have been set for this mission yet.
13

Blockers / risks

What could stop this?

No risks have been logged for this mission yet.
14

Next actions

What actually needs to happen next.

No next actions have been set for this mission yet.
15

How can I help?

Enleashed is collaborative — concrete ways to get involved with this mission.