The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/Marketing/Clinician to CEO
Clinician to CEO artwork

#202 | The NUMBER ONE Reason Clinicians Say They Love Your MedTech Product But Still Don't Buy It

Clinician to CEO · 2026-06-09 · 12 min

0:00--:--

Key moments - from our scoring

Substance score

34 / 100

Five dimensions, 20 points each

Insight Density13 / 20
Originality11 / 20
Guest Caliber0 / 20
Specificity & Evidence8 / 20
Conversational Craft2 / 20

Medtech founders frequently encounter enthusiastic feedback - 'that's clever, I see the benefits' - followed by silence and no purchase. Hakeem Aade diagnoses this common failure: solving a problem doesn't guarantee adoption; solving a priority does. Healthcare organizations face dozens of problems (staff shortages, budget constraints, workflow inefficiencies), but only prioritize a few. The distinction matters because priorities attract budget and resources, while problems often don't. Aade presents a practical four-step assessment framework: Step One asks whether the problem ranks in the customer's top three priorities versus further down the list. Step Two explores consequences - what happens if the problem goes unsolved, since behavior change happens when staying the same becomes uncomfortable. Step Three observes actual customer behavior: have they already allocated budget, created teams, or trialed solutions? This reveals whether claimed priorities match real action. Step Four identifies who benefits most and has decision-making authority, because urgency and ability to influence drive adoption. The episode targets medtech founders deciding whether their product solves a genuine priority or merely a perceived problem.

Key takeaways

  • →Problems are abundant in healthcare, but priorities - issues with consequences serious enough to demand action and budget - are what actually drive product adoption.
  • →Ask customers to rank where your challenge sits among their current priorities; if it's consistently outside the top three, you've found a problem but not a priority.
  • →Behavior reveals truth: customers already investing budget, creating project teams, or trialing alternatives are signaling a genuine priority; years of inaction suggest the opposite.
  • →Focus engagement on the person with the strongest reason to act and decision authority (e.g., the theater manager trying to increase throughput, the hospital executive focused on productivity) rather than everyone who acknowledges the problem.
  • →Before investing further in product development, marketing, or distribution, validate that you're solving a priority - something customers cannot afford to ignore - not just a problem.

Topics in this episode

Go-to-market strategy for medtechPriority vs. Problem frameworkCustomer behavior assessmentDecision-making unit identificationHealthcare workflow inefficienciesTheater efficiency optimizationStaff shortages and patient safetyBudget allocation indicatorsConsequences and urgency in adoptionHealthcare commercialization

Questions this episode answers

Why do customers say a medtech product is interesting and clever but then never buy it?

They're complimenting the solution to a problem, not committing to fixing a priority. Clinicians may acknowledge an issue exists without perceiving it as urgent or consequential enough to change behavior, allocate budget, or adopt a new solution.

How do you know if a problem is actually a priority for customers?

Ask customers to rank where that challenge sits relative to everything else they're dealing with; if it's consistently in the top three priorities, it's genuine. A true priority has negative consequences if left unsolved and motivates actual action.

What's the difference between a problem and a priority in medtech sales?

A problem is something that exists; a priority is a problem with consequences serious enough that customers will invest budget and resources to solve it. Problems are abundant; priorities get action.

How can you tell if a customer is truly committed to solving a problem?

Look at their behavior: Have they allocated budget, created a project team, trialed alternatives, changed processes, or assigned responsibility? If they've lived with the problem for years and done nothing, it's likely not a real priority despite what they say.

Who should a medtech founder focus on to drive product adoption?

Identify the person experiencing the most pain, who benefits most if solved, and who has decision-making authority - usually someone like a theater manager, operational lead, or hospital executive focused on throughput or productivity, not just clinicians who agree the problem exists.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

13 / 20

The episode delivers a clear, actionable framework (problem vs. priority) that is genuinely useful for medtech founders, but it is repetitive and relies heavily on restating the same core idea across four steps rather than introducing fundamentally new concepts. The distinction between priority and consequence is valuable, but the supporting reasoning is thin - mostly analogies to personal life and generic hospital examples rather than novel mechanisms or surprising data.

The companies that achieve adoption aren't necessarily the ones solving the biggest problems. They're more often than not the ones that are solving the highest priorities.
People don't change just because something is better. They change because staying the same becomes uncomfortable, and it keeps them up at night.

