Plan to Throw One Away

When building something genuinely new, plan to build a pilot version expecting to discard it, because you will anyway. The first full attempt teaches what the real design should be, and delivering it as the product ships your learning draft.

Why it Matters

The hardest problems are not understood until you have built a solution once. Treating the first build as a disposable learning vehicle, rather than the deliverable, turns inevitable rework into a deliberate, cheaper step. Brooks later refined this toward incremental development, but the core, expect the first design to be wrong, stands.

Signals

• Shipping the first version of a novel design, then fighting its early misconceptions for years.
• Surprise that the real requirements emerged only after building.

Benefits

Faster convergence on a good design, and the freedom to learn without defending early mistakes as permanent.

Risks

Planning to throw two or three away and never converging; or the opposite, refusing to discard a flawed first system because of sunk cost.

Tensions

"Build to throw away" conflicts with the cost and pressure to ship the first thing built, and with treating every artifact as precious; the discipline is to invest in learning, then redo.

Examples

Building a prototype to discover the interface, then rewriting it cleanly; an incremental approach that grows a skeleton rather than betting everything on one complete first design.