Designing For User Empathy

🚫 How to Run UX Research Without Access To Users. With practical techniques to avoid guesswork and gather insights if you can’t talk directly to users. Attached cheatsheet (with and without access to users) by Nielsen Norman Group. 🚫 Ask for reasons for no access to users: there might be none. ✅ First, study job openings to map existing workflows/tasks. ✅ Make friends with sales, customer success, support, QA. ✅ Find colleagues who are the closest to your customers. ✅ Convey your questions indirectly via your colleagues. ✅ If you can’t get users to come to you, go where they are. ✅ Ask to observe or shadow customers at their workplace. ✅ Listen in to customer calls and interview call centre staff. ✅ Request access to analytics, CRM reports, call centre logs. ✅ Use Google Trends to find product-related search queries. ✅ Gather insights from search logs, Jira backlog, support tickets. ✅ Explore past/ongoing NPS and Voice-of-Customer programs. ✅ Study reviews, discussions, comments for your product/competitors. ✅ Map key themes and user sentiment on TrustPilot, AppStore etc. ✅ Recruit users via UserTesting, Wynter (B2B), Maze, UserInterviews. ✅ Ask for small but steady commitments: 5 users × 30 mins, 1× month. 🚫 Avoid ad-hoc research: set up regular check-ins and timelines. As H Locke noted, if we shed the light strongly enough from many sources, we might end up getting a glimpse of the truth. Ironically, the stakeholders who can’t give you time or resources to talk to users often are the first to demand evidence to support your initiatives. Sometimes the reason why companies are reluctant to grant access to users is simply the lack of trust. They don’t want to disturb relationships with big clients which is carefully maintained by the customer success team. They might feel that research is merely a technical detail that clients shouldn’t be bothered with. Show that you deeply care about that relationship and that you don’t want to disturb it any way. What you do want though is to reduce costs and risk — the risk of drawing wide-reaching conclusions from very little research, or none at all. Your best shot is to explain research as a powerful risk mitigation tool. And: search for people whose priorities align with yours — people who value and see the impact of UX in their units. They would absolutely love to support your work because it also supports their work — and they will put up a good word for you if they only had known that you existed. ✤ Useful resources: UX Research Cheat Sheet, by Susan Farrell from NN/g (attached) https://lnkd.in/eUTHKWvF What Can You Do When You Have No Access To Users?, by H Locke https://lnkd.in/ewHEKhBS UX Research When You Can’t Talk To Users, by Chris Myhill https://lnkd.in/ez5-b6zf #ux #research

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.

Last week, I coached a product team through a user interview debrief. They were excited! Users had shown enthusiasm for a new feature! 🎉 But when I asked, “What problem does this solve for them?” the room went quiet. 🫣 This happens more often than we’d like to admit. 🧠 The Trap: Mistaking Enthusiasm for Validation When users say, “That sounds great!” we often interpret it as validation. But here's the catch: - Users want to be polite. - They might not fully understand their own needs. - As product teams, we may hear what we want. This is why relying solely on user enthusiasm can lead us astray. 🔍 The Solution: Semi-Structured Interviews We need to dig deeper to understand our users truly. Semi-structured interviews strike the right balance between guidance and flexibility. Key practices include: - Start with hypotheses: Identify what you believe to be true. - Ask open-ended questions: Encourage users to share experiences, not just opinions. - Listen actively: Pay attention to what’s said—and what’s not. - Probe for underlying needs: Seek to understand the 'why' behind their behaviours. This approach helps uncover genuine insights, leading to solutions that truly resonate. 🌟 Imagine the Impact By adopting this method: - Teams build products that solve real problems. - User satisfaction increases. - Resources are invested wisely, reducing wasted effort. It's not just about building features—it's about delivering value. 🦾 Take Action Next time you're planning user interviews: - Prepare a set of hypotheses. - Design questions that explore user experiences. - Remain open to unexpected insights. Remember, the goal is to understand your users, not just confirm your assumptions deeply.

