Creative Innovation Exercises

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.

When empathy meets design, magic happens. Doug Dietz's story is proof. Discover how he did it. As product managers, we are constantly looking for ways to improve user experiences and create meaningful results. At GE Healthcare, Doug Dietz transformed the MRI experience for paediatric patients, providing a compelling example. The Problem Despite building a cutting-edge MRI scanner, Dietz noticed a young patient's tremendous anxiety while using it. This revealed a key flaw in the machine's design: it did not account for children's emotional needs. The Use of Design Thinking Dietz used design thinking to redesign the MRI experience. 1/ Empathise: He spoke with kids in daycare centres and sought advice from child life experts to understand their viewpoints. 2/ Define: It was shown that 80% of young children needed anaesthesia because they were afraid of the MRI process. 3/ Ideate: To generate creative ideas, a varied team comprising volunteers, hospital employees, and specialists from a nearby children's museum worked together. 4/ Prototype: Developed the "Adventure Series," which turned MRI rooms into spaceships and pirate ships. 5/ Test: The Children's Hospital of Pittsburgh piloted the updated experience, which resulted in notable enhancements. The Results ↳Patient satisfaction scores increased by 90% ↳The need for sedation dropped from 80% to 10% ↳Anxiety levels in children decreased, making it easier for them to remain still during procedures ↳The reduced need for anesthesiologists allowed more patients to be scanned each day, improving efficiency and reducing costs The Key Takeaways for Product Managers 1/ Innovation Is Driven by Empathy: A thorough comprehension of user experiences can reveal unmet requirements and stimulate game-changing solutions. 2/ Reframe the problem: Dietz switched from focussing on the machine to developing the complete patient experience. 3/ Holistic Problem-Solving: More thorough solutions result from addressing the user experience's emotional and functional elements. 4/ Collaborative Ideation: Including a range of stakeholders encourages innovation and reveals fresh viewpoints. 5/ Iterative prototyping: Creating and testing prototypes in real-world contexts to validate ideas and inform necessary refinements. 6/ Measurable impact: The redesign enhanced operational effectiveness and patient experience. Doug Dietz's case study highlights how effective design thinking leads to transformative solutions for challenging problems in healthcare and beyond. Dietz and his colleagues developed a solution that not only soothed children's anxieties but also enhanced operational effectiveness and medical results by prioritising empathy and rethinking the entire process. Your Turn: ↳ How have you applied design thinking principles in your projects?  Share your thoughts in the comments below! 👍 LIKE this post, 🔄 REPOST this to your network and follow me, Monica Jasuja

From MVP to MLP - A Lesson I Learned at Amazon When I first joined Amazon in 2016, I kept hearing a term I hadn’t heard anywhere else: MLP - Minimum Lovable Product. Up until then, I lived and breathed MVP - Minimum Viable Product. Ship fast. Validate. Iterate. Learn. That mindset builds speed, but sometimes… it leaves the heart behind. MLP changed how I thought about building. It wasn’t just “Does it work?” It became “Will someone love using this?” That’s when I started pairing our delivery mindset with journey maps, empathy maps, and design, tools that help us see beyond the feature and into the feeling. Because “lovable” isn’t about adding polish; it’s about understanding what users need, fear, hope for and find delightful. MVP asks: Is it viable? MLP asks: Is it meaningful? The best teams I’ve seen - whether at Amazon, Expedia, or AI feature teams now - are the ones that balance both: tight execution and deep empathy. Because when you build with empathy, your product doesn’t just get adopted - it gets remembered. I’m curious - when you’re building something new, how do you know when it’s viable and when it’s lovable? #Leadership #ProductDesign #AI #Innovation #CustomerObsession #EmpathyMaps

 𝟭 𝗧𝗵𝗶𝗻𝗴 𝗠𝗼𝘀𝘁 𝗨𝗫 𝗗𝗲𝘀𝗶𝗴𝗻𝗲𝗿𝘀 𝗦𝘁𝗶𝗹𝗹 𝗙𝗼𝗿𝗴𝗲𝘁: 𝗘𝗺𝗽𝗮𝘁𝗵𝘆 Most “modern” websites get this wrong: They chase trends and tech- But forget the human on the other side: • They obsess over aesthetics • They build cool features • They wow with motion and AI → But they forget empathy And without empathy? You’re not building experiences You’re just shipping screens 𝗛𝗲𝗿𝗲’𝘀 𝘄𝗵𝗮𝘁 𝗲𝗺𝗽𝗮𝘁𝗵𝘆 𝗿𝗲𝗮𝗹𝗹𝘆 𝗹𝗼𝗼𝗸𝘀 𝗹𝗶𝗸𝗲 𝗶𝗻 𝗨𝗫: ↳ It’s not about fancy gradients. ↳  It’s about emotional safety. →  It’s about reducing friction-both physical and emotional 𝗦𝗽𝗼𝘁𝗶𝗳𝘆 𝗱𝗶𝗱𝗻’𝘁 𝘄𝗶𝗻 𝘄𝗶𝘁𝗵 𝗷𝘂𝘀𝘁 𝗱𝗲𝘀𝗶𝗴𝗻  ↳ They tuned into moods  ↳ Built moments that feel personal 𝗛𝗲𝗮𝗱𝘀𝗽𝗮𝗰𝗲 𝗱𝗶𝗱𝗻’𝘁 𝘀𝘂𝗰𝗰𝗲𝗲𝗱 𝘄𝗶𝘁���� 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝘀  ↳ They calmed people with color  ↳ Reassured them with gentle reminders This is empathy in action Not decoration- direction 𝗛𝗲𝗿𝗲’𝘀 𝗵𝗼𝘄 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝗶𝘁 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗼𝘄𝗻 𝗱𝗲𝘀𝗶𝗴𝗻 𝗽𝗿𝗼𝗰𝗲𝘀𝘀: 𝗗𝗲𝘀𝗶𝗴𝗻 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗳𝗲𝗲𝗹𝗶𝗻𝗴, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝘁𝗵𝗲 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻  ↳ Map the user’s emotional journey  ↳ Remove moments of confusion or stress Use data, but feel what the user feels  ↳ Emotional analytics > vanity metrics  ↳ Real eyes, journey maps, user interviews And think globally  ↳ Translate culture, not just copy  ↳ Design that respects context wins loyalty 𝗕𝗲𝗰𝗮𝘂𝘀𝗲 𝗿𝗲𝗮𝗹 𝗨𝗫 𝗶𝘀𝗻’𝘁 𝗷𝘂𝘀𝘁 𝘂𝘀𝗮𝗯𝗹𝗲 ✓  It’s relatable ✓ It’s respectful ✓ It remembers that your user is human If your design isn’t resonating, you don’t need better features. You need deeper empathy.

