Rethinking Success: Are You Optimizing for the Wrong Metrics?
- Nidhi Sharma

- Feb 2
- 4 min read
Updated: Feb 4
Success often feels like a straightforward goal: hit your targets, deliver results, and move forward. But what if the problem isn’t your performance?
What if you’re simply optimizing for the wrong thing?
I’ve seen many teams and leaders struggle, not because they lack skill or effort, but because they focus on metrics that don’t truly reflect progress or value. This post explores how to identify when you’re optimizing for the wrong metrics and how to shift your focus to what really matters.

Why Metrics Matter More Than You Think
Metrics guide decisions. They tell us whether a project is on track, whether a product is meeting user needs, or whether a team is performing well. But not all metrics are created equal. Some measure activity rather than impact. Others reflect vanity rather than value. When you optimize for the wrong metrics, you risk:
Wasting time on tasks that don’t move the needle
Misleading stakeholders about real progress
Demotivating teams who feel their efforts don’t translate into meaningful outcomes
For example, a delivery lead might focus on the number of completed tasks per sprint. While velocity is important, it doesn’t always reflect whether those tasks deliver customer value or solve real problems. Similarly, a product manager might track downloads or sign-ups without considering user engagement or retention. These are classic examples of vanity metrics data points that look impressive but don’t provide actionable insights into business performance.
Signs You’re Optimizing for the Wrong Metrics
Recognizing the problem is the first step. Here are some common signs:
Metrics improve, but outcomes don’t: Your numbers look good, but customer satisfaction, revenue, or team morale stay flat or decline.
Teams focus on hitting targets rather than solving problems: People chase metrics instead of understanding why those metrics matter.
Stakeholders question the value of delivered work: If your reports show progress but stakeholders remain unconvinced, it’s a red flag.
Metrics encourage gaming or shortcuts: When teams find ways to boost numbers without real improvement, the metric is flawed. This phenomenon is captured in Goodhart’s Law, which states: “When a measure becomes a target, it ceases to be a good measure.” Originally formulated by British economist Charles Goodhart, this principle warns that optimizing for a metric often undermines its usefulness as an indicator of real progress.
How to Identify the Right Metrics
Choosing the right metrics starts with clarity about your goals. Ask yourself:
What outcomes truly matter to our customers or users?
Which metrics reflect those outcomes directly?
Are these metrics actionable and understandable by the team?
Do they encourage behaviors aligned with our mission?
For example, instead of tracking the number of features released, focus on user adoption rates or customer feedback scores. Instead of measuring hours worked, track cycle time or lead time to understand efficiency. As John Doerr emphasizes in Measure What Matters, effective goal-setting requires focusing on outcomes that truly matter, not just outputs that are easy to count.
Practical Steps to Shift Your Focus
Map metrics to outcomes
Involve your team
Use qualitative data
Review and adjust regularly
Avoid metric overload
Velocity is a popular metric. But velocity alone doesn’t guarantee value delivery. One team I worked with shifted from tracking story points completed to measuring customer satisfaction after each release. This change helped them prioritize features that users actually wanted, improving both morale and business outcomes.
In IT delivery, uptime and incident counts are common metrics. But focusing only on uptime might ignore user experience during slowdowns or partial outages. Adding metrics like mean time to recovery (MTTR) and a user-reported issues-balanced view of system health provides a balanced view of system health.
Avoiding Common Pitfalls
Don’t confuse activity with progress. Just because a team is busy doesn’t mean they’re effective.
Beware of metrics that encourage short-term thinking at the expense of long-term goals.
Avoid metrics that are easy to measure but hard to influence.
Don’t ignore the human side. Metrics should support, not replace, conversations and judgment.
Final Thoughts: Making Metrics Work for You
The metrics you choose shape the work you do and the outcomes you achieve. When you optimize for the wrong metrics, you risk wasting effort, misleading stakeholders, and demoralizing teams who sense their work isn’t creating real value.
But when you focus on the right metrics, those that reflect genuine outcomes and align with your mission, you create clarity, drive meaningful progress, and build trust with both your team and your stakeholders.
Start by asking yourself: What outcomes truly matter? Which metrics reflect those outcomes most directly? And are my current metrics encouraging the behaviors that lead to success?
The answers to these questions will guide you toward metrics that matter. And when you measure what matters, you create the conditions for real, sustainable success.
References and Further Reading:
Goodhart’s Law and Metrics Optimization:
- Goodhart’s Law (Wikipedia) - Understanding how metrics become targets and lose effectiveness
- The Four Flavors of Goodhart’s Law (Holistics) - Deep dive into different types of metric gaming
- What is Goodhart’s Law? (Splunk) - Practical applications in business and technology
Measuring What Matters - OKR Framework:
- Measure What Matters by John Doerr - The definitive guide to Objectives and Key Results
- What Matters (whatmatters.com) - Official OKR resources and examples
- OKRs Guide (Asana) - Practical implementation of the OKR methodology
Vanity vs. Actionable Metrics:
- Vanity Metrics vs Actionable Metrics (UserPilot) - Understanding the difference in SaaS contexts
- Vanity vs. Actionable Metrics in Marketing (ClicData) - How to identify metrics that drive decisions
- What Are Vanity Metrics? (Mailchimp) - Identifying misleading data points





👍