Skip to main content

Jeff Bezos on the Problems With Proxies and Managing to Metrics!

13 min read Published Jul 16, 2026

Metrics help founders understand what is happening inside their companies.

They track customer acquisition, retention, revenue, product usage, support requests, returns, conversions, and dozens of other indicators. Without metrics, leaders would be forced to make important decisions based largely on assumptions.

But Jeff Bezos warns that metrics can also become dangerous when companies forget what those numbers were originally designed to measure.

“That metric isn’t the real underlying thing.”

A metric is often only a proxy—a measurable signal used to represent something more complicated.

Customer happiness, trust, loyalty, product quality, and employee engagement are difficult to measure directly. Companies therefore create numbers that help them estimate whether those outcomes are improving.

The problem begins when the organization starts caring more about improving the number than improving the outcome behind it.

For founders across the startup ecosystem in Canada, Bezos’s lesson is straightforward: use metrics, but never confuse the dashboard with the customer reality it is supposed to represent.

A Metric Is Usually a Stand-In for Something Else

Bezos uses the hypothetical example of a company tracking customer returns per unit sold.

At the time the metric is created, the reasoning may be sensible. A high return rate could suggest that customers are unhappy with the product, while a lower return rate could indicate better quality and stronger satisfaction.

But customer returns are not the same as customer happiness.

A customer may keep a product and still dislike it. Returning it may be inconvenient, expensive, or not worth the effort. Another customer might return an excellent product simply because they purchased the wrong size or selected the wrong model.

The metric offers useful information, but it does not tell the complete story.

That distinction is easy to understand when the metric is first introduced. The person who created it likely knows why it matters, what its limitations are, and how it connects to the larger business objective.

Over time, that context can disappear.

New employees join. The company grows. Reporting systems become more formal. Leadership begins reviewing the number every week or every quarter.

Eventually, the metric becomes the objective rather than a tool for understanding the objective.

How Metrics Become Detached From Their Purpose

Bezos explains that inertia can develop after a company has managed to the same metric for several years.

The organization continues measuring it because it has always been measured.

Teams build reports around it. Employees receive targets connected to it. Managers discuss it in meetings, and bonuses may depend on improving it.

But few people stop to ask why the metric exists.

Meanwhile, the world may have changed.

Customer expectations evolve. Technology creates new behaviours. Distribution channels shift. The company introduces new products or begins serving different audiences.

A metric that once provided a strong indication of customer happiness may now capture only a small part of the customer experience.

This is especially common in larger companies, where metrics can become deeply embedded in processes.

But startups are not protected from the problem.

A young company can quickly become focused on sign-ups, downloads, website traffic, follower counts, leads, or completed demos without understanding whether those activities are creating meaningful customer value.

The number may be increasing while the underlying business is becoming weaker.

Managing the Metric Can Produce the Wrong Behaviour

Once employees are evaluated according to a metric, they naturally search for ways to improve it.

That is not necessarily a problem. The difficulty arises when the easiest way to improve the metric does not improve the result it was intended to represent.

Suppose a company wants to reduce its customer return rate.

One team might improve product quality, write clearer descriptions, strengthen packaging, and provide better guidance before purchase. These actions could reduce returns while genuinely improving customer satisfaction.

Another team might make the return process more difficult.

The metric improves because fewer customers successfully return their purchases. But customers are now more frustrated, and trust in the company decreases.

The number looks better while the actual customer experience becomes worse.

This is a common risk when metrics become targets.

Teams begin optimizing what is visible and measurable, even when those optimizations damage the larger goal.

Founders therefore need to ask not only whether a metric is improving, but also why it is improving.

Do Not Confuse Activity With Customer Value

Startups often rely on activity-based metrics because they are easy to track.

A company might measure:

  • Website visitors
  • App downloads
  • Sales calls
  • Product demonstrations
  • Email subscribers
  • Social media impressions
  • Features released

These numbers can provide useful operational information. However, they do not automatically prove that customers are receiving value.

A product may generate thousands of downloads but have very few active users. A sales team may complete hundreds of calls without creating strong customer relationships. A product team may launch several features that customers never use.

Activity can create the appearance of progress.

Customer outcomes are what determine whether that progress matters.

Founders should connect activity metrics to questions such as:

Are customers staying?

Are they solving the problem that brought them to the product?

Are they willing to pay?

Are they recommending the company to others?

Would they be disappointed if the product disappeared?

A useful metric should make the company better at answering these questions.

Metrics Must Be Revisited as the Company Changes

A startup’s most important metrics will likely change as the business develops.

Before launch, the team may focus on customer interviews and problem validation.