Empathy is a continuous mindset, not a one-shot deal. Without this mindset, teams falter. Plenty of teams treat empathy as a front-end exercise. Check the box, run the interviews, set requirements. That's how you end up eighteen months in, building something nobody actually needs. Or launching a product that no one wants, just to meet a deadline Develop and exercise empathy at all levels of innovation. You'll save time in the end, and deliver a much better solution. 👉 Level 1 Empathy: The problem worth solving. Empathy starts with the people living the problem. Listen for frustration. Watch what they actually do - not what they say they do. Understand what the problem costs them: time, clinical risk, downstream outcomes, money. The clearest signal you can get: are clinicians, patients, or care teams actively working around this problem? Workarounds are a vote. No workarounds means keep looking. 👉 Level 2 Empathy: The guiding lights for an ideal solution. Empathy does not stop once you understand the problem. It shapes the standards you refuse to compromise. What makes the device or procedure you develop special is how you frame the design constraints, or guiding lights. Test these with stakeholders. ↳ Specific clinical performance ↳ Required safety profile ↳ Usability ↳ Margins at a specific pricing ↳ System complexity constraints These are not aspirations or tradeoffs. They are design goals set with extensive research, tested in the market, and adopted with deep conviction. 👉 Level 3 Empathy: The solution concepts. This is where empathy becomes a learning loop. Build prototypes. Put them in front of users early. Invite criticism. Watch where people hesitate. Notice where they improvise around your concept the same way they improvised around the original problem. Don't defend the design. Learn from feedback and iterate. A team that pivots its design is doing rapid innovation. A team that pivots its problem after raising capital never had the right footing. Speed only creates value once you know three things: the problem is real, the target is clear, and the concept can meet every guiding light. Empathy is not one step. It is the thread running through all three levels - and the reason some teams ship solutions that survive first contact with the real world while others wonder why adoption stalled. 💬 Where does your team need more empathy right now: understanding the problem, defining an ideal solution, or testing concepts? Third in a series on leading with empathy. Follow ➕ Chris Danek for more on leading with empathy, rapid innovation, and startups.

Deep understanding of customers isn’t just a best practice — it’s the foundation for designing offerings that truly resonate, solve important customer problems, and foster long-term loyalty.   In my experience, the most successful innovations start not with assumptions, but with genuine curiosity and care for the people we serve.  Seeing the world through our customers’ (or in my case at AAA, our Members’) eyes creates empathy that isn’t just about understanding their needs—it’s about *feeling it* from the customer’s perspective.   Examples:   💵 Intuit’s “Follow Me Home” program sends teams to observe real customers using their products in daily life, leading to hundreds of customer-inspired improvements.    🔪 OXO famously designed its Good Grips kitchen tools after watching people with arthritis struggle in the kitchen—putting empathy at the center of product development.   🛒 IDEO, when redesigning a digital shopping cart, didn’t just ask shoppers what they wanted; they spent hours watching and listening, uncovering pain points no survey could reveal.    📦 Amazon’s obsession with customer feedback and behavior led to one-click ordering & personalized recommendations.   … and here at AAA, we’re continually researching what our Members need, why they join, why they don't join, why they lapse, etc... to understand how we can help create more Member value by solving important problems for them.   Here are a few things that are working for us: 🔷 Observe customers/Members in real contexts—don’t just ask them, observe and listen… including digital behaviors. 🔷 Use empathy mapping to capture not just what customers/Members are doing, but how they are feeling throughout their journeys. 🔷 Involve cross-functional teams in customer research for richer insights.   The future belongs to companies who design experiences with — not just "for" — their customers.  �� How are you using empathy and deep listening to shape your next big idea?   #CustomerExperience #Empathy #Innovation #Leadership #CX2025