2
1 Comment

Your measurement system determines which problems you can actually see

I've been thinking about a question one of you asked recently: how do you decide what to optimize vs what to investigate?

The answer is usually determined by something you don't consciously choose - your measurement system.

Three months into a project, you're looking at a dashboard. The metrics on that dashboard feel like facts - this conversion rate is real, this churn is real. But they're not facts. They're the output of every decision you made about how to measure.

Someone built the funnel. Someone picked those utm parameters. Someone decided when signup actually counts. Someone configured the analytics.

Those decisions were made months ago when you knew less. And now they're invisibly steering what you can see and what you can't.

Last week I saw a post where the founder spent a whole week reading a dashboard that couldn't possibly show them a signup, because the goal never fired. The analytics worked perfectly. The measurement system was perfectly broken.

You can't see what you don't measure. And you can't measure what you don't think to instrument.

So the real work isn't optimizing against your metrics. It's periodically asking - what am I not measuring? What problems exist outside my dashboard?

That's where customer conversations matter. Not as a tactic, but as a diagnostic tool. The person who actually uses your product will see problems your metrics can't show you. Not because they're smarter - because they use a completely different measurement system (called reality).

The switch is simple: stop trusting the dashboard more than you trust the person in front of you. Measure what the person shows you, then update your system.

on August 6, 2026
  1. 1

    This resonated with something I ran into while building a WordPress product. We kept refining what we measured, but eventually realized the harder question to me was "What assumptions are our measurements quietly making?"

    The dashboard always looked objective because the numbers were real. But the choice of what counted, what was ignored, and where events were instrumented had already shaped what we were able to notice.

    I really liked your reminder that customer conversations aren't competing with dashboards but they're often what reveals the parts of reality the dashboard was never designed to see.