Empathy in Design Process

I've found empathy mapping most valuable during early project phases and presentations. Nothing convinces leadership to greenlight a project like showing them you truly understand your target audience's pain points. But, they're not for every situation. For straightforward projects with well-understood users, a quick check-in might be sufficient. The key is using empathy maps as tools for insight, not checkbox exercises. I've seen firsthand how they break down communication barriers between departments. The beauty of empathy mapping lies in its simplicity. The classic version has four quadrants – Says, Thinks, Does, and Feels — though I've found adding "Sees" and "Hears" can provide even more context for certain projects. What matters isn't the exact format but the conversations it sparks. Here's what works in my experience: - Start with a clear purpose. Are you trying to align your team around user needs? Inform a specific design decision? The goal shapes everything that follows. - Ground your map in reality. The most valuable maps come from actual user data – interviews, surveys, support tickets – not assumptions. I've watched teams realize how much they'd been projecting their own preferences onto users when confronted with real feedback. - Make it collaborative. Bring together people from different departments to fill out the map. The magic happens when your developer suddenly realizes why that feature the marketing team kept pushing for actually matters to users. - Keep it alive. The best empathy maps evolve as you learn more. I keep ours visible and revisit them regularly, especially when we're making crucial decisions.

We built fast systems. Somewhere along the way, we forgot to build kind ones. That’s why this simple Korean idea stayed with me. Before a call connects, the caller hears a small voice saying, “You’re about to talk to my mom.” Or my dad. Or my sister. And everything shifts. Not because callers become kinder people overnight. But because the system reminds them that the person answering is human too. It brought back a lesson I learned early in my career building financial products. If you design only for efficiency, you get compliance. If you design for humanity, you get trust. And trust is what makes systems scale. This Korean example is not customer service innovation. It is behaviour design. A tiny nudge that restores empathy in a space where it quietly disappeared. It made me think about how often we build products to optimise flow, not feeling. We fix the steps, but forget the state of the person going through them. We reduce friction, but overlook the fear, frustration or vulnerability underneath. A small tip for product leaders: If your system interacts with people at stressful or uncertain moments, your first job isn’t speed. It’s care. A sentence. A tone. A pause. A reminder that a human sits on the other side. Because most friction in modern life doesn’t come from systems failing. It comes from human connection thinning. We already know how to build fast. The next frontier is learning how to build kind. Not every solution needs a feature. Sometimes it needs a feeling. What would your product look like if empathy was part of the design spec?

99.9999% of case studies I see don't address: → Empathy Way too much "Next, I did this..." Not enough "Here's why we did this..." A well-placed persona image in your study is not a substitute for genuine user understanding. Some ways you can highlight empathy: → Core Needs: Begin your narrative by highlighting the user's fundamental needs. Make their pain points the core of your story, just as you did with your designs. → Insights: Distill the core needs into your primary insights. Showcase these. They guided your design decisions. Let them guide your case study. → How Might We's: A good way to frame problem-solving based on each insight. These show the uncovered potential. → Outcomes: Shift your focus from solely what you've learned to how your solution positively affected the user. How did it make their life better? Tell the story through the user's eyes, not merely as a designer ticking off a checklist. Empathy should have guided every step of your design process. Let it guide your story, too. #ProductDesign #PortfolioTips

Design Thinking is About Caring Design Thinking is, at its core, about caring for others. Barbara Weedman once witnessed a poignant moment: a single mother struggling to complete a job application at a public computer while holding her baby. She typed with one hand, corrected mistakes, and ultimately left without finishing—exhausted and defeated. When Henrico County began constructing a new library, Weedman asked the architects a simple but powerful question: Could they design computer workstations tailored for parents with infants and toddlers? The result was the Fairfield Parent+Child Carrel—a dedicated workstation with privacy panels, directly connected to a secure play area for young children. This thoughtful space includes a healthcare-grade vinyl mat, a mirror at baby height, and interactive panels that librarians can update for seasonal activities. This initiative embodies Life-Work Integration, moving beyond the traditional notion of work-life balance. Too often, leaders overlook that performance is a byproduct of humanistic values such as empathy, fairness, and collaboration. By nurturing people, businesses become more productive, ethical, and impactful. This is the essence of Design Thinking: enhancing our world through care. The stages, tools, and canvases are merely instruments—the true driving force is empathy. - When we care, we become curious—analyzing trends, defining problems, and understanding customer pains and gains. - When we care, we ideate—aligning ideas, products, and solutions with real human needs. - True value lies not just in customer experience, but in solving problems, saving time, creating opportunities, ensuring accessibility, and fostering safety and self-actualization. We can only be truly empathic if we care. By Design. If this resonates, share it with your network. ---

