Presenters

Source

The Trap of Measurement: Why What You Measure Isn’t Always What You Manage 🚀

Have you ever heard the phrase, “What gets measured gets managed?” It’s a common refrain in leadership, echoing through engineering teams and beyond. While seemingly straightforward, this principle holds a hidden complexity. Today, we’re diving deep into why simply measuring something isn’t enough – and why it can even backfire.

The Naive View: Tracking Time and Actions ⏱️

The surface-level understanding of “what gets measured gets managed” often leads to initiatives like tracking employee time or counting the number of actions taken on a platform. The logic is simple: if you know where time is spent, you can optimize it. However, this approach is naive. It assumes measurement is neutral and doesn’t impact behavior. This isn’s true.

The Intervention: Measurement Changes Behavior 🎭

The core issue isn’t that measurement itself is bad, but rather that it’s an intervention. It triggers a response, a management action. When people realize they are being observed – even subtly – they change their behavior.

  • Gaming the System: Imagine tracking story points to measure velocity. Teams might inflate estimates to appear more productive, leading to a false reading. Or, they might deflate estimates to avoid looking less productive, creating a downward spiral.
  • Unintended Consequences: Focusing solely on metrics can distract from broader goals. A team might prioritize easily measurable tasks over more critical, but less quantifiable, work.
  • The Illusion of Control: Measurement can give the feeling of control, when in reality, it’s creating a complex feedback loop that’s difficult to predict.

It’s Not About Avoiding Metrics, It’s About How You Measure 🎯

So, what’s the solution? Don’t abandon metrics altogether! The key is to recognize measurement as an intervention and manage it strategically.

  • Collaborative Measurement: Instead of imposing metrics, involve the team in deciding what to measure. This fosters ownership and reduces the likelihood of gaming the system.
  • Focus on Outcomes, Not Just Actions: Shift the focus from easily quantifiable actions to broader outcomes. Instead of tracking the number of tickets closed, focus on customer satisfaction.
  • Continuous Inspection: Regularly review your metrics and their impact. Are they driving the desired behavior? Are there unintended consequences? Be prepared to adjust your approach.

Feeding vs. Starving: The Principle of Sustained Effort 💾

Jonathan Catrell highlights a powerful analogy: If you want something to survive, you feed it – you invest time, money, and attention. If you want it to die, you starve it. This applies to metrics too. Saying you care about something without actively measuring or investing in it is a recipe for failure.

Key Takeaways: A Framework for Thoughtful Measurement 🌐

  1. Measurement is Intervention: Recognize that any metric will influence behavior.
  2. Collaborate, Don’t Dictate: Involve the team in choosing what to measure.
  3. Focus on Outcomes: Prioritize metrics that reflect genuine progress.
  4. Inspect and Adapt: Continuously evaluate your metrics and adjust as needed.
  5. Feed, Don’t Starve: Actively invest in the things you want to see improve.

By embracing this nuanced perspective, we can move beyond the naive interpretation of “what gets measured gets managed” and create a framework for thoughtful, impactful measurement that truly drives positive change.

Appendix