Engagement Journey
Assessment, MVP or PoC, planning, implementation and operation: one journey for every capability.
At a glance
Every NGT engagement runs the same five phases: Assessment, MVP or PoC, Planning, Implementation and Operation. It starts from a maturity score and an agreed target level. It ends with your team, or NGT under SLA, running what was built.
The Assessment scores today against NGT's maturity checklist. The target level is agreed before anything is built.
An MVP or PoC shows the solution working early. The plan and estimate come after, from what it taught.
Enablement, runbooks and hyper-care come before hand-over. Then your team runs it, or NGT does under SLA.
The Five Phases
The lifecycle under every NGT capability. Each phase ends at a gate where results are reviewed and the next step agreed.
- 01Assessment
- Assess the current state
- Score maturity against NGT's checklist
- Agree the target level with you
- 02MVP / PoC
- A quick, working demo
- Fail fast and move forward
- Re-estimate if the PoC changes the picture
- 03Planning
- Master plan
- Work breakdown structure (WBS)
- Cost estimate
- 04Implementation
- Build the solution
- Run the full deployment plan
- Confirm the target level is reached
- 05Operation
- Monitor and maintain production
- Run under SLA, or hand over
- Keep improving
A DevSecOps roadmap, a landing zone, a developer platform and an AI agent all go through the same five phases. Only the checklist and the tools change.
What Goes In, What Comes Out
Your goals and constraints go in. At every gate you receive something you can check.
- Gates, not a big bangReview, adjust, align and consent before each next phase starts.
- Evidence before estimatesThe plan is made after the PoC, from what it showed.
- Hand-over planned from day oneTraining, runbooks and hyper-care are part of the plan, not an afterthought.
Explore Engagement Journey
3 pages, each a few minutes to read.
Frequently asked questions
What customers ask first.
It depends on the capability and the estate. In NGT's DevSecOps framework, Scan takes 2–3 weeks and Evaluate 1–2 weeks.
Cloud assessments scale with servers and applications; the scope is agreed first.
No. Start where you are: an assessment alone, engineers joining a running programme, or operations of a platform you already have. The phases describe how NGT works when it owns the outcome end to end.
A checklist per capability that places each area at Initiate, Challenger or Mastery. The Maturity Model page shows what is checked.
That is what the PoC is for: fail fast and move forward. The approach or the estimate changes before the full plan is made.
Templates and infrastructure code, dashboards and runbooks, playbooks, SLOs with error budgets, documentation and training, after hyper-care has let the system settle.
As an accelerator under engineers' control: FleziLift cross-checks migration files, and AI assistants draft code, tests and documents for review. Decisions and sign-off stay with NGT's architects and with you.
