FAQ: Customer Development for Product Managers
What is customer development?
Customer development is the opposite of product development, or “if we build it, they will come” thinking. We all know that’s not the case – often you build it, and no one cares.
The idea is to validate that you have a market, with problems, that they’re willing to pay to solve — and then build something that solves those problems. The emphasis is on learning and discovery before you write a 50-page spec or spend months writing code. Read Eric Ries’ post What Is Customer Development for a lot more detail.
“This doesn’t sound like anything new,” you may be thinking, and you’re pretty much right. There are plenty of examples of successful companies who used interviews and cheap prototypes to validate ideas before committing to building them.
What has changed is the availability of free/cheap tools and direct access to customers through social media, making it more practical for an individual product manager to do this on their own, on a skunkworks basis even.
But asking the customer what they want never works –
I know. Customers tend to ask for “me-too” features, or they ask for something and then after you build it, say “I know we asked for this, but it isn’t what we really wanted.”
Customer development isn’t asking customers what they want – it’s seeking to understand what they need, how they work, where their pain points and highest priorities are. Customers may not be able to articulate what they want, but they can’t hide what they need.
What will I learn?
The short answer: how people are really getting a task done, who is doing what, and why it sucks.
The more detailed answer: What you should be learning from customer development interviews
How is this different from usability testing?
Usability testing teaches you whether or not people are capable of using your product; it doesn’t tell you how likely they are to actually buy it.
In usability testing, you learn about the product you’ve already built. If your product hypothesis was wrong, it’s kind of too late to do much about it. In customer development, you learn about your customer before you build the product. That way, if your product hypothesis is proven wrong, you can change course quickly without having wasted resources and time.
How long will it take?
I don’t know.
Sorry, but that’s the truth. I can’t guarantee that this methodology will get you useful answers in two days or two weeks. I can guarantee that you’ll start learning useful new tidbits from your first customer interview, but it may not be something actionable.
At KISSmetrics, I quickly learned that the reason so many companies loved our Survey.io customer development survey is that “I don’t have to write anything – you tell what I should be asking and how to ask it”.
People don’t like to write – in fact, they’ll put off a task if it requires them to think and write something. That was a good insight, but not enough (on its own) to drive any new product decisions. We needed more of those insights before they added up to something we could base a product on.
For this reason, customer development needs to be a process — not a project. Always be listening, always be asking why, and always be testing hypotheses, and it will pay off. You just never know when.
How do I get started?
If you already have existing customers, reach out to one today and schedule some time to talk with them about how they get their jobs done. Ask about how they use your products, but also take a step back and ask about the general task that your product is supposed to help them with (i.e. if your product is a bug tracker, ask them about QA testing in general).
You don’t have a hypothesis to test (yet), so this is just an open-ended conversation. Let the customer talk. The Evolution of the Customer Development Interview has good tips.
You may be at a company who has existing products and customers, but you don’t have access to them. As insane as this is, it’s not uncommon to try and lock the product managers up in a little room to wrangle up requirements somehow. The fastest way to get access is probably to bargain directly with sales.
Ask to join them on a sales visit or conference call. Offer to help with demos. If you have to promise to be a “fly on the wall” in order to make them feel comfortable, do it. In my experience, customers love having a product manager in the meeting – they feel like you’re an ally who isn’t just trying to sell them — and as a result, they’re often MORE likely to buy. (Tell your salesfolk that.)
How can I find customers before I’ve even built a product?
How were you planning on finding them after you’ve built a product?
Seriously, this is the million-dollar question, and the answer is not “we’ll build it and they’ll come” or even “we’ll advertise a LOT” — unless you’re Apple, Microsoft, Google, or Facebook, you don’t have the dollars or distribution to make those work.
So you have to get creative. I’ve previously written about how to find prospective customers using methods that take less than $20 and a couple days.
How do I convince my boss that this is a good use of my time?
Unless your boss is already a devotee of Toyota Lean Manufacturing processes or Four Steps to the Epiphany, start out skunkworks style. Remember, bosses like solutions, not problems. Don’t say “we need to be doing X”, figure out how it can be done and prove the benefits.
Carve out some time, do some customer interviews. Work with a designer to throw together a fake splash marketing page for a new product and get feedback. Once you’ve learned something useful, use that to get buy-in for making this a permanent part of your process.
How does this change when I have an established brand and customers?
You may need to create somewhat more polished splash pages/demos in order to not hurt your credibility.
You may also feel more comfortable testing concepts without connection to your company name. Using another domain name is a good option and worth the time to set up if you’re going to be running experiments frequently. But you can go even simpler and use tools like shared Google docs (create a new Google account that isn’t linked to your name) or Skitch to post screenshots privately.
Where can I learn how to do this?
Books:
- The Four Steps to the Epiphany
- Tuned In: Uncover the Extraordinary Opportunities That Lead to Business Breakthroughs
- Inspired: How To Create Products Customers Love
Blog posts:
- Why Your Customer Feedback is Useless by Laura Klein
- 7 More Ways People Suck at Customer Development Interviews by Laura Klein
- The Evolution of the Customer Development Interview by Sachin Agarwal
- Customer Development Interviews How-to: Finding People by Cindy Alvarez
- Customer Development Interviews How-to: What You Should be Learning by Cindy Alvarez
- How I Learned to Grok Customer Development by Ash Maurya
- How I Built My Minimum Viable Product by Ash Maurya
- Customer Development Checklist for my Web Startup by Ash Maurya
- What Is Customer Development? by Eric Ries
- When NOT to listen to your customers; when NOT to rely on split-tests by Eric Ries
- How to Develop Your Customers Like You Develop Your Product by Nivi at VentureHacks
- Customer Development is not a Focus Group by Steve Blank
- Customer Development – Past, Present, and Future by Steve Blank
- Customer Development Update (and why I’m sticking with 1-on-1 talks) by Giff Constable
- Seller Beware: Customers Have Their Own Agenda by Brant Cooper
- How to Find Early Adopters by Brant Cooper
People to follow on Twitter:
- @ashmaurya
- @brantcooper
- @cindyalvarez
- @ericries
- @giffconstable
- @hnshah
- @lauraklein
- @richcollins
- @sgblank
- the #leanstartup and #customerdev hashtags
