The utilisation number that lies
80% utilisation. 30% of it was rework and interruptions.
Utilisation measures activity, not value. An engineer at 90% utilisation might be spending half their time on preventable rework, context-switching between clients, or waiting for information. High utilisation with low productivity is worse than lower utilisation with focused output.
The scenario:
You want to understand true engineer productivity, not just time logged.
The prompt:
You're analysing engineer productivity.
Data: [paste time entries, ticket data, categories]
Create an analysis that:
- Breaks down utilisation by productive vs. non-productive work
- Identifies top time sinks (rework, waiting, interruptions, admin)
- Calculates effective utilisation (billable value delivered / time spent)
- Benchmarks across team members and clients
- Proposes interventions for the biggest productivity drains
Include a dashboard design for ongoing monitoring.