Measuring What Matters

The Danish Assumption

Barry was born in Denmark, a country where digital-first isn't a strategy. It's just how things work. Danes trust apps. They trust digital invoices. When Barry showed them a beautiful in-app billing breakdown with animated charts and real-time usage data, they loved it.

So when we expanded to France, we brought the same product. Same sleek interface. Same digital-only invoices. Same assumption that modern meant better.

Our metrics looked fine at first. App downloads were strong. Activation rates were healthy. The few satisfaction surveys we sent showed decent scores. The product team was confident.

Then the support tickets started piling up.

The Wake-Up Call

In one month, our operations team received over 400 requests for PDF invoices alone. That's not a feature request. That's a fire alarm.

What We Were Actually Measuring (And Why It Failed)

Let me be honest: we were measuring vanity metrics. App store ratings. Feature adoption percentages. Time spent in app. Numbers that made dashboards look green but told us nothing about whether we were actually helping people.

We were so proud of our digital invoice that we never asked whether customers could actually use it for what they needed.

The problem with metrics like NPS or CSAT is that they measure willingness to answer a survey, not actual life improvement. A customer might give you a 7 out of 10 while simultaneously being unable to prove to their landlord that they live at their apartment—because your app doesn't generate the document they need.

We were measuring the interface. We should have been measuring the outcome.

The Three Fires We Didn't Know Were Burning

When we finally sat down with our support data—really sat down, reading tickets one by one, calling customers back, listening—we found three massive problems hiding behind our green dashboards:

1. The PDF Invoice Crisis: 34% of all tickets French customers needed official PDF invoices as proof of accommodation for banks, employers, and government offices. Our digital-only approach made this impossible.

2. The Bill Breakdown Mystery: 28% of all tickets Customers couldn't understand their charges. Our summary view was clean but too abstract—they wanted line-by-line details to verify they weren't being overcharged.

3. The Dynamic Pricing Confusion: 22% of all tickets Hourly price changes were normal in Denmark but completely foreign to French customers. They didn't understand why their rate fluctuated—or how to benefit from it.

84% of our support load came from three problems. Three problems we could have caught if we'd been measuring the right things.

The Cultural Blindspot

Here's what we learned about the difference between Danish and French customers—and why it matters for any product expanding across cultures:

🇩🇰 Denmark	🇫🇷 France
Digital documents are legally accepted everywhere. High institutional trust. Customers comfortable with dynamic systems. Energy market liberalized for decades.	Paper documents still required for many official processes. Lower trust in new digital services. Fixed pricing is the norm. Dynamic energy pricing was brand new.

The PDF invoice wasn't a "nice to have." For French customers, it was essential infrastructure. Without it, they couldn't rent apartments, open bank accounts, or complete administrative procedures. We'd built a product that literally prevented people from participating in normal life.

And we had no metric that captured this.

Redefining Success

We threw out our old dashboard and started over with a simple question: What would actually make our customers' lives better?

Not "satisfied." Not "engaged." Better.

For an electricity customer, that meant:

• Administrative freedom: Being able to prove they live where they live
• Financial clarity: Understanding exactly what they're paying for
• Economic control: Knowing how to save money with dynamic pricing
• Independence: Solving problems without calling support

So we built new metrics around these outcomes:

The Redesign That Mattered

With clear problems and meaningful metrics, the solutions became obvious:

1. Official PDF Invoices We added a single button: "Download invoice" It generated a properly formatted document that met French administrative requirements—complete with all the legal details that institutions needed to see.

• One-tap download from billing screen
• Automatic email option for monthly invoices
• Format validated against French administrative requirements

2. Extended Bill Breakdown We kept the beautiful summary view but added an expandable "See full details" section. Every charge, every tax, every fee—explained in plain French, not energy-industry jargon.

• Expandable line-by-line breakdown
• Plain language explanations for each charge type
• Comparison with previous month built in
• Visual indicators for unusual charges

3. Dynamic Pricing Education This was the biggest lift. We couldn't just show prices—we had to teach an entirely new concept. We rebuilt the pricing planning screen and added contextual explanations throughout the app.

• Daily price forecast with plain-language recommendations
• "Best times to use electricity" widget on home screen
• "Why is my rate different?" contextual tooltips
• Monthly savings summary showing dynamic pricing benefits
• Interactive onboarding explaining dynamic pricing

The Results

We rolled out the changes over six weeks. Here's what happened:

But the number I'm most proud of isn't on that dashboard. It's this: zero customers have contacted support for a proof-of-residence document since launch.

That's not a metric most companies track. But it represents hundreds of people who were able to sign leases, complete paperwork, and get on with their lives—without us getting in the way.

What I Learned

Some of these seem obvious in retrospect. That's usually how the best UX lessons work.

Measure life outcomes, not interface interactions. "Can customers prove they live at their address?" is a better metric than "Do customers rate the billing screen 4+ stars?"

Support tickets are research data. Every ticket represents a failure to anticipate a real need. Read them. Call customers back. The patterns will show you what your metrics are missing.

Cultural context isn't a localization checkbox. It's not about translating strings. It's about understanding what your product means in someone's actual life. A digital invoice means something different in Copenhagen than in Lyon.

Features that seem unnecessary might be infrastructure. We thought PDF export was outdated. For French customers, it was the difference between being able to rent an apartment or not.

Education is a product feature. When you're introducing something genuinely new (like dynamic pricing), explanation isn't documentation. It's core UX.

The Bigger Picture

There's a tendency in product design to optimize for elegance. We strip away features, simplify interfaces, remove friction. And often that's right.

But sometimes what looks like friction is actually function. Sometimes the "outdated" thing (the PDF, the detailed breakdown, the explanatory text) is exactly what makes a product usable in someone's real life.

We weren't designing for users. We were designing for an imaginary user who lived in Denmark, trusted digital systems, and already understood dynamic energy pricing. That user didn't exist in France.

The lesson isn't "always add invoice download." The lesson is: your metrics should measure whether you're helping people live their lives, not whether they're clicking the buttons you want them to click.

When we started measuring what actually mattered, administrative success, financial clarity, genuine understanding, the right design decisions became obvious. The support tickets disappeared. And for the first time, we could honestly say our French customers loved the product.

Not because they gave us good survey scores. Because they stopped needing to call us.