In healthcare, innovation is often measured in features and functions: more data points, smarter algorithms, sleeker hardware. Yet anyone who has spent time on a hospital ward or in a clinic knows a different truth: many “advanced” products sit unused in cupboards, or are quietly worked around by nurses and doctors who find them confusing, slow or simply unfit for the way medicine is actually practiced.
It is not that the technology is weak. It is that the design is indifferent.
Over the past two decades, a different way of building products has gradually made its way from design studios into hospitals and medtech companies: design thinking – a user-centered methodology popularized by IDEO and its founder David Kelley. At its core, it is a structured way of doing something that medicine claims to value but rarely systematizes in product development: listening.
Rather than starting with what is technically possible, design thinking begins with what is humanly necessary – with patients, clinicians and the everyday routines in which any new tool must survive.
Why so many medical products miss the mark?
On paper, modern healthcare is saturated with innovation: connected monitors, AI decision support, home diagnostics, digital therapeutics. In reality, a surprising number of these solutions are:
- too complex to use in the rush of a real shift,
- poorly adapted to cramped rooms, noisy environments or tired hands,
- misaligned with clinical workflows and documentation requirements,
- or simply tone-deaf to what patients actually worry about day to day.
The result is a quiet kind of failure. Devices are technically “implemented” but used only partially, reluctantly, or not at all. Software is rolled out, then circumvented with paper notes and unofficial spreadsheets. From the outside everything looks modern; from the inside very little has changed.
That is precisely the gap design thinking is meant to address.
Step one: empathy in a place not famous for it
The first stage of design thinking is empathy – not as an abstract virtue, but as a disciplined practice. In a medical context, this means spending time where care actually happens: at the bedside, in outpatient clinics, in patients’ homes. It means watching, listening, asking questions that do not presume the answer.
Consider a seemingly simple product: a device for monitoring diabetes.
In a traditional development process, engineers might start by listing technical requirements: accuracy thresholds, connectivity standards, battery life. The interface is something to be “designed” later.
A design thinking process starts differently. The team interviews people living with diabetes, follows their routines, and asks:
- When and where do you actually check your glucose?
- What do you find hardest about current devices?
- When do you skip a measurement, and why?
- What do you fear most when looking at a result?
The answers tend to be disarmingly concrete. Patients complain that readings are hard to see at night without waking a partner. That numbers flash by too quickly. That they are not sure what to do with a particular value, beyond vague advice to “keep it in range”.
Empathy work does not produce a feature list. It produces a nuanced picture of daily life with a disease – and it is from this picture that meaningful products can be drawn.
Defining the real problem
Only after listening does design thinking ask the next question: What is the problem we are actually trying to solve?
In our diabetes example, the issue may not be “insufficient data”. Patients already have data. The problem might be “unclear meaning”: people do not know how to interpret their numbers in the flow of a busy day, or how to translate them into simple, actionable decisions.
Formulated this way, the design brief shifts. The goal is no longer “build a device that measures glucose more often,” but rather “create a system that helps patients understand – at a glance – what their numbers mean and what they should do next.”
That is a different, more human problem. And it invites different, more practical solutions.
Generating ideas: many wrong turns before one right one
Design thinking then moves into ideation – structured brainstorming that deliberately combines different perspectives. Clinicians, patients, designers, engineers, sometimes even administrators are put in one room and asked not for “the answer,” but for many imperfect options.
For the diabetes device, this might yield:
- a simplified screen that uses color coding rather than small numbers,
- an app that turns each reading into a short, plain-language suggestion,
- a feature that shares trends with a clinician only when something unusual appears,
- haptic alerts for people who cannot or do not want to look at their phone.
At this stage, the ideas are not judged as final. Their value lies in expanding the space of possibilities beyond what any single expert would propose alone.
Prototyping and testing: learning in the real world
If traditional medical device development is a long, linear road, design thinking is more like a looped path. Prototypes are made quickly – on paper, in simple click-through apps, with 3D-printed shells – and given back to users not as polished products, but as questions:
- Does this help?
- What confuses you?
- What would you change?
In our example, a team might give a rough app to a small group of patients for two weeks. They may learn that the color coding is reassuring but that the language is too technical. Or that people want fewer notifications, not more. Or that older patients prefer a simple physical device to a smartphone at all.
Crucially, this feedback is not an afterthought. It shapes the next prototype, which is then tested again. Each cycle removes friction, misunderstandings and small frustrations – the sorts of things that, unaddressed, quietly kill adoption later.
A Real-World glimpse: redesigning a hospital intake form
Design thinking is not limited to devices and apps. Sometimes the most meaningful changes are surprisingly mundane.
In one European hospital, a team applied design thinking to something as simple as the patient intake form in the emergency department. The original form was dense, full of clinical jargon and organized around the hospital’s internal workflows, not the patient’s experience. It routinely delayed triage and confused people in distress.
The team began by observing patients as they filled out the form, noting where they hesitated or asked for help. They interviewed nurses and admissions staff, who admitted they often ignored parts of the form because “no one has time for that anyway.”
Using design thinking, the team redefined the problem as: “How might we collect the minimum necessary information in a way that is fast, clear and emotionally manageable for a person in crisis?”
They then co-created a new, shorter form with patients and nurses, tested multiple versions over several weeks and gradually refined wording and layout. The final version reduced average completion time by several minutes per patient and lowered the number of incomplete forms dramatically.
No new technology was introduced. Yet the change improved flow, reduced stress and freed staff for more meaningful tasks. It is a small but pointed example of what happens when design thinking is taken seriously in healthcare.
Iteration as a habit, not a phase
The last step in design thinking is testing in real conditions, followed by more refinement. For medical products, this can mean pilot deployments in selected clinics, careful measurement of how often and how correctly a tool is used, and structured interviews with users after weeks and months, not just days.
The key is to treat launch not as the end of the process but as another iteration. If patients consistently misinterpret a certain screen, the answer is not “they need better training,” but “the design is not doing its job.”
A different way of building health technology
Design thinking does not guarantee success. It does, however, dramatically increase the odds that what is built is usable, understandable and relevant – qualities still surprisingly rare in the medical technology landscape.
At Medical Innovation Institute, we see this daily in our work with startups and healthcare organizations: the projects that invest time in empathy, problem definition, prototyping and iterative testing are the ones that clinicians adopt and patients trust. The ones that skip these steps often look impressive in pitch decks and procurement documents, but struggle quietly once they meet reality.
As healthcare systems face rising expectations and constrained resources, the question is not whether we can produce more digital tools. It is whether we can design tools that people actually want to use.
Design thinking, applied with rigor rather than as a buzzword, offers a way forward: a method for anchoring innovation not in what is technologically dazzling, but in what is humanly needed.