Vanity metrics vs action indicators
The number of tasks created, hours logged in, or messages exchanged measures activity, not progress. A good indicator has three properties: it depends on the team (they can influence it), it changes fast enough to trigger an action, and it has a clear threshold ("beyond X, we step in").
The five basic indicators
1. Completion rate
Tasks completed / tasks planned for the period. Below 80% over two consecutive cycles, either the scope is underestimated or the capacity is overestimated.
2. Velocity
Effort points completed per sprint. It's compared sprint to sprint for the same team — never between teams. The trend matters more than the absolute value.
3. Cycle time
Time between when a task starts and when it finishes. It reveals bottlenecks: if cycle time grows while workload is stable, something is lingering somewhere.
4. Blockers
Number of blocked tasks and their cumulative age. A blocker older than three days deserves an explicit decision, not patient silence.
5. Workload per person
Distribution of tasks and effort points. The goal isn't mathematical equality, but the absence of an invisible breaking point.
Pitfalls to avoid
The numeric goal that becomes a target: set "improve velocity" and the team will inflate its estimates. Measure to learn, not to score.
The dashboard nobody reads: if nobody looks at an indicator for two weeks straight, remove it. Every surviving metric should have a ritual attached to it.
The average that hides everything: a 90% completion rate can hide a critical milestone at 0%. Always look at the distribution, not just the average.
In practice with FluidOps
The Reports & Analytics module calculates these indicators by week, month or year, with workload per member and the projects-team connection map. The Scrum sprint provides velocity, and Kanban provides cycle time. Try it in the analytics demo.