Version two is a lie

A product-planning maxim: make the current release useful for its stated purpose without depending on future improvements that may not arrive. Prefer a bounded, coherent capability and communicate unbuilt plans as uncertain future work.

This maxim asks whether the current version can fulfill its stated purpose if planned improvements never arrive. Future work depends on people, priorities, and resources that may change. A coherent first version therefore needs a bounded use that works end to end; it does not need every feature the team can imagine.

Inspect dependencies in the user's actual task. If an export is essential to using a report, an attractive display without export may leave the promise incomplete. Reduce the promise, supply a dependable present workaround, or finish the necessary step before release. Keep future improvements visible as plans with owners and uncertainty, rather than counting them as capabilities already delivered.

When to use it

When building or iterating on products; when evaluating market opportunities; when deciding resource allocation; when scaling operations.

How it can help

Directly applicable to building, launching, and scaling products and businesses. Helps prioritize actions, identify market opportunities, and build sustainable competitive advantages.