Product in Practice: Shifting from a Feature Factory to Continuous Discovery at Doodle

Stephanie Leue, then Chief Product Officer at Doodle, describes moving a team that had been run as a top-down feature factory toward continuous discovery. Despite good data access, customer feedback channels, and a new UX researcher, the teams kept building what they already had planned and neglected the discovery phase. A workshop exposed gaps in defining problems and hypotheses, confusion about what continuous discovery means beyond customer interviews, and constant pressure from engineering to keep shipping. Afterward, teams mapped their problem spaces and the PM-designer partnership grew stronger. The conversation also covers how a single researcher can coach teams across different levels of research, using a three-level framework of vision, strategy, and opportunity space. It matters because it shows that discovery habits don't follow from having the tools; they require explicit practice and leadership time.

01Key takeaways

• Good data and customer feedback systems do not create discovery habits; teams need explicit practice in it.
• Make sure everyone can write a real problem statement and tell apart problems, hypotheses, and assumptions before running research.
• Continuous discovery means choosing the cheapest tool that can prove or falsify an assumption, not only interviewing customers weekly.
• Give teams protected time to map their problem space, even when that delays shipping, because the speed gains compound later.
• Use a leveled framework (vision, strategy, opportunity) to match research depth to the decision at hand.
• Increase PM transparency about how decisions are made so designers and researchers gain confidence and join the process.

02Key sections

From feature factory to product-led

Doodle's roadmap was set top-down by leadership, and Stephanie's goal was to build autonomous teams that own their domains. She first tried to transplant the process she had used at her prior company, which proved too simple.

Good infrastructure, weak discovery

Data, customer success, and feedback systems were strong, yet teams kept building planned features and rationalized them afterward. The discovery phase was neglected because the backlog already seemed obviously justified.

Workshop reveals the basics gap

Even experienced teammates struggled to write a true problem statement and distinguish problems, hypotheses, and assumptions. Discovery was also mistakenly equated with weekly customer interviews rather than choosing the right validation tool.

Flight levels and researcher as coach

A decision stack of vision, strategy, and opportunity space helps the team see what research each level needs. The lone UX researcher coaches PMs and designers rather than doing all the research herself.

Balancing time and pressure

Mapping the problem space requires pausing delivery, which is hard to justify to engineering and leadership. Insights from opportunity-level work also feed back up into strategy and vision over time.

03From the post

“Leading a product team (or several teams) comes with its own set of challenges that’s often similar to but distinct from the hurdles individual product contributors face. There’s pressure coming from all directions—your company leaders expect you to deliver business results while your product teams may be”

04Frameworks mentioned

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