Skip to content

The Customer is Always Right, Right?

Share This Post:

As Founders and Product Owners, we’ve always been told that the “Customer is always right” and we strive to bend over backwards to make prospective customers happy. But when you’re soliciting feedback on a new product concept, should you take what they say at face value? In this blog, we’ll consider five persona traits to watch for in your discovery calls and how to handle them.

Agreeable Andy – Likes What You’re Doing

Agreeable Andy is likely to go along with your product concept and validate many of your assumptions, hopes and beliefs. He may even go so far as to say “Sure, I’d buy it if it was available today.” You need to be mindful that Agreeable Andy doesn’t always do what he says. Also, people like Andy are trying to be helpful and supportive but they provide little constructive feedback. While their words may be gratifying, they could inadvertently undermine your customer validation efforts and send you in a dangerous direction.

Agreeable Andy

To get past supportive sentiment and dig down to real insights, always use open-ended questions that don’t lead the interviewee to any particular answer. Try to understand what key performance metrics the person/department/company uses, and understand how your solution can support those metrics in an objective quantifiable way. Ask questions to get at what would actually trigger real action. You can also consider throwing in some provocative challenge questions that cause the interviewee to think differently about the problem.

Solo Sam – A Market of One

Solo Sam has a problem that needs to be solved and you’re coming along at the right time to help him with it. He’s happy to tell you all about it and will give you valuable feedback on what a solution might look like. He might even pay for the solution (albeit at a discount) in return for his guidance. But if you can’t find a large enough, homogenous market, you don’t have a business.

solo sam

To root out people like Solo Sam, it’s important to speak with several potential customers until you are getting consistent feedback to confirm the problem is commonly applicable and the solution would fit with many other customers with little or no modification.

Seemore Sally – Likes to Learn

Seemore Sally loves to learn. She’s genuinely interested and asks lots of questions to understand what you’re doing. She’ll even give lots of praise about your solution. But the relationship is rather one-sided in that Sally doesn’t share specific insights into her real problems or how her organization would buy a solution such as yours. Don’t be seduced by her interest and praise as it can be an unwelcome drain on your precious time.

Seemore Sally

During your customer discovery calls, make sure you’re in control and leading the discussion to get your questions answered. Ask probing questions, and if you’re not getting the specific evidence you need to support your business, then by all means, add her to your marketing list and share your white papers, but move on to others who can give you the insights you need.

Mirage Mary – Hard to Pin Down

Mirage Mary is passionate about her business. In fact, Mary is a complainer who is quick to point out the inadequacies of others, but is not in a position to do anything about it. She likes to talk and is happy to expound at length about all that is wrong with the company or the industry at large yet it’s hard to pin her down to collect the evidence you’re looking for to validate your business concept.

Mirage Mary

There’s a lot to be learned from Mirage Mary with respect to the problem and although it may be hard to pin her down with objective metrics to quantify the problem, but it’s worth giving it a try. Don’t expect Mary to buy your product, but that’s fine as long as she can educate you and others within the organization or in competing businesses can corroborate your value proposition and are in a better position to purchase when the product is ready.

No Problem Neil – Problems? What Problems?

No Problem Neil is easy to spot and it will become evident within the first few minutes of your discovery call. He’s happy doing his job and likes the comfortable routine of the status quo. But don’t give up too quickly, there’s still something to be learned from Neil.

No Problem Neil

Although Neil is hard-pressed to speak to any problems he would like to solve, Neil can speak at length about the current way things are done. He may even be able to help with value questions like “If we could shrink the time it takes to do “X” from one week to one minute, what would that mean for your business?”

Conducting customer discovery calls is critical to the success of any new product concept, but knowing whom to speak with, what to pull out of the conversation, and how to pick up the right insights from the discussion is important. Occasionally, you may want to consider what not to take away from the discussion.

For more information, please contact the Evidology Group and we’ll lead you through the Concept Validation process. We’ll also share more templates, tools, and best practices.

More To Explore

From Pitch to Purchase in HealthTech

From Pitch to Purchase in HealthTech

The Lean Startup methodology has become a go-to framework for building businesses and products worldwide. However, when it comes to B2B HealthTech, a sector with enormous complexity and regulation, applying these principles can be fraught with challenges.

Read More »

How do you ask someone you don’t know for a “discovery conversation”?