Over 80% of users skim, so when a PDP tries to say everything at once, it ends up saying nothing. A cluttered PDP gets more friction than function. Overwhelming users, leading to: - less time spent on page - missing value cues - fewer checkouts A well structured PDP doesn’t overwhelm, rather presents the information in a clear and digestible manner. Encouraging them to take action. In this post, I’ve broken down 12 changes I made to make the PDP easier to read and more focused on what actually helps users purchase. 1. Highlight customer satisfaction upfront. Show how many customers have purchased in the announcement bar. This builds immediate social proof that stays on all your pages. 2. Add benefit-focused badges above the product name. These help shoppers understand what key problems the product solves without needing to read through paragraphs. 3. Keep the title clear, and use a short subtitle to summarise the product and its core benefit. This helps users get both the “what” and the “why” at a glance. 4. Show the number of reviews beside the rating. It adds transparency and makes the rating feel more trustworthy, especially for first-time visitors. 5. Clarify price and pack size early. It saves users from searching for basic details which keeps attention focused on the purchase. 6. Use a context-rich main image. Featuring the product in its real-world use makes it easier to understand what’s being sold and how it fits into everyday life. 7. Expand image thumbnails beyond angles. Include images that show packaging and portion size to help customers evaluate fit and quality. 8. Add 2–3 bullet points above the fold. These help break down the product’s key benefits clearly, making it easier for skimmers to understand what makes it different. 9. Reinforce trust near the Add to Cart section. This is where buying hesitation happens so highlight things like delivery speed, return policies, or support to reduce friction. 10. Use icon-based highlights instead of long descriptions. Visual markers help users absorb information faster and keep the layout clean and scannable. 11. Break down product details visually. Showing ingredient percentages or content breakdowns in a simplified format helps make complex info more digestible. 12. Use accordions (not horizontal tabs). This allows users to expand only what they need, keeping the page organized and improving mobile usability. 13. Bring related variants closer to the decision zone. Show similar options earlier to help customers switch easily without needing to scroll to the bottom. Other UI/UX changes I did – Reduced text density to improve readability – Used consistent icons to simplify scanning – Added color cues for visual balance Found this useful? Let me know in the comments. PS: This checklist helps PDPs be clear and easy to follow without cramming in too much at once. This in turn will help the users make informed decisions that drive action. 

Wow. I just built 3 mini-apps for PMs in under 10 minutes: an empathy mapper, a journey analyzer, and a competitive analysis tool with Opal (Google Labs). No PRD. No Figma. No tickets. Just an idea → an experience. Instead of debating documents, I’m now sharing working mini-apps with my team ask them "react to this, let’s refine it” I used Opal to prototype the vibe with an: -Empathy Mapper -User Journey Analyzer -Competitive Landscape Tool Each one took minutes. Each one was immediately shareable. Each one changed the conversation. Use Opal when: -You want to validate an idea before writing a PRD -You need a quick tool for a workshop or meeting -You want to make research or concepts visible -You want to better empathize about your user Think of Opal as your 10-minute lab. If it takes longer than that, move it to a full prototype — that’s where other AI prototyping tools come in. Tips for PMs adopting this workflow -Start tiny. Your first Opal app should take under ten minutes. That constraint keeps you focused on intent, not polish. -Think in verbs, not nouns. Prompts like “summarize feedback” or “visualize trends” produce far better prototypes than static descriptions. -Collaborate live. Invite designers, engineers, and stakeholders into the session. Watching the prototype evolve creates alignment faster than any meeting. -Reflect. After every prototype, note what worked. Each build sharpens your prompting instincts and your product intuition. 🔗 Guides + masterclass in the comments 👇

