Picking sharp problems, increasing virality, and unique product frameworks

Oji Udezue is a product leader who has worked at Microsoft, Atlassian, Calendly, Twitter, and currently serves as chief product officer at Typeform, and he has also advised startups and invested. The conversation covers his frameworks for choosing workflows and sharp problems, zone of benefit, ICP definition, continuous customer discovery and listening, onboarding and activation, network-effect-driven virality, and the practice of 'forest time' for leaders.

01Key learnings

• Map B2B SaaS opportunities on two axes: how many departments a workflow touches and how frequently it runs; high-frequency niche workflows are a strong place to build.
• Confirm a problem is sharp by drawing customer workflows before and after your product and measuring how much shorter they become, aiming for two to three times improvement.
• Products must be noticeably better than the status quo, roughly three times faster or more capable, before customers will switch or pay.
• Define your ICP by watching which early users care enough to pay, often a specific department whose core job depends on the workflow you solve.
• Make customer conversations a recurring calendar habit for PMs, designers, and engineers rather than an ad hoc task, since discovery friction is what kills it.
• Build a customer listening system that processes signals already flowing in from support tickets, reviews, NPS verbatims, churn surveys, and bug reports.
• Keep onboarding setup to a few essential steps, make optional learning available on demand, and define activation as a sequence of increasing milestones.
• Virality is customer-augmented marketing and only works on a genuinely great product; synthetic referral tactics fail if the product itself disappoints.

02Frameworks mentioned

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