# Fast

If you only change one thing about how you operate, make it this: go faster.

Not because hustle is a personality. Because every outcome you care about is a rate — learning per week, product per quarter, decisions per day. Stretch the denominator and the numerator dies. A team that ships weekly runs fifty-two experiments a year. A team that ships monthly runs twelve. That gap is not a rounding error. It is the whole game.

I treat speed as non-negotiable because the alternative is a polite fiction: that thinking harder will substitute for contact with reality. It will not. Plans are guesses. Shipping is the grade. Slow work is usually an unmade decision wearing a costume. The shorter loop wins. Everything below is that argument, written out.

Sam Altman has said he has yet to meet a slow-moving person who is very successful. That tracks. Speed is not a vibe. It is a requirement.

## Speed Is a Learning Rate

- You learn per unit of contact with reality, not per unit of thinking.
- Ship more often → touch reality more often → learn more per week.
- Every plan is a guess. Shipping is how the guess gets graded.
- Rapid feedback loops beat good foresight. Nobody predicts; everybody iterates.
- Moving fast means building more and learning faster — that is why it is a value, not a mood.

*Nat Friedman: you learn more per unit time because you make contact with reality more frequently — [nat.org](https://nat.org/)*

## The Math of Time

- A week is 2% of the year. A month is 8%. Slipping "just two weeks" is real money.
- Time is the denominator. Every metric you care about is *something per unit time*.
- A team that iterates weekly runs 52 experiments a year. Monthly runs 12. The gap compounds.
- Momentum is oxygen. It is very hard to get back once it is gone.
- Slow is expensive. Wrong is often cheap and reversible.

## Speed Lowers the Cost of Trying

- Whatever you do quickly feels cheap to start, so you do it more — and doing it more is how you get good.
- Whatever you do slowly feels expensive, so you avoid it, so you stay slow. The loop runs both ways.
- Systems that clear work quickly get fed more work. Slow systems starve — people stop bringing them things.
- Fast replies pull more ideas out of people. Slow ones train the team to stop asking.
- Speed is therefore upstream of quality, not opposed to it. You get good at what you repeat.

*James Somers, "Speed matters: Why working quickly is more important than it seems" — [jsomers.net/blog/speed-matters](https://jsomers.net/blog/speed-matters)*

## Speed Forces Focus

- There is no time for bullshit at high speed. Politics, theatre, and vanity work die first.
- Deadlines are a forcing function for scope. Speed is a scoping tool, not just a pace.
- Fast teams cut the 80% of work that does not matter, because they have to.
- "Slow is fake." Slow work usually hides an unmade decision or an unowned problem.
- If a project has no clock, it has no priority.

## Decide Fast

- Decide at about 70% of the information you wish you had. At 90% you are already late.
- Sort decisions into reversible and irreversible. Reversible ones get a light process — walk through the door.
- Irreversible decisions deserve care. Most decisions are not irreversible.
- Get good at recognising and reversing a bad call quickly. That is what makes speed safe.
- Slow, high-quality decisions are the classic failure mode of big companies. Quality *and* velocity, or you are already old.
- Push decisions to the person closest to the problem. Waiting for approval is pure latency.

*Jeff Bezos, 2016 shareholder letter: the 70% rule and one-way vs two-way doors — [aboutamazon.com](https://www.aboutamazon.com/news/company-news/2016-letter-to-shareholders)*

## Urgency Is Manufactured by Leaders

- Left alone, every organisation drifts to a lethargic pace. Entropy always wins by default.
- Most organisations carry enormous slack. It is invisible until someone puts a clock on it.
- A 20% improvement changes nothing. Aim for 5x — the difference must be palpable.
- Set the tone. The team's energy will never exceed the leader's.
- Companies slow down as they grow because they fear mistakes more than they fear lost opportunity. Invert that.
- Escalate blockers loudly and immediately. A blocked person waiting quietly is the most expensive thing in the building.
- Ask constantly: why can't this happen today? Most timelines are inherited, not derived.

*On refusing inherited timelines: Ben Kuhn, "Be impatient" — [benkuhn.net/impatient](https://www.benkuhn.net/impatient/). Same idea from the learning side in Derek Sivers' ["There is no speed limit"](https://sive.rs/kimo): a semester of music theory, taught in an afternoon.*

## Compress the Loop

- Observe → orient → decide → act. Whoever cycles faster and more accurately wins.
- Get inside the competitor's loop: by the time they respond, you have already moved again.
- Attack cycle time directly — build time, review time, deploy time, approval time.
- Most delay is queue time, not work time. Find the waiting, not the working.
- Speed is your main advantage over large competitors. It is the one thing they cannot buy.

*John Boyd's OODA loop, originally from air combat, now standard in business strategy — [OODA loop](https://en.wikipedia.org/wiki/OODA_loop)*

## Ship Early, Ship Often

- Small batches ship faster, break less, and are easier to debug.
- Launch before you are comfortable. If the first version does not slightly embarrass you, you shipped too late.
- Shipping generates the only real asset: data.
- An idea that does not exist yet changes nothing. Products that do not ship rarely change the world.
- Do it manually before you build the system. Never automate a process you have not yet run.

*The "move fast" value as originally written down — build more, learn faster, and fear lost opportunity more than mistakes: [Facebook's 2012 founder's letter](https://www.snopes.com/fact-check/move-fast-break-things-facebook-motto/) and [the Little Red Book](https://fieldnotesbynick.substack.com/p/facebooks-little-red-book)*

## What Fast Is Not

- Fast is not rushed. Rushing is skipping steps; fast is removing them.
- Speed without direction just gets you lost sooner. Orient better, not only quicker.
- Fast is not permanent chaos. Sustained tempo requires clean systems and low debt.
- Do not accelerate a broken process. Delete and simplify first, then speed up.
- One-way-door decisions are the exception where deliberation is worth the time.

## It Has Been Done Before

Patrick Collison keeps a running list of ambitious projects completed at speeds that look impossible today — aircraft, buildings, moon missions, programming languages, wartime infrastructure, each with the number of days it actually took. Read it in full: **[patrickcollison.com/fast](https://patrickcollison.com/fast)**

Two things stand out:

- The timelines are absurd by modern standards — and none of them were achieved with better technology than we have now.
- The fastest examples skew *old*. What changed was process, permission, and appetite for risk — not physics.

The constraint on your timeline is almost always organisational. Treat any schedule as a claim someone has to defend, not a fact.

## Sources

- Nat Friedman — [nat.org](https://nat.org/)
- Patrick Collison — [Fast](https://patrickcollison.com/fast)
- James Somers — [Speed matters](https://jsomers.net/blog/speed-matters)
- Ben Kuhn — [Be impatient](https://www.benkuhn.net/impatient/)
- Jeff Bezos — [2016 Letter to Shareholders](https://www.aboutamazon.com/news/company-news/2016-letter-to-shareholders)
- John Boyd — [OODA loop](https://en.wikipedia.org/wiki/OODA_loop)
- Facebook's Little Red Book — [overview and excerpts](https://fieldnotesbynick.substack.com/p/facebooks-little-red-book)
- Sam Altman — [How To Be Successful](https://blog.samaltman.com/how-to-be-successful)
- Derek Sivers — [There is no speed limit](https://sive.rs/kimo)