The Two-Week Rule

Marty Cagan argues that many product teams delay validating their ideas with real customers until it is too late, and that this delay is a common cause of disastrous product results. He notes that people often agree in principle with customer validation yet still wait months before doing it, by which point teams are emotionally and technically over-invested. To counter this, he offers a concrete rule: never go more than two weeks without putting product ideas in front of real users and customers. Early ideas are expected to be incomplete and to fail, and the goal is to find the big misses quickly while there is still time to adapt. Managers are encouraged to enforce the rule and facilitate testing.

01Key takeaways

• Get ideas in front of real customers early, before teams become emotionally and technically committed to them.
• Adopt a maximum gap of two weeks between customer contact and testing product ideas.
• Expect early ideas to be incomplete and expect big misses; the aim is to find them quickly.
• Keep refining ideas, but treat customer feedback as the primary source of facts rather than internal opinion.
• Managers should enforce the cadence, facilitate sessions, and debrief learnings after each one.

02Key sections

The cost of delayed customer contact

Cagan opens with several failed companies whose problems stemmed from waiting too long to talk to customers. He draws on Steve Blank's observation that facts exist only outside the building.

Why teams wait too long

As time passes, teams become more entangled with their original idea, making them afraid to show it, overconfident, or pressured by developers to start building. Customers eventually reveal the reality, usually painfully.

The two-week rule

Cagan proposes a specific cadence: never go more than two weeks without testing ideas with real users. He stresses that incomplete ideas and likely rejection are acceptable and part of failing fast.

Role of product leaders and managers

Product managers should keep refining ideas, but managers should enforce the rule, facilitate customer testing, and press teams for learnings after each session. The overall goal is evidence of success rather than opinion.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.