UX Design Feedback Loops

Product managers & designers working with AI face a unique challenge: designing a delightful product experience that cannot fully be predicted. Traditionally, product development followed a linear path. A PM defines the problem, a designer draws the solution, and the software teams code the product. The outcome was largely predictable, and the user experience was consistent. However, with AI, the rules have changed. Non-deterministic ML models introduce uncertainty & chaotic behavior. The same question asked four times produces different outputs. Asking the same question in different ways - even just an extra space in the question - elicits different results. How does one design a product experience in the fog of AI? The answer lies in embracing the unpredictable nature of AI and adapting your design approach. Here are a few strategies to consider: 1. Fast feedback loops : Great machine learning products elicit user feedback passively. Just click on the first result of a Google search and come back to the second one. That’s a great signal for Google to know that the first result is not optimal - without tying a word. 2. Evaluation : before products launch, it’s critical to run the machine learning systems through a battery of tests to understand in the most likely use cases, how the LLM will respond. 3. Over-measurement : It’s unclear what will matter in product experiences today, so measuring as much as possible in the user experience, whether it’s session times, conversation topic analysis, sentiment scores, or other numbers. 4. Couple with deterministic systems : Some startups are using large language models to suggest ideas that are evaluated with deterministic or classic machine learning systems. This design pattern can quash some of the chaotic and non-deterministic nature of LLMs. 5. Smaller models : smaller models that are tuned or optimized for use cases will produce narrower output, controlling the experience. The goal is not to eliminate unpredictability altogether but to design a product that can adapt and learn alongside its users. Just as much as the technology has changed products, our design processes must evolve as well.

Stop asking clients "what's your feedback?" Well, I don't mean don't ask for feedback. Obviously you should. But "what do you think?" is an open invitation to chaos. I made a small cheat sheet in Framer that you can bookmark for your next design review. Every designer has lived this meeting: you present refined brand concept and someone reopens the logo discussion. Someone else mentions a competitor. The color debate starts again. Suddenly the entire project is back at square one and you're playing design ping-pong with six people who all have different opinions about blue. The problem is that nobody defined WHAT kind of feedback the work actually needs right now. One trick I learned at IDEO is naming the feedback mode at the beginning of every session. Not "any thoughts?" but what kind of thinking we're doing today. Here's the framework I use: [Inspire mode] When we're exploring what the brand could become, ask questions like: → Which references feel closest to your ambition? → Which ones feel completely wrong? → Where should this brand sit culturally — more institutional or more experimental? [Challenge mode] When we need to stress-test the concept, ask: → Does this feel too safe or too bold for where the company is today? → What objections would users or investors raise? → Would this still feel right if the company scaled 10×? [Decide mode] When it's time to commit, ask: → Which direction best reflects the company's future, not just today? → What trade-offs come with this choice? → If we shipped this tomorrow, would you defend it publicly? [Refine mode] When the direction is right but the details need tuning, ask: → What parts feel strongest? → Where does something feel slightly off — even if you can't articulate why? → Where do you want more clarity or emphasis? [Polish mode] When the work is almost ready to ship, ask: → Anything unclear before launch? → Are there key use cases we haven't stress-tested? → Anything that makes you nervous about rollout? Once I started doing this, feedback sessions stopped being fight-or-flight situation. And the framing can be very simple in practice! For example: “For this review I’d love to stay in inspiration mode. I’m not looking for approval yet — I’m trying to understand what territory feels right for the brand. Which of these directions feels closest to your ambition, and which ones feel completely wrong?” Or later in the project: “Today we’re in refine mode. The concept is already chosen, so I’m mostly looking for signals on details — what parts feel strongest, and where something feels slightly off.” A tiny shift in framing, but it changes the entire conversation. I hope it might save you from at least one unnecessary “i don’t like this shade of blue” debate!

