Most organisations measure delivery.
Very few diagnose it.
I built FlowMaster — an analytics engine that connects to your Jira and reveals what your dashboards are hiding: metric gaming, flow debt, constraint violations, and the gap between your stated process and your real one.
What your dashboards are hiding
Metric gaming
Teams manipulate statuses, clone items, and time their updates to make the numbers look right. This isn’t a data quality problem. It’s evidence that your incentive structure rewards appearance over reality. When people feel unsafe reporting the truth, the metrics lie for them.
Flow debt
The gap between your stated cycle time and your actual cycle time grows wider every quarter. Your governance reports green while your delivery reality drifts. Flow debt is governance theatre made measurable — the divergence between what the organisation says it does and what it actually does.
Invisible constraints
The same bottleneck has been in the same status for months. Everyone knows about it. Nobody has the authority or incentive to fix it. Persistent bottlenecks aren’t process problems — they’re evidence that your organisational design has a structural constraint that no amount of process improvement will address.
WIP explosion
Work in progress is three times your capacity. New work keeps arriving. Nobody says no. Chronic WIP above policy isn’t a discipline problem — it’s an accountability failure. Nobody in the structure has the authority, incentive, or information to throttle demand.
Why I built it
I didn’t licence someone else’s analytics tool. I built one. Because the existing tools show you charts. I needed an instrument that shows you structural dysfunction.
FlowMaster implements Daniel Vacanti’s Actionable Agile Metrics methodology with full statistical rigour — percentile-based forecasting, process behaviour charts with control-rule detection, and backtested predictions. Then it goes further: anomaly detection that catches 15 types of metric gaming. Flow debt quantification that measures how far your stated process has drifted from reality. A coaching engine that produces prescriptive WIP interventions with severity and confidence scores.
110 analytical modules. Built by a practitioner who needed answers, not dashboards.
How it works
Connects to your Jira
Zero infrastructure. No agents to install. FlowMaster reads your delivery data directly — cloud or on-premise — and starts building the diagnostic picture within hours.
Runs eight analytical engines
Cycle time percentiles. Bottleneck radar. Process behaviour charts. Anomaly detection. Flow debt quantification. WIP coaching. Monte Carlo forecasting. AI-powered insights. Each engine reveals a different dimension of your delivery system.
Produces evidence, not reports
Percentile-based forecasting — never averages. Statistical process control that distinguishes signal from noise. Backtested predictions that validate their own accuracy. The diagnostic tells you what’s structurally true, not what you want to hear.
Questions it answers
Speed
- ●Are we getting faster or slower?
- ●Which work types take the longest?
- ●Where do items actually spend their time?
Flow
- ●Is demand exceeding capacity?
- ●How much work is aging beyond policy?
- ●Are we starting more than we’re finishing?
Process Health
- ●Is our process stable or erratic?
- ●Are teams gaming the metrics?
- ●Where are the structural bottlenecks?
Forecasting
- ●When will this epic actually ship?
- ●Which items are at risk of breaching SLA?
- ●How reliable are our own predictions?
When the metrics lie
FlowMaster’s anomaly detection engine scans for 15 patterns of metric gaming: identity swapping, status manipulation, timestamp tampering, selective reporting, workflow bypasses, bulk status changes at sprint boundaries.
These aren’t data quality issues. They’re evidence. When teams systematically game their metrics, it tells you something about the power structure they operate in — the incentives, the psychological safety, the gap between what leadership asks for and what reality allows.
Most analytics tools would flag this as dirty data. FlowMaster flags it as a diagnostic signal.
How it connects to my work
Transformation
The diagnostic grounds every engagement in evidence. Anomaly flags reveal broken incentives. Flow debt measures governance effectiveness. Bottleneck patterns expose structural constraints. The transformation starts with what the data actually says.
Learn more →Coaching
For executives: data-driven conversations about organisational health, not assumptions. For practitioners: a teaching instrument that builds flow literacy, analytical capability, and the skill of reading delivery data as a diagnostic tool.
Learn more →Speaking
Live demonstrations that show audiences their own patterns — not slides about theory. When you see anomaly detection flag systematic gaming in a real dataset, the conversation about power structures stops being abstract.
Learn more →