Product Startup Podcast Episode 137: Get Better Customer Feedback at Launch

Listen Now

Guest: Matt Selbie, President of Opiniator, with more than 25 years of experience researching and implementing customer feedback programs.

Host: , founder of Product Startup and the leading expert in hardware startup consulting. A hardware entrepreneur since 1999, Kevin has advised more than 1,500 founders and built and scaled MAKO Invent through its acquisition by TriMech in 2024.

Episode Overview

Matt Selbie explains why useful feedback depends on asking the right person, near the experience, about a clearly defined part of the product. He covers focused questions, data-driven answers, common feedback fallacies, vulnerability analysis, and turning launch responses into specific product and business decisions.

Podcast cover for Episode 137 about get Better Customer Feedback at Launch

What You’ll Learn in This Episode

  • Companies don’t consider feedback in their corporate strategy for their physical hardware products.
  • Ask the right people.
  • Ask as close to the experience as you possibly can.
  • Ask the right product feedback questions, and figure out exactly what you specifically want to find out.
  • The fallacies in customer feedback.
  • Breaking down the feedback into clear, actionable questions.
  • It is better to focus on clearly data-driven answers rather than general intent open-ended questions.
  • Ask two questions about one feature of your product. Vulnerability analysis.
  • Think about feedback not just for product development but also for how to sell.
  • Feature creep without consulting customers.
  • Hardware product feedback at a product launch.
  • Give the respondents the eventual data.
  • Qualify the respondents.
  • Make the feedback 2 minutes or less.
  • Retail store camouflage of your product.
  • The one thing to make someone consider buying.

Episode transcript

This transcript is provided for accessibility and reference. Download the SRT transcript.

Read the full episode transcript

Kevin Mako: Hello, product innovators. Today we learned from a top feedback expert on how to get valuable customer insights from your physical product launch.

Narrator: You're listening to the Product Startup Podcast, the show that helps bring your product idea to life by chatting with successful inventors,

Narrator: product developers, manufacturers, and hardware industry professionals. Our goal here is to get to the bottom of what makes a product successful, from initial

Narrator: idea to getting your product on store shelves. We're taking you step by step to build. a functional product and scale your product business, hosted

Narrator: by Kevin Mako, one of North America's leading experts on hardware development for small product businesses. Now, onto the show.

Kevin Mako: Welcome back, everyone. Today I'm very excited to introduce Matt Selbie to the show. Matt is the

Kevin Mako: president of a pinnader, a software platform that collects real-time feedback from product customers. He's spent over 25 years researching, strategizing, and implementing customer

Kevin Mako: feedback programs. Today, Matt is going to share some valuable knowledge in how inventors startups and small manufacturers

Kevin Mako: should properly collect customer feedback, when to do it, how to do it, and the importance

Kevin Mako: of it, along with breaking down clear, actionable steps you can use for maximizing the right kind of feedback at your product launch. Now, on to the episode.

Matt Selbie: Hey, Matt, welcome to the pleasure.

Kevin Mako: Thank you very much indeed for having me on. Looking forward today to talking to you about feedback.

Kevin Mako: It's something that's very important to me, very important to hardware brands, especially as they're both getting the idea out to market.

Kevin Mako: And of course, once they do get to market, how do they maximize that customer feedback to help grow their brand and grow the product?

Kevin Mako: So what better person than to talk to you today about this? You're heavily involved in real-time customer feedback, which we'll get into.

Matt Selbie: But first and foremost, how did you get to where you're at today? You can probably tell I'm a Brit. We're based in Portland and Oregon. And my background is largely an oil and gas.

Matt Selbie: But I was always very interested in how any business can make decisions that are customer driven at what's called the point of experience.

Matt Selbie: So the point at which the product or the service is being consumed. So on the service level, it could be when you pick up your car from it being repaired

Matt Selbie: on the product level from you reviewing a bottle of water on the shelf or a new product. And the reason that that's important for you,

Matt Selbie: You and any business, certainly all of those that are listening here, is that without customer-driven

