Platform Engineering · 06 of 6
How we build it
Adoption with decision gates, the three-stream programme, the roadmap and how we measure value.
Adoption with decision gates
- Assessmentbaseline and target
- Analysis & planningMVP with 2–3 pilot apps
- Pilotgo / no-go
- Implementation & optimisationplatform in daily use
01
Adoption with decision gates
Each phase ends at a gate where we review, adjust, align and check compliance with you.
- 01Assessment
- Vision and outcomes
- SDLC, tools, platform, operations
- Security, people and culture
- 02Analysis & planning
- Gaps, strategy and roadmap
- Toolchain and dashboards
- Supported languages and targets
- Governance model
- 03Pilot
- Implement the MVP
- Evaluate against objectives
- Train and hand over
- 04Implementation & optimisation
- More teams and services
- Support and troubleshooting
- Operate and optimise
02
A three-stream programme
Large platforms run as three streams in parallel, each with its own team and plan.
- Developer-platform streamPortal, golden paths, pipelines and self-service, built in increments with pilot teams.
- Landing-zone streamThe cloud foundation underneath: accounts, network, identity federation and guardrails.
- Programme & insourcing streamPlanning, adoption and knowledge transfer, so your engineers run and extend the platform.
Developer platformLanding zoneProgramme & insourcingOne platform programme
03
Quick win, mid term, long term
A typical shape for a platform programme over two to three years.
1 of 3
Quick win
An MVP portal and the first golden-path templates for pilot teams.
- Portal with service catalogue and docs
- First templates: application, IaC and pipeline together
- Pilot teams onboarded
04
Do and avoid
Avoid Do
Starting point✕Every team and use case at once✓The workflow with the most friction
Scope✕Every feature before the first user✓A thinnest viable platform, then grow
Ownership✕A side project✓A product with a team, roadmap and users
Measurement✕Nobody measures success✓Delivery, adoption and cost from the start
Organisation✕A big-bang reorganisation✓Team by team
Freedom✕A walled garden✓Paved, not walled
05
How we measure value
| Lens | What we track | The question |
|---|---|---|
| DORA | Deployment frequency, lead time, change failure rate, time to restore | Faster and safer delivery? |
| SPACE | Satisfaction, performance, activity, communication, efficiency | Better work for developers? |
| Adoption | Teams and services on golden paths, self-service requests | Are people choosing it? |
| Cost | Cost per team and component, provisioning time saved | Is it worth running? |
06
Platform team roles
SourcesNGT Platform Engineering deck v1.2 (Sep 2026)NGT Platform Engineering Service Offering v1.0 (2025)NGT Service Offering v3.2 (Jul 2026)NGT Service Offering v2.0 (Mar 2025)NGT FinOps Service Offering (Mar 2025)