Originality

11 / 20

The core insight - that solving a problem doesn't guarantee adoption unless that problem is a priority - is sensible but not particularly original. The four-step framework (problem/priority, consequences, existing behavior, stakeholder analysis) is fairly standard product-market fit thinking repackaged for medtech. The episode lacks contrarian takes or first-principles reasoning; it reads more as commonsense advice wrapped in structure.

The existence of a problem does not automatically create demand for your product, even if it's solving a problem.
Many people will always tell you that the problem is important. Far fewer will actually do something about that problem.

Guest Caliber

0 / 20

This is a solo host episode with no guest. The host, Hakeem Aade, is framed as an advisor/coach for medtech founders but provides no evidence of having built or scaled a medtech company himself. Without a guest operator or practitioner who has actually executed at scale, this fails the guest caliber dimension entirely.

I'm your host, Hakeem Aade.

Specificity & Evidence

8 / 20

The episode is almost entirely devoid of named examples, real companies, specific metrics, or concrete data. There are only vague hypotheticals: 'a product that saves nurses five minutes per shift,' 'a solution that reduces theater inefficiencies,' generic hospital problems like 'staff shortages' and 'patient safety concerns.' No dollar figures, no timelines, no case studies - just abstraction and analogies.

Let's imagine you developed a product that saves nurses five minutes per shift.
You've developed a solution that reduces theater inefficiencies.

Conversational Craft

2 / 20

This is a monologue, not a conversation. There is no host challenging a guest, no follow-up questions, no productive disagreement, and no back-and-forth exploration of ideas. The structure is purely didactic instruction with rhetorical questions asked to the listener rather than to an interlocutor. It reads as a lecture, not an interview.

So have you ever shown a customer your product and heard, phrases like this, Oh, that's really interesting.
Let's just take a s- a sidestep away from healthcare for a second and think about your own life.

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

problem40priority19product15solution11problems11solving10step10priorities10adoption9customers8trying8three7consequences7budget6likely6happens6

Episode notes

Have you ever received great feedback on your MedTech product, only to discover that positive conversations don't translate into adoption? Many MedTech companies assume that solving a genuine healthcare problem is enough to drive adoption. Unfortunately, that's rarely the case. In this episode, Hakeem explains why customers only act on problems they see as priorities and shares a practical four-step framework to help you assess whether your solution is likely to secure attention, budget, and adoption. By listening you'll discover: Why solving a healthcare problem doesn't automatically create demand How to determine whether your target customers see the problem as a genuine priority A simple framework for identifying the people, consequences, and behaviors that drive adoption decisions Play this episode now to learn how to identify whether you're solving a problem customers can live with - or a priority they can't afford to ignore.

Full transcript

12 min

Transcribed and scored by The B2B Podcast Index.

In today's episode, you're gonna learn how to tell whether you're solving a problem that customers genuinely care about enough to change behavior, allocate budget, and adopt that new solution. Welcome to Clinician to CEO, the podcast helping clinicians simplify your go to market strategy so that you can stop guessing and turn your working prototypes into international MedTech businesses. i'm your host, Hakeem Aade. Let's get started.

three things that you're gonna discover in this episode are, number one, why solving a problem isn't enough to get your product adopted. Number two, how to tell whether a problem is actually a priority. Number three, a simple four-step framework to assess whether customers are likely to adopt your solution. So have you ever shown a customer your product and heard, phrases like this, Oh, that's really interesting.

Oh, that's really clever. Oh, I can definitely see the benefits." So you get very excited, but then nothing happens. There's no pilot, there's no evaluation, there's no budget, there's no next meeting, and there's no orders coming in.

All you get is radio silence. Now, if you've ever experienced that, you're not alone because, in fact, one of the biggest mistakes I've seen in med tech isn't actually poor technology, it's not poor solutions, it's assuming that because something that you've developed solved the problem means that people automatically want it Unfortunately, that is not always the case. So don't get too excited when you think you've solved a problem because healthcare is full of problems, and you know that.

Every hospital has problems. Every clinician has problems. Every procurement team has problems. The question isn't for your product or your solution, does a problem exist that you're solving?

The question actually is that problem important enough for somebody to do something about it? And that's what we're gonna explore today. Because the companies that achieve adoption aren't necessarily the ones solving the biggest problems. They're more often than not the ones that are solving the highest priorities.

