Product

Core Focus for Innovation: The Hedgehog and the Product-Line Massacre

The V/TO's core focus — purpose plus niche — sounds like the least innovative section of the whole organizer: a fence around what you'll do. It's actually the section that makes innovation survivable, because unfocused companies innovate by accretion until the portfolio kills them. Apple's 1997 product massacre and LEGO's near-death diversification are the two best-documented cases of focus as a rescue operation — and both show that the fence is what makes the bets inside it affordable.

Core Focus for Innovation: The Hedgehog and the Product-Line Massacre

Core focus is the V/TO section that innovation people instinctively resist: Wickman asks for your purpose and your niche — the business you are in, stated tightly enough to imply all the businesses you are not in — and that sounds like a fence built precisely where explorers want open range. The whole point of transformational bets is to escape the current niche, isn’t it?

It isn’t, and the two best-documented corporate rescues of the modern era are both stories of innovation recovered by focus, not from it. The confusion comes from collapsing two different things: focus of identity (what capability and customer we organize around) and breadth of activity (how many things we currently ship). Companies die of unfocused activity while calling it innovation. The fence isn’t the enemy of the portfolio from the three-year picture post — it’s what makes the portfolio affordable, because every bet inside the fence compounds a shared capability, and every bet outside it pays full price for everything.

The intellectual anchor: three circles, honestly answered

The serious version of “core focus” is Jim Collins’s Hedgehog Concept from Good to Great (2001): the intersection of three honestly-answered questions — what can you be the best in the world at (crucially: not what you want to be best at, and not what you’re merely competent at), what drives your economic engine, and what are you deeply passionate about. Collins’s finding was that the great-transitioning companies in his sample operated inside that intersection with near-monastic consistency, while comparison companies chased anything that looked like growth.

For innovation strategy the hedgehog does one specific job: it converts “should we pursue this opportunity?” from a fight about optimism into a test with criteria. Does this bet use or extend the thing we can be best in the world at? If yes, it’s an adjacent or transformational bet in the portfolio sense — it borrows an existing superpower and stretches it. If no, you’re not innovating; you’re conglomerating one project at a time. Peter Lynch coined the investor’s word for it — diworsification — and the finance literature put a number on the corporate version: Berger and Ofek’s 1995 study of thousands of firm-years found diversified firms traded at a 13–15% average discount to the sum of their focused parts. (Later work contests how much is causation versus selection — troubled firms diversify — but either reading supports the same operating conclusion: breadth is not free.)

Apple, 1997: innovation by subtraction

The most famous focus story in business is usually told as a leadership story; told as an innovation story it’s more instructive. When Jobs returned in 1997, Apple was shipping dozens of products — a dozen Macintosh variants with numbered names nobody could distinguish, the Newton, Cyberdog, OpenDoc, printers — and had lost over a billion dollars that fiscal year. Per Isaacson’s account, Jobs killed roughly 70% of the product line, and in a September product-strategy meeting drew the two-by-two grid that became legend: consumer and pro across one axis, desktop and portable down the other, four products total. The next fiscal year Apple posted a $309 million profit; the four quadrants filled with the iMac, Power Mac, iBook, and PowerBook.

The line everyone quotes from that era — “deciding what not to do is as important as deciding what to do,” via Isaacson — is usually read as time-management advice. The strategic content is sharper: the massacre wasn’t the opposite of innovation, it was its precondition. The iMac, and everything after it, was built by engineers and capital that had been spread across twenty mediocre products the year before. A focused product grid is a capacity-liberation event — the 70/20/10 allocation from the one-year plan post only exists if the 70% isn’t secretly 100% spread across zombie lines. When people say focus and innovation are in tension, Apple 1997 is the counterexample: the company innovated more, and more famously, with four products than with forty.

LEGO: the fence rebuilt after the flood

If Apple shows focus liberating innovation, LEGO shows what “innovation” without core focus does to a company. Through the late 1990s and early 2000s, LEGO — advised by the era’s best consultancies to diversify away from a “mature” toy — launched theme parks, software, jewelry, television, and brick lines (Galidor, Explore) that progressively abandoned the brick itself. The result, documented in David Robertson’s Brick by Brick: sales fell roughly 30% in 2003 and another 10% the following year, and the company recorded the largest loss in its history, close enough to insolvency that family ownership was on the table.

