Implementation · controlled 90-day proposition
Prove the operating model before scaling the platform.
A credible national programme does not start by integrating everything. It starts with a narrow set of decisions, programmes, source owners and users, then proves that connected evidence changes the way delivery is understood and acted upon.
Pilot sequence
Every phase has an output and a gate.
Select each stage to see what is delivered and what must be true before the pilot moves forward.
Start with the decisions, not the software.
Map the highest-value leadership and programme decisions, the reporting routes that currently support them, the people accountable for the evidence and the security boundary around each source.
Decision and briefing auditPriority programme shortlistData-owner mapSecurity discoveryBaseline success measures
What must be true next.
Proceed only when the pilot has named users, named decisions, named source owners and agreed success measures.
No phase assumes access to live restricted systems. Integration and identity work only advances with authorised owners and an agreed security model.
End-to-end case journey
One issue. One connected operating record.
This illustrative journey demonstrates the behaviour the pilot should prove: an exception moves through delivery, sector context, leadership and assistant retrieval without changing its underlying facts.
01
A delivery dependency worsens
02Grid reliability programme moves to decision status with high risk.
Delivery exposes the exception
03The shared programme record shows 54% progress, evidence freshness and the next milestone without creating a separate dashboard version.
Sector context explains the dependency
04Energy intelligence shows the programme alongside related portfolio risk and cross-programme dependencies.
Leadership receives a decision
05Confirm the accountable owner and recovery date for the dependency.
Command Assistant explains the record
06A user can ask for the issue, open its sources and move directly to the programme, sector or governance context.
The next cycle has a traceable outcome
The decision, updated evidence and programme movement can be reflected in the same operating record rather than another detached briefing artefact.
Success measures
Measure operating value, not presentation quality.
The pilot should be judged by what changes in briefing, evidence, escalation, retrieval and repeat use. Large financial claims should only follow evidence.
Measure how much manual collation is removed from priority briefing workflows.
Measure how quickly a delivery exception reaches an accountable decision owner.
Measure the share of priority records supported by evidence inside the agreed freshness window.
Measure whether users can move from national signal to programme, province, dependency and evidence.
Measure whether users find the right programme, region, sector or knowledge record without leaving the service.
Measure whether target roles return to the product during real operating cycles.
Pilot deliverables
A complete product-and-operating package.
By the end of the pilot, a sponsor should be able to evaluate the product, governance model, adoption evidence and technical route to scale together.
This route is an implementation proposition. Timings and outputs are designed to make a controlled pilot concrete; actual scope would be agreed with authorised programme, data, security and leadership owners during discovery.