Flow metrics dashboards: The repeating story of visibility without decision-making

Most delivery organisations don’t lack data. In fact they swim in data.

What they lack is understanding what to do with the data. To quote Douglas Hubbard "we should care about a measurement because it informs key decisions”​

But it is rare to come across an organisation that understands well why they measure in the first place.

In recent years it has become easy to create dashboards. They are everywhere, beautiful colours, impressive charts, etc. And yet, despite all this “visibility”, the same problems keep repeating: work gets stuck, forecasts fail, and escalations become the norm.

That’s because most dashboards are not built to support action. They are built to make someone look good.


Dashboards don’t improve flow


They can be pretty and easy to put together.

But a dashboard will not improve delivery on its own.

Instead, what improves delivery is:
    •    noticing issues early,
    •    agreeing it matters,
    •    and doing something different as a result.

If your dashboard doesn’t change behaviour, then it is decorative.

Worse, it can create the illusion of control while actively preventing intervention. People assume that because something is “being tracked”, it is also being managed. But often, it isn’t.


The most common dashboard failure mode


Most status dashboards answer the wrong question.

They answer: “How are we doing?”

What delivery leaders actually need answered is:

“Where should I be paying attention right now?”

That difference makes all the difference.

A dashboard that summarises last month’s averages is useful for looking back. It is nearly useless for managing work in progress.


Why organisations love charts that don’t hurt


There’s a reason dashboards gravitate toward:
    •    average cycle time
    •    throughput trends
    •    cumulative flow diagrams
    •    historical distributions

These charts are safe because

• They don’t point at specific items.
• They don’t force uncomfortable conversations.
• They don’t require immediate decisions.

And also, they don’t stop things going wrong.


What a flow dashboard is actually for


A proper flow metrics dashboard exists to support “right action, right time”, not reporting.

That means it must:
    •    surface current risk
    •    make delays obvious
    •    highlight where flow is breaking down
    •    invite action rather than explanation

This is why we (kanban practitioners) insists on a small, specific set of flow metrics. Not because they’re academically pure, but because they’re operationally useful.


The four metrics that matter (and why)


A flow dashboard should be anchored around four measures:
    •    Work Item Age – What is at risk now
    •    Cycle Time – What “normal” looks like
    •    WIP – How much has been started
    •    Throughput – How much actually finishes

Everything else is secondary.

These four metrics exist because together they allow you to reason about flow in real time.
Not when it’s already too late.


Why CFDs are so often misused
​

Cumulative Flow Diagrams deserve a special mention, because they are widely misunderstood.

CFDs are excellent for:
    •    spotting long-term stability issues
    •    identifying structural bottlenecks
    •    analysing systemic change over time

They are not so excellent for:
    •    managing individual items
    •    spotting immediate delivery risk
    •    deciding what to do today


And yet, many teams stare at CFDs during daily discussions, hoping insight will magically emerge.

Actually that’s a little unfair. There are other teams that don’t even stare at CFDs or anything else remotely useful.

However CFDs explain why things happened. They don’t tell you what to fix right now.


Dashboards should point


A good flow dashboard should feel slightly uncomfortable.

It should make it obvious that:
    •    certain items are ageing too long
    •    WIP is crowding a part of the workflow
    •    forecasts are becoming less reliable
    •    blocked work is being tolerated

If someone can look at your dashboard and say “interesting” without feeling any urgency, then your dashboard is not doing a good job.


When Everything Is Green, that means your thresholds are wrong

Another common anti-pattern: dashboards that never show problems. When I say dashboard I also include manually created reports. I’ve worked with many managers who always make the reports look nice and not showing any issues.
If nothing ever looks risky, then one of three things is true:
    1.    You are genuinely perfect (unlikely)
    2.    Your thresholds are meaningless
    3.    You’ve designed the dashboard to avoid discomfort
Flow metrics only work when they create tension between what is happening and what you want to happen.

When there is no tension, there is no improvement.


Dashboards are for leaders


Teams should use flow metrics to manage work.
Leaders should use flow metrics to manage decisions.

A delivery leader should be able to look at a dashboard and immediately see:
    •    where intervention is needed
    •    which risks require escalation
    •    what trade-offs are becoming unavoidable

If your dashboard does not make these signals obvious then it must be improved before it can be useful..


The real test of a flow dashboard

Here’s the simplest test you can try.


After your next dashboard review, ask the following question

“What decision did we make today, that were different because of what our dashboard is showing?”

If the answer is “none”, then your dashboard needs improvement. It might be well-intentioned, beautifully presented, etc. but it may not be as useful as it can be.


Visibility is only valuable when it enables action


Kanban is not about transparency for transparency’s own sake. It’s about enabling better decisions earlier, with fewer surprises and time and space to correct flow.

Flow dashboards exist to reduce the time between signal and response.

In the next post, I’ll look at Custom Workflow Definitions, and why inaccurate workflows quietly invalidate every metric you collect, regardless of how good your dashboard looks.