What does it mean that fail fast fail cheap?

Design systems that surface errors early when they are easiest and cheapest to correct.

Example: You spend six months writing a book before showing it to anyone. When you finally share the manuscript, three beta readers independently tell you the central premise is flawed — the argument you built 80,000 words around does not hold up under scrutiny. Six months of work, structured around a foundation nobody tested. Compare this to a writer who drafts a two-page outline of the core argument, shares it with five people in week one, discovers the premise needs restructuring, and pivots before writing a single chapter. Same book. Same ambition. One writer spent six months building on an untested foundation. The other spent two days testing the foundation before building on it. The second writer failed faster, failed cheaper, and ended up with a stronger book.

Try this: Identify one project or commitment you are currently in the middle of — something you have been working on for at least two weeks without external validation. Write down the three riskiest assumptions embedded in that project: the things that, if wrong, would invalidate the most work. For each assumption, design a test you can run in under 48 hours that would surface whether the assumption holds. Run the cheapest test today. You are not looking for confirmation. You are looking for the earliest possible moment of disconfirmation — the point where reality can correct you before you invest further.