Design
The product itself
Service design and user experience. The workflow, the handoffs and the actual experience of the user — and how they check the information behind a recommendation and correct that information — mapped with the people who own the process.
Data and analytics architecture. Decisions modelled first, then the data models and standards — with ownership, quality and retention settled — that let a second team build on the first.
Security and compliance by design. Security, information governance and assurance settled in the first weeks, alongside your own security people.
Deliver
Getting it built and into use
Product management. Someone accountable for the outcome rather than the activity, from discovery on the ground to adoption in live service, with the data the product depends on in the roadmap.
Delivery management. The backlog, releases, environments, testing and data migration from first sprint to live service, with assurance and quality gates built in.
Programme management. The problem stated so a team can act on it, the funding bid and business case, and governance — data governance included — stood up before delivery is judged against it.
Sustain
The team that evolves it
Operating model design. Where teams sit, what they decide, how their work is promoted from forward deployed teams to the centre, and how they work with the chief data office.
Supplier and commercial management. Your suppliers formed into one team, with goals aligned, one route for escalation and clear accountability for the data each holds.
Change management and adoption. Data quality standards enforced through practice, your people checking and correcting information as part of everyday work, benefit baselined before go-live and measured after, and your own team strengthened to own the capability.