Conference Presentation, Fireside Chat
How to Build Products Users Love with Kevin Hale (How to Start a Startup 2014: Lecture 7)
- Predicted growth drivers include the gap between conversion rates and churn, with a 1% reduction in churn yielding the same growth impact as a 1% increase in conversion but at lower execution cost, while the speaker identifies the "customer intimate" path as the only market dominance strategy requiring almost no capital.
- Strategic plans to reduce friction and support volume involve redesigning help guides to resemble magazine covers, inserting API credentials automatically into code for logged-in users, reducing documentation complexity by one-time efforts, and focusing engineering resources on internal tools and self-help features rather than new feature development.
- Forecasted user experience improvements rely on treating human-technology interaction as relationship manufacturing, utilizing specific design choices like poetic sign-up forms or "rawr" tooltips to seduce users, and implementing a "since you've been gone" feature to highlight changes during user absences, with the caveat that core functionality must be solid before adding humor.
- Anticipated outcomes from operational and engineering practices include a support-driven development model where engineers handle customer support, the "red phone" experiment which prompts engineers to fix recurring bugs after two or three calls, and the "King for a Day" initiative to democratize product decisions, alongside a remote work model with a four-and-a-half-day week and a 15-minute rule to resolve 90% of non-critical issues internally.
- Risk factors and potential negative outcomes identified include stonewalling customer inquiries as a primary churn cause for startups, siloing engineering from support creating a "divorce" from consequences, limiting thank-you cards to high-paying customers after the first year disappointing loyal users, and the failure of adding wit to products lacking core functionality.
- Specific quantitative predictions include John Gottman's research achieving 85% accuracy in predicting divorce within four years (rising to 94% with hopes and dreams), the "emotional state" field on Wufoo being filled 75.8% of the time, a programming contest with a custom battle axe prize generating over 25 high-quality applications, and a one-time documentation reduction leading to a 30% overnight decrease in support workload.
- Plans for team management and hiring involve contracting remote employees via month-long side projects to assess self-management, asking candidates to write handwritten breakup letters to test tactful communication, and utilizing a shared Dropbox to-do list to create a social pressure trail for accountability, while avoiding demoralizing contests like the "crunch mode" trip-bitch practice.
- Expectations for long-term organizational health include a requirement for developers to interact with users for a minimum of two hours every six weeks to prevent design degradation, the "best overall solution" path enabling growth among passionate niche users to uncover universal values, and the belief that focusing on first-dollar and first-user acquisition values will naturally align the rest of the business trajectory.
- Forward-looking behavioral predictions suggest that breaking the feedback loop causes people to feel divorced from action consequences, that users will universally appreciate attempts to smile or be seduced by software, and that handwritten thank-you cards will clarify company mission and knit teams together.
- Material expectations for customer sentiment indicate that providing outlets for emotions will decrease exclamation marks, curse words, and all-caps communications, while a first impression acts as a significantly lower pass/fail threshold for new interactions compared to established relationships.