Business & Strategy
Section 1
Core Idea
"Version Two" is a lie because it rarely arrives as promised. When teams say "we'll fix it in V2," they're using a future release as an escape valve for present-day trade-offs — and V2 almost never materialises as imagined. New priorities, new fires, and scope creep consume the roadmap. The real work happens in continuous iteration on V1, not in a mythical clean-sheet rewrite. The danger: promising V2 lets teams ship knowingly broken V1s, expecting a future they won't get. The discipline: build V1 to a real standard, then iterate incrementally. Don't bet on a future version that may never come.
Free playbook
Get The Business Model Playbook
58 business models, one visual page each: how the money flows, the metrics that matter, and who runs it. Free when you join the Faster Than Normal email.
Free. No spam. Unsubscribe anytime.
Section 2
How to See It
Product
You're seeing Version Two is Lie when the backlog is full of "V2 items" — features, fixes, and debt explicitly deferred to a future major release that has no schedule, no team, and no real commitment.
Strategy
You're seeing it when a team uses "we'll do it right in V2" to justify shortcuts now. V2 becomes a credit card: borrow quality today, pay back never.
Section 3
How to Use It
Don't promise V2 to justify shipping a bad V1. Hold V1 to a real standard. If you must defer, put it on the iteration backlog with a deadline — not in a "V2 someday" bucket. Kill the concept of a major future rewrite; replace it with continuous small releases.
Decision filter
"Are we deferring this to V2 because it's genuinely lower priority — or because V2 is a comfortable fiction that lets us avoid the hard work now?"
As a founder
Ban "we'll fix it in V2" as a justification for shipping broken work. If something is worth doing, schedule it in the iteration backlog with a date. If it's not, cut it explicitly. Treat every release as V1.x and iterate continuously. The team that ships 50 small improvements beats the team waiting for a mythical V2.
Section 5
Founders & Leaders
Elon MuskCEO, Tesla & SpaceX
Musk ships imperfect V1s — then iterates relentlessly. Tesla's original Roadster and early Model S had rough edges, but Musk's teams improved them through continuous OTA updates and manufacturing tweaks rather than waiting for a mythical V2. SpaceX iterated Falcon 1 into Falcon 9 through incremental changes, not a single clean-sheet redesign. The lesson for founders: ship V1 at a real standard, then improve it weekly. Don't promise a future version as an excuse to ship poorly today.
Section 7
Connected Models
Reinforces
MVP
MVP ships the minimum to learn. Version Two is Lie reinforces the point: the learning and value come from iterating on the MVP, not from promising a grand V2 that never arrives.
Reinforces
Most Value Created After V1
If most value is created after V1, then betting on a separate V2 misallocates attention. The value is in continuous improvement, not in a future rewrite.
Tension
Technical Debt
Technical debt accumulates when teams defer quality. V2 is often cited as when the debt will be repaid — but that day rarely comes. The tension: accept some debt, but pay it down in each iteration rather than deferring to a mythical V2.
Section 8
One Key Quote
— Reid Hoffman"If you are not embarrassed by the first version of your product, you've launched too late."
Section 11
Summary & Further Reading
"Version Two" is a lie because it rarely arrives as promised. Don't use a future release to justify present-day shortcuts. Ship V1 to a real standard, then iterate continuously. The value is in the grind after launch, not in a mythical rewrite.
01
Book
Build-measure-learn loops; iterate instead of planning large future releases.
02
Book
Ship small and often; replace big-bang releases with incremental deployment.
03
Book
SpaceX's iterative approach: constant improvement over clean-sheet redesigns.