Why Every Delivery Lead Should Care About Flow Metrics

Let’s get this out of the way: if you’re a delivery lead and you’re not using Kanban metrics, you’re flying blind. I am aware that’s unexpectedly direct coming from me.. so bear with…

Sure, you might get the impression that things are going okay. Tasks are moving. Your velocity in story points looks good 🙄. People are busy. Your board “looks fine.” (What is fine?!) And let’s not forget my “favourite” phrase - “At least everything is in progress, so that’s good!”

But that’s not good!!

Without proper flow metrics, what you have is guesswork dressed up as process. It might be good enough for the theatre your organisation plays but that’s all it is. Guesswork doesn’t scale, especially when you still have to give a good answer to the question “When will it be done?”.

This is where Kanban metrics step in. And you already knew that but it’s just that getting good answers is… well, difficult. I know.

Tracking with purpose

Let’s copy a famous phrase and start with why?. Why do we track:

•  Spot problems before they escalate
•  Have meaningful conversations with stakeholders
•  Forecast with confidence
• Create a shared understanding of how work flows and where it gets stuck

Remember, we measure to reduce uncertainty. (See Douglas Hubbard’s work).

When used well, kanban metrics help you lead proactively. Instead of answering, “We’ll try to get it done.” to an arbitrarily chosen deadline, you can say, “There’s an 85% chance we’ll finish it by next Friday.” That’s reducing uncertainty the other one is giving (probably false) hope.

What Are These Metrics, Exactly?

Thanks to the hard work of many clever folks, we’ve now got access to some seriously useful flow-based insights. Here are ten key ones every delivery lead should know:
    1.    Work Item Age Tracking: See how long each item has been in progress.
    2.    Service Level Expectation (SLE) Visualisation: Show when something is “at risk” of taking too long.
    3.    Pull-Based WIP Control: Prevent overloading teams.
    4.    Flow Metrics Dashboard: At-a-glance view of cycle time, WIP, throughput, and aging.
    5.    Custom Workflow Definitions: Reflect your team’s actual process (not just “To Do / Doing / Done”).
    6.    Blocked Item Visualisation: Highlight what’s stuck, not just what’s in progress.
    7.    Forecasting with Historical Data: Use past cycle times to predict future outcomes (Monte Carlo style).
    8.    Ageing Risk Highlights: Call out items at risk of becoming “silent blockers.”
    9.    Work Item Breakdown Support: Make big things small before they derail timelines.
    10.    Pull Signals: Let the system tell you when to start new work (instead of a backlog sprint panic).

Each of these tools offers a view of your system, and collectively, they give you a full picture of how value is flowing (or not flowing) through your team.


Why This Matters (Especially in Real Life)

You’ve probably been in at least one of these situations:

• A card’s been “in progress” for 3 weeks, and no one can quite explain why, there’s just one thing after the other and it never ends. It’s one of those things, Sigh..
• You’re asked when a feature will be ready, and your only honest answer is, “It depends.” or worse you make your engineers have a guess.
• Half the team is busy, while the other half is waiting on blocked work and picking up even more work while waiting. It makes sense, right! Sigh…
• A stakeholder drops a last-minute request, and you have no data to show how that impacts your flow. So you stop other work and jump on it instead.

Kanban metrics help you respond with evidence, not just instinct. Instinct is great but instinct + data is better.

In the olden days I used to spend hours typing in numbers from the physical board and then piecing together timelines in spreadsheets. Now, I just pull up the flow metrics dashboard and the story tells itself.

Metrics are signals and prompts for conversations

When implemented well, Kanban metrics aren’t just about the numbers. They’re signals that should prompt a conversation:
    •    “Why is this item still in progress after 12 days?”
    •    “Should we pause new work until this ageing card gets resolved?”
    •    “If we keep this pace, we’ll miss our SLE, do we need to shift priorities?”

Mature teams will understand it and will value it. Others really need to grow up because these signals are essential for improving the flow of work. It’s about building awareness, creating alignment, and protecting focus.

In-Person or Remote? It Doesn’t Matter

Whether you’re running hybrid teams, fully remote squads, have AI workers or everyone’s huddled around a whiteboard in the same room , flow metrics still matter and still work. You just need to surface them regularly:
    •    Pin metrics to team dashboards
    •    Make them part of daily standups
    •    Use them in retros to highlight systemic issues
    •    Share forecasting visuals in stakeholder updates

They make the invisible visible.

What you’ll gain by using these metrics

• Leading indicators    
• Fewer surprises
• Faster feedback loops
• Better prioritisation decisions
• Improved team autonomy
• More realistic stakeholder expectations

In short: your job gets easier, your team’s work gets smoother, and your delivery becomes more predictable. Tell me your don’t want that?

TL;DR

If you want to stop firefighting, start leading with data. Kanban metrics don’t take over the process, they reveal where the process needs support.

And once you see the patterns? You won’t want to go back.

Ready for the deep dives? I’ll now work through ten short, practical posts, one for each Kanban metric. Each will include:
    •    Why it matters
    •    How to implement it (in-person & remote)
    •    A quick example from delivery life

Stay tuned > next up: ​Work Item Age - The Only Metric That Tells You the Truth