Designing Healthcare Products Starts with Empathy
People First. Product Thinking.
Early in my career, I spent five years implementing medical management applications for health plans across the country. I wasn't designing software from a conference room—I was sitting beside nurses, care managers, utilization management teams, and operational staff, watching how they actually worked. Most of the people using these systems weren't interested in software features, technical architecture, or the latest technology. They simply wanted tools that helped them complete their work more efficiently so they could spend more time focusing on the members they served.
That experience fundamentally changed how I think about product development. The best healthcare products don't begin with technology. They begin with understanding the people whose work the technology is meant to support.
Technology teams often begin by asking, What can we build? or What new capability can we add? Those are important questions, but they are rarely the first questions we should ask. Before deciding what to build, we should understand who we are trying to help, how they work today, what constraints they face, and where they are experiencing friction. Only then can we determine which problems are truly worth solving.
In healthcare, that distinction carries unusual weight. Every additional click, confusing workflow, or poorly considered process doesn't simply affect productivity. It influences the time clinicians spend with members, how easily providers navigate administrative requirements, how efficiently operational teams move work forward, and how confidently leaders make important decisions. Good product design isn't measured by the sophistication of the technology. It's measured by whether the technology quietly helps people accomplish meaningful work.
Over the past twenty years, my role has evolved from implementing configurable workflow platforms to helping shape enterprise healthcare products, AI-enabled analytics, and clinical transformation initiatives. Although the technologies have changed dramatically, the underlying responsibility has remained remarkably consistent. Empathy isn't limited to end users. Every healthcare product exists within a larger system of people whose priorities, responsibilities, and constraints are different—but equally important.
Clinicians think about patient care. Operations teams think about consistency and throughput. Providers think about administrative burden. Executives think about organizational strategy and sustainability. Technology teams think about implementation, scalability, and delivery. None of those perspectives are wrong. Product leaders create value by understanding how those perspectives intersect before deciding how a product should evolve. The strongest products rarely emerge because one group had the best idea. They emerge because someone invested the time to understand every perspective before bringing those perspectives together into a coherent solution.
That responsibility becomes even more important as artificial intelligence becomes part of everyday healthcare workflows. AI can organize information, summarize documentation, identify patterns, and surface insights at a scale that wasn't previously possible. What it cannot do is determine which competing priorities matter most within a particular organization or workflow. Those decisions still require people who understand the clinical, operational, and human context surrounding the technology.
Empathy also requires more than simply talking to users. Product teams sometimes mistake user research for user understanding. A handful of interviews, a workshop, or a brief observation session can produce useful feedback, but those activities alone do not create empathetic products. Real empathy changes decisions. It challenges assumptions, reshapes workflows, and occasionally requires abandoning ideas that appear attractive from a technical perspective because they do not meaningfully improve the experience of the people expected to use them. If user research simply validates what the team already intended to build, then the exercise has become confirmation rather than discovery.
Rapid technological change makes that discipline even more important. Artificial intelligence allows organizations to prototype, develop, and deploy new capabilities far more quickly than ever before. That speed creates tremendous opportunity, but it also creates a temptation to redesign products simply because the technology now makes change easier. Every interface revision, workflow adjustment, or newly introduced AI capability asks users to invest something. They must relearn familiar processes, rebuild habits, and regain confidence in tools they already understood. Individually those changes may appear small. Collectively they create cognitive fatigue. Over time, users begin spending more energy adapting to the product than accomplishing the work the product was intended to support.
Progress should never be measured by how frequently a product changes. It should be measured by whether those changes reduce effort, strengthen trust, and genuinely improve the experience of the people doing the work. Technology should adapt to people more often than people are expected to continually adapt to technology.
Technology will continue to evolve, and the products we build ten years from now may look nothing like today's platforms. The responsibility of product leaders, however, is unlikely to change. Our role is not simply to introduce new capabilities. It is to understand the people, workflows, incentives, and relationships that surround those capabilities before deciding how they should be applied.
The best healthcare products begin with empathy—not as a research activity, but as a design discipline that continues to shape every product decision.
