The bait, then the rug-pull.
In 1997, Steve Jobs returned to an Apple in freefall and faced a packed WWDC auditorium of developers whose work he had just killed. The question from the crowd is blunt: what about OpenDoc? His answer takes three minutes and becomes one of the most-replayed leadership clips in history.
Where the time goes.
01 · Title card + challenge
Black title card opens the clip. Audience member immediately challenges Jobs about killing OpenDoc. Jobs confirms it dead, then pauses.
02 · Honest apology
Jobs acknowledges the real pain of the people whose work was killed. Admits Apple had lousy engineering management. People going in 18 different directions — good engineers, lousy management.
03 · The farm metaphor
Jobs introduces the farm metaphor: animals going in different directions, total less than sum of parts. Sets up the need for a fundamental direction reset.
04 · The reframe
The pivot: focusing is not about saying yes — it is about saying no. Delivered quietly but with full conviction.
05 · The cost of no
When you say no, you piss off people. They talk to the press and you get shitty articles written about you. Jobs says Apple has been taking lumps like an adult and he is proud of that.
06 · Dead weight and the promise
Calls out people who left who had not done anything in seven years acting like the company will collapse. Closes the loop: focus is about saying no, and the result will be great products where the total exceeds the sum of the parts.
07 · Why OpenDoc specifically
Returns to the original question. Not great technology. Did not fit. The rest of the world was not going to use it. The OpenDoc team was trying to rewrite it in Java anyway — which was basically starting over. No sense.
Visual structure at a glance.
Lines you could clip.
"Focusing is about saying no."
"The total is less than the sum of the parts."
"Good engineers, lousy management."
"The result of that focus is going to be some really great products where the total is much greater than the sum of the parts."
How they spent the runtime.
Word for word.
Strategy is subtraction.
Every kill decision you make will piss someone off — say no anyway, take the lumps publicly, and let the results answer for you.
- When you kill a feature or product, acknowledge the real pain first — Jobs spent 30 seconds validating the hurt before defending the decision.
- Name the failure honestly: lousy management, too many directions, total less than sum of parts. Audiences respect the diagnosis.
- The reframe is more powerful than the defense: do not argue why OpenDoc was bad — reframe killing it as what focus requires.
- Taking lumps publicly and calmly is its own brand signal. Apple absorbed shitty press coverage like an adult — that composure read as confidence.
- Apply to MCN+: every tool you kill or exclude is a focus decision. Frame the kills as the product strategy, not as an apology.
What saying no actually costs.
Focus is not a productivity trick — it is a series of losses you choose to absorb so that the thing you keep can actually become great.
- Every time you say no to something, someone who cared about that thing will be upset. That is the price — not a bug, just the cost.
- The people who push back hardest when you cut something are often the people who built it, not the people who use it. Know the difference.
- If you are spreading yourself thin, the total of your effort is less than the sum of its parts. That gap is the cost of not saying no.
- The question is not what to add next — it is what to kill so that what stays can compound.
