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
  1. Assessmentbaseline and target
  2. Analysis & planningMVP with 2–3 pilot apps
  3. Pilotgo / no-go
  4. 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.

  1. 01Assessment
    • Vision and outcomes
    • SDLC, tools, platform, operations
    • Security, people and culture
    Baseline and targetReview
  2. 02Analysis & planning
    • Gaps, strategy and roadmap
    • Toolchain and dashboards
    • Supported languages and targets
    • Governance model
    MVP with 2–3 pilot appsAlign
  3. 03Pilot
    • Implement the MVP
    • Evaluate against objectives
    • Train and hand over
    Go / no-go
  4. 04Implementation & optimisation
    • More teams and services
    • Support and troubleshooting
    • Operate and optimise
    Platform in daily use
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 pointEvery team and use case at onceThe workflow with the most friction
ScopeEvery feature before the first userA thinnest viable platform, then grow
OwnershipA side projectA product with a team, roadmap and users
MeasurementNobody measures successDelivery, adoption and cost from the start
OrganisationA big-bang reorganisationTeam by team
FreedomA walled gardenPaved, not walled
05

How we measure value

LensWhat we trackThe question
DORADeployment frequency, lead time, change failure rate, time to restoreFaster and safer delivery?
SPACESatisfaction, performance, activity, communication, efficiencyBetter work for developers?
AdoptionTeams and services on golden paths, self-service requestsAre people choosing it?
CostCost per team and component, provisioning time savedIs 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)