Matt Selbie: feedback, that is driven by those people that you want to buy your product, you won't grow because you'll just be making a guess as to what you think is

Matt Selbie: important, in my view, that'll never do you any good. And it's being sort of borne out by the statistics. So one of the alarming ones here in the US is that 90% of

Matt Selbie: all US businesses collect some form of customer feedback. That's the good news, at which point, Kevin, you might be popping open

Matt Selbie: the champagne, you're out of a job, your design firm goes to hell in a handbasket. The bad news is that only 10% of those 90 actually do anything

Matt Selbie: with the feedback. Now, can you imagine any other more colossal waste of customer resources and business resources? So I think the point to your

Matt Selbie: listeners is that as they think about product development, what are they doing to actively encourage

Matt Selbie: feedback and more importantly, what are they going to do with the feedback when it has been received?

Kevin Mako: So there's a collection phase and then there's an action phase. That's incredible because

Kevin Mako: amazing that the companies are actually going through the effort to collect this super valuable feedback. These are feedback data points from real customers helping

Kevin Mako: guide what they want for the future of the business. And yet so little of that actually turns into action. What is it that is kind of

Kevin Mako: the main problem here and how can a hardware startup that's emerging that's either trying to get their first product to market or maybe they're trying to leverage

Kevin Mako: their customers of their first product to release a second version of the product or increase the brand in any way that they see fit.

Kevin Mako: How can companies do this better, especially in the hardware space? And I know you've done a ton of work with retail chains, a ton of work with hardware companies that are actually

Kevin Mako: launching at exhibitions and how that actually can be kicked back, all this sort of stuff. So what can these hardware startups do to get great feedback?

Kevin Mako: And then, as you said, let's get into it down the road. How do they take action on that?

Matt Selbie: So let's start with collection first and then get to action later. Well, let me give you a how not to do it. So one of the things that I love to do is I ride motorcycles.

Matt Selbie: A few years ago, I actually bought a new motorcycle. That was all fine and dandy. But guess what, Kevin, six weeks after the event, after the purchase, I was called by

Matt Selbie: the motorcycle manufacturing company to say, first question was, quote, did the sales assistant explain all of the features on the three bikes that you tested?

Matt Selbie: Now, I don't know about you, Kevin.

Matt Selbie: I barely remember the names of my children. I certainly can't remember what I had for breakfast. So if you expect me to think about

Matt Selbie: the accuracy of some dude with spots who tried to sell me a motorcycle from six weeks ago, you've got no chance.

Matt Selbie: So the good news is, is they targeted the right customer. Clearly, I was in their consideration set because I'm in the store buying a bike. So the first thing that I

Matt Selbie: would say to your folk who are developing products is ask the right people. There is no point in

Matt Selbie: asking a broad array of the public unless you have a better sense of who is in your what is called a consideration set.

Matt Selbie: Who's likely to buy it? There's no point trying to ask me what I think about razors when you and I both have beards. Not a good start.

Matt Selbie: So the first thing is ask the right people. The second thing is ask as close to the experience as you possibly can.

Matt Selbie: So what would have been much better in that motorcycle example is asking me at the time of consideration. What was it

Matt Selbie: like trying to buy that motorcycle? So on a product side is ask them as they are using it, ask them

Matt Selbie: as they're trialing it, as they're feeling it, as they're reviewing it. And what is the functionality like. The problem that you find is the memory decays over time.

Matt Selbie: And so we know that at least 30% of the accuracy decreases within the first week. And we knew this because of all of the

Matt Selbie: work we did in retail. Asking somebody what happens a week ago, 30% of that is gone. So get your

Matt Selbie: folk to ask the questions at the point of experience or as close to as possible. The third thing is,

Matt Selbie: You know, we talk just now about the statistic about 90% and then 10% only ever do anything with it? Well, it's because that 80%, i.e.

Matt Selbie: the people who don't, ask really dumb questions,

Matt Selbie: breathtakingly stupid questions, either because they haven't thought about it or because they're using a survey methodology that's outdated.

