GoodRead

Global by Design: Why the Hardest Constraints Make the Best Products

Start with the toughest price and performance constraints, solve them from first principles, and the result can travel upward into wealthy markets. My review of Global by Design by Amos Winter and Vijay Govindarajan, with the three merits test and the engineering habits worth stealing.

Amos Winter and Vijay Govindarajan, Harvard Business Review Press, 2026. My rating: 4 out of 5.

Most of us were taught to build for the rich market first and strip features to reach everyone else. Defeaturing looks like the obvious way to make a product viable in a price sensitive market. Winter and Govindarajan argue for the opposite. Start with the toughest price and performance constraints, solve those from first principles, and the result can travel upward into wealthy markets. They call this reverse innovation.

The book draws lessons from Gillette, Mahindra and Mahindra (Roxx), Tata (nano), GE (CT scanner for India) and many others, and it does not stop at success stories. It also covers the failures, the challenges behind them and what each one taught, which makes it a framework to work from and not a collection of cherry-picked wins. Several of those challenges still need practical solutions from the reader, and that is where I spent most of my time.

The innovation gap

The authors plot price against performance. Emerging markets often ask for a very low price and very high performance, a point far from what existing technology delivers. I have seen this in the market for many years. Customers want the best of every specification at the cheapest price in the market. I always found that absurd, questioned the rationale, and spent years fighting to sell the value of a high priced solution. Then I realised that a product designed with conventional lenses will fall short of customer expectations and will fail to scale. The space between that target and the current technology curve is the innovation gap. De-featuring a product only slides it down the same curve and costs reliability, so the book asks for a jump to a new curve, built on two kinds of insight together: socioeconomic (how people live and work) and technical (the physics and cost drivers behind the problem).

Price against performance chart. Existing technology curve rises steeply. A target point sits at the required performance and price ceiling, below the curve, and the vertical distance between them is the innovation gap.
The innovation gap: the distance between existing technology and the price and performance a target market requires.

The anchoring example is the Leveraged Freedom Chair, an all-terrain wheelchair with a lever drivetrain made from bicycle parts. Users slide their hands along the levers to change the mechanical advantage, so the person acts as the gearbox. Repairs stay local, and the same architecture later returned as the GRIT Freedom Chair for the US market.

Three merits before any design work

A project earns attention only if it has problem merit, innovation merit and value merit.

  • Problem merit: the problem is well defined, solvable at scale and worth solving, and it is stated without a preferred solution. “Build a low-cost laptop” fails this test. “Educate children at scale in low-resource settings” passes.
  • Innovation merit: no adapted or de-featured version of an existing product can meet the target.
  • Value merit: every stakeholder in the chain, from customer to manufacturer to retailer to investor, gains something. The authors call matching these interests “exploring the and space.” Where interests conflict, the “or space,” products such as clean cookstoves and free wheelchairs end up unused.

In our own project intake, each proposal is scored on strategic alignment and on risk across four pillars (financial, technological, logistical and people), product management fills the sheet, and NPD team then confirms doability. The three merits ask different questions: whether the problem has been framed without a solution in mind, and whether an adapted design could already meet the target. Those are the two I want to check our sheet against.

Requirements before solutions

The design chapters insist on defining requirements independent of the solution. The Reinvent the Toilet campaign shows the cost of ignoring this: the real requirement is to stop people ingesting pathogens, and the name narrows the search to toilets. The Tata Nano shows the secondary-requirement version. The team optimised for the cheapest car and missed that buyers did not want to be seen owning one. The authors group such surprises as unknown unknowns that appear as secondary effects, outside the core performance spec.

Engineering habits from the middle chapters

  • Back-of-the-envelope math before investment. A bicycle-powered home generator, for example, cannot meet its claimed output given how much power a person can sustain.
  • The parts bin. Past designs that are already amortised, colleagues’ knowledge and off-the-shelf parts come before new development.
  • Judging where machines help. People still beat machines at dexterity and perception. Machines win on computation and physical power.
  • The most critical module first. The Wright brothers separated flight into modules and validated wing lift and drag before anything else.
  • Sensitivity analysis. In the GEAR Lab’s drip irrigation work, cutting emitter pressure roughly tenfold was predicted to halve system pumping power.
  • Parts count. P&G’s Guard razor for India has four parts. The Vector has fifteen and the Mach3 has twenty-five.

Scaling across markets

The last stage keeps the core value and architecture fixed and changes features for each market, deciding for each whether it should delight, satisfy or only meet a basic need. Segmentation decides whether the new product reaches customers you could not serve before or eats into the line that already earns. The Honda Super Cub, designed in 1958 for noodle delivery riders, passed 100 million units. GE’s compact ultrasound, built for rural China, later found buyers in emergency rooms and at accident sites in wealthy countries.

What I am taking back to my team

The book gave me a design method. The part I am carrying back to my team is the organisational half, because the questions that decide whether a reverse innovation survives inside a large company are only touched on in the book. It names inertia and margin dilution as traps, then moves on. Who scores the project at intake, and against which criteria? Who owns the KPIs of the clean-sheet team, and are they the same as those of the premium line it might undercut? What happens when a sponsoring business unit reads the new product as a threat to its own numbers?

My experience of setting up project intake points to a process answer. The scoring has to be transparent, product management should own the sheet, and sponsoring teams should hear a project is under review before any decision to stop it, not after. A cannibalisation question belongs in that same sheet, scored before the build, because a team that discovers it at launch has already spent the budget. The book’s advice to differentiate deliberately is sound, but it reads as a design instruction when it is also a governance one: someone has to be accountable for the differentiation, with authority to enforce it across business units.

One caveat I kept in mind while reading: many of the case studies come from the authors’ own MIT work, so some of the examples are curated toward their method.

I would still recommend the book to anyone who funds or runs R&D. Read it with your own project intake sheet beside you and mark where the three merits questions are missing.

Join the discussion

This site uses Akismet to reduce spam. Learn how your comment data is processed.