What is it?
Process Efficiency Observation follows a piece of work through a defined period and records what is happening to it: value-creating work, necessary support, delay, movement, checking, rework or waiting.
What's it really for?
It is for seeing the process from the work's point of view. People can be occupied throughout while the customer, file, component or decision spends most of its life waiting for attention.
You know when…
Everyone is working hard and every diary is full. The application still takes twelve days despite requiring about forty minutes of actual handling. Nobody owns the other eleven days because they are spread neatly between teams.
Have a go
- Select one real item and define the start and finish. ☐ Follow it without interfering. ☐ Record activity, delay, movement, hand-offs and rework in time order. ☐ Separate elapsed time from touch time. ☐ Review the observation with the people doing the work and identify the largest sources of lost flow.
Why it works
Direct observation restores the time that process descriptions tend to omit. Small stops and hand-offs become visible, allowing the team to compare active work with total elapsed time.
Look for…
Long queues between short tasks, repeated checking, batching, searching, avoidable movement, unclear readiness and work returning to an earlier stage.
Watch out…
Observation is not surveillance. Explain the purpose, protect individuals and study the work rather than rating the person. One case is a clue, not a complete performance claim.
Worth noticing…
The awkward gaps between departments are often invisible to each department and completely visible to the work.
Try next…
Use a Process Map to capture the sequence. Use Spaghetti Diagram when movement dominates. Use Value Stream Mapping to examine flow across the wider system.