Matt Selbie: And what we see a lot is someone will say, Kevin the boss will say to Matt, hey, get some customer feedback. And then Kevin's buddy will say,

Matt Selbie: hey, can you get some customer feedback as well? So you end up with this war and peace novel of ridiculous questions that's designed to confound and confuse.

Matt Selbie: So the first thing is ask the right person. The second is ask at the point of consideration. And then the third thing that should be

Matt Selbie: your beacon is what is it you want to find out? Don't ask for the world, but what specifically do you want to find out?

Matt Selbie: Do you want to find out about functionality, color, form? function, feel, what is it that you don't know that

Matt Selbie: is critical in order for you to make the next version of the product even better? And for crying out loud, even if you and your

Matt Selbie: folk on listening to the podcast, only remember one thing. It is do not ask more than one open-ended

Matt Selbie: question. Never, ever, ever ask more than one open-ended question. Because to reply to an open-ended

Matt Selbie: question like, hey, what do you think of the product, Kevin? Is very, very taxing on the person who's being asked because they have to go through their

Matt Selbie: brain and say, oh, well, what does that mean? What do I like? What do I dislike? It's very, very difficult. A much better question is about the color of the product.

Matt Selbie: What do you like? What have you seen better? Does this fit what the product is trying to convey?

Matt Selbie: So you break that response choice down into something that's much more manageable. and Kevin, of course, it's therefore able to be analyzed, because

Matt Selbie: once you get the feedback in, if you don't do any analytics on it, then why have you bothered? So I would think those are a few

Matt Selbie: things making sure that whatever you get in, you action, and then you ask, has this become any better? Has this changed it for the good?

Matt Selbie: And it's like a never-ending cycle, taking a product,

Kevin Mako: never really getting over the finishing line, but honing in on the right feature set. for that particular audience.

Kevin Mako: I love the fact that you broke it down into three key actionable items. The first two seem relatively simple to do, although a lot of people don't do it.

Kevin Mako: Asking the right people, number one, and asking them at the time. So assuming that those two are nailed, the third one is where it could get a bit strategic.

Kevin Mako: And that's where you're trying to ask the right questions.

Kevin Mako: So from what I understand from you, you want your questions to be very specific and maybe have one semi-open-ended question, but still be trying to be trying to.

Kevin Mako: to box in that open and question to deal with intent. I want to talk about intent a bit so we can break that down.

Kevin Mako: What sort of intent should a hardware company be looking for when you mean make sure that your questions are targeted? What exactly does that kind of mean and possibly

Matt Selbie: even some examples around that so that we can understand how to ask great questions in that kind of third portion of your three step process?

Matt Selbie: Sure. Intent is a really tricky item. It's you and I and everybody listening knows what intent means.

Matt Selbie: I know what the word means. But when you're asking people, what do you intend to do?

Matt Selbie: That's a really difficult question, even though they understand it, because I'm saying to you, Kevin, knowing that this widget is red, do you intend to

Matt Selbie: buy it? Kevin isn't buying it at the moment. And Kevin, when he wants to buy it, has now got a consideration set of products ABC.

Matt Selbie: And it may not be that red is the right color. So we have, I would really caution your audience into thinking about intent questions.

Matt Selbie: Rather focus on measurement of what's being done now into, is it blue or green? Blue, because you can measure that.

Matt Selbie: Please rate this on a scale of one through five, very efficient, inefficient, and so on. You can measure that. Be very careful

Matt Selbie: with intent questions because you get a lot of false positives. There's a famous one out there that you and your folk will have probably heard. It's called the net promoter.

Matt Selbie: question. The net promoter question is one that I am not a fan of, and I'll tell you why. And you remember,

Matt Selbie: Kevin, we just spoke about asking questions at the point of consumption, at the point of experience. Okay. So imagine you're at an exhibition hall.

Matt Selbie: Imagine you're staring at a product on the retail shelf. Asking someone on a scale of zero to 10, how likely are you to recommend this to a friend or

Matt Selbie: colleague is fraught with difficulty because it's an easy question to answer in front of a computer with a cup of coffee or a beer in one hand.