You developed a product, have one in development, or have a dazzling vision described in PowerPoint. You understand the need to validate your plans and ideas by talking with potential customers and others who can offer critical insights. Scheduling a conversation with friends and colleagues can be easy. It’s not so easy to ask someone who doesn’t know you for 30-45 minutes of their valuable time. How do you ask in a way that increases the likelihood of getting a “yes”? First, what are some reasons people wouldn’t talk with you? They: Don’t have time Don’t care about the topic Have no idea who you are or unsure if you’re dodgy Think you’re trying to sell them something Second, what are some reasons people would talk with you? They: Have an interest in the topic; it’s relevant to them Like to share their opinions with others Want to be helpful Comfortable they’re not getting a sales pitch This brings us to an example request which we’ll deconstruct after you read it. Note there is no one “right way” to do this but there are many “wrong ways” to make the ask. And you will need to experiment with the structure and wording based on responses or lack of responses. Here we go: Subject: Asking for your feedback and advice Hi, I found your blog post on quality control really interesting. Your point about using AI and machine learning to identify automation faults stood out for me. Given your quality control knowledge, your help would be appreciated. Briefly, I’m developing a next-generation QA software tool that automatically processes production line plans to identify the optimal QA process overlay. The goal is to dramatically reduce QA planning time to speed time-to-market and reduce QA rework to increase cost savings. To help confirm I’m creating something of value with the right feature set, would you mind spending 30-45 minutes on the phone with me to get your thoughts? To be clear, this is not a sales pitch. I’m seeking real-world feedback to guide product and go-to-market plans. Please let me know if we can arrange a call for next week. Thanks, Alice CEO/Co-Founder, Acme Co. Now let’s break it down:   Make your email as short and concise as possible, certainly no longer than the above example. On a closely related point, use short paragraphs. Reading a big block of text takes too much work; it needs to be easily scanned.   The subject line should clearly state the “ask” using a friendly and personal tone. If the recipient likes to share their opinion and likes to be helpful, they will continue to read.   In the first paragraph, connect to that person. Why are you asking for help from them? You may have seen their name on a website, read about a talk they gave at a conference, read their blog, or scientific paper. You may have found a tidbit on their LinkedIn profile. Maybe someone they know mentioned their name to you. Failing all those scenarios, simply refer to their role/position and likely interests as being the point of relevance.   In the second paragraph, succinctly describe what your product does and its value proposition. You should also provide context by stating your status. Are you designing, developing, or redesigning, for example?   In the third paragraph, state your end goal (e.g. validate your value proposition and supporting functionality) and the specific ask (e.g. time on the phone, meet for coffee, etc.)   In the third paragraph, state what you are not going to do and reinforce this message by saying how what you learn will be used.   Close by asking when they might free for a conversation. Take a somewhat open-ended approach while creating a slight sense of urgency. Asking “can we talk tomorrow at 10 am” makes it more likely you’ll get a “no”. That’s too urgent and likely a booked time. Similarly, asking for “sometime in the future” is too wide open and doesn’t create any sense of urgency.   There’s lots more to be said but let me provide a bit more guidance before letting you get back to your day. Starting with, don’t just send the email and forget about it. After a suitable pause anywhere from three to five business days, send a polite follow up. Forward your original email with three or four sentences saying something like, “I hope you don’t mind that I follow up from reaching out to you last… As mentioned earlier, I am seeking… Your feedback would be appreciated. Are you able to join me on a call…?” In fact, it may take a few follow-ups before you stop to avoid been labelled as a spammer or you get a response that says: “Hey, thanks for your follow up. I was really busy. I’m interested in helping and can talk next Tuesday at 3 pm.” Don’t be discouraged by a low acceptance rate. If 8-10% of the people you email agree to a conversation, you’re doing fine. Should you encounter a lower rate, carefully review how you present yourself: why you contacted them, how you describe what you do, and what you’re asking. Even with a decent acceptance rate, I encourage you to constantly review these items and experiment. If someone is curious, likes being helpful, or possibly flattered by this request, they will read your email and offer their assistance. You’ll be on your way to increasing your customer knowledge. Good luck! For more information, please contact us at the Evidology Group. We’ll share a guide on how to structure effective customer conversations. Of course, if interested, we would be happy to learn about your business, share our experiences, and discuss whether we may be of assistance. You may also wish to read Ash Maurya’s book, Running Lean, which contains lots of practical advice on finding prospects and testing your ideas.

Read More »

Subscribe to Our Blog

Subscribe to our blog and find out about our upcoming webinars.