So what I wanna do now is get into the four-step framework, which will help you assess whether customers are likely to adopt your solution or not. And then at the end of each of those steps, I wanna give you an action to go away and actually implement. So step one is it a problem or is it a priority? Because let's be honest about it.

As I said, you all know that healthcare is full of problems. I don't care where you are in the world, you've got probably long waiting lists, you got staff shortages, you got budget pressures, training gaps, communication issues, workflow inefficiencies. The existence of a problem does not automatically create demand for your product, even if it's solving a problem. Because hospitals don't solve every problem.

They solve the problem that matter the most. Now, let's just take a s- a sidestep away from healthcare for a second and think about your own life. You probably have dozens of problems. Maybe you need to exercise more, as we all do.

Maybe you should organize your finances better. Maybe you should - you need to clear out your garage. They're all problems, but it doesn't mean that you're gonna work on all of them because they may not all necessarily be priorities. And until they become priorities, you don't do anything about them.

So healthcare works exactly the same way. Let's imagine you developed a product that saves nurses five minutes per shift. That is a genuine benefit. So everybody thinks, "Oh I've found a problem.

I've got a solution that can actually reduce that five minutes per shift." So it's a real problem. But if the hospital is dealing with staff shortages, patient safety concerns, and financial pressures, your problem may not make the priority list of that healthcare facility. So you may prove a problem exists, and you may produce the product that solves that problem.

But if you never prove it's important enough to act upon, then actually your product or solution is not gonna be adopted. So the action I want you to take based on this step one, is go and speak to three customers this week and ask them, where does this challenge rank compared with everything else that you're dealing with right now? Not, what do you think of the product? Not, can you see the benefits?

'Cause they'll be - they, they'll say yes, and they'll give you positives. But I want you to ask them that question, because then what you're effectively asking is how important is solving this compared with your other priorities? Because if it's consistently in the top three, then you want to keep going. If it's number 17 for that list, you've found a problem, but you may not have found a priority, and priorities are what drive adoption.

So If you haven't found a priority, you've only found a problem, then you have to do a bit more digging. You need to find out If there's other consequences that can become priorities for that problem. So that's step one. Is it a problem or a priority?

You need a priority before you start moving on. So now let's take that a step further, and the step two is what happens if they do nothing? Because one of the biggest challenges founders find when they're focusing entirely just purely on the benefits, i.e.

, We save time, we improve efficiency, we reduce workload of course, those things matter But what really drives adoption is consequences. What happens if they don't solve that problem? So if a hospital ignores a staffing problem, what's gonna happen? Patients wait longer.

That's a consequence. Staff become overwhelmed. Consequence. Costs increase.

I think you get where I'm going. Performance suffers. That's why staffing becomes a priority. Now think about your product or solution.

If nobody adopts it, what happens? Does risk increase? Do costs increase? Does revenue fall?

Do outcomes worsen? Does somebody lose sleep? i.e.

, what's the consequence? And the term I always use is what is keeping that customer up at night? What are the consequences? Because if nothing really changes or they perceive that nothing's gonna change if they don't do anything, then adoption becomes really difficult.

Because People don't change just because something is better. They change because staying the same becomes uncomfortable, and it keeps them up at night. So the action I want you to take here for step two is go and ask your customers what happens if this problem never gets solved. If the answer is not much really, or they're not that concerned about what the consequence may be, then you've got a lot of work to do.

You need to, again, start finding some consequences that actually resonate with them and keep them up at night. If the answer is, however, it creates risk, it costs money, it slows us down, it affects outcomes, now you're getting closer to what we would describe as a genuine priority. Because priorities have consequences, and consequences get focus from your customers and budget. So you've now tried to identify whether it's a problem or a You're thinking you've got a priority because it's got consequences.

You then move on to step three, are they already trying to fix it? Because we wanna now start looking at behavior, because behavior will tell you far more than what they actually say. 'Cause they may well say, "Oh yeah, it's a priority. These are all the issues that happen."

But we wanna now look at whether they're doing anything about it. Many people will always tell you that the problem is important. Far fewer will actually do something about that problem. So let's imagine that somebody says, "Oh yeah, it's a real big issue."

Obviously, what you're gonna ask them is, "Okay, what have you done about it? Because if it's a big issue, surely you've done something about it." Now, if they've allocated budget or they've created a project team, they've trialed alternative, they've changed processes, they've written policies, they've assigned responsibility, then that's a really good sign that you've got a genuine priority because their behavior is matching their words, i.e.

, they're doing something about it. But If they've lived with the problem for 10 years and done absolutely nothing, then maybe it's not the priority that they've been claiming it is. A-and one of the best indicators of future adoption is whether somebody's already trying to solve the problem today because if they're already looking for a solution, and they've tried different things, then you're joining an active conversation about how to solve this priority. But if they're not trying to do anything, and they're not looking for a solution, then you're actually trying to create a priority or a problem, and that's significantly harder.

So the action that I want you to take here is to go and ask three customers, "What have you already done to solve this problem?" And then what you're looking for, obviously, is evidence of action. The more effort they've already invested, the more likely it is that you're dealing with a genuine priority, and the more likely it is that they're gonna do something with your product or solution So then moving on to step four, who has the most to gain? So let's assume you've now identified a genuine priority.

The next question is, who benefits most if this problem gets solved? 'Cause that's who you really want to be speaking to, because not everyone, cares equally about problems. And this is where actually many med tech companies start to lose momentum. They do the first three steps.

They've got a genuine problem But the challenge is that lots of med tech companies spend all their time talking to people who agree that the problem exists- instead of talking to the people who have the strongest reason to act. So let me just use a simple example. You've developed a solution that reduces theater inefficiencies. The surgeon is going to appreciate that.

The theater team may love it. But who feels the biggest impact? Maybe it's the theater manager trying to increase throughput. it could be the operational lead trying to reduce delays.

it May well be the hospital executive trying to improve productivity. And the strongest opportunity for you to get that product adopted is usually found where the pain is the greatest, and the ability to influence the change is the highest because that's where urgency lives, and urgency drives adoption. And I've got a whole workshop on how you can identify the right people with the problem and the urgency to act, and how you then put that decision-making unit together so that you can influence adoption through that decision-making unit.

But for now, the action I want you to take is write down who experiences the problem, who benefits if it is solved, and who can influence the decision. And then once you've wr-written those down, ask yourself which of those people have the strongest reason to act, because that's the person that you should spend most of your time trying to understand and influence. Because If you can convince the person who cares the most, then everything becomes easier, and it's much more likely you're gonna get your product adopted.

So let's go back to where we started. You show somebody your product. They tell you it's interesting. They tell you it's clever.

They tell you they can see The benefit, and you're getting very excited, but then nothing happens. The problem, as I've said, often isn't your product. The problem is that you've only found a problem, but you've not found or identified a priority, and there's a huge difference, and I'm hoping that in this episode you can clearly see the difference because priorities get attention, priorities get budget, priorities get resources, but problems often do not. So before you spend any more money on developing the product further because someone's given you some feedback, before you spend any more money on marketing, before you recruit another distributor, before you attend another trade show, ask yourself one simple question: Are you solving a problem or are you solving a priority?

Because as I said before, the companies that are gonna achieve adoption are not necessarily the ones with the best technology. They're the ones solving problems that customers cannot afford to ignore And if you're building a MedTech business and you're not sure whether your next move should be around evidence, market access, commercialization, distributor strategy. Or adoption. Do not guess.

Book a healthcare export accelerator diagnostic Call with me. Use my link in the show notes. And in that session I'll help you identify the specific constraints blocking your momentum and the commercial move most likely to unlock your progress. Thanks for tuning in.

Until next time, thanks for listening. Keep challenging your assumptions and keep growing.

More from Clinician to CEO

All episodes →
  • #209 | 5 Lessons You Should Know Before Commercializing & Exporting Your MedTech Product (For Clinicians)37 / 100
  • #208 | The NUMBER ONE Mistake Clinicians Make When Commercializing Your MedTech Product70 / 100
  • #207 | The Ugly Baby Problem Every MedTech Founder Must Avoid When Exporting (For Clinicians)86 / 100
  • #206 | 5 Lessons Every MedTech Company Should Learn Before Exporting to Japan52 / 100
  • #205 | The #1 Mistake MedTech Companies Make When Choosing Export Markets66 / 100
Explore the best B2B Marketing podcasts →
All Clinician to CEO episodes →