Zero to One Means Pruning Fast

Pruning Beats Building Speed

Casey Winters ends his essay on building SuperMe with a sharp line: "Zero to one isn't about building fast. It's about pruning fast."[[1]](https://www.caseyaccidental.com/p/zero-to-one-subtraction)

Zero to one is the stretch before product/market fit, when you are still finding out what users truly want.

Most teams read speed as shipping velocity. Winters points somewhere else.

The deciding skill is how fast you spot what is not working and remove it on purpose.

Surface Area and Conviction

Winters says building SuperMe made something obvious: "zero to one isn't just about speed. It's about surface area and conviction."[[1]](https://www.caseyaccidental.com/p/zero-to-one-subtraction)

Surface area is how much a team builds: features, experiments, bets.

Conviction is a firm view of what the company must own. It is the base.

Pruning rests on both. Surface area gives you options to cut, and conviction tells you which ones to keep.

Expect Things to Fail

Winters is blunt: "You will try things that don't work."[[1]](https://www.caseyaccidental.com/p/zero-to-one-subtraction)

Failure is part of the plan at zero to one. The real risk is letting dead features linger, eating time and attention.

So pruning runs as a cycle: try a bet, watch it, recognize what fails, cut it, and try again with sharper focus.

Know What You Must Own

Winters ties every cut to one condition: "If you don't know what you need to own, you won't know what to remove."[[1]](https://www.caseyaccidental.com/p/zero-to-one-subtraction)

Before asking whether a feature works, ask whether it is part of the core you must protect.

Core pieces that struggle get protected and improved. Non-core pieces that work can stay for now. Non-core pieces that fail get cut.

Without that anchor, cutting becomes guesswork.

What Pruning Is Not

Pruning fast does not mean trying less. Winters assumes you will build things that fail.

Cutting without knowing what you must own is not pruning either. It is just shrinking.

Picture two questions: does the team try a lot, and does it know what it must own?

Only a team doing both is pruning fast. Try little and you learn slowly. Build lots without an anchor and you sprawl.

Styles Shaped by Context

Winters and co-founder Ludo first saw each other's styles while scaling Pinterest.[[1]](https://www.caseyaccidental.com/p/zero-to-one-subtraction)

Ludo had an "intuition for when to hack and when to scale engineering systems." Winters could "strategically prioritize and frame problems" for the organization.[[1]](https://www.caseyaccidental.com/p/zero-to-one-subtraction)

At Whatnot, Ludo operated at more scale. Winters, a part-time advisor, was "more direct and less patient."[[1]](https://www.caseyaccidental.com/p/zero-to-one-subtraction)

Both companies already had product/market fit. SuperMe started from scratch.[[1]](https://www.caseyaccidental.com/p/zero-to-one-subtraction)

Why Old Partners Can Differ

After years together, Winters expected to know Ludo's style. At zero to one, he found their approaches "quite different."[[1]](https://www.caseyaccidental.com/p/zero-to-one-subtraction)

That surprise makes sense. Scaling, part-time advising, and building from scratch each reward different behaviors.

An operating style is not a fixed trait. It is a response to context.

So agreement earned while scaling does not transfer automatically to a blank page.

Putting It to Work

Use this lens on your own early-stage work.

First, write down what you must own. That list decides every cut.

Then let surface area grow on purpose and review bets on a steady rhythm. Ask what is not working, and remove it.

With co-founders, talk openly about how each of you works in this context, not the last one.

According to Casey Winters, before product/market fit the most important speed is how fast a team _____.

• removes what isn't working
• ships new features

Answer: removes what isn't working

Winters closes his essay with: "Zero to one isn't about building fast. It's about pruning fast." The useful speed is recognizing what isn't working and removing it, not adding more features.

Winters says zero to one depends on two things: _____, which is how much a team builds, and _____, which is firm belief in what the company must own.

Answer: Winters says zero to one depends on two things: surface area, which is how much a team builds, and conviction, which is firm belief in what the company must own.

Surface area measures how much a team builds. Conviction is paired with it: knowing what you need to own lets you decide what stays and what gets cut.

A startup team cuts several features at random to "move faster," without deciding what the company must protect. Why is this not the pruning Winters describes?

• Pruning must be guided by knowing what the company needs to own
• Pruning should only happen after product/market fit is reached
• Pruning means cutting as many features as possible, as quickly as possible
• Pruning is about shipping replacement features faster than competitors

Answer: Pruning must be guided by knowing what the company needs to own

Winters writes: "If you don't know what you need to own, you won't know what to remove." Pruning is guided by knowing what the company must protect. Random cutting lacks that guide, so it is not real pruning.