Key Moments

Picking sharp problems, increasing virality, and unique product frameworks | Oji Udezue (Typeform)

Lenny's PodcastLenny's Podcast
People & Blogs7 min read77 min video
Sep 14, 2023|11,148 views|272|19
Save to Pod
TL;DR

Product frameworks are mental shortcuts that need to be understood fundamentally to be adapted, not blindly followed. True virality stems from solving sharp problems exceptionally well, not synthetic tactics.

Key Insights

1

B2B SaaS market can be segmented into four quadrants based on workflow breadth (everyone vs. niche) and frequency (high vs. low), with high-frequency, everyone workflows being the most profitable but hardest to enter.

2

For a product to be adopted, its solution must be at least 2-3 times better than the status quo, shrinking workflow or increasing output significantly, to overcome switching costs and human inertia.

3

Activation milestones at Calendly included creating the first meeting (basic) and then five meetings within a week (powerful), and at Typeform, publishing a form and receiving responses.

4

Network effects are powerful because they create value for passive members as more people join, making it hard to dislodge established platforms like Twitter, which has achieved critical mass.

5

True product virality is customer-augmented marketing, driven by an exceptionally well-built product that solves a sharp problem, rather than relying solely on synthetic tactics like referral links.

6

Onboarding should be split into mandatory (essential setup, ~3 screens) and optional (beneficial, random access) components, prioritizing brevity and clarity to substitute for sales efforts.

Navigating the B2B SaaS landscape with a workflow quadrant

Oji Udezue introduces a framework for identifying high-potential B2B SaaS markets by analyzing workflows along two dimensions: breadth (how many departments are affected) and frequency (how often the workflow is executed). Workflows affecting 'everyone' and done 'frequently' (e.g., collaboration, email) are intuitively the most profitable but also the most competitive, often dominated by giants like Microsoft and Google. Conversely, 'high-frequency niche' workflows (e.g., Jira for developers, martech tools) offer a strong opportunity for SaaS success. The framework suggests that success for companies in less favorable quadrants (low-frequency, niche or everyone) often involves strategically moving towards higher-frequency or broader adoption, for instance, by developing modules used daily by a specific department. This approach helps founders and investors predict success by segmenting the market and understanding the strategic pathways to scale.

The 'zone of benefit' requires a 3x improvement to be noticed

For a product to gain traction, it must offer a benefit that is not merely incremental, but significantly impactful. Oji Udezue’s ‘zone of benefit’ concept posits that a product needs to be at least two to three times better than the existing solution to capture user attention and justify switching costs. This means either drastically shrinking the time or effort required for a workflow, or delivering substantially more output in the same amount of time. This requires a deep understanding of human behavior, which often strives for leisure, indicating that a product must provide a substantial acceleration or efficiency gain for users to perceive its value and be willing to adopt it. Focusing on a 'sharp problem' that deeply affects users makes it easier to define this zone of benefit and identify the ideal customer profile (ICP) who will be least price-sensitive due to the high value they receive.

Defining sharp problems and finding your ideal customer profile

A 'sharp problem' is one that is materially felt by customers, stealing their time, energy, money, or focus. Founders are advised to seek out these problems, as solving them provides a significant tailwind, making it difficult to fail even with minor mistakes. By contrast, a product built on a nebulous or less painful problem requires substantial marketing investment and is vulnerable to even small errors. Identifying a sharp problem can be done by mapping the current workflow and envisioning how a solution would drastically shorten it (e.g., 2x or 3x reduction). For instance, Calendly's sharp problem lies in scheduling for sales, marketers, and recruiters, where efficient scheduling is crucial for earning money or attracting talent. Typeform's sharp problem is making the web more conversational and human-centric for marketers and product teams seeking better customer engagement, enabling websites to 'talk' to users effectively.

The power and pitfalls of product frameworks

While frameworks serve as valuable mental models or shortcuts, Oji Udezue emphasizes the importance of understanding the fundamental principles behind them. He likens this to being able to derive an equation in mathematics rather than just memorizing it. Given the inherent uncertainty in product management and software development, blindly applying frameworks without understanding their underlying logic can be detrimental. Effective use of frameworks requires adapting them to the specific stage of a company (startup, growth, scaling) and the unique problems being addressed. This ability to adapt and derive insights allows product leaders to navigate complex situations more effectively, rather than being constrained by rigid templates. His upcoming book aims to provide practical guidance on product management for product-led growth, highlighting this need for fundamental understanding.

Continuous customer discovery and listening strategies

Customer discovery is presented as a critical, ongoing process, but Oji differentiates between 'discovery' (optimizing for specific goals) and 'continuous conversations' or 'listening.' For continuous conversations, he advocates for embedding customer interaction directly into the calendars of product managers, designers, and marketers, making it a default activity rather than an opt-in task. This reduces friction, a key barrier to consistent discovery. Customer listening, a newer concept he is exploring, involves actively 'scarfing up' signals from social media, app stores, support tickets, churn surveys, and NPS feedback. The goal is to efficiently process these constant signals to understand customer delight and business ambition, a practice he believes the industry can significantly improve upon. While techniques like pop-up surveys linked to scheduling tools can work, ensuring the 'right' customer is engaged is paramount.