"A Multifaceted Vision of the Human-AI Collaboration: A Comprehensive Review" provides some interesting and useful insights into effective Humans + AI work, drawn from across the literature. Some of the specifics insights in the paper: 🧭 Use the five-cluster framework to tailor collaboration depth. The framework defines five types of human-AI collaboration: (1) Humans as optional tools, (2) Consensus-based coordination, (3) Asynchronous collaboration, (4) Humans and AI as co-agents, and (5) Humans directing AI. Choose the type based on your task: use cluster 1 for personalization (e.g. recommender systems), cluster 2 for group decision-making, clusters 3 and 4 for task co-execution, and cluster 5 when human judgment must lead the process. 🧠 Let humans steer the learning loop. Design workflows where human feedback isn't just collected but actively changes the model. Show users how their input influences outcomes, and ensure systems update based on their corrections—failing to do so erodes trust and engagement fast. 🔄 Support iterative improvement through clear feedback cycles. Let users provide input at multiple points in the workflow—before, during, and after AI output. Use real-time feedback, editable suggestions, and memory-based personalization (e.g., saving past preferences) to refine collaboration with each loop. 📣 Grant users communication initiative. Don’t restrict user interaction to predefined prompts—enable them to ask questions, challenge decisions, or suggest new directions. This increases user autonomy, supports trust, and improves performance in both individual and group collaboration. 🛠️ Customize AI outputs to user-specific contexts. Embed features that allow tailoring of recommendations, predictions, or decisions to individual preferences or needs. For example, let users tweak rehabilitation goals in health tools or input content preferences in recommender systems. 🤖 Use AI as an impartial coordinator in group settings. In scenarios with multiple human participants—such as disaster planning or multi-user workflows—deploy AI to synthesize input, allocate tasks, and reduce bias. Ensure the system is transparent and users can reject or adjust AI decisions. 🔐 Prioritize human-centered design values. Build systems that are transparent (explain why outputs were generated), trustworthy (learn from user feedback), accessible (usable by non-experts), and empowering (give users control over high-level behavior). These are essential for lasting, ethical collaboration.

The 𝐏𝐚𝐭𝐢𝐞𝐧𝐭 𝐑𝐨𝐨𝐦 𝐨𝐟 𝐭𝐡𝐞 𝐅𝐮𝐭𝐮𝐫𝐞 (𝐏𝐑𝐨𝐅) teaching case shows how a large healthcare consortium and a small group of manufacturers collaborated to rethink innovation in a highly regulated sector. At its core, the case demonstrates how PRoF turned the interaction between two very different communities into its main innovation engine. The large consortium represents the healthcare user community: nurses, doctors, caregivers, patients, and hospital managers who express the lived reality of care. Their contribution is experiential and value-based. Through structured “brainwave sessions,” they surface latent needs and convert them into broad keywords such as comfort, privacy, dignity, or anti-loneliness. These keywords form a shared language that avoids technical jargon and allows hundreds of users with diverse perspectives to converge around common priorities. The small consortium consists of manufacturers, architects, and designers who have the capabilities to transform these user insights into concrete room concepts. Their commercial goals are kept strictly outside the creative process, allowing trust to grow between the groups. Once the user community defines the keywords, the producer community develops prototypes, after which the large consortium returns to evaluate and refine them. This modular sequencing keeps tensions low, ensures rapid progress, and prevents commercial logic from dominating user needs. The interaction between these two communities solves a longstanding problem in healthcare innovation: suppliers often misunderstand user needs, while users lack the means to innovate. PRoF bridges this gap by letting users drive ideation and letting producers translate that insight into solutions. What emerges is a genuinely user-oriented innovation ecosystem in which neither community could succeed alone, but together they generate concepts that reshape expectations of care design. You can find the case study at HBSP: https://lnkd.in/e6nxTFM7 #UserCentricInnovation #Collaboration #OpenInnovation #CrossCommunityCollaboration #HealthcareEcosystems #CoCreation #Ideation