What building for new parents taught me about product design 👶🏼 Most products are built assuming one thing: That the user is at their best. Focused, in control, and ready to explore. But parenthood turns that upside down. When you're holding a newborn at 3AM, you’re not looking for smart features. You're looking for clarity, comfort, and someone you can trust. That’s the first big lesson I learned as a founder in the mom and baby space. You’re not just building for a user. You’re building for a vulnerable life stage. Here’s what shifts when you do that: ↳ Emotions run high ↳ Time is scattered ↳ Every decision feels heavy ↳ The mental load is already overflowing ↳ Trust becomes everything So what matters more than classic “differentiators”? The experience. The empathy. The ability to make someone feel just a little less alone. In this space, I’ve learned to value: ↳ Simplicity over features ↳ Reassurance over polish ↳ Flexibility over funnels ↳ Conversation over conversion Because for a new parent, even a small friction can feel like failure. And a gentle helping hand can feel like a lifeline. If you’re building in parenting, healthcare, mental wellness, or any space where emotions run deep, it helps to set aside the traditional playbook and begin with this question: How can I show up with care? I’d love to hear from others. What has empathy-led design looked like in your journey? Let’s swap stories.

Your solution is technically perfect. But something’s missing.” I said those words in a packed review meeting at Amazon Connect. The architecture on screen was brilliant, optimized, scalable, elegant. But the business stakeholders weren’t nodding. They were checking their phones. And I saw it clearly: the translation gap. Our engineering lead had built a masterpiece for the builder’s eye. But for the people funding it, using it, championing it? It was a beautiful book written in a language they couldn’t read. I recognized the moment instantly, because I’d lived it before. At Microsoft, I once pitched a technically flawless design to execs. The tech crowd applauded. The business side passed. Not because it didn’t work, but because it didn’t resonate. That was the moment I realized: Technical excellence without human understanding is just noise to the people who need to act. So at Amazon, we did something radical. We stopped the review. We didn’t add more slides. We asked a different question: “How does this change the day-to-day life of, a contact center agent ?” The next architecture proposal started with her story. The system didn’t just reduce latency. It made her feel respected. Trusted. Heard. That changed everything. From then on, we embedded empathy into engineering: •Engineers shadowed real users before writing code. •Every design doc started with a human narrative. •We built “empathy metrics” right alongside performance metrics. This wasn’t soft skills. This was integration intelligence: the ability to make technical brilliance humanly meaningful. If you lead engineering in the AI era, remember: Your best solutions won’t win if they don’t translate. Build systems that resonate, not just operate. Learn more in my book Metashift - chapter 7 #TechLeadership #AI #MetaShift #EngineeringExcellence #HumanCenteredDesign

Healthcare brings together people who care deeply about supporting others during challenging times. Translating that empathy into the physical environments where care happens requires intentional techniques, regardless of your role. Here are approaches that create truly empathetic spaces: Observing Beyond the Obvious Watch the Transitions - Don't just observe the main event. Watch the family member who gets lost returning from the cafeteria, the nurse searching for supplies between patient rooms. These in-between moments reveal where empathy is most needed. Notice the Workarounds - When staff tape signs over official wayfinding or families create makeshift privacy barriers, they're showing you where the space fails. These adaptations are acts of empathy. Observe Across Time - A space that works at 2pm may fail at 2am. Consider the night shift nurse, the anxious family waiting through surgery, the patient who can't sleep. Listening Differently Ask About the Hard Days - "Tell me about a day that didn't go well here" reveals what people actually need when things are difficult. Listen for What's Not Said - When someone says "it's fine" but their body language says otherwise, you're learning about unmet needs they may not feel comfortable naming. Create Space for Unexpected Voices - The environmental services worker knows things clinicians don't see. The family member who stayed overnight has insights day staff miss. Experiencing the Environment Walk the Journey - Physically walk from parking through registration to appointment, experiencing every confusing sign, every uncomfortable wait, every moment of uncertainty. Sit in the Waiting - Spend real time in waiting areas. Feel the anxiety. Notice the lack of privacy. Experience the acoustic chaos. Empathy requires feeling, not just seeing. Try the Space During Distress - Navigate wayfinding while upset. Have a private conversation in a "private" space. Test whether someone could cry without everyone noticing. Engaging with Complexity Seek Out Conflicting Needs - The family who needs to talk versus the patient who needs quiet. Empathetic design acknowledges and manages these tensions. Design for the Everyone - True empathy means considering cognitive differences, cultural practices, sensory needs, and varied family structures. Consider the Staff Experience - Burned-out staff can't provide emotional support. Spaces that sustain caregivers support better patient care. Translating Understanding into Action Prototype with Real Users - Mock-ups with actual patients, families, and staff reveal what works before construction begins. Design for Dignity - Does this preserve privacy during exposure? Maintain autonomy during dependence? Support connection during isolation? Return and Learn - Visit completed projects after occupancy. Empathetic design includes the willingness to learn from mistakes.

