Key Moments

How to Build Products Users Love with Kevin Hale (How to Start a Startup 2014: Lecture 7)

Y CombinatorY Combinator
Science & Technology4 min read49 min video
Mar 24, 2017|101,669 views|2,679|45
Save to Pod
TL;DR

Build products users love by focusing on user experience, relationships, and support-driven development.

Key Insights

1

Cultivate passionate user bases by creating products users love, not just use.

2

Prioritize 'enchanting quality' beyond basic functionality in product design.

3

Treat new user acquisition like dating and existing user retention like marriage.

4

Integrate customer support directly into the development process (Support Driven Development).

5

Focus on reducing the 'knowledge gap' for users through intuitive design and resources.

6

Long-term success hinges on customer intimacy and emotional connection, not just price or product features.

THE ESSENCE OF PRODUCTS USERS LOVE

Kevin Hale defines 'products users love' as those that foster a passionate user base unconditionally invested in the product and company's success. He contrasts this with simply building products people 'use.' This approach moves beyond a purely mathematical view of growth (conversion rate vs. churn) to a more human-centered perspective. The core philosophy is that focusing on the values that help acquire the first user and the first dollar is the most effective path to significant long-term success, an idea he cultivated through his experience with Wufoo, a successful online form builder acquired by SurveyMonkey.

THE ART OF FIRST IMPRESSIONS AND ENCHANTING QUALITY

Hale likens acquiring new users to dating, emphasizing the critical role of first impressions. Origin stories, like the first kiss or how a couple met, are retold and shape relationships. Similarly, a product's initial interactions—the first email, login experience, or customer support contact—are crucial opportunities to 'seduce' users. He introduces two Japanese concepts of quality: 'at-tashi' (taken-for-granted quality/functionality) and 'me-doki' (enchanting quality). Products with me-doki offer pleasure beyond mere function, like a pen's weight or ink flow, making the user experience delightful and memorable, similar to Wufoo's dinosaur login or Vimeo's interactive elements.

MARRIAGE: FOSTERING LONG-TERM USER RELATIONSHIPS

Extending the relationship analogy, Hale compares retaining existing users to a successful marriage. He draws on marriage researcher John Gottman's work, which identifies key predictors of relationship success or failure. Gottman found that successful couples don't avoid conflict but manage it constructively. Hale maps common marital conflicts (money, kids, sex, time, jealousy, in-laws) to customer support issues (pricing, billing, performance, competition, partnerships). Ignoring these issues, particularly through 'stonewalling' or lack of response in customer support, is a major cause of churn and relationship breakdown. Proactive, empathetic customer support is vital for long-term retention.

SUPPORT DRIVEN DEVELOPMENT: CLOSING THE FEEDBACK LOOP

A significant problem in startups is the 'broken feedback loop,' where technical founders become divorced from the consequences of their actions post-launch. To combat this, Hale advocates for 'Support Driven Development' (SDD), a practice where everyone, including engineers and designers, participates in customer support. This direct exposure to user problems and feedback creates accountability and humility, leading to higher quality software. SDD fixes the feedback loop by making the builders the supporters, ensuring they understand user pain points firsthand and are motivated to fix bugs and improve the product based on real user interactions.

REDUCING THE KNOWLEDGE GAP FOR INTUITIVE PRODUCTS

Hale introduces Jared Spool's concept of the 'knowledge gap'—the difference between a user's current understanding and the knowledge needed to effectively use an application. He argues that the common approach of adding more features often widens this gap. Instead, focus should be on reducing it by making the app more intuitive. Wufoo spent 30% of its engineering time on internal tools and self-help resources like FAQs and contextual help links. Redesigning documentation, like Wufoo's magazine-style guides or Stripe's integrated API key examples, significantly reduces customer support load and improves user experience, highlighting the power of investing in usability.

MAINTAINING PASSION AND DELIVERING VALUE

Sustaining user engagement requires continuous effort, likened to the second law of thermodynamics where energy must be continually added to prevent systems from running down. While blogs and newsletters are common, they often reach only a small percentage of users. Wufoo implemented a 'Wu Alert System' that notified users of new features upon login, showcasing constant improvement and reinforcing value. This created a perception of ongoing development and a strong return on their subscription. Additionally, handwritten thank-you notes, a practice stemming from a personal anecdote about receiving better Christmas gifts after sending notes, became a weekly ritual that fostered team cohesion and user appreciation.

