Brian Rhea Brian Rhea

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:

“I realized that the product was a vitamin, not a painkiller.”

- Jane Portman

What a perfect analogy to keep in mind as you’re working on your startup.

Most people know they should be taking vitamins. They’d probably even tell you, “Yes! I would love that!” during customer discovery.

For example, the One-A-Day multivitamin that you and I both ought to be taking sounds incredible!

MedTech Startup: “Imagine that I could help you improve heart health, maintain healthy blood pressure, support your immune system, strengthen your bones, and increase your energy. And here’s the best part! It’s all contained within a single pill that you take once in the morning!”

Everyone:

Jobs to Be Done Forces of Progress

Everyone two weeks later:

Jobs to Be Done Forces of Progress

The thing is, people set reminders to take their vitamins, but they keep painkillers close at hand.

You don’t have to be reminded to take an Excedrin. You reach for it when you’ve got a headache.

With a vitamin, you have to introduce the customer to some non-urgent problem in the future (important as it may be) and convince them that your pill is the solution.

It’s not impossible. There are plenty of successful vitamin companies.

But which would you rather try to sell? A vitamin that people turn to when they remember they should be taking it? Or an Excedrin they keep in their purse, bag, nightstand, glove box, and overnight kit?

Telltale Signs Your Startup is a Vitamin

Earlier this year I was working with a founder who’d already built about 85% of a fairly complicated product. We were doing a batch of customer interviews and every now and then the participant would say something that tangentially related to the software the founder had already built. The founder’s ears would perk up and she’d point to the phone and nod emphatically to those of us in the room. “Yes. That right there! That’s it!” she was trying to say.

“Ohhhh dear,” I thought.

If you’re doing customer research and you find yourself convincing the prospect that they’ve got a problem you can solve, chances are you created your solution too early and you probably created a vitamin.

Yes, the problem might exist. Yes, you may have found a way to address it. But, if you’re getting excited every time you catch just a glimpse of the problem in your customer’s workflow, that could be a bad sign.

Look for Signs of a Headache

Customer-centric research goes in search of a problem first. I won’t belabor the metaphor, but it’s a lot more like seeing someone pinching their forehead and groaning rather than pleasantly going about their day with a slight Vitamin C deficiency.

To discover the pain and then design a way to solve it, you need to run some high-impact customer interviews and listen to the customer without searching for validation of what you’ve already built.

Claire and Gia over at ForgetTheFunnel.com have a killer webinar to help you know which tools to use, which questions to ask, and which questions to avoid.

And if you’re still uncomfortable running these interviews after watching that video, shoot me an email let me know where you’re stuck.

What Do You Think?

Are some vitamins worth building? What are other distinctions between SaaS products that are vitamins vs painkillers?

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.

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.