Matt Selbie: You can really think about it. In an environment where the response is going to be very limited, it's much harder. I don't know whether I'm going

Matt Selbie: to recommend this to my friends. Maybe I don't recommend anything to my friends. So my advice to you and the folk there is be

Matt Selbie: very, very careful when you have intent questions, particularly of the, if we changed it from blue to green, would you buy it?

Matt Selbie: Because I think that's going to give you spectacularly bad results. A much better question would be, is blue the right color?

Matt Selbie: And then ask why blue is the right color. And more to the point saying, if you weren't going to buy this blue widget, who is the

Matt Selbie: competitor that you are most likely to buy something of similar functionality from. Because now you've got something very, very hard and accurate.

Matt Selbie: And a better question after that is, so tell me out of these five reasons, why is it that you would choose brand X over you? So again, you're trying to limit the

Matt Selbie: amount of thinking time. You are trying to limit the amount of open-ended opportunity to describe

Matt Selbie: something in weasel words, which are very hard to interpret, and

Kevin Mako: you've tried to be very, very specific. So I know you are honing us down the intent road. I'm trying to shepherd you back on the non-intent road.

Kevin Mako: So keeping it clear, actionable, and essentially data-driven. I like how you mentioned as well that you're going to ask a question that you're really looking for the answer

Kevin Mako: for. And hopefully if you're a hardware startup, you've got a pretty clear either opportunity or pain point that you see. And you're trying to get real customer feedback.

Kevin Mako: You know, does this hurt your hand or does it not hurt your hand, you know, this device or whatever else? But then you're asking now for a secondary question in addition to that.

Kevin Mako: So the competitive question you ask is, if you're not buying my product and you are intending to buy a product like this, who specifically are you going to buy?

Kevin Mako: And why did you choose that product as opposed to my product? So you're getting the, I guess the data-driven answer that you want.

Kevin Mako: And then you're trying to go one step further into

Matt Selbie: getting actual data back that you can analyze that answer and try and figure out if there's a trend

Matt Selbie: based on various users who are, I guess, migrating away from the product for that reason, right? I agree. There's another way of thinking about this as well.

Matt Selbie: I know in the software world and the hardware world, and to a certain extent the services world, when there is a startup or a company

Matt Selbie: that's just trying to make its decision on products more transparent based on data, there is a tendency to want to have feature creep.

Matt Selbie: If only we had handles that are upside down or it's in blue and spots or it plays the star spangled batter, wouldn't it be much better? That's the kiss of death.

Matt Selbie: So one of the ways we try to think about this is to answer two questions about the same attribute.

Matt Selbie: Some people call this, Kevin, vulnerability analysis. Some people call it key driver analysis. Either of the two terms is just fine.

Matt Selbie: So let me give you an example. Remember, you're asking two questions about one facet or one feature.

Matt Selbie: The first question is right now, using a scale of one to five, how well does this product meet X need?

Matt Selbie: I'll say, let's just use color for the sake of this argument. How well does having a red color meet your need? So it's a how well does it do right now?

Matt Selbie: The second question is, how important is color to you in the selection of a

Matt Selbie: product. It's a two-pronged question about the same facet. Now, when you plot this on a two-by-two

Matt Selbie: matrix, on the x-axis is the how well do we do, on the y-axis is how important is it to the customer? Let me give you an example.

Matt Selbie: Is red the right color and we do that really well? That's going to be on the right-hand side.

Matt Selbie: But if red is irrelevant to the customer, that position is going to be at the bottom right. So you're basically producing something and you're doing really well,

Matt Selbie: but it's completely irrelevant to your prospective customer. So this vulnerability work or key

Matt Selbie: driver work is critical for the startup to understand out of an array of feature properties

Matt Selbie: that they think are important. It's a way of sorting them out and then sorting them out on the basis of how well you do them.

Matt Selbie: Because if red isn't unimportant, for a question, Crying out loud, guys, time out here. Pick something that's really important that will make a

