Commandix guide
Flow Analytics
Flow Analytics explains how work moves through the system. It is the measurement layer behind bottleneck conversations, delivery forecasting, and workload decisions.
Last updated July 8, 2026
How to use date ranges
- Open Constraints -> Flow Analytics.
- Set start and end dates or use quick ranges: 7 days, 30 days, or 90 days.
- Review each chart after the data reloads.
- Use shorter windows for active operational problems and longer windows for pattern analysis.
Metric reference
| Metric | Meaning | How to use it |
|---|---|---|
| Cumulative flow diagram | Shows task counts by status over time. | Look for widening bands. A growing active or blocked band means WIP is accumulating faster than work is finishing. |
| Cycle time | Time from ACTIVE to DONE. | Use it to measure how long work takes once it begins. |
| Lead time | Time from creation to DONE. | Use it to measure customer or stakeholder waiting time. |
| Flow efficiency | Active work time divided by total lead time. | Low efficiency means work waits more than it moves. |
| Completed tasks | Throughput for the selected range. | Use it to see whether system output is improving. |
| Work type distribution | Business project, internal project, operational change, and unplanned work counts. | Use it to reveal whether strategy is being crowded out by maintenance or firefighting. |
| Workload heatmap | Open work by person and status. | Use it to spot overload, blocked people, and uneven load. |
| Aging WIP | Active or blocked tasks aging beyond normal expectations. | Use it to find work that needs intervention before it becomes a delivery problem. |
Why the cumulative flow chart can be empty
The cumulative flow diagram needs status history or enough task transitions in the selected date range. If it is empty, widen the date range, make sure tasks have moved through statuses, and confirm completed work exists in the period. Empty flow data does not always mean the workload dashboard is empty; workload can show current open work even when historical flow data is missing.
Workload dashboard vs identified constraint
The workload dashboard answers "who has the most visible work right now?" The identified constraint answers "what limits system throughput the most?" Those can be different. A person with many open tasks may not be blocking the highest-value projects or deals. A person with fewer tasks may be the constraint if their queue blocks downstream work, goals, or revenue.