Communication gaps and weak feedback loops hurt business success. [Client Case Study] A large hospital network noticed declining patient satisfaction scores. Even with state-of-the-art facilities and technology, patients reported feeling unheard, frustrated, and confused about their care plans. The executive team assumed the problem was with staff training or outdated workflows. ‼️ Mistake: Relying on high-level reports and not direct frontline feedback. Nurses, doctors, and administrative staff communicate differently based on their backgrounds, generations, and roles. - Senior physicians prefer face-to-face or email communication - Younger nurses and tech staff rely on instant messaging and digital dashboards - Patients (especially elderly ones) need clear verbal explanations, but many received rushed instructions or digital paperwork ‼️ Mistake: Differences weren't acknowledged and crucial patient information was lost, leading to errors, frustration, and decreased trust. Frontline staff experienced communication challenges daily but lacked a way to share them with leadership in a meaningful way. ❌️ Reporting structures were too slow or ineffective. Feedback was either ignored, filtered through multiple levels of management, or only addressed after major complaints. ❌️ Executives made decisions based on outdated assumptions. They focused on training programs instead of fixing communication systems. ❌️ Systemic decline Employee burnout increased as staff struggled with inefficient systems. Patient satisfaction declined, leading to lower hospital ratings and reimbursement penalties. Staff turnover rose, increasing costs for recruitment and training. 💡 The Solution: A Multi-Channel Communication Strategy & Real-Time Feedback Loop ✅ Physicians, nurses, and patients receive information in ways that align with their preferences (e.g., verbal updates for elderly patients, digital dashboards for younger staff). ✅ Digital tool that allows staff to flag communication issues immediately rather than waiting for annual surveys. ✅ Executives hold regular listening sessions with frontline employees to better understand challenges before making changes. The Result - Patient satisfaction scores improved - Employee engagement increased - Operational efficiency improved Failing to adapt communication strategies and strengthen feedback loops affects reputation, retention, and revenue. (The 3Rs of a successful organization.) Frontline operations directly impact customer and employee experiences. This hospital’s struggle isn’t unique. Every industry faces the risk of misalignment between leadership decisions and frontline realities. Weak feedback loops and outdated communication strategies create costly inefficiencies. If your employees don’t feel heard, your customers won’t feel valued. Business suffers. Are you listening to the voices that matter most in your business? If not, it’s time to start.

𝗗𝗮𝘁𝗮 𝘁𝗲𝗹𝗹𝘀 𝘆𝗼𝘂 𝗪𝗛𝗔𝗧 𝗵𝗮𝗽𝗽𝗲𝗻𝗲𝗱; 𝗙𝗶𝗲𝗹𝗱 𝘁𝗲𝗮𝗺𝘀 𝘁𝗲𝗹𝗹 𝘆𝗼𝘂 𝗪𝗛𝗬. The "Hybrid Sales Model" is failing if your data is siloed. There is a statistic from McKinsey’s 2024 B2B Pulse that every Commercial leader needs to see: B2B decision-makers now use 𝟭𝟬 𝗱𝗶𝘀𝘁𝗶𝗻𝗰𝘁 𝗰𝗵𝗮𝗻𝗻𝗲𝗹𝘀 during their journey. In Pharma, this means a Healthcare Professional (HCP) might watch a webinar (Marketing), visit a portal (Digital), and meet a Rep (Sales). Too often, the Sales Rep has no idea the webinar happened. When Sales and Marketing operate in silos, the "Omnichannel" experience becomes a "Multi-channel" noise factory. The HCP gets a generic email from Marketing the day after a Rep visit, referencing a totally different topic. That’s not engagement; that’s collision. To fix this, 𝘄𝗲 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗺𝗼��𝗲 𝗳𝗿𝗼𝗺 "𝗖𝗮𝗺𝗽𝗮𝗶𝗴𝗻𝘀" 𝘁𝗼 "𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗘𝗻𝗴𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗝𝗼𝘂𝗿𝗻𝗲𝘆𝘀." That means:  • 𝗨𝗻𝗶𝗳𝗶𝗲𝗱 𝗩𝗶𝗲𝘄: The CRM must show all interactions (digital + in-person) to the Rep in real-time.  • 𝗥𝗲𝗽-𝗧𝗿𝗶𝗴𝗴𝗲𝗿𝗲𝗱 𝗘𝗺𝗮𝗶𝗹: Empower Sales teams to trigger marketing-approved digital content based on their face-to-face conversations.  • 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗟𝗼𝗼𝗽𝘀: Marketing needs 𝗾𝘂𝗮𝗹𝗶𝘁𝗮𝘁𝗶𝘃𝗲 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 from the field to adjust digital tactics. Data tells you what happened; field tells you why. Set up a 15-minute "Insight Swap" meeting between one Marketing Brand Manager and one District Sales Manager. No slides. Just discuss: "What questions are customers asking you right now that our current emails aren't answering?" Sales leaders: Does your team currently see digital interactions in their CRM before they step into a clinic? #PharmaSales #SFE #Omnichannel #CustomerEngagement #PharmaTrends

