Introducing a new metric should be straightforward. After all, you’re simply trying to help the team better understand how work flows through the system.
Yet many Scrum Masters know it rarely feels that simple. The moment a new chart appears, the questions begin.
“Why are we measuring this?”
“Who is going to see these numbers?”
“Is this going to be used to evaluate us?”
If you’ve ever heard questions like these, you’re not alone. They reveal something important.
The challenge usually isn’t the chart on the screen. It’s everything people believe that chart represents. Before teams can use delivery data to improve, they need confidence that it won’t be used to judge them. That’s where many well-intentioned measurement initiatives succeed or fail. Teams don’t resist metrics. They resist what metrics have represented.
It’s easy to conclude that a team “doesn’t like metrics.” In reality, that’s rarely true.
Most teams are naturally curious. They want to understand why work takes longer than expected. They want to know why some items move smoothly while others seem to sit still. They want to become more predictable. What they don’t want is to feel like every chart is another way to evaluate their performance.
Many teams have experienced delivery data being used to compare people, rank teams, explain missed deadlines, or justify performance decisions. Even if your intention is completely different, those past experiences don’t disappear the moment you open a dashboard.
People don’t just see a chart. They see the history that comes with it.
As a Scrum Master, it’s worth remembering that you’re not introducing metrics into a blank environment. You’re introducing them into a team that already has experiences, assumptions, and expectations about measurement.
Recognizing that changes the conversation before you’ve even shown the first chart.
Explain the purpose before you explain the metric
One of the most common mistakes is jumping straight into what the metric measures.
“We’re going to start looking at Cycle Time.”
Technically, that’s correct. But it doesn’t answer the question people are actually asking.
They’re not wondering what Cycle Time means. They’re wondering why it matters.
Instead, begin with the problem you’re trying to solve.
For example:
“Over the last few Sprints, we’ve noticed that some work is taking much longer than expected. Rather than relying on opinions or memory, I’d like us to understand what our delivery data is telling us so we can learn from it together.”
Now the conversation feels different. The metric isn’t the objective, learning is.
When people understand the purpose, they’re far more likely to see the chart as a tool rather than a judgment.
Good metrics improve systems
One of the healthiest mindset shifts a Scrum Master can make is remembering that metrics exist to help us understand the system. Not the individuals working within it.
Flow metrics naturally encourage that perspective because they focus on how work moves.
Questions like these lead to productive discussions:
Notice what those questions don’t ask.
They don’t ask who’s working the hardest.
They don’t ask which developer is the fastest.
They ask how the system is behaving.
Imagine your team’s Cycle Time increases. The least useful question is:
“Who caused this?”
The insightful question will be:
“What changed?”
Perhaps work has become more complex, reviews are taking longer, priorities are changing more frequently, or too much work is in progress at the same time.
The data points you toward the conversation. It doesn’t replace it.
Remove uncertainty before it creates resistance
One of the simplest ways to build trust is to be explicit about what the metrics won’t be used for.
Don’t assume everyone already knows.
Say it out loud.
For example:
Instead, they’re there to help us understand how work flows so we can improve it together. That simple conversation removes uncertainty before uncertainty turns into resistance.
Curiosity is more valuable than certainty
One of the biggest mistakes teams make is treating charts as answers. They’re not. Instead, they’re evidence. Imagine your Aging Work chart suddenly shows more work sitting in progress than usual. It’s tempting to conclude that delivery is slowing down.
Instead, become curious.
Has the nature of the work changed?
Have new dependencies emerged?
Are reviews taking longer than they used to?
Have priorities shifted?
The chart tells you something has changed. The team helps you understand why. The best Scrum Masters don’t use data to prove a point. They use it to ask better questions.
Let the team discover the insights
It’s easy for Scrum Masters to become the narrator of every chart. Resist that temptation.
Instead of immediately explaining what you see, ask the team first.
“What stands out to you?”
“What surprised you?”
“What do you think is happening here?”
You’ll often hear perspectives you hadn’t considered. More importantly, people are far more likely to trust conclusions they’ve helped reach than conclusions they’ve simply been given.
That’s when the charts stop feeling like reports and start becoming shared tools for learning.
Trust is the first metric that matters
We often focus on improving predictability, reducing Cycle Time, or limiting work in progress.
Those are all worthwhile goals. But none of them happen without trust. If people believe the data exists to judge them, they’ll naturally protect themselves. If they believe it exists to help the team learn, they’ll engage with it honestly.
The charts don’t change.
The data doesn’t change.
What changes is the environment in which the data is introduced.
Trust is the first metric that matters.
Because when trust is present, delivery data becomes more than information.
It becomes the starting point for better decisions, stronger collaboration, and continuous improvement.
Building trust doesn’t end with introducing your first metric.
It’s something you strengthen through every conversation, every retrospective, and every decision your team makes together.
If you’d like practical guidance on putting these ideas into action, download our free Scrum Master’s Guide to Metrics That Build Trust.
Inside, you’ll learn how to:
Because the goal has never been to collect more metrics.
It’s to help teams learn, improve, and deliver with confidence.
👉 Download the free Scrum Master’s Guide to Metrics That Build Trust.