HomeResourcesMental modelsClimbing the Wrong Hill

Climbing the Wrong Hill

Greedy improvements can trap you on a nearby peak; sometimes you must go down or sideways to reach a higher hill.
Author

Chris Dixon (popularised, 2009); roots in optimisation (hill-climbing / simulated annealing)

model type
,
about

Chris Dixon’s 2009 essay uses the computer-science idea of hill-climbing to explain why smart people and teams can get stuck pursuing the “closest” improvement instead of the best opportunity. The more rugged the landscape, the likelier you are to stall on a local maximum unless you periodically explore new starts or allow short-term setbacks. 

How it works

Fitness function – the metric you’re optimising (conversion, margin, learning). It defines the “hill” you’re on.

Local vs global optimum – hill-climbing takes the best immediate step; it often stops at a local peak. 

Rugged landscapes – many peaks/valleys from constraints and complementarities; easy to get trapped.

Exploration vs exploitation – balance small safe gains with periodic broad searches.

Escaping traps – new start points, bigger moves, or simulated annealing: occasionally accept a worse move to find a taller hill. 

Path dependence – early choices narrow later options; switching costs can keep you on the wrong hill.

use-cases

Product & UX – A/B tests that yield tiny wins around a weak concept; try concept resets or new acquisition channels.

Strategy – stuck in a crowded segment; sample a different segment, model or distribution play.

Pricing & packaging – legacy tiers create a local maximum; test new bundles/metrics.

Operations – process tweaks hit a ceiling; re-sequence work, shrink batches, alter hand-offs.

Career design – “good job, wrong hill”; accept a short dip to move to a higher trajectory.

How to apply
  1. Choose N restarts (e.g. 5–10) in distinct starting regions – different ICPs, channels, bundles, tech approaches.
  2. Run a short local climb on each start for a fixed budget (e.g. 2–4 sprints), optimising locally without cross-contamination.
  3. Measure peaks on a common horizon (same window and metric to avoid early-spike bias).
  4. Select the best hill – commit resources there and continue local optimisation.
  5. Repeat periodically (quarterly or at big regime shifts) to avoid being trapped on a local maximum.
pitfalls & cautions

Wrong metric – optimising a proxy that doesn’t map to the mission.

Premature convergence – declaring victory on a low hill because micro-tests “win”.

Under-exploration – never sampling the better region; over-protecting the current curve.

Over-exploration – thrash from constant resets; burn focus without compounding.

Ignoring switching costs – the higher hill exists, but the valley crossing bankrupts you.