Kevin Mako: difference. All we're trying to do in all of this, Kevin, is to come down from the 30 ,000 feet,

Kevin Mako: make real-time decisions based on strategic questions that are product-specific.

Kevin Mako: That's incredibly valuable stuff. You must have listened to some of these podcast episodes

Kevin Mako: because one of the big things that we talk about here is not just feedback, but it's feature creep, especially in hardware. Because hardware is a difficult.

Kevin Mako: space. If you add a feature, that means you are doing a tremendous amount of work to engineer,

Kevin Mako: test, incorporate that into manufacturing, produce the thing, and then serve it via warranty or however you're serving that feature.

Kevin Mako: So a single feature, not only in and itself can be very complicated, but in hardware, it usually has these interactive relationships to other

Kevin Mako: parts of the product, which can also create new problems and pain points. So feature creep becomes something that you need to hyperanalyze. One of the big messages that we put on

Kevin Mako: the show, especially to a new hardware product coming out on the market or even a new innovation, is really to stick to the core innovation and do a really good job of that one or

Kevin Mako: maybe two sets of features. From there, what you're talking about can really help the audience when they're looking

Kevin Mako: at this product or at the time of use to determine maybe these other three, four, five features, first of all, which of them should you do? Which don't matter at all?

Kevin Mako: And if they're on there, what is the actual importance of those individual features? Because that's something that is always very

Kevin Mako: difficult to ascertain, especially as the innovator, you've got all these crazy ideas, brilliant

Kevin Mako: ideas, really, but what's very difficult to ascertain is what is the actual market reaction to these things?

Kevin Mako: Correct. What better way to do it than actually having the market tell you. So you

Kevin Mako: know where to funnel that money, which really is what it comes down to, time and money to add those

Kevin Mako: features in to get them onto where there's your next version of the product or your

Matt Selbie: pro version of that product or possibly even a stripped down version of that product. You're trying to sell the mass retail. All these things factor into that feed.

Matt Selbie: back loop, which is where your advice here could become very helpful. Well, and also it has ramifications around not just product design, which I know we're talking

Matt Selbie: about today, but imagine if you had a product that you thought you could sell based on six advantages, speed, safety, color, handles, whatever it is.

Matt Selbie: Well, now you're talking about a colossal marketing budget to be able to incorporate all of these things, where it's generally, as you know,

Matt Selbie: in the selling of this thing, the messaging of it, you can really only talk about two or three. So one of the benefits of this type of vulnerability review is

Matt Selbie: that it will give you those two or three. One of the exercises that we've done in the past, which is why we prefer vulnerability,

Matt Selbie: that is the two questions about the same facet, rather than incorporating a list and you say, hey, Kevin, these are these five facets, just rank them one, two, three, four, five.

Matt Selbie: That's a really arbitrary process that involves a lot of thinking. Why is it that this is number three where it's so close to number four?

Matt Selbie: And your head sort of slightly explodes with it.

Kevin Mako: We find the vulnerability way a much more important way to distinguish between these different facets that focuses the

Kevin Mako: mind on the right things to focus on. Very useful. And I love how you're mentioning both the product development side and the sales side. Those two generally go hand in hand.

Kevin Mako: That's one of the incredible advantages of focusing on an MVP, very clear, very niche first version of your product. It's not just the eases in developing it, manufacturing.

Kevin Mako: it, refunds, defects, et cetera. I mean, you save a tremendous amount of cost up front, but being able to hone down on that

Kevin Mako: message, which is that what is the one key driver of your product? What's your tagline?

Kevin Mako: What's that major impact statement that really resonates with the hearts of your actual users? Either way, whether it's development or whether it's sales, this is still going to be

Kevin Mako: applicable in both fields. I want to talk a bit about somebody who is launching a new product.

Kevin Mako: You've done a lot of work in exhibition halls where people are showcasing for the first time their product to a general audience.

Kevin Mako: Sometimes it can be more specific if you have certain interest groups coming to your booth. But imagine somebody's launching a product in one way or another, whether it's on

