10 Metric Misuses to watch out for / call-out when observed

[#1]

Metrics are powerful—but only with a ‘growth mindset’ intention – that is to elevate, optimise, unlock and empower. When the intention comes from fear, they can be weaponised, undermining trust, demotivating teams, and distort decision-making.

Here are 10 anti-patterns, or misuses to watch out for and call out when you see it:

1️⃣ Vanity Metrics – Numbers that look good but lack real insight (e.g., lines of code). Focus on outcomes, not outputs.
2️⃣ Metrics as a Blame Tool – Using data to single out individuals erodes trust. Metrics should drive learning, not fear.
3️⃣ Ignoring Team Context – Not all teams are the same. Metrics should reflect their unique goals and challenges.
4️⃣ Overloading with Metrics – Too many data points create confusion. Prioritize a few key indicators that matter most.
5️⃣ Optimizing a Single Metric – Focusing on one number (e.g., velocity) can lead to unintended consequences like burnout.
6️⃣ Lack of Transparency – Withholding data from teams fosters distrust. Open access builds alignment and ownership.
7️⃣ Misaligned Incentives – Tying bonuses to specific metrics encourages gaming the system instead of true improvement.
8️⃣ Short-Term Thinking – Looking at metrics in isolation misses long-term trends. Watch for patterns over time.
9️⃣ Feature Factory Mentality – Prioritizing output over quality and team well-being leads to burnout and high turnover.
🔟 Ignoring Feedback Loops – Metrics should evolve with teams. Regularly review and adjust based on real outcomes.

The takeaway? Metrics should guide improvement, not control behavior. Balance quantitative data with qualitative insights, and always focus on the inputs that create great outcomes.

What’s your experience with metrics in DevEx? Which of these anti-patterns have you seen?

[Christine Kihanya]

So sensible. I've definitely seen the vanity metrics used alot and while they're impressive, they don't tell the story.

[Luis Ortiz - Catapult Labs]

Metrics should be a tool for growth, not a mechanism for fear or control.
We’ve seen firsthand how the wrong approach to metrics can lead to unintended consequences—teams optimizing for velocity alone, focusing on output over impact, or even feeling pressured to "game the system" to meet arbitrary targets.

One of the most powerful ways to counteract these anti-patterns is by creating continuous feedback loops where teams can reflect not just on the numbers, but on the why behind them. For example, retrospectives that integrate both quantitative metrics and qualitative insights help teams understand the bigger picture—what's working, what’s not, and how they can adapt without feeling micromanaged.

How do teams using Atlassian balance data-driven decision-making with maintaining trust and motivation? Would love to hear what’s worked for other teams.