Shadowing handlers without turning observation into theatre

Shadowing is still one of the most reliable ways to understand handler workflow analytics for support apps. Numbers show where time goes; sitting beside the work shows why. The risk is theatre: handlers narrate every click, skip shortcuts they normally use, or apologise for every pause.

Agree the frame before the session. Explain that you are mapping the path through the apps, not scoring the person. Ask the handler to work a normal mix of tickets. Limit narration to moments where a decision is invisible on screen — for example, choosing which queue to check first after a break.

Take notes in the order of the journey: login friction, queue pick, customer context, knowledge lookup, collaboration, wrap-up. Capture clock times only when they illuminate a bottleneck, not as a personal stopwatch. If something feels slow, ask whether that is usual or a one-off outage.

Remote observation works when screen share is stable and the handler can mute customer audio for privacy. Keep sessions under ninety minutes. Fatigue makes people perform more, not less.

Afterward, share a short summary of the path you saw and invite corrections. Handlers often name workarounds that never appear in official process docs. Those corrections belong in the assessment brief; they are evidence, not gossip.