Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Jeff Patton warns that if you keep testing rough features on mainstream customers, they often eventually say they have had it and will not try new things. Release-to-learn depends on early adopters; after disappointing the majority, you have a reacquisition problem, not an acquisition problem.

Related Insights

Don't assume customers will be offended by an unfinished product. If your current product releases already frustrate them, they will likely jump at the chance to participate in a new, more collaborative process. Frame the MVP as an opportunity for them to help you build something better.

Users won't permanently reject a rough product if you respond to their feedback and ship improvements almost immediately. This rapid iteration turns initial frustration into loyalty. Slowness, not product roughness, is the real danger that causes users to lose interest.

The weeks following a launch are for intense learning, not just promotion. The goal is to quickly identify high-adopting customer segments and then execute mini 'relaunches' with tailored messaging specifically for them, maximizing impact and conversion.

As articulated by Eric Ries in 'The Lean Startup,' raw speed of shipping is meaningless if you're building in the wrong direction. The true measure of progress is how quickly a team can validate assumptions and learn what customers want, which prevents costly rework.

True speed isn't shipping broken products to everyone; it is responsible iteration with opt-in user groups. This approach distinguishes valuable A/B experiments from unacceptable "spaghetti at the wall" testing by targeting willing early adopters who understand the experimental status.

Your first customers will be patient with major failures if you're tackling a critical problem they have no other solution for. 7 Learnings' first price upload was a "disaster," but the customer stuck with them because the need was immense.

Customer.io finds users provide more candid, constructive criticism for features in beta. There's an implicit understanding that the product is still malleable, so users are more willing to report bugs and request features, whereas post-launch, frustrated users often just churn quietly.

Don't build a perfect, feature-complete product for the mass market from day one. It's too expensive and risky. Instead, deliver a beta to innovator customers who are willing to go on the journey with you. Their feedback provides crucial signals for a more strategic, measured rollout.

Don't expect your first customers to adopt your product's full, evolved capabilities. They will likely always see it as the limited version they first bought. It's more effective to position the mature product to new customers rather than trying to change the minds of early adopters.

To manage the risk of a large-scale launch, identify and release smaller, self-contained features to users months in advance. American Express used this to test benefit enrollment mechanics before their main Platinum card launch, reducing uncertainty and gathering real-world data.