Stop Watching the Scoreboard. Watch the Game.

The metrics hiding in plain sight that tell you where you’re headed — before you get there

Photo by Vanburn Gonsalves on Unsplash

Most teams I’ve worked with are excellent at looking backwards.

End of sprint — count the points. End of quarter — compile the report. Something goes wrong — trace back through the timeline to find where it started. There’s a whole ritual around it. Color-coded dashboards, burndown charts, sprint summaries. All of it pointing at what already happened.

And I get it. Those numbers are there. They’re clean. They don’t require you to argue about interpretation. The sprint ended, here’s what got done, moving on. But here’s what I kept noticing — by the time those numbers showed a problem, we were already living inside the problem. The metric wasn’t a warning. It was a verdict.

I remember a particular sprint — deep into a product release cycle — where everything looked fine on paper. Velocity was steady. The burndown was tracking. Nobody was raising flags. But if you were actually in the team, you could feel something shifting. Conversations in standups were getting shorter. People were giving quick “all good” updates and logging off. Pull request reviews were taking longer than usual, piling up quietly. A couple of people had stopped pushing back in planning — not because they agreed, but because they’d learned it didn’t change anything.

The lagging metrics didn’t catch any of that. The sprint closed out fine. The numbers looked fine.

Two sprints later, the team was exhausted and two of our strongest people had started quietly updating their CVs.

No dashboard caught it. Because we weren’t measuring the right things.

That experience is what pushed me toward leading indicators — and honestly, toward a completely different way of thinking about what measurement is even for.

Leading indicators don’t measure what happened. They measure what’s building. They’re the early tremors before the earthquake — quieter, harder to point to, but far more useful if you’re paying attention.

The tricky part? They’re rarely on the standard Agile reporting template.

Here’s what I’ve learned to watch instead:

• How fast is work actually moving? — Not how much got done, but, how long did individual pieces of work sit waiting? A story that spends three days in “In Progress” and two days in “In Review” before anyone picks it up isn’t a velocity problem. It’s a flow problem. And flow problems are fixable, once you can see them.
• How often are we getting interrupted mid-sprint? — Every unplanned item that lands in a sprint mid-cycle is a signal. One or two? Normal. Consistently five or six? That’s not a planning problem. That’s a boundary problem, or a stakeholder expectation problem, or both. The frequency of mid-sprint disruption tells you more about a team’s real working environment than any end-of-sprint report.
• Are people actually talking to each other? — This one sounds soft. It isn’t. The quality and texture of conversation in a team — in standups, in retrospectives, in planning — is one of the most reliable leading indicators I’ve found. When people start shortening their answers, hedging their estimates, going quiet in retros… something is wrong upstream. The numbers won’t show it yet. The conversation already has.
• What’s the ratio of new work to finished work? When teams are pulling in more than they’re completing, WIP creeps up silently. It doesn’t explode overnight. It accumulates. And by the time you see it in your throughput numbers, you’re already managing the backlog of a team that’s been underwater for weeks.

None of these are on a standard report. Most of them require you to actually watch — to be present in the work, not just summarizing it afterward. That’s uncomfortable for some organizations. Watching the game is slower than reading the scoreboard. It requires judgment. It requires conversation. It doesn’t produce a neat slide.

BUT, it’s the difference between seeing where you’re going and finding out where you’ve been.

The shift I’d encourage isn’t to throw out your lagging metrics — they still have value. It’s to STOP treating them as your primary signal. Use them to confirm what your leading indicators already suggested. Let the scoreboard validate what you saw in the game, not surprise you with news you could have had weeks earlier.

Something to try this sprint — Pick one leading indicator your team isn’t currently tracking. Flow time, unplanned work frequency, WIP ratio — anything that lives upstream of your usual metrics. Watch it for two sprints without making it official. See what it tells you that your current dashboard doesn’t. Then decide if it belongs on the WALL.