You're still designing like coding costs a fortune. That's why your ideas always arrive too late. 🧠 What if our design process was… backwards? For years, our craft was built around one fear: building the wrong thing is expensive. So we stacked layer after layer of protection: functional docs, PRDs, detailed specs, pixel-perfect Figma files, reviews, committees, validations — all before a single line of code was written. That made sense when: shipping a prototype took 3 weeks, spinning up a dev team was costly, every iteration was a mini-project. But with Claude, Figma AI, Lovable & co, reality has shifted: a clickable version "good enough to test" can take 30 minutes, not 3 weeks. In that world, the old process "think → specify → design → build" is becoming a bottleneck. The role flips: From 🔒 "block construction until everything is validated" To 🎯 "build fast, then use design to shape, fix, and refine." So what does this new workflow look like? 1️⃣ Start with a problem, not a document One clear sentence is enough as a brief. Ex: "Designers struggle to get honest feedback on their portfolio from peers." 2️⃣ Build the roughest version first With Lovable, Claude Code or any other tool, generate a functional prototype — even an ugly one. Not a beautiful Figma. Something real and clickable. 3️⃣ Actually use it Test it yourself, break it, feel where it gets stuck. You no longer guess the friction — you live it. 4️⃣ Design after, not before This is where UX design reclaims its full value: fix what blocks, simplify what overwhelms, add clarity, consistency, hierarchy. 5️⃣ Show the product, not the spec Instead of a 20-page doc, send a link: "Try it, tell me what's confusing." Feedback is grounded in something real, not hypotheses. 6️⃣ Iterate at the speed of conversation Got feedback? Adjust in minutes, not at the next sprint. Iterate on something concrete, multiple times a day if needed. 7️⃣ Document after the fact Documentation becomes the trace of what exists, not a prediction of what might exist. It comes once the experience has been proven. This shift doesn't mean "stop thinking." Quite the opposite: you think at every step — grounded in real feedback, user tests, and data — rather than long theoretical debates. The real shift, for designers and PMs, is accepting that: value is no longer in producing docs, but in taste, judgment, and the ability to iterate fast on something real. 📎 Free resource I packed this process into a ready-to-use prompt. Paste it into Claude, Lovable or Cursor — and you'll have a functional prototype in 30 minutes. https://lnkd.in/dse5WQYB No Figma. No PRD. Just something clickable in 30 minutes. If this post made you think — save it. 🔖 In 6 months, you'll wonder why you didn't apply it sooner. #claude #lovable #workflow

