Brian Rhea Brian Rhea

The 4 Reasons Someone Will Try Your Product

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

My friend, Andy, wrote those eight words on a whiteboard almost two years ago and they’ve found their place in my head like a well-written poem ever since. Those are the four basic reasons someone will start using your thing.

Your product or service has to save time, save money, make money, or make happy. But, before letting yourself off the hook too soon, and telling yourself, “Oh sure, this will definitely save my customers some money. Once I launch they’ll come streaming in,” you need to know that saving some time, some money, or making some money, isn’t gonna cut it.

There’s a fairly predictable thing about us humans, and that’s that we’re really into our habits and we’re fearful of the unknown.

So, even if your new solution will save someone a measure of hours per week resulting in (by your sales page’s calculations!) a non-trivial figure over the course of a year, their first response will probably not be clicking “Sign Up!”. Their natural, DNA-deep, first response will probably be asking themselves if they can save those few hours themselves with something more known and familiar. Something they can do themselves.

To overcome habit, fear, and anxiety, you’re gonna have to save someone a lot of time, save them a lot of money, make them a lot of money, or make them very happy.

Incremental improvements can help you keep customers you’ve already got, but incremental improvements over their current solution will not convince them it’s worth the effort and risk to change.

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.

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.

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.

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.