How often do we design with people, instead of for them? It’s easy to fall into the trap of thinking that creativity is something only designers hold the key to. But when we pause and engage with communities, we realize something powerful: Creativity thrives within the community itself—it just needs the right conditions to flourish. Take, for example, the Collective Action Toolkit (CAT) by Frog. It’s not just a tool; it’s a framework that empowers communities to solve problems by tapping into their collective strength. Through a series of activities—like clarifying goals and imagining new ideas—small groups around the world have used this toolkit to not only share their thoughts but to take decisive action that addresses their concerns. The beauty of this approach is in its adaptability. It’s not a one-size-fits-all model. Each group can mould it to fit their unique needs, ensuring that everyone’s voice is heard and valued. But collaboration, as we know, isn’t always easy. There’s often discomfort, sometimes even conflict, when differing ideas meet. Yet, as designers, navigating these challenges is where true progress happens. As Otto Scharmer and Peter Senge, leaders in organizational development, have shown, it's in this space of tension that new solutions are born. A recent contribution from @Design Impact offers a set of guiding principles for designers to keep in mind when working with communities. One of these, “Value me for who I am, not who I’m told to be,” resonates deeply. It’s a reminder that behind every design is a real person, with history, emotions, and passions. When we acknowledge that, we move beyond simply gathering feedback—we tap into real leadership within the community. At the end of the day, Social innovation isn’t just about creating a product or service. It’s about co-creating, about building alongside communities rather than handing down solutions. It’s about fostering a space where everyone’s creativity can shine, and where long-term, sustainable change is possible. Have you been part of a design process that values community leadership? What challenges—and opportunities—did you encounter along the way?

Micro-interactions are no longer just a “nice-to-have” in UX— They’re a critical tool for guiding user behavior, building brand connection & improving retention. These small, purposeful elements like a progress bar, a loading animation, or a subtle vibration make a big difference when done right. How micro-interactions add value: 1. Clearer navigation: → Progress indicators or hover effects help users understand where they are— → And what’s happening— essential for reducing frustration. 2. User confidence: → Actions like a confirmation checkmark after a form submission reassure users that their actions are successful. 3. Brand differentiation: → Unique micro-interactions tailored to your brand’s identity make your app or website stand out in a crowded market. Here’s how to use them effectively: a. Prioritize user intent: → Focus on moments where users might feel uncertainty. → Such as waiting for a process to complete or interacting with a new feature. b. Keep it seamless: → Ensure micro-interactions don’t slow down or overwhelm the user experience. → They should complement, not complicate. c. Iterate & test: → Small doesn’t mean insignificant. → Test micro-interactions with real users to see what resonates. Let’s take a look at why they matter for retention: Memorable experiences aren’t always about big features— They’re often about how smooth & satisfying the small moments feel. By optimizing these “micro” details, you can create loyal users who notice the care & thought in your design. What are the overlooked moments in your user journey where micro-interactions could shine?

Product success isn’t random. Here are 7 patterns I’ve noticed in teams that build great products when it comes to user research: 1. They research user workflows, not just features: Instead of asking "How do you like our checkout flow?" they map out the entire buying journey, from first awareness to post-purchase experience. 2. They involve builders in the process: When engineers experience user struggles firsthand, they don’t need a spec to “think user-first.” They build with shared context, not just requirements. 3. They go beyond business metrics: They track things like ‘time to user's first success’ and ‘how often users achieve their intended outcome’ 4. They research edge cases and power users: Power users and edge cases stress-test the product in ways mainstream users won’t. Great teams learn from them before the market demands it. 5. They listen between the lines: When users say "I need more customization," great teams dig deeper to understand the underlying need 6. They research non-users as much as users: Most teams obsess over active users. The best ones invest in understanding the quiet 'no thanks' moments from people who bounced or churned. 7. They share research insights across the entire company: Sales, marketing, and customer success teams all get regular exposure to user research. Everyone stays connected to user reality. The best teams treat users as complex humans with jobs to be done & not data points. They invest in understanding the full context of how their product fits into users' lives, work, and goals. Which of these do you swear by? Comment or DM - let’s compare notes!