User feedback is a barometer of feeling, not a to-do list. Listen to your users with empathy, but innovate with conviction, says Infosys co-founder Nandan Nilekani. Too often, we treat feedback as direct product advice: Remove this feature. Lower the price. Change the design. But we must understand that users are not product experts. Their feedback usually reflects their own emotions, confusion, or aspirations, rather than the actual solution for the wider user base. Henry Ford’s famously said: “If I had asked people what they wanted, they would have said faster horses.” Because people didn’t know a car was possible. Their real need was faster travel, not a better horse. This happens all the time in product development. Flipkart found that “cash on delivery is risky” wasn’t about payment method. It was about trust. Fixing policies and transparency increased prepaid orders by over 30 percent in smaller cities according to RedSeer. Zomato heard “your app is too complicated.” The real issue was first-time digital buyers. Adding guided onboarding boosted order completion by 25 percent. A BCG India study showed 72 percent of user feedback is emotional, not actionable without digging deeper. If you take every comment literally, you end up with a bland product nobody loves. But if you treat feedback as a compass, you can build something people didn’t even know how to ask for. Here’s what helps me handle feedback effectively: ✅ Listen for emotion ✅ Ask why multiple times ✅ Find the underlying need ✅ Don’t react blindly ✅ Balance insights with your product vision If you take every comment literally, you’ll end up with a product nobody loves. But if you treat feedback as a compass and a barometer of sentiment, you can build something users didn’t even know how to ask for.

Struggling to prioritize what truly matters in your UI design? Imagine transforming user feedback into actionable insights that elevate your design. Today, I’m sharing a step-by-step guide on how to use user feedback to prioritize attributes using Object-Oriented User Experience (OOUX) principles. Step 1️⃣ : Collect User Feedback 🟢 Gather Diverse Feedback Sources: ✔ User Interviews ✔ Surveys and Questionnaires ✔ Customer Service Logs ✔ Usability Testing Sessions ✔ Social Media Comments ✔ Online Reviews 🟢 Identify Key User Pain Points and Desires: ✔ Look for recurring themes and issues. ✔ Highlight specific feedback that pertains to particular attributes of your objects. Step 2️⃣ : Categorize Feedback 🟢 Sort Feedback by Object: ✔ Group feedback according to the object it pertains to (e.g., User, Product, Event). 🟢 Identify Attribute Mentions: ✔ Note down attributes mentioned in the feedback (e.g., “User’s history,” “Event’s profitability”). Step 3️⃣ : Prioritize Core Content and Metadata 🟢 Distinguish Between Core Content and Metadata: ✔ Core Content Attributes (🟨): Unique identifiers, essential data (e.g., username, event name). ✔ Metadata Attributes (🟥): Sorting, grouping, and filtering information (e.g., tags, categories, event date, time). 🟢 Rank Attributes Based on User Value: ✔ Use methods like MoSCoW (Must have, Should have, Could have, Won’t have). ✔ Focus on attributes that solve key user pain points or enhance user satisfaction. Step 4️⃣ : Create Object Maps 🟢 Define Objects and Relationships: ✔ List objects identified from feedback. ✔ Establish relationships (e.g., “🟦 EVENT has 1 USER who created it,” “🟦 EVENT has 0-many COMMENTS”). 🟢 Map Out Attributes: ✔ Create detailed object maps with attributes categorized as core content (🟨) or metadata (🟥). ✔ Ensure attributes are clearly defined and consistently applied across objects. Step 5️⃣: Validate with Users 🟢 Prototype and Test: ✔ Create low-fidelity prototypes or wireframes incorporating prioritized attributes. ✔ Conduct usability tests to validate the importance and utility of the attributes. 🟢 Iterate Based on Feedback: ✔ Make adjustments based on user testing results. ✔ Continuously refine the prioritization and object mapping process. Using user feedback to prioritize attributes ensures that your design is user-centered and effectively addresses user needs. This process not only enhances user satisfaction but also streamlines development by focusing on what matters most to users. How do you incorporate user feedback into your design process? Let’s discuss in the comments! #OOUX #UXDesign #UserFeedback #UserExperience #UIDesign #DesignThinking #ProductDesign #CustomerSatisfaction #ContinuousImprovement