Onboarding as a substitute for sales

Onboarding's primary role in Product-Led Growth (PLG) is to substitute for traditional sales and account management, especially for products serving millions of customers. It must approximate the helpfulness and approachability of a human interaction. This process is framed as understanding the buyer's mindset, drawing inspiration from retail and inventory management for its simplicity and effectiveness. Effective onboarding breaks down the user's journey into key stages: value proposition understanding, simplicity/value assessment, trial, and decision-making. It should consist of mandatory elements (essential setup, like Calendly's calendar connection) that are brief (ideally under three screens) and optional elements for curious users offering deeper exploration. Wizards, while common, have had limited benefit; showing clear examples of successful use cases post-mandatory onboarding is more powerful.

Network effects and the enduring power of platforms like Twitter

Network effects are crucial for the longevity and dominance of platforms. They occur when the value of a product or service increases for existing users as more people join the network. For example, the more people use a file format like Microsoft Word, the more documents you can read and interact with, creating value for you without any action on your part. Twitter's resilience, despite significant internal disruption, is a testament to its strong network effects – users remain because others are there. This creates a critical mass where people join because they know others are already present. While negative network effects or external factors can threaten a platform's revenue or operational stability, the core user base often persists due to the inherent value of the network itself, making businesses built on strong network effects extremely difficult to dislodge.

Understanding Virality as Customer-Augmented Marketing

Virality is fundamentally about high-quality word-of-mouth, where customers effectively market the product for you. Oji Udezue distinguishes this authentic virality from 'synthetic virality,' which relies on tactics like referral links but fails if the core product is subpar. True virality stems from building an exceptional product that solves a sharp problem exceptionally well. Examples like Uber, which drastically compressed the workflow of hailing a cap, or Slack, whose adoption spread organically through teams, illustrate this. Even Hotmail's early 'viral tag' worked because Webmail itself was revolutionary and solved significant user problems. This customer-augmented marketing allows companies to reduce marketing spend, reallocate resources to product development, or gain a competitive edge. The foundation of virality, therefore, is consistent high-quality execution and genuine customer delight.

B2B Workflow Quadrants

Data extracted from this episode

QuadrantFrequencyBreadthCharacteristicsExamples
High Frequency, Broad (Everyone)DailyAll DepartmentsMost profitable but hardest to enter, dominated by large playersEmail, Collaboration tools (Slack), Calendaring, Knowledge Management (Notion)
High Frequency, NicheDailySingle DepartmentThrives, high potentialJira, Recruiter tools, MarTech, SalesStack
Low Frequency, Broad (Everyone)InfrequentAll DepartmentsChallenging, may require module for daily use (e.g., Finance)Expense tools
Low Frequency, NicheInfrequentSingle DepartmentChallengingFP&A planning

Common Questions

The framework involves analyzing workflows along two dimensions: breadth (how many departments it applies to) and frequency (how often it's executed). This creates four quadrants, with high-frequency workflows being the most profitable but also the most competitive.

Topics

Mentioned in this video

Software & Apps
Slack

Mentioned as an example of a product that achieved virality through solving a sharp problem, not synthetic means. It initially had limitations in connecting to organizations but gained traction through word-of-mouth.

Calendly

Aji served as Chief Product Officer here. It's used as a prime example of a successful PLG product, particularly its effective onboarding and scheduling capabilities that drove virality, and its ICP was identified as sales and marketing professionals.

Typeform

Aji is currently Chief Product Officer. It's presented as an example of a company moving from low-frequency to high-frequency niche by focusing on marketers and product people, and is discussed in the context of onboarding and activation.

Jira Product Discovery

A sponsor product mentioned as a prioritization and roadmapping tool built by Atlassian, designed to help product teams gather ideas and create roadmaps.

Coda

Mentioned as a company operating in the high-frequency, everyone workflow quadrant, with its CEO being a friend of the speaker.

Microsoft Word

This word processing software is used as an example of network effects, where the value increases as more people use the file format, allowing more documents to be read.

Notion

Mentioned as an evolution of word processing and workspace tools, falling under the 'everyone workflows' category.

Confluence

Cited as an evolution of workspace tools and an example of Atlassian's efforts to move from niche to 'everyone workflows'.

Jira

An example of a high-frequency niche workflow tool, often used by developers.

SurveyMonkey

Mentioned as an example of a company that has expanded its market by offering more bundled solutions and focusing on specific customer types.

Evernote

The former founder of Evernote created 'Camera,' a product mentioned as an example of a 'sharpish' but not sharp enough problem that ultimately didn't gain broad traction.

Camera

A product created by a former Evernote founder during the pandemic, discussed as an example of a 'sharpish' problem that wasn't painful or transformative enough to gain significant traction.

Hotmail

Historically, it had a viral tag at the bottom of emails, but its virality was also driven by being one of the first revolutionary webmail services that solved significant problems for users.

Unlox

A product Aji uses to optimize his Mac workspace, allowing phone-based proximity login/logout.

More from Lenny's Podcast

View all 26 summaries

Found this useful? Build your knowledge library

Get AI-powered summaries of any YouTube video, podcast, or article in seconds. Save them to your personal pods and access them anytime.

Get Started Free