Kevin Mako: Kickstarter, whether it's direct consumer on their website, whether it's at a trade show. What are some tips

Matt Selbie: for hardware companies that you see in addition to what we talked about already that are some either really good

Matt Selbie: questions asked or really good ways to frame their feedback loop or just other tips and tricks to get that good feedback on an initial launch of their new product.

Matt Selbie: One of the things that we find has an enormous impact is if you say to a prospect,

Matt Selbie: whoever comes to the booth or whomever you are requesting of that feedback, is we will give you the results of the feedback that we collect.

Matt Selbie: So I'm basically saying to Kevin, Kevin, I really respect your time giving the feedback here today.

Matt Selbie: We're going to be committing to reviewing the feedback and then we will let you know what happens. One of the reasons that that's important is because now Kevin feels important

Matt Selbie: enough to know that whatever he gives, two minutes, five minutes, whatever that is, it's going to make a

Matt Selbie: difference. So we know that the response rate goes up by at least 10 % when you do that. So first thing

Matt Selbie: I would say is make a commitment to make that at least back to Kevin or more public in general.

Matt Selbie: You don't need to go into the warts and all of it, but that would be the first thing. The second thing is to qualify a person who's giving the feedback.

Matt Selbie: Now, I know that that's something we just talked a little bit about beforehand. There is no point asking my dad, who's 86, to

Matt Selbie: give you feedback about an Xbox controller. Absolutely none whatsoever. So have a number of questions that you can qualify the person, not

Matt Selbie: based upon intent to purchase,

Matt Selbie: but are these the right sort of people that are in your wheelhouse that might purchase at some point? So that would be the second one. So I have a couple of qualifying questions.

Matt Selbie: The third one is to make that feedback short. So let me give you an example. In what's called an out of home point of experience feedback

Matt Selbie: session, which is what we're talking about, an exhibit booth, make sure that the feedback that's been requested lasts no more than two minutes.

Matt Selbie: If it goes beyond two minutes, we find that the quality and the accuracy of the answers diminishes.

Matt Selbie: rapidly because people get bored. How much more is Kevin going to ask me? You've got to be kidding. This question is just like the one I asked earlier.

Matt Selbie: Just keep it short and manageable and tell Kevin up front, hey, Kevin, we want two minutes of your time. A fourth one is to say, okay, so we've

Matt Selbie: talked a little bit about vulnerability analysis. We've spoken a little bit about some of the key things.

Matt Selbie: One of the questions should be particularly end, okay, Kevin, we didn't score five out of five for handle design.

Matt Selbie: What is the one thing we can make this product be to make it part of your future consideration? So again, let me break that down.

Matt Selbie: I'm not asking you for the meaning of life. I'm not asking you for your mother's maiden name or what your dog had for breakfast. I'm asking you for one thing.

Matt Selbie: Why is that important? Because now Kevin only has one thing that's occupying him and it's top of mind.

Kevin Mako: It will be the thing that he's thinking about first, which means he can regurgitate it easier. So when you add those four things together,

Kevin Mako: the feedback session at the exhibit hall or wherever is going to be the most productive and you can get through the most people.

Matt Selbie: Does that all jive? This is incredible that you've broken it down into clear, actionable steps. I have so much appreciate the tactical approach to it.

Matt Selbie: You deal with a lot of this in the service that you offer now. Talk a bit about what you're doing to help people get that real-time data and get it in the right way.

Matt Selbie: Well, I mean, we have a software as a service technology that allows feedback to be delivered at this point of consumption.

Matt Selbie: And the reason that we did it, Kevin, is I'm sure that you're a coffee drinker. Okay. Now, there is no point asking you feedback on

Matt Selbie: the cup of coffee you're drinking now tomorrow. Absolutely none whatsoever. The only feedback that's relevant is what you're experiencing right now.

Matt Selbie: So the feedback software that we have can be used at really any point in what's called the customer journey from whether they're parking their car to eventually buying

Matt Selbie: the product at checkout. But it couldn't be about any part of that journey. Could they find car parking space? Were the people friendly? Could they find the product?

