Ready to build
Work is specified enough to start. We note how “ready” is declared—ticket states, branch opens, or kickoff ceremonies—because lead-time clocks often start too late or too early.
The delivery map
A shared picture of how change moves—so baselines, risk signals, and bottleneck studies talk about the same stages.
Stages we measure against
Every engagement starts by naming these lanes for your applications. Silence outside the map is intentional.
In development
Coding and local validation. We separate active coding time from blocked time when environments, dependencies, or unclear requirements stall progress.
In review
Peer review, compliance checks, and automated gates. Waiting for reviewers dominates many Hong Kong product orgs; we measure queue age, not only review duration.
Waiting to ship
Merged but not released—freeze windows, shared staging locks, or batching policies. This lane often hides more delay than the build itself.
In production
Released and observable. We track failed changes, rollback speed, and whether recovery signals exist when a release goes wrong.