Jørgen Vig Knudstorp, made CEO in 2004 at thirty-five, ran the Apple play in Danish: back to the brick. The element library — which had roughly doubled as every themed set demanded bespoke pieces — was cut roughly in half; the Legoland parks were majority-sold in 2005; the businesses with no connection to the core system of play were killed. And the recovery that followed wasn’t retrenchment-instead-of-innovation — it was some of the most successful innovation in the company’s history (Mindstorms’ community turn, the licensed-universe engine, eventually the movie) — all of it radiating from the brick rather than fleeing it. Robertson’s own framing of the lesson is the hedgehog restated: LEGO’s near-death experiments failed not because they were creative but because they were creative about someone else’s business, where LEGO’s accumulated capability counted for nothing.

Writing the core focus for an innovation strategy

On the V/TO the section is two lines — purpose and niche — and the innovation-strategy version needs a third, so write all three.

The capability sentence (the hedgehog’s first circle, honestly): the thing you can be best in the world at, stated as a capability rather than a product — Apple’s wasn’t “computers,” and LEGO’s wasn’t “toys”; they were something closer to integrated hardware-software experience and systematic creative construction. Products expire; the capability is what your ten-year target should be denominated in.

The niche sentence: whom you serve and with what, tight enough that a stranger could sort ten opportunities into inside/outside in a minute. This is the fence — and note what the fence is for: it doesn’t forbid transformational bets; it prices them honestly. A bet outside the fence needs to either be redrawn as a capability extension, be run as a spin-out where the parent’s focus doesn’t tax it, or not be run.

The subtraction ledger — the addition experience suggests: a standing list of what the focus obligates you to stop. Every planning cycle, the fence should kill something, publicly, the way the quarterly rocks cadence kills experiments. A core focus that has never cost you an attractive-looking opportunity is a slogan, exactly as a value that never cost you a hire is a poster.

The order of the V/TO is doing quiet work here: values (previous post) decide whether people dare to bring bets; focus decides which bets belong to you. Only then does the organizer let you talk about targets and pictures — because a ten-year target set by an unfocused company is just the largest of its distractions. Next in the V/TO’s numbering comes the section everyone’s surprised is in a vision document at all: the marketing strategy — who, exactly, the first customers of your next bet will be.

About the author

Prakash Poudel Sharma

Engineering Manager · Product Owner · Varicon

Engineering Manager at Varicon, leading the Onboarding squad as Product Owner. Eleven years of building software — first as a programmer, then as a founder, now sharpening the product craft from the inside of a focused team.

The Innovation V/TO

8 parts in this series.

An eight-part series running Traction's full Vision/Traction Organizer as an innovation strategy stack, ordered by V/TO section — core values as the permission structure, core focus as the hedgehog, the ten-year target as a long bet held with institutional patience, marketing strategy as beachheads, the three-year picture as a steerable portfolio, the one-year plan as metered money, rocks as ninety-day experiment contracts, and the issues list as the machine that surfaces bad news. Referenced stories throughout: IBM's EBOs, Tesla's master plan, AWS, ASML's EUV, Apple's 1997 product cull, LEGO's near-death, the Challenger, and the Concorde fallacy.

  1. 01Core Values for Innovation: The Permission Structureprevious
  2. 02Core Focus for Innovation: The Hedgehog and the Product-Line Massacre← you are here
  3. 03The Ten-Year Target: Long Bets and Institutional Patienceup next
  4. 04Marketing Strategy for Innovation: Beachheads and The List
  5. 05The Three-Year Picture: An Innovation Portfolio You Can Steer
  6. 06The One-Year Innovation Plan: Rocks, Metered Money, and a Kill Cadence
  7. 07Rocks for Innovation: The Ninety-Day Experiment Contract
  8. 08The Issues List for Innovation: Surfacing Bad News at Line Speed
Join the conversation0 comments

What did you take away?

Thoughts, pushback, or a story of your own? Drop a reply below — I read every one.

Comments are powered by Disqus. By posting you agree to theirterms.

0:000:00