Measure the wait, not only the work
Queue time between developer network stages is often where delivery actually slows — and where analytics stay quiet.
Work duration tells you how long a job ran. Wait duration tells you how long the path sat idle between stages. Developer network workflows routinely lose hours in review queues, approval gates, and cross-team handoffs that never emit a marker.
Instrument enter and leave events for each wait. Pair them with the active work intervals. Application analytics then show whether slowdowns come from compute or from coordination.
Without wait signals, teams optimise the wrong stage and wonder why lead time barely moves.