Designing For User Empathy

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. 

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?

One of the parts of my role that teaches me the most is watching how customers and technicians use our solutions in real conditions not in demos, but in the environments where our products actually operate. During a recent field visit, I noticed a technician spending 30% more time on a step we had always assumed was simple. It wasn’t a technical issue, it was a clarity gap. That moment pushed us to rethink the experience around the product. We rebuilt the onboarding guide, added clearer step-by-step visuals, simplified indicators, and introduced a short training module. The hardware didn’t change but the confidence with which people used it did. This reminded me that customer-centricity isn’t only about performance metrics. It’s also about reducing friction and supporting the people who rely on our products every day. Studies indicate that nearly 70% of consumers return products if they find them difficult to operate, and 54% return them due to installation difficulties. Even a 10% improvement in ease-of-use can lift customer satisfaction by almost 20%. Some of the most meaningful improvements don’t come from upgrading the product but from making the experience a little easier and a lot clearer.  #WomenInLeadership #CleanEnergy #EaseOfUse #GEON

Design isn’t just about how things look, it’s about how people feel using what you’ve made. After working on some products previously, I’ve learned that user satisfaction doesn’t just happen at the end. It’s shaped by the choices we make as designers at the very beginning. Here’s what I’ve seen consistently lead to more satisfied users: ◽Clear understanding of the user’s real problem (not just the founder’s idea) ◽Designing with the business model in mind, so UX supports sustainability ◽Collaborating with developers early to avoid designing things that can’t be built ◽Tight feedback loops with actual users, not just internal opinions ◽Simplicity over flash—most users want clarity, not cleverness User satisfaction isn’t an option in product development. It’s how products grow, retain, and resonate. Here’s a health & wellness design exploration I created recently—rooted in simplicity, purpose, and the user’s point of view. #userinterface #userexperiencedesign #userinterfacedesign #uiux #usercentricdesign #figma #uidesign #uxdesign

Traditional usability tests often treat user experience factors in isolation, as if different factors like usability, trust, and satisfaction are independent of each other. But in reality, they are deeply interconnected. By analyzing each factor separately, we miss the big picture - how these elements interact and shape user behavior. This is where Structural Equation Modeling (SEM) can be incredibly helpful. Instead of looking at single data points, SEM maps out the relationships between key UX variables, showing how they influence each other. It helps UX teams move beyond surface-level insights and truly understand what drives engagement. For example, usability might directly impact trust, which in turn boosts satisfaction and leads to higher engagement. Traditional methods might capture these factors separately, but SEM reveals the full story by quantifying their connections. SEM also enhances predictive modeling. By integrating techniques like Artificial Neural Networks (ANN), it helps forecast how users will react to design changes before they are implemented. Instead of relying on intuition, teams can test different scenarios and choose the most effective approach. Another advantage is mediation and moderation analysis. UX researchers often know that certain factors influence engagement, but SEM explains how and why. Does trust increase retention, or is it satisfaction that plays the bigger role? These insights help prioritize what really matters. Finally, SEM combined with Necessary Condition Analysis (NCA) identifies UX elements that are absolutely essential for engagement. This ensures that teams focus resources on factors that truly move the needle rather than making small, isolated tweaks with minimal impact.

The secret behind Gmail's 1.8 billion users wasn't innovation or marketing. It was a simple question asked of only 100 people. At 26, Paul Buchheit built Gmail's first version in just one day. But what he did next was revolutionary. His approach was simple: make 100 people completely satisfied with the product before showing it to the world. The team embedded a straightforward question in the interface: "Are you happy? Yes or no." When users answered "No," Paul personally reached out with a follow-up to understand what it will take to make them happy users. This philosophy of deep, narrow appeal rather than broad mediocrity became their north star. Instead of building something "good enough" for all, they built something exceptional for a small group and expanded from there. I've applied this same principle at flutrr too. 1. When building India's first multilingual dating platform, we didn't just chase user numbers. 2. We focused on creating meaningful connections for those struggling with language barriers in online dating. 3. We even remove thousands of profiles monthly to maintain quality. It might sound counterintuitive, but as Paul proved, it's easier to grow from deep satisfaction than convert indifference into love. Product success isn't measured by how many people use your creation, but by how deeply it solves real problems for those who do. The one feature that creates genuine happiness for your users is where your growth potential truly lies. How often do you get this question from apps you love? #user #feedback #growth #product

