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

Core Philosophy and Growth Metrics

• Growth is defined as the interaction between conversion rate and churn, with the gap between them indicating speed.
• The speaker's thesis: The best path to a billion-dollar valuation is to focus on the values used to acquire the first user.
• Wufoo (acquired by SurveyMonkey in 2013) raised only $118,000 for a team of 10, yet achieved a 29,000% return to investors.
• In contrast, the average startup raises $25 million and yields a 676% return to investors.
• Wufoo was run remotely from Florida with no office, relying on word-of-mouth growth rather than paid advertising.

Product Philosophy: "Enchanting Quality"

• The speaker applies Japanese quality concepts: Atatame hinshitsu (taken-for-granted functionality) and Mediokiteki hinshitsu (enchanting quality).
• "Enchanting quality" involves creating pleasurable, memorable interactions beyond basic utility, similar to a relationship's origin story.
• First impressions in software must be memorable; negative first moments (e.g., "picking nose" analogies) are rarely forgiven, unlike minor faults in long-term relationships.
• Examples of enchanting execution cited:
  • Wufoo: A dinosaur logo with a "rawr" tooltip on the login page.
  • Vimeo: Playful fart sounds triggered while scrolling or searching.
  • Quora (formerly a wine app): A signup form written as a poem.
  • Roku: Visual metaphors for scaling backend services via "knobs and levers."
  • Chocolat (Code Editor): Using Comic Sans to signal insider status to their specific user base.
  • Hurl: High-quality design for error messages (404s) rather than generic text.
  • MailChimp: Redesigning help guides to look like magazine covers, which doubled readership and cut support tickets.
  • Stripe: Automatically embedding API credentials into code examples, eliminating manual copy-pasting.
• Wufoo launched an API contest where the prize was a custom-forged medieval battle axe instead of consumer electronics to match company culture.

Long-Term Relationships: Customer Support as a Metaphor

• Marriage researcher John Gottman predicts divorce with 94% accuracy based on couples discussing hopes and dreams for one hour.
• Gottman's "Four Horsemen" of relationship failure map to customer support issues: Criticism, Contempt, Defensiveness, and Stonewalling.
• Stonewalling (ignoring support requests) is identified as a primary driver of early-stage churn.
• Wufoo maintained a 7–12 minute response time during business hours despite processing 800 emails/week with a team of 10.
• Support-Driven Development (SDD): The practice of requiring engineers and designers to perform customer support to close the feedback loop.
  • At Wufoo, developers handled support for 4–8 hours per week.
  • This practice reduced churn and improved product intuition by exposing engineers directly to user emotions.
• Wufoo tested an "Emotional State" dropdown in support tickets; it was filled out 75.8% of the time (vs. 78.1% for browser type).
• Adding the emotional outlet reduced the frequency of exclamation marks, curse words, and all-caps in support emails by making users more rational.
• Research by Jared Spool indicates that direct user exposure (min. 2 hours, every 6 weeks) is required to prevent software design quality from degrading.

Retention and "Keeping the Fire"

• Relationships fail due to the "Second Law of Thermodynamics" (entropy); passion requires constant energy input.
• Wufoo built a "Since You've Been Gone" tool to highlight new features implemented since a user's last login, which became a top-rated feature.
• The company instituted a culture of writing handwritten thank-you cards to users weekly, evolving from a Christmas ritual to a daily habit to maintain connection.
• Productivity is maximized by focusing on reducing the knowledge gap (simplifying the product) rather than adding features that increase the knowledge gap.
• 30% of Wufoo's engineering time was allocated to internal tools and self-help documentation to reduce support load.
• One documentation iteration reduced customer support volume by 30% overnight.

Organizational Structure and Remote Work

• Wufoo operated with a 4.5-day work week; Fridays were reserved for meetings and administrative tasks.
• The "15-minute rule" was enforced: non-critical discussions could not exceed 15 minutes; if unresolved, they were tabled for Friday review.
• Accountability was managed via shared text file to-do lists in Dropbox, creating social pressure through transparency.
• Performance reviews and profit-sharing were tied to customer support performance and project completion.
• Hiring for remote roles involved:
  • Contracting a month-long side project to test self-management.
  • "Breakup letter" writing exercises to assess empathy and communication skills under pressure.
• The company avoided crunch mode after a failed internal competition demoralized an employee; they prioritized sustainable pacing.

Q&A Highlights

• Diverse User Bases: Focus on the most passionate niche first (e.g., Pinterest targeting design bloggers) to establish universal values.
• Balancing Product vs. Marketing: Treat marketing as a "tax" for poor product performance; remarkable products generate organic word-of-mouth.
• Decision Making: Use customer support data to identify underlying problems rather than just feature requests; prototype small versions (1–2 weeks) to validate direction.
• Culture Building: The "King for a Day" program allowed employees to direct engineering resources for 48 hours, boosting morale and democratizing product ideas.
• Failed Experiments: The "crunch mode" contest (first to finish 7 items vs. "trip bitch" punishment) was abandoned due to negative morale impacts.