Empathy Isn’t Missing — It’s Misframed I’ve watched this video countless times. Every time, I don’t see generosity. I see design. I used to believe people ignore the truth because they don’t care. Now I realize it’s because they don’t see what I see. Empathy isn’t a lack of compassion — it’s a lack of perspective. And perspective can be designed. The words didn’t change the man’s story — they changed our frame of perception. When language shifts from description to contrast, it activates awareness. That’s the mechanism behind empathy — it’s not emotional contagion, it’s cognitive reframing. → We respond to difference, not repetition. → We act when a message bridges our world with someone else’s. → We feel when language turns distance into proximity. Here’s how I try to apply that lesson in my own work: ✅ Reveal contrast, not condition. Don’t describe pain — expose the gap between what is and what could be. ✅ Design for awareness before emotion. Help people notice first; feeling follows naturally. ✅ Make others participants, not observers. Use framing that transfers perspective, not pity. ✅ Use silence strategically. Leave room for the reader to complete the meaning. Because empathy doesn’t start with emotion — it starts with architecture. The right words don’t tell people what to feel. They help them feel what was already true. 💭 The Question 👉 When you communicate — are you trying to make people care, or helping them notice what they’ve been blind to all along? #LeadershipDesign #FramingEffect #CommunicationStrategy #CognitiveEmpathy #BehavioralPsychology #PerceptionDesign Video credits: Dr. Marcell Vollmer

Start with people. Invest in real end user problems, not in fleeting ideas. That is the role of designers in the innovation process, and it is pivotal. This video shows why. Because more than most, designers empathize with end users. They put themselves in the shoes of an 8-year-old patient who will soon have their first MRI exam. And ask: what do they really need?   The answer: they want reassurance. That is why solutions like Pediatric Coaching matter so deeply. To help children prepare for their MRI exam in an engaging way. So they can get confident, finish the exam, and say: “It wasn’t scary at all!”

AI isn’t just about working faster. It’s about working smarter—and more human.   If your AI playbook is only about automating tasks or cutting costs, you’re missing the entire point.   The leaders who will own the next decade aren’t chasing efficiency.  They’re building empathy into every algorithm.  Think about this:  → Most AI strategies today treat users like data points. → The disruptors see people. → They’re asking, “How does this make someone feel?” not just “How does this make the process cheaper?”  Here’s what that looks like in action:   AI tools in water management that prioritize community wellbeing, not just leak detection.   Industrial IoT platforms that adapt to stress signals from real workers, not just sensors.   CleanTech analytics that help cities serve people, not just optimize grids.  It’s not about sentiment analysis or chatbots pretending to care.  Empathy in AI means designing for real human outcomes.  It means:   → Listening to the frontline worker who hates her dashboard. → Adjusting recommendations based on lived experience, not just clicks. → Acknowledging the anxiety that comes with new technology.  Efficiency as a goal?  That’s yesterday’s news.  Empathy as an outcome?  That’s how you build loyalty, trust, and real impact.  The companies that get this right will win bigger than anyone optimizing for speed alone.  So, ask yourself: Are you building tech for humans, or for processes?  The future belongs to those who answer, “Humans.”  Comment below: Have you seen a product or tool recently that truly felt designed with empathy?