Skip to content
NZT

Concepts

The seven phases

Discovery, Architecture, UX, Build, Verify, Ship and Learn. What each NZT phase covers, and why a phase comes in only if it changes what is going to be built.

Seven phases. Not seven mandatory steps.

A phase comes in only if it changes what gets built. Skipping is normal; skipping silently is not.

What each phase covers

Discovery · nzt-discovery

What to build, for whom and under which rules: requirements, business rules, specs, stories and changes to existing features.

Architecture · nzt-architecture

How to solve it: components, stack, domain model, technical design, ADRs, RFCs and diagrams.

UX · nzt-ux

Screens, flows, design system, usability review and the end-user manual as interactive HTML.

Build · nzt-build

The code, and the tests that travel with it.

Verify · nzt-verify

Design and run API or UI tests, create and clean up test data, measure performance and record evidence.

Ship · nzt-ship

Versioning, CI/CD, deployment and observability.

Learn · nzt-learn

Teach you instead of doing it for you: curriculum, lessons, exercises, assessment and spaced review.