Steve Jobs kept rejecting the Mac calculator. Every day, the developer would incorporate his feedback. Every day, Jobs would find something new to criticise. The background was too dark. The buttons were too big. The lines were the wrong weight. It went on for days. Then the developer did something clever. Instead of going away and guessing again, he built a tool that let Jobs adjust every visual parameter himself: button sizes, line thickness, background patterns. All controlled through pull-down menus. Jobs sat down with it for ten minutes. Made his choices. Done. That design shipped with the Mac in 1984. It stayed virtually unchanged for 17 years. Here's what strikes me about that story: the problem was never Jobs's taste. It was the communication gap between what he wanted and what he could articulate. Once he could interact directly with the design rather than describe it in words, the answer came quickly. I see the same pattern in KPI design all the time. When a consultant (or a data team, or a senior manager) disappears into a room and returns with a finished KPI framework, the feedback cycle can be brutal. People push back. Revisions multiply. Weeks pass. And even when something is finally agreed, the people who'll be measured by it feel little ownership over it. Contrast that with what happens in a well-run KPI Tree workshop. When people are actively involved in building the tree, debating which drivers matter, and shortlisting the measures themselves, the output doesn't just arrive faster. It arrives with buy-in already built in. The same principle applies when designing dashboards. Showing stakeholders a finished dashboard and asking for feedback is a bit like Jobs being asked to approve someone else's calculator. People struggle to articulate what's wrong. Put them in a room with a prototype and let them interact with it, and you'll hear things like "that metric should be here, not there" and "I need to see this by region, not total." Specific, actionable, useful. The lesson from a ten-minute design session in 1982 still holds: you get better outcomes, faster, when the person who has to live with the result is involved in creating it. Not as a reviewer. As a participant. How much of your KPI or dashboard design process actually involves the people who'll use it? #KPIs #kpiblackbelt #performancemanagement #MeasureWhatMatters #Leadership

We keep asking frontline workers the wrong question at the wrong time. Here's why creating multiple feedback channels motivate employees to actually want to give feedback. Most of us want feedback from frontline employees but only ask for it at the end of training programs. "What did you think of the course?" isn't the question that will improve our programs. The better questions happen outside of individual training moments: - What do you wish you'd known a week earlier in this role? - What information would have saved you time or stress? - When you're having a day where you’re on fire at this job, what are you doing differently? We need to create multiple feedback channels because people respond differently. Some prefer anonymous surveys with open-ended questions. Others will be more honest in conversations with their direct managers. Use existing communication tools rather than adding new ones. People already have too many platforms to check. ***Most importantly: act on the feedback we receive and show people their input led to changes*** Not every frontline worker cares about making learning better. Some are just trying to get through their shifts. That's okay. But the ones who do engage will give us insights we can't get any other way. They'll tell us when we're teaching things too late in the process, focusing on the wrong skills, or missing critical information entirely. We need to listen to the people doing the job every day. They know things about performance that no instructional designer or learning leader can guess.

90% of your customer feedback is invisible. It's silently costing you millions. Most businesses think they're listening to customers. They're not. They're hearing fragments. English-only surveys. Delayed reports. Cultural context lost in translation. After analyzing 100+ datasets, here's what we found: Real-time, multi-language feedback systems increase customer satisfaction by 42%. But most companies are still doing this wrong: → Feedback sits in silos for weeks before anyone sees it → Non-English responses get ignored or poorly translated → Cultural nuances disappear in generic sentiment analysis → By the time insights reach decision-makers, the moment is gone Here's what actually works: → Capture feedback in the customer's native language → Translate with cultural context, not just words → Build dashboards that show trends as they happen → Connect emotional intelligence to data interpretation → Link social sentiment and in-house feedback to financial outcomes The companies getting this right aren't just collecting more feedback. They're hearing the full story. In real time. Across every language and culture. That's the difference between reacting to problems and preventing them. When you can see what 90% of businesses miss, you don't just improve customer experience. You create a competitive advantage. What's one step you'll take this week to uncover hidden feedback?