After releasing an early product, engagement and retention may become more important. Once the company begins generating consistent revenue, customer acquisition cost, lifetime value, and profitability may receive greater attention.

A metric that is appropriate at one stage may become less useful at another.

For example, total user registrations may matter during the earliest phase of a consumer product. But as the company grows, active usage and retention could become much stronger indicators of product health.

Similarly, a business may initially measure the number of qualified leads generated. Later, it may discover that lead-to-customer conversion and customer lifetime value provide more meaningful information.

Founders should regularly review their dashboards and ask:

  • What business outcome is this metric supposed to represent?
  • Does it still reflect that outcome accurately?
  • Has customer behaviour changed?
  • Are teams manipulating the number without improving the customer experience?
  • What important information is the metric missing?

These questions prevent measurement systems from becoming permanent simply because they are familiar.

Combine Quantitative Data With Customer Reality

Metrics are strongest when they are supported by direct customer understanding.

A retention chart may show that users are leaving, but it cannot always explain why. Customer interviews, support conversations, reviews, usability testing, and sales feedback can reveal the causes behind the numbers.

The reverse is also true.

A few positive customer comments may feel encouraging, but quantitative data can show whether those experiences are common across the customer base.

Founders need both perspectives.

Numbers help identify patterns. Customer conversations provide context.

A business that relies only on anecdotes may misunderstand the size of a problem. A business that relies only on dashboards may miss the human experience behind the data.

When these sources disagree, leaders should investigate rather than automatically trusting whichever one supports their existing opinion.

What Startup Founders Can Learn From Bezos

Bezos’s warning offers several practical lessons for startup founders in Canada.

Define the outcome before selecting the metric

Begin with what the company genuinely wants to improve.

If the goal is customer happiness, decide what customer happiness looks like before choosing the numbers used to track it.

Record why each important metric exists

Document the original reasoning behind major metrics.

This makes it easier for future team members to understand what the number represents and recognize when it is no longer useful.

Review incentives carefully

Employees will usually respond to the targets they are given.

Before attaching bonuses or performance reviews to a metric, consider how someone might improve the number without improving the business.

Use multiple indicators

One metric rarely provides a complete view of a complicated outcome.

Customer happiness may require examining retention, complaints, referrals, support interactions, reviews, and direct feedback together.

Investigate sudden improvements

A better number is not always good news.

When a metric changes significantly, understand what caused the change and whether the underlying customer experience improved as well.

Keep listening to customers

Dashboards should support customer understanding, not replace it.

Direct conversations can reveal changes in expectations that the company’s existing metrics have not yet captured.

Use your founder network for perspective

A strong founder network in Canada can help entrepreneurs challenge the metrics they have become accustomed to watching.

Other founders, operators, mentors, and investors may notice when a team is celebrating activity rather than meaningful customer outcomes.

The most useful startup support for founders helps leaders question not only their results, but also how those results are being measured.

How Managing to Proxies Creates “Day 2” Thinking

Bezos connects poorly understood metrics to what he calls Day 2 thinking.

Day 1 organizations remain curious, adaptable, and focused on customers. They question assumptions and adjust as the world changes.

Day 2 thinking begins when process replaces purpose.

The company continues following systems because those systems already exist. Teams manage reports rather than reality. Decisions become slower, and the organization gradually loses contact with what customers genuinely need.

Managing to outdated proxies is one way this happens.

The company may appear disciplined because it has detailed dashboards, targets, and reviews. But if nobody understands why the numbers matter, that discipline becomes empty.

The business is measuring itself carefully without necessarily measuring the right things.

Avoiding Day 2 thinking requires leaders to repeatedly return to the underlying truth.

Why was this metric created?

What are we actually trying to achieve?

Does this number still help us achieve it?

When the answer is no, the metric should change—even when the organization has been using it for years.

Why This Matters to the Startup Ecosystem in Canada

The startup ecosystem Canada is building increasingly values data-driven decision-making.

That is a positive development. Founders need evidence to evaluate products, markets, campaigns, and investments.

But being data-driven does not mean following every number without question.

It means understanding what the data represents, where it is incomplete, and how it connects to customer value.

A metric should help founders see reality more clearly. It should not become a substitute for reality.

Startups have an advantage because they are usually smaller, faster, and less attached to long-established processes. Founders can change how they measure progress before outdated systems become deeply embedded.

The key is to remain alert.

Use metrics. Review them consistently. Hold teams accountable.

But never forget that the metric is only valuable when it helps improve the thing that truly matters.

In Bezos’s example, that thing is not the return rate.

It is customer happiness.