Matt Selbie: What does that product look like on the shelf? And one of the things that I would encourage, I know we've been talking about product feedback.

Matt Selbie: I know we've been talking about product development. But at some point, you have to assume that,

Matt Selbie: the product that is in this laboratory condition that is in your design studio or in a small

Matt Selbie: business garage with kind of cups of noodles hanging over their head with these sweat on their brow developers, you need to understand how that product is going to

Matt Selbie: look in situ. So we can talk about retail, for example. There is a phenomena in retail called camouflage, retail camouflage. So imagine

Matt Selbie: Kevin has developed a beautiful blue widget and it's going to be sitting. in the category of widgets, on the shelf of widgets, at the

Matt Selbie: back end of a store. What you need to do is to also design what you think that product needs to do to stand out

Matt Selbie: amongst the widgets that are there. Otherwise, you're going to get lost. I don't care whether the thing has got, it could have a cake with dancing girls coming out of it.

Matt Selbie: Unless it's seen, all of that stuff will be wasted. So one of the things that we do a lot in retail, exhibits and exhibitions as well, is to get

Matt Selbie: feedback about the way it's situated. Can I see it? What was the most important thing that struck me?

Matt Selbie: What other product that was adjacent got my attention even more? So it's really worth your audience

Matt Selbie: thinking about the situation of the product once it's left the aseptic conditions of the

Matt Selbie: laboratory and design place that you've spent so much time talking about. So don't just get product

Matt Selbie: feedback, but once it's situated, get feedback on the efficiency of its placement. How does your software fit into all this?

Matt Selbie: Well, because we allow that feedback to occur at the point of consideration. So we do quite a lot of work in retail where you've basically got two audiences.

Matt Selbie: You've got a shopper, but you've also got a browser, someone who's walking around the store thinking, I might buy it, I might not buy it.

Matt Selbie: And so what you typically see is signage that's adjacent to the product that invites feedback using the cell phone, whether they text in, call

Matt Selbie: in, QR code in, or go online. And we do it in various languages and then walk that person through a very short, specific list of

Matt Selbie: questions that the product company doesn't know the answer to. So we did one recently with a water company.

Matt Selbie: The very thing that they thought was going to drive sales was inconsequential in the ranked list

Kevin Mako: of things that we found that was important to that buyer in considering what water to bring to the

Matt Selbie: market. And this is particularly important when the product is being introduced, because that's when the vision is the freshest.

Matt Selbie: So that's how we can help in these types of environment. Matt, much appreciated for all your words of wisdom today. I'll also put in the show notes links

Matt Selbie: to your software and your LinkedIn and all that sort of stuff. Thanks again for being on the show. It's been a pleasure talking to you. I hope it's been of some value.

Matt Selbie: and keep putting out the great stuff. Absolutely. Thanks, Matt. Appreciate it. Thanks. Bye now.

Narrator: Thanks for tuning in to this episode of the Product Startup Podcast, the show that teaches you what it really takes to bring your product to market

Narrator: and turn it into a big success. This podcast series is brought to you by Mako Design + Invent,

Narrator: the original and leading firm in North America to provide global caliber in-to-end physical consumer product development to startups, inventors,

Narrator: and small product business clients. If you're looking for product development help on your invention, head over to MakoDesign.com.

Narrator: That's M-A-K-O Design dot com for a free consultation from one of Mako Design's Ford Design Studios from coast to coast.

Narrator: Thanks for listening and see you next time.

Customer Feedback Strategy for Product Founders

Collect Feedback You Can Actually Use

Work directly with Kevin Mako to define what you need to learn, who should answer, when to ask, how to structure the questions, and how results should influence the product, launch, positioning, or next iteration.

Kevin can help you separate evidence from polite opinions, identify the highest-risk assumptions, and build a feedback loop across prototypes, pilot runs, launch, support, and repeat sales.

Request a Customer Feedback Strategy Call

Tell Kevin what you need to learn, who has used the product, and why the feedback collected so far is not decisive.