In my calls and your emails, I see similar patterns. The angst of metrics rarely comes from the metric itself… it people stress about what the metric says about them or their job.
In the case of design work, that means moving away from pure evaluation and toward momentum of making quick decisions with intuition (yes, intuition and metrics work together).
→ Measurement feels like support, people will open up.
→ Metrics that feel like judgment, they shut down or meander
Here’s a way to look at this (problems based on many of my email exchanges)
Start with business goals, not dashboards
Teams will get in a better rhythm when conversations start with the result they want. Work backward to the signals that help them get there.
Make metrics shared (try not to own them)
If design, product, and engineering all influence an outcome, then no single team has to defend it alone. This removes a lot of fear.
Track metrics that show progress
Trying to be perfect doesn’t work. Things like clarity, comprehension, effort, and sentiment help people see forward movement before the big results show up.
Treat numbers as a learning tool.
I like to say we paint with numbers. When a metric is framed as an early warning system, you start to see it as an early warning sign to prevent pain rather than expose failure.
In my experience, people buy into measurement the moment it helps them move faster. especially when it helps avoid surprises and argue less.
Once they feel that lift (sorry, disney plug for nathaliesmith), the fear fades. In our work, that usually takes a couple weeks of solid iteration to get the hang of it.
Which leads me to, how do you frame measurement in your org so teams actually want to use it?
