"What cool new products are you using?"
We all ask this question. It's a common conversation starter, especially in the startup community. I'm particularly fond of this topic--I enjoy geeking out about products, writing design deconstructions, and swapping discoveries with smart folks. But these conversations provide more than just entertainment value: They are also a great learning opportunity. Understanding the subtleties of good and bad products is critical for product builders. As Paul Buchheit says, you must "live in the future" to shape it. Playing with early, innovative products can provide a competitive advantage.
This was the basis for Product Hunt. Here's how we prototyped it.
The concept was simple: to build a community for product people to share, discover, and discuss new and interesting products. But when I came up with the idea, I lamented the amount of work needed to build a first version of Product Hunt. Even a basic Ruby on Rails app would take me weeks to build. Although confident in my idea, I didn't really know if anyone else would use a service like this. I wasn't about to spend dozens of my nights and weekends building something no one cared about. How could I bring it to market sooner to test my hypothesis?
It was unusually chilly that morning in San Francisco when I walked to my office, Philz Coffee. I ordered and claimed my usual seat. After unloading my MacBook, I peeked at my to-do list to find something I jotted the previous week:
- Create Product Hunt
In a burst of motivation to make Product Hunt a reality, I brainstormed ways to build a quick MVP to see if people cared to share and discover products. After noodling over a few ideas, I was reminded of Linkydink, a link-sharing tool by the friendly folks at Makeshift. Simply create a group and invite people to share links with other contributors and subscribers. Each day, the collection of posts are emailed to the group. "This is perfect!" I thought, mentally fist-pumping with excitement.
Within 20 minutes, I had an MVP.
I sat back, sipping my coffee, anxious to see how people would respond.
Immediately, I received overwhelmingly positive feedback, first from Ash Bhoopathy, entrepreneur-in-action at Sequoia Capital.
Fun experiment, I've been wondering why something like this hasn't existed on a larger scale. It's probably the PM / growth dude's best replacement for 'Dribbble' for collecting inspiration.
Then from a partner at Union Square Ventures, Andrew Weissman:
Love how you have all kinds of VCs subscribed! Build an angel list syndicate off this list and disrupt them (us) ;-).
And then from Talton Figgins, product support lead, Disqus:
Wrote this idea off at first when I first read about it but after checking out some of the recommendations (Peak, Sqwiggle, Calm, and Cycloramic) I'm hooked. Can't wait to check out more.
Within two weeks, over 170 people had subscribed to product discoveries from 30 hand-picked contributors, consisting of startup founders, VCs, and prominent bloggers. Even more encouraging were the numerous unsolicited emails and in-person conversations expressing their love and support of the project.
It's still very early but these signs of traction are encouraging, especially considering the minimalism of the "Linkydink MVP" and my (intentional) lack of marketing of the product. Granted, I didn't launch the MVP with a blank slate. Years of blogging, relationship building, and projects like Startup Edition have given me an audience and network of supporters. The term "startup" is deceiving. Successful companies don't start up overnight; they are founded upon years of experience and help from others that must be earned.
The results of the MVP gave me confidence in the idea: I had found something compelling. I began to research technology to build a complete product. Some of my engineering friends recommended Sinatra or Ruby on Rails. Unfortunately, I didn't have any experience with these frameworks and while assured in my idea, I was still operating with many hypotheses of what the product could be. I wanted something sooner to test my next series of assumptions. I started to look into Sacha Greif's Telescope, an open-source app for creating your own Hacker News or Reddit-like community. Pleased, I reached out to my good friend and designer/developer Nathan Bashaw to get his thoughts:
Yes! Eight days later, we launched Product Hunt.
The "20-minute Linkydink MVP" was a great starting point. It allowed me to validate some assumptions very quickly and observe real user behavior without a single line of code. Entrepreneurs often assume an MVP needs to be "built." The purpose of an MVP is to learn, to validate and invalidate assumptions. There are almost always faster ways to do this than building a product.
Next time you have an idea for a new product or startup, ask these questions before touching a line of code:
- Identify your assumptions: What assumptions do you have about your idea? What must be true for the product to succeed? How do you identify your audience?
- Test your assumptions: With your riskiest assumption in hand, brainstorm ways to validate or invalidate that assumption quickly. Use landing page tests, Wizard of Oz experiments, customer interviews, and other tactics to gather feedback from your target audience.
- Learn and iterate: If your assumption in the previous step is invalid, reevaluate the idea and your target audience. If you're lucky enough to be right, congratulate yourself and test the next riskiest assumption.
This lean approach and mentality was used to birth Product Hunt and its ongoing development.
Over Thanksgiving break, my talented friend Nathan built the first version of Product Hunt. On November 26th we began seeding the community with a few select founding contributors. A week later, we formally launched in the press, receiving another healthy spike of adoption and feedback.
This is just the first post of a series where I will share the strategies, tactics, and surprises we encounter building Product Hunt. Check back on FastCo.Labs for more, or subscribe to my blog to follow along.
[Image: Flickr user Jennie Rainsford]