THE PATH TO MARKET DOMINANCE THROUGH CUSTOMER INTIMACY

Hale references a Harvard Business Review article outlining three paths to market dominance: best price, best product, or best overall solution (customer intimacy). While price and product dominance require significant resources, customer intimacy is accessible to all companies, regardless of stage or funding. It requires humility and good manners. Wufoo's success, demonstrated by its high investor return relative to funding, was largely due to this customer-centric approach. By focusing on understanding and delighting users, companies can compete effectively and achieve remarkable growth, often driven by word-of-mouth rather than expensive marketing campaigns.

Building Products Users Love: Key Takeaways

Practical takeaways from this episode

Do This

Focus on the 'enchanting quality' (mid keku) beyond basic functionality.
Create memorable 'first moments' beyond the obvious login or signup.
Inject personality and wit into forms, error messages, and documentation.
Involve the entire team in customer support to fix the feedback loop.
Directly expose developers to users regularly (at least every six weeks for two hours).
Prioritize reducing churn by improving existing features and user experience.
Timestamp new features to show users the ongoing value they receive.
Practice humility and modesty by saying 'thank you' genuinely.
Focus on niché, passionate users in the early stages.
Respect remote workers' time with structured workweeks and short, focused meetings.
Use simple tools like shared to-do lists for accountability.
Hire by assessing remote work capability and empathy through practical tests.
Emphasize customer intimacy for market dominance if you can't compete on price or product alone.

Avoid This

Don't just aim for functional products; aim for products users love.
Don't neglect the small details and interactions that create 'first moments'.
Don't make all products follow the same generic template (like Yahoo's login form).
Don't silo technical teams from the consequences of their actions; fix the feedback loop.
Don't assume users understand complex information without clear, engaging documentation.
Don't rely solely on blogs or newsletters; ensure active users see value.
Don't ignore the emotional state of users seeking support.
Don't add features solely to increase functionality; focus on reducing the knowledge gap.
Don't forget that reducing churn is as impactful as increasing conversion and often cheaper.
Don't make customers wait excessively for support or make them feel forgotten.
Don't fall into the trap of 'stonewalling' customer feedback.
Don't mistake 'crunch mode' for a sustainable productivity strategy; it can be demoralizing.
Don't just interview candidates; test their remote work and customer support skills.

User Support Metrics at Wufoo

Data extracted from this episode

Support ChannelUser Volume (Approx.)Response Time (9 AM - 9 PM)Response Time (9 PM - Midnight)Response Time (Weekend)
Direct Support (10 people for 500,000 users)400 issues/week (800 emails)7-12 minutes1 hour24 hours

Emotional State vs. Browser Type Feedback at Wufoo

Data extracted from this episode

FieldFill Rate (%)
Emotional State75.8
Browser Type78.1

Impact of Documentation Redesign at Wufoo

Data extracted from this episode

ActionResult
Redesigned documentation (AB tested)Reduced customer support by 30% overnight

Jared Spool's Guidelines for Direct User Exposure

Data extracted from this episode

FrequencyDurationRequirement
Minimum every six weeksAt least two hoursDirect, real-time interaction (not through reports/graphs)

Wufoo's Developer User Exposure vs. Spool's Guidelines

Data extracted from this episode

SourceExposure Time per Week
Wufoo Developers4-8 hours
Jared Spool's Minimum2 hours (every six weeks)

Market Dominance Strategies (HBR Article)

Data extracted from this episode

StrategyFocus AreaExample Companies
Best PriceLogisticsWalmart, Amazon
Best ProductR&DApple
Best Overall SolutionCustomer IntimacyLuxury Brands, Hospitality

Common Questions

Kevin Hale defines building products users love as creating things with a passionate user base that users unconditionally want to see succeed. This goes beyond mere functionality and focuses on building a relationship with the user, making them feel emotionally invested in the product and company.

Topics

Mentioned in this video

More from Y Combinator

View all 362 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.

Try Summify free