svpg
FREE newsletter

Subscribe via RSS

Subscribe

Tag Cloud

product management product discovery management company culture product portfolio planning product owner product development process product strategy product manager product marketing user experience design great products innovation marketing agile scrum project management user testing engineering prototype testing

Browse by Date

  • January 2012
  • December 2011
  • October 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • HOME
  • Services
    • Product Management
    • Product Marketing
    • Technology
    • User Experience
    • Public Workshops
  • Articles
    • Index
    • Blog
  • Clients
  • Resources
  • Company
    • Team
    • Manifesto
    • Contact Us

The Two-Week Rule

Posted by Marty Cagan on August 23, 2009

Tags: product discovery

I need to interrupt my series of articles on product portfolio planning because over the past week I learned of three completely different companies that all had fairly disastrous product results for the same core reason: they delayed talking to customers until it was too late.

Steve Blank has a great line about this: “In a startup, no facts exist inside the building, only opinions.”  And of course anyone that reads this blog knows that I believe strongly that the most important thing that a product leader must do is put his ideas in front of real customers and watch their response.

Yet often I meet people that have read my book or attended a workshop and say they totally and completely agree, yet they still hold off for months before they get any real validation of the ideas with the people that matter – the prospective customers and users.  And every day that goes by the product team gets increasingly deeper and more entangled with their original idea to the point that now they’re either too scared to show it to customers for fear of having to start over, or they are so confident that it will be great that they think they can just skip to development, or they’ve got developers screaming at them just to give them something to build.

But one way or the other, eventually customers see it and typically the reality hits hard.

So for those people that believe in principle that they need to validate their product ideas with real customers, but are unsure of how “baked” the idea needs to be, I offer this very specific rule: Never go more than two weeks without putting your product ideas in front of real users and customers.

Does this mean your ideas won’t be fully fleshed out yet?  Yes and good.  Does this mean that customers might not like your ideas?  Yes and good.  Remember it’s all about failing fast.

You can and should continue to refine your product ideas – it’s not like you have two weeks to define everything.  But please, please get out of the office and put your ideas in front of real users while you still have time to adapt.  Just assume that you have some big misses in there and your objective is simply to figure out what they are as quickly as you can.

If you are a manager of product managers, you can help by enforcing this rule and facilitating the customer testing, and pressing the product team for learnings after each session.

Your job as a product leader is to define a successful product, and have evidence that the product will be successful, not just your opinion.  You won’t find that evidence inside your building.


  • Product Management
  • Product Marketing
  • Technology
  • User Experience

© 2009 Silicon Valley Product Group. All rights reserved.