This standard ensures teams measure time spent in each stage of their delivery workflow, making bottlenecks and wait states visible. By tracking time-in-status data, teams can continuously optimise flow and reduce wasted effort.
Aligned with our "Limit Work in Progress (WIP)" policy, this standard promotes faster, more predictable delivery and stronger collaboration. Without it, bottlenecks remain hidden, lead times stretch, and continuous improvement stalls.
Level 1 – Initial: No visibility into time spent in workflow stages. Bottlenecks are anecdotal, and delays are not actively tracked or addressed.
Level 2 – Managed: Some teams begin tracking time-in-status data, typically through tooling defaults or manual methods, but usage is inconsistent and insights are not routinely actioned.
Level 3 – Defined: Time-in-status measurement is established as a standard practice. Teams consistently apply this approach using shared tools and regularly review flow metrics.
Level 4 – Quantitatively Managed: Bottlenecks and wait states are benchmarked and tracked over time. Teams use data to inform delivery decisions, experiments, and process improvements.
Level 5 – Optimising: Time-in-status insights are embedded into team retrospectives and governance. Metrics continuously shape prioritisation, reduce delays, and enhance delivery predictability.