Being Responsive is Critical for Successful Customer Development

Most customers tolerate bugs. Most customers tolerate products with missing features that they need (or think they need!) Most customers tolerate the quirks and hiccups that come with new technology and software. This is true of early adopters, but it’s even true to some degree, of late adopters. Customers can be quite forgiving. But what they won’t tolerate is being ignored. Even the feeling or inkling of being ignored can set customers into a rage; and worse, have them looking for alternative solutions to yours.

The way to avoid this is simple: Be Responsive.

Set an early precedent with your startup – that becomes part of your company’s culture – around the importance of responsiveness. And use those customer interactions to learn from them. Your goal is to keep customers happy, but early on it’s so much more than that. You have to learn and understand if that happiness will translate into ongoing product use. You have to learn about customers’ usage, and whether it’s inline with assumptions you’ve made. You have to collect feature feedback and assess the relative importance of those requests. You have to understand the perceived value (or lack thereof) that they’re getting, and analyze any quantitative data you may have.

Being responsive also means being proactive. Don’t wait for customers to reach out with complaints. Don’t expect happy customers to contact you constantly with glowing testimonials. Reach out on a regular basis, create those ongoing touch points and keep customers happy, all the while gathering the intel you need to improve their lives even further going forward.

Responsiveness can mask all sorts of product issues. You’ll be amazed at how forgiving customers will be simply because you responded quickly (almost always more quickly than they expect too!) Responsiveness eases tension, impresses people (because they’re not used to it), and changes how people perceive the product they’re struggling with and the entire company that makes the product. This doesn’t mean you can build crappy products and get away with it just by being responsive. But at the early stages of product development, when you’re putting rough versions into customers’ hands, being responsive is your best tool for keeping people happy and learning how to improve the product itself.


Defining Success

The Lean Startup model is all about running experiments, learning and making informed decisions on what to do next. I’m clearly a believer in the model, but there are some parts of it that are quite nuanced and challenging to figure out. One of those is with respect to experimental design.

A good experiment needs a few things including a hypothesis (that’s testable) and a sizeable enough group of testers. It also needs a definition of success. A good experiment either fails or succeeds. In order to know if an experiment has failed or succeeded, you have to have a measurement for success (anything else is failure). Without a clearly defined target / definition of success, you’ll likely end up in a wishy washy middle ground. You may be running an experiment and collecting metrics, but you can’t really interpret the results without something to compare them to. The missing definition of success leads too easily to a positive justification of the results, after the fact.

So what can you do?

Before starting an experiment, define success. Put a line in the sand. If you cross it, you’ve succeeded. If not, you’ve failed. Remember: Success in this case doesn’t mean you stop learning and iterating, it just means you move to the next experiment and the next phase of your startup.

Defining success is very hard.

There may be market or competitive comparables that you can use. There are a fair number of published numbers for certain things that lots of startups deal with: engagement, conversion rates, etc. But it’s definitely hard to put a stake in the ground and know that if you get there, you’ve succeeded (at least in the experiment you’re running.)

From what I’ve seen, most startups don’t do this very well. They’re not sure how to define or measure success, they base a great deal on gut and intuition. I’m all for gut and intuition – you need both in droves to be a successful entrepreneur – but they’re also great liars. Entrepreneurs are great at fooling themselves (and sometimes we have to in order to keep going!) A pre-defined measure of success can’t lie. It might be wrong, but it turns very gray issues into more black-and-white ones.

There’s very little in a startup that’s black-and-white, but you owe it to yourself before you start anything (whether it’s early validation of your idea, testing the value of a specific feature, implementing a business model, etc.) to come up with a definition of success.


Customer Validation Really Starts with In-Person Interviews

When you have a startup idea, the first instinct is to pitch it to friends and colleagues. This can be somewhat helpful, because they may provide insight that you hadn’t thought of yet, or quickly validate some of your concerns based on their questions. They may be familiar with a competitor worth looking at, or know people in the space that can help. Or they may be able to brainstorm with you and “sniff test” your ideas, which can be revealing about your thought process and where you need to focus. But unless they’re potential customers, it doesn’t really count as quality feedback.

Hopefully most entrepreneurs realize they need more feedback than what they can get from friends and colleagues. Unfortunately, many will want to throw up an online survey and drive traffic to it, hoping to get respondents and quality information. This isn’t where you should start.

The problem at this stage is that you don’t even know what questions to ask. And a good survey assumes you do. It assumes you know what you want to ask and that you’re nearing the stage (or you’re at the stage) where quantitative survey data is helpful for validating or invalidating your assumptions. Before you get to doing a survey — which can be helpful — you need to meet people in-person.

I realize this is tough. You may not have experience interviewing people and interpreting feedback. You may not be sure how to find people to interview. But it’s an incredibly valuable step. It’s the most effective way to get honest, open-ended feedback from people (who you think are in your target market). And it will also increase your own personal confidence and communication skills. It’s almost guaranteed that the original hypotheses and assumptions you had going into the in-person interviews won’t survive, but it’s almost guaranteed that you’ll tease out interesting ideas, trends and new opportunities. You won’t get that kind of rich qualitative data from surveys.

Set a goal to speak with at least 20 people.

Find them by any means necessary. If you have to pay them, do it. They’ll still be honest with you. People love to talk about their problems. Don’t be shy.

By the tenth person you’ll see patterns in people’s answers, and you’ll start adapting your questions accordingly. You don’t need to speak with hundreds of people to get what you need – which is ultimately validation (or invalidation) of your idea. Refine the qualitative data from in-person interviews into more pointed, quantitative survey questions and then try and attract a larger audience to take a survey. The data collection from the survey can further support the findings of in-person interviews. But the process has to start with in-person interviews.


Ben Yoskovitz
I'm VP Product at GoInstant.

I'm also a Founding Partner at Year One Labs, an early stage accelerator in Montreal. Previously I founded Standout Jobs (and sold it).

My bio »

or

Follow me on Twitter

Get updates and special content
When I publish new content, get it directly in your inbox. Subscribers will get special stuff as well not available on the blog (but I promise it will be infrequent + high quality.)
or

Subscribe via RSS Feed

Get the Lean Analytics Book!
Advertisement
Startup Resources
Find Stuff
My Photos