Operations metrics need journeys, not orphan counters
A backlog age chart means little if application analytics never see the hand-off that actually stalled the work.
Digital operations intelligence fails quietly when counters float free of the journeys that produce them. Teams celebrate a falling queue length while fulfilment still waits on a silent approval step that never emits an event.
Start by listing the operator-visible stages that must complete for a period to count as healthy. Then check whether those stages fire into your application analytics with stable identities. Gaps between board health and floor reality usually show up as escalations without matching signals.
A practical fix is to pair volume KPIs with completion KPIs — for example, cleared items per attempt window — and review both in the same weekly ops pack.