One size solutions don’t work because people aren’t one size. Disability doesn’t exist in isolation. Our identities overlap and that shapes how we experience the world. And when you ignore that, you exclude people plain and simple. Image ID: infographic titled "Intersectionality & Disability," designed to explain why "one-size-fits-all" solutions are ineffective by highlighting that disability is experienced differently based on other aspects of a person's identity. The infographic is organized into several key sections: What is Intersectionality? Defines it as a way to understand how overlapping identities—such as disability, race, ethnicity, gender, age, socioeconomic background, and religion/culture—combine to shape unique barriers or advantages. Why It Matters: Emphasizes that disability is part of human diversity, and because barriers and experiences differ, inclusion must consider the "whole person." A central "Key Idea" box states: "If we design for only one identity, we exclude many." Examples in Practice: Illustrates failures of narrow design, such as wheelchair-accessible buildings lacking multilingual signage, mental health services that ignore cultural stigma, and digital tools that are accessible but not affordable. Common Gaps & What This Means in Practice: Lists common shortcomings (e.g., accessibility without affordability, inclusion without cultural awareness) and actionable steps for inclusive design, such as listening to diverse lived experiences, co-designing, and regularly reviewing who might be excluded. Our Shared Responsibility: Concludes that everyone has a role to play by recognizing differences, challenging assumptions, designing for diversity, and including all voices. Visual Style The infographic uses a clean, professional, and accessible design with soft pastel colors, friendly iconography, and clear, structured headings. At the bottom right, there is a circular logo featuring a network of icons representing diversity, labeled "DIVERSELY DISABLED STAFF NETWORK." #DisabilityInclusion #Intersectionality #Accessibility #InclusiveDesign #A11y #DesignForAll #DiversityAndInclusion

One of the key ways to demonstrate the value of UX research is by measuring success metrics. Without these, it can be hard to show the impact of your work on the product or the business. But how exactly can we measure success in a UX research project? Here are a few critical steps and metrics to consider: 1. Align with Business Goals: ↳ Start by identifying the KPIs tied to business goals. Whether it’s conversion, adoption, or drop-off rates, the research should connect to metrics that matter for the company’s success. By linking research insights directly to business outcomes, you show stakeholders how UX impacts their key priorities. 2. Behavioral Metrics: These are the data points tied to how users interact with your product, such as: ↳ Task Success Rate: How many users successfully complete the task? ↳ Time-on-Task: How long does it take users to complete a task? ↳ User Error Rate: How often do users make mistakes during the task? Tracking these helps identify friction points in the user journey and quantifies the effectiveness of your designs. 3. Attitudinal Metrics: These reflect how users feel about the product or experience: ↳ Net Promoter Score (NPS): How likely are users to recommend your product? Although this one is definitely not my favorite, most businesses care a lot about NPS. ↳ Customer Satisfaction (CSAT): How satisfied are users with the product? ↳ Perceived Ease of Use: How easy do users think the product is to use? Gathering these insights gives you a clear sense of user sentiment and overall satisfaction. 4. Usability Metrics: For more specific insights, you can track usability metrics like: ↳ System Usability Scale (SUS): A quick way to assess perceived usability. ↳ Completion Rates: How many users completed a given task without assistance? 5. Impact on KPIs: Finally, after research is complete and changes are implemented, re-measure these metrics to show improvements. Demonstrating a reduction in error rates or an increase in task success ties UX research directly to improved product performance. By clearly connecting UX metrics to business KPIs, you help stakeholders see the concrete value that research brings to the table. These success metrics aren’t just numbers — they’re proof of how UX research improves user experience and drives business impact. How do you measure success in your UX research projects?