Queue Time Attribution
Splitting elapsed lead time into work and waiting, and naming which queue each wait sat in.
Lead time is the number leadership asks about and the least actionable on its own, because it aggregates two things with completely different remedies. Work time responds to skill, tooling and scope. Wait time responds to policy, batch size and capacity — and it is usually the larger share by a wide margin.
Attribution means resolving the elapsed time into named queues: awaiting refinement, awaiting review, awaiting a test environment, awaiting a release window. Ticket state transitions usually contain enough to do this without new instrumentation.
What it reliably produces is a redirection of effort. The instinct when delivery is slow is to look at the build or the developers; attribution normally shows the largest single block is a release window or an environment queue, both of which are policy decisions rather than engineering capability. It also protects against the classic error of optimising a step that then waits longer at the next queue, changing the total by nothing at all.