Introduction

Imagine sitting in yet another product review meeting and watching the team tear through decisions like they were checking items off a grocery list. Feature approved. Design direction locked. Timeline confirmed. Next.

Then this junior developer, maybe six months out of college, raises their hand. “Um, sorry, but what if someone’s grandmother tries to use this?”

Dead silence.

You would think your team had never considered that older adults might need to manage their blood pressure medication. So engrossed in building this sleek diabetes tracking app literally designed for ourselves. Tech-savvy thirty-somethings who think a clean interface means three buttons max and assume everyone has perfect vision.

That question should stop us cold not for its intellectual tone, but it was obvious, because some of us would not have thought about it. As healthcare technology professionals, you are caught up in shipping fast and ticking off the bugs that you forget the most basic thing: who is going to use this? An important aspect for Healthcare UX Best Practices.

It got me thinking about something I had read years ago in some research paper. When your brain feels rushed or pressured, it defaults to this ancient survival mode. Everything becomes about reacting to situations rather than responding to situations consciously with a brief pause. Fight or flight stuff. Which is fantastic if a bear is chasing you, but terrible if you are trying to build something that will not accidentally hurt people.

The prefrontal cortex, that is the part that handles complex thinking, basically takes a backseat. You start making decisions based on gut feelings and assumptions you did not even know you had, and in care industry? That is dangerous territory.

Scenario 01

Consider a scenario of a team launching a prenatal care app, and were so proud of how streamlined they had made everything. One-tap appointment scheduling. Instant test results. Beautiful, minimal design. The works.

Two months after launch, the usage data came back. It was… bad. Not just disappointing bad, but actively concerning bad. Statistics revealed that only the creamy layer of the society used the app whereas the women in rural areas, those juggling work and family responsibilities, those sharing phones with family members, were not using it at all.

Turns out, the team’s “streamlined” design assumed constant internet access. The “minimal” interface assumed perfect English literacy. The “instant” notifications assumed people wanted to be pinged about their pregnancy at random hours.

The team built something elegant that completely missed the point – Healthcare UX Best Practices.

Think about the ones checking their blood pressure in community centers because they did not have reliable home internet. The ones who would have loved appointment reminders but could not afford unlimited texting plans. As healthcare technology professionals and the innovators in the healthcare business we all have good intentions, sure, but good intentions do not make up for not thinking things through.

Scenario 02

Picture a team getting excited about adding voice commands to a medication reminder app. “It’s so much easier than typing,” they say. Everyone nodded. Made perfect sense.

“What if you have a thick accent?” someone asked. “What if English is not your first language? What if you live in a noisy apartment?”

One designer mentions her grandmother, who had been struggling with her new smartphone partly because voice recognition never understood her Korean accent. Another person talks about their neighbour, an elderly veteran who lived alone but had thin walls and he had never felt comfortable talking to his phone about his medications.

These are not edge cases. They are just cases we do not think about when we are moving fast in the design of digital health solutions.

Scenario 03

Imagine someone in the early-stage Parkinson’s, and struggling to use a pharmacy app to refill their prescriptions. You watch the elderly miss those same buttons seven times in a row. Getting more frustrated each time. By the end, they just give up and call the pharmacy instead. Which defeats the whole point of having an app, doesn’t it?

Healthcare apps are not like other apps. People are not casually browsing. They are often stressed, confused, maybe dealing with a new diagnosis or trying to manage a chronic condition. Fear changes how you interact with technology.

Scenario 04

I remember talking to this woman, Maria, who had been diagnosed with diabetes. Smart lady, she ran a small business, managed three kids, not someone you would call tech-phobic. However, she was terrified of making a mistake with her blood sugar tracking. Every button click felt high-stakes because, well, it was.

She was convinced that changing anything would mess up her medical records somehow. She would rather enter a new reading and let her doctor figure out the discrepancy.

As healthcare professionals we design for accuracy and flexibility. All those users like Maria need are reassurance and forgiveness.

Summary

Critical thinking is not some special talent you are born with. It is more like… remembering to look both ways before crossing the street. The more you question your assumptions, the better you get at spotting them before they become problems.

In the startup world, that feels almost heretical. We are supposed to move fast and break things, right? Except in healthcare, breaking things means breaking people’s trust, their access to care, their ability to manage conditions that might literally kill them if mismanaged.

So yeah, be the person in meetings who asks uncomfortable questions now. Who slows things down. Who makes everyone consider scenarios they would rather not think about.

This makes the solutions more thoughtful and inclusive which is more likely to actually help the users they are meant to serve.

It is not revolutionary stuff. It is just remembering that behind every user story is an actual person with actual problems that might be more complicated than we assumed.

Next time you are in a planning meeting, try asking one simple question: “What could go wrong here?” Not in a paranoid way, but in a curious way. See what happens. I bet someone in the room will pause, think for a moment, and bring up something nobody else considered.

Six Small Questions That Change Everything

Simple questions that gently interrupt the autopilot and nudge us toward a wider view.

Category	Reflective Question	Real Example
WHO	Who is not represented here?	Have we tested this with non-English speakers or people unfamiliar with digital tools?
WHAT	What assumptions are we running with?	Are we equating “tech-savvy” with “young,” while many older adults use smartphones daily?
WHERE	Where could this feature misfire?	Would late-night notifications disrupt users with PTSD or sleep disorders?
WHEN	When might this unintentionally cause stress?	Could a refill reminder create panic if someone just changed meds with their doctor?
WHY	Why might someone challenge this idea?	Would a nurse push back if alerts made workflows harder, not easier?
HOW	How are we measuring success beyond KPIs?	Are we considering patient understanding and confidence, not just engagement rates?

Try This: A Tiny Challenge

Here is a low-pressure challenge for this week:

• Take a screenshot of those six reflective questions
• Keep them on your desktop, notebook, or desk
• Use one in a real meeting
• Notice what happens—Do people pause? Does the mood shift? Does someone bring up something no one else considered?

You do not have to change everything at once. Just start with one good question.

Great design does not just answer problems. It asks better ones and leads to Healthcare UX Best Practices.

 

References

1. Arnsten, A. F. T. (2009). Stress signalling pathways that impair prefrontal cortex structure and function. Nature Reviews Neuroscience, 10(6), 410–422.
2. Facione, P. A. (1990). Critical Thinking: A Statement of Expert Consensus. The Delphi Report.
3. Flavell, J. H. (1979). Metacognition and cognitive monitoring. American Psychologist, 34(10), 906–911.
4. Halpern, D. F. (1998). Teaching critical thinking across domains. American Psychologist, 53(4), 449–455.
5. Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.
6. Lieberman, M. D. (2013). Social: Why Our Brains Are Wired to Connect. Crown Publishing.
7. Perrone-Bertolotti, M. et al. (2014). What is inner speech? Frontiers in Psychology, 5, 185.
8. Rock, D., & Schwartz, J. (2006). The neuroscience of leadership. strategy+business, 43.
9. Seligman, M. E. P., & Csikszentmihalyi, M. (2000). Positive psychology: An introduction. American Psychologist, 55(1), 5–14.
10. Siegel, D. J. (2012). The Developing Mind. Guilford Press.
11. Tversky, A., & Kahneman, D. (1981). The framing of decisions. Science, 211(4481), 453–458.