Hidden capacity is often time trapped between actions rather than time people are withholding. App events can reveal recurring queues, repeated hand-offs and work reopened after an avoidable interruption.
Map waiting before speed
Start with elapsed time across the workflow and compare it with active handling time. Large gaps deserve a conversation: some protect quality, while others expose unclear ownership or batching.
Look for changes that remove friction—better routing, fewer duplicate entries or clearer thresholds—before asking anyone to work faster.
Protect the recovered time
Agree in advance whether released capacity should reduce a backlog, create resilience or support improvement. Otherwise, the benefit is quickly absorbed and becomes invisible again.