Management by Subtraction: Steve Jobs and the Via Negativa

Steve Jobs returned to Apple in 1997, and the company was in chaos.

Apple had dozens of product lines. Hundreds of SKUs. A confused strategy. The company was trying to make computers for every market, every price point, every use case. Employees didn't know what they were supposed to be building.

Jobs' response: cancel 70% of the products.

Not "what should we build?" but "what should we stop building?"

This is management by subtraction.

The Decision

By many measures, the decision looked wrong. Jobs was eliminating revenue streams. Eliminating products meant some customers would leave for competitors. Some employees would be laid off or reassigned.

But the subtraction accomplished something that addition never would:

• Clarity: With four product categories instead of dozens, everyone knew what Apple was about
• Focus: Resources could concentrate on what mattered instead of spreading across everything
• Quality: The four products could be refined obsessively instead of managed loosely
• Speed: Decision-making became faster with fewer stakeholders and fewer products to maintain

The iMac, the four products that remained, became legendary. Not because they were the only possible products, but because the subtraction forced focus that produced excellence.

Why This Is So Difficult

Subtraction is harder than addition because:

Addition creates winners. Someone gets a new product, a new feature, a new budget. They're happy. They advocate for it.

Subtraction creates losers. Someone loses their product, their project, their position. They resist. They lobby. They sabotage.

In democratic organizations, addition always wins because the winners are numerous and vocal. The losers are few and punished for complaining.

But the organization suffers because it becomes bloated and unfocused.

Where This Shows Up

Product management: Most companies add features constantly. The interface becomes cluttered. The software becomes bloated. The performance degrades. Then, a new competitor emerges with a simpler product, and the bloated company fails.

The solution is subtraction: remove features that don't serve the core use case. Make the product simpler. Make it faster. Make it focused.

Organizational structure: Companies accumulate departments, layers, and roles. No one is responsible for eliminating them. HR expands. Finance expands. Marketing duplicates itself across divisions.

The solution is subtraction: eliminate redundancy. Flatten the structure. Force people to do more with less, which produces efficiency or reveals waste.

Meetings: Most organizations have too many meetings. Add a new initiative and someone creates a weekly meeting about it. Never eliminate the old meeting.

The solution is subtraction: if you're going to add a meeting, eliminate two. Force ruthless prioritization.

Processes: Companies accumulate processes for compliance, control, and efficiency. Then, the processes start optimizing for themselves rather than the company.

The solution is subtraction: periodically, eliminate 20% of all processes. Departments that can't function without them will scream. Those screams reveal which processes actually matter.

The Implementation

How do you actually subtract?

1. Inventory everything

Make a list of every product, feature, process, meeting, rule, and initiative. Be specific.

2. Rank by impact

Which of these actually matter? Which drive the outcome you care about?

The bottom 20% should be the target for removal.

3. Remove ruthlessly

Don't tinker. Don't compromise. Remove.

The resistance will be fierce. But the alternative is to have the competitors do the subtracting for you (by making a better, simpler product and driving your bloated company out of business).

4. Reassign, don't fire

The people working on the eliminated products might be valuable elsewhere. Reassign them. But discontinue the product.

The Psychology

There's a psychological reason subtraction is rare:

When you add, you can point to the new thing. "Look what I built." Career advancement is tied to what you launched.

When you remove, you eliminate something someone else built (or you built). There's no credit. The benefit is invisible (the company that functions better without the bloat).

The incentive structure rewards addition and punishes subtraction.

But the most valuable management move is often subtraction.

Modern Example

Look at any bloated tech company's product line versus a lean competitor:

Bloated company: 15 products, most legacy, most in slow decline, most cannibalizing each other

Lean competitor: 3 products, each exceptional, each with a clear market

The lean competitor eats the bloated company's lunch. Not by being better at each individual product, but by being ruthlessly focused.

The Principle

Here's the principle:

Before you add, remove. If you're adding a new feature, remove an old one that's less important. If you're launching a new product, discontinue an old one. If you're creating a new process, eliminate an existing one.

The constraint forces prioritization.

The company that subtracts ruthlessly becomes focused. The focused company becomes excellent at fewer things. The excellent company wins.

The company that adds continuously becomes bloated. The bloated company is beaten by the focused one.

Steve Jobs understood this. The decision to cancel 70% of products, in 1997, was the move that saved Apple.

Not the move that made it larger. The move that made it coherent.

And coherence, in the market, beats size.