Brian Rhea Brian Rhea

Never Ask Your Customers: Would You Use This?

“Would you use this?” is probably the worst and most expensive question you could ask a customer.

I made this mistake plenty of times early on in my career when I thought I was doing what it takes to filter out the bad ideas from the good by showing customers a demo and asking what they thought.

The problem is, people have a very generous idea of how ambitious and open to change their future selves are going to be. And when I say “generous” I mean, “dead ass wrong.”

How many times have you commited to a new diet or exercise regimen, only to have Future You flake out when it gets inconvenient?

Anticipating that customers will change their existing workflow — even if it would be good for them — is no different.

So, don’t ask people, “would you use this?”

They’ll say yes either because they can see the advantages or they don’t want to hurt your feelings. But, when they’re in their day-to-day context, just trying to grind out their work and keep the shit to shoe-level, they’ll fall back on their default workflow the majority of the time.

Instead of asking about their future aspirational behavior, ask about their past actual behavior.

“What solutions have you tried to fix that problem?”

“Have you paid for any services that might address that?”

If the answers to those questions are, “None” and “No” then you’ve saved yourself a ton of time and effort compared to a “Yes” that might have come from a sexy design you might have put in front of them.

In his book, “The Mom Test,” Rob Fitzpatrick lays out three simple rules to follow during every customer interview:

  1. Talk about their life instead of your idea
  2. Ask about specifics in the past instead of generics or opinions about the future
  3. Talk less and listen more

This is good advice because it puts all of the focus where it should be, on your customer. As entrepreneurs, we tend to be outwardly confident, very convincing, and great at pitching. These are all terrible traits to bring into a customer research project if you intend on doing any actual research.

I’ll say it again for the folks in the back. The things that make you a great entrepreneur will make you really terrible at conducting customer interviews.

Check your confidence at the door. Suspend your undying faith in your idea. Never ever pitch. Ever.

JTBD App Now in Beta!

I'm working on a JTBD app to help you build better products!

JTBD is an amazing tool, but it can be pretty confusing. I'm working on a product to help teams like yours conduct Jobs to Be Done research you can actually use.

Request early access today!

Related posts

If you're still reading, you'll probably like these.

You Need a Plan, Just Not a “Business Plan”

If you’re early stage and small, take advantage of those strengths with an equally small and nimble business plan.

Product Risk and Market Risk

Understanding the difference between these two types of risk should change how you approach customer research.

Focus On the Problem

One of the most common mistakes people make early on is jumping to a solution too quickly and getting attached.

Don't Build a Vitamin, Build a Painkiller

Last week, I was recording an episode with Jane Portman for my podcast (stay tuned for links and release dates) and as we were talking about moving on from a previous early-stage startup she’d built and sold, she said something that jumped out at me:

Customer Interview Tips & Tricks to Save Time & Money

If you haven’t heard this nugget of truth yet, you will soon: “You’ve got to get out of the building.”

Brian Rhea on UI Breakfast Podcast

The following is a transcript of an interview with the Jane Portman on the UI Breakfast Podcast.

Using JTBD to Increase Acquisition and Decrease Churn

When someone is deciding between sticking with their current solution or switching to a new offer, they find themselves weighing their decisions against the forces of Push, Pull, Anxiety, and Habit.

Jobs to Be Done Framework on the Product Popcorn Podcast

Hello and welcome to Product Popcorn- the podcast that explores topics related to product management

Jobs to Be Done Interview Guide

There's only so much to be learned by reading about or even listening to someone else conduct a Jobs to Be Done interview. You gotta get out there and put the theory into practice yourself.

Pretend the Stakes Are Low Even If They Aren't

When you're kicking off customer interviews to collect feedback on a design or prototype, one of the most important things you should say is:

Is Your Market Leader Susceptible to Disruption?

Do you find yourself in a market with a long-standing, dominant player, and you’re wondering:

Using a JTBD Survey to Quantify Unmet Customer Needs

In this post, I’ll show you step-by-step how I’ve used the approach described in Tony Ulwick’s book, "What Customers Want" to help my clients get a much better handle on what to build, what to improve, what to leave alone, and what to ignore.

How to Write Jobs to Be Done Example Statements

If you're trying to integrate Jobs to Be Done into your design process, you've probably found yourself looking for some concrete examples of Jobs to Be Done statements to be sure you're on the right track.

Start Over with Simplicity or Reduce Complexity?

I was having a conversation with a client recently and they’d more or less come to the conclusion that they needed to do a hard reset on the company and rebuild their application.

The 4 Reasons Someone Will Try Your Product

  • Save Time
  • Save Money
  • Make Money
  • Make Happy

Kano Model (Part 2): Creating Your Survey

Using a Kano-based survey, you can avoid false positives (“Oh, sure I'd totally use that!” ... never uses it) and identify the features your product actually needs to have to satisfy and delight your customers.

Ready to know what your customers actually want? Get in touch.