WhoBuilt

Communicate with Users, Build Something They Want

Oct 4, 2017· 49 min· 71K views·Watch on YouTube

Speaker

Ryan Hoover, founder of Product Hunt, talks with a Y Combinator host about validating ideas, growing a product community, and building a company and team.

Validate with simple tools

Hoover says Product Hunt began as an email list that took about 20 minutes to set up and quickly drew a few hundred subscribers. Email, Typeform, and Stripe can help founders test interest and willingness to pay before investing in code. He says early growth, including roughly 50% month-over-month growth in visits, helped demonstrate demand to YC.

Build with and communicate with your audience

Hoover describes Ship as a toolkit for announcing products, collecting emails, and getting feedback. Product Hunt had previously combined tools such as Mailchimp, Typeform, and InVision to do this. He argues that involving users and responding to them increases the chances of building something they want.

Grow a community through relationships

Hoover says his writing and relationships with founders and investors helped attract Product Hunt’s first few hundred subscribers. Press and guest articles brought early users, and he personally invited makers to join conversations about their products. Later, community members could tag makers, and a bot notified them at scale.

Use accountability and delegate as the team grows

Hoover says YC’s weekly group office hours created accountability and encouraged the team to follow through. As Product Hunt hired, its processes changed, while a data-driven and customer-focused culture continued. He learned that changing a designer’s work himself caused frustration, and that founders need to give skilled teammates autonomy.

Make distributed work and product discovery work for users

Hoover says Product Hunt had 17 people across eight or nine time zones, with about two-thirds outside San Francisco. A distributed team widened hiring options, reduced location constraints, and may have helped the company understand international users. He also describes serving both people who enjoy a daily stream of products and those who prefer a weekly digest.

Takeaways

  • Test demand with the simplest useful version, such as an email list, before building software.
  • Ask potential users for feedback early and keep them involved as the product changes.
  • Build an audience and relationships before launch so early users are ready to participate.
  • Use regular check-ins to create accountability, then give specialists room to do their work.
  • Choose communication formats that suit different users, from frequent updates to a concise weekly digest.

Mentioned in this talk

Search inside this talk

What was claimed 14

Show all 14 facts

Related talks