UX Design Feedback Loops

As you start working with more and more stakeholders, there is a natural tendency to try accomodate every bit of feedback received. This is something we refer to as "Design by committee". It's also a surefire way to build subpar experiences by combining multiple irrelevant ideas into a single solution, rather than thinking deeply about the problem being solved and what the right solution is. Here is what the situation usually looks like: - Stakeholder A: "This competitor app is doing it that way." - Stakeholder B: "I showed this to my partner, and they didn't like it." - Stakeholder C: "Let's rethink this as it won't be clear to users." Some of the feedback above is valid, whereas other pieces are purely opinion-based, with no particular evidence or logical argument. It's your role as a designer to cut through the noise, eliminate pure opinion, debate where needed, and ultimately arrive at a solution that addresses the original problem, both for the business and the user. I have a simple decision tree I've used throughout my career as a thought process when dealing with feedback from multiple stakeholders. It boils down to four questions: 🟢 Is it clear and specific? ↳ If not, clarify it. 🟢 Is it supported by evidence or logic? ↳ If not, debate it. 🟢 Will it help us meet the objective? ↳ If not, kindly disregard. 🟢 Is it feasible? ↳ If not, save it as a fast-follow or future idea. If all the checks above are met, it's worth actioning the feedback. It still doesn't mean you have to act on every single suggestion, but it does mean you can quickly narrow down to a much smaller pool of items to consider. -- If you found this useful, consider reposting ♻️ What else have you found helpful in dealing with feedback from multiple stakeholders? Let me know in the comments 👇 PS: I'm working on a larger content piece on managing and working with stakeholders, dropping in the next few weeks. Find the link to the newsletter in the first comment.

At the top of the "are doomed to repeat it" category is the notion of "spec-driven development" (SDD). Though some claim that SDD is all about very tiny specs that encompass only a tiny amount of work, the vast majority of comments I see on the topic are hyping old-school waterfall big-up-front design as if that's a new, innovative idea. It's pushed by the most irresponsible of the vibe-coding crowd, who imagine that, if only the prompt were more detailed, they'd get better results. They won't. We stopped working from big up-front specs decades ago for a reason—the approach fails in every context but the most boring ones: either the same program written over and over again, or something that effectively implements a mathematical formula of some sort. In that last case, a spec-driven approach will probably yield a UX so bad that it makes the formula implementation irrelevant. People don't know what they need until they get something into their hands and try to use it. Any way of working that doesn't acknowledge that truth will fail. I suppose, if the only thing you've ever experienced is chaos, SDD seems like an improvement, but believe me, it's not. In my experience, incremental feedback-driven approaches always yield better outcomes. Collaboratively develop a strategic goal. Collect enough information to start. Start. Get feedback as you work. Adjust. Works like a charm.

Following user feedback is a Product Management virtue. Is there an actual way to implement it, between all the noise, bugs, and stakeholder requests? Well… Most teams claim they are customer-driven. Yet the moment you open Zendesk, App Store reviews, survey results, and Slack threads, you instantly remember why everyone quietly avoids this work. Feedback is everywhere, contradictory, emotional, duplicated, and nearly impossible to turn into decisions.  It is chaos disguised as “insights.” This is why the new Amplitude AI Feedback release caught my attention and made it all the easier to decide to partner with them on this update. It successfully connects what users say with what they actually do, in one workflow. No extra tools.  No extra tabs. You see their words, frustrations, and praise. You see their behavior. And AI transforms it into ranked themes, rising trends, top requests, and complaints. Noise turns into clarity. Opinions turn into patterns. Patterns turn into action. And because it is native inside Amplitude, it kills the biggest problem in feedback work: Fragmentation. Everything flows into analytics, session replay, and cohorts, creating a full loop from insight to fix. You can trace why an issue matters, how many users care, how it impacts behavior, and which actions you should take. Finally, a single source of truth for PMs, UX, CX, and marketing. I’m also genuinely impressed with the supported sources of feedback: App Store, Google Play, Zendesk, Intercom, Freshdesk, Salesforce Service, Gong, Trustpilot, G2, Reddit, Discord, and X. Slack arrives in Q1, and there will be more! If you ever felt overwhelmed by feedback, this is one of the first attempts I have seen that genuinely solves the operational pain, not just the reporting part. It launches… Today! Take a look: https://lnkd.in/dAJKeTez What was the most successful update you know that came from the product’s users? Let me know in the comments. #productmanagement #productmanager #userfeedback

Iteration and feedback are fundamental to creating high-quality designs as they drive continuous improvement and ensure the product aligns with user needs and goals. Here's why they matter: 1. Validating Assumptions Iteration helps test and refine initial ideas, ensuring they solve real problems instead of relying on unproven assumptions. 2. Centering User Needs Feedback reveals user pain points and areas for improvement, making designs more effective and user-friendly. 3. Encouraging Innovation Iterative cycles allow for exploring multiple ideas, leading to creative and unexpected solutions. 4. Reducing Development Costs Identifying and fixing design issues early saves time and resources in later development stages. 5. Enhancing Collaboration Feedback fosters teamwork, ensuring designs align with technical, business, and user needs. 6. Building Confidence in the Solution** Repeated refinement ensures the final design is well-tested and ready to deliver value. #uiuxdesign #mobileappdesign #userexperience #productdesign

Navigating the product development process is a bit like guiding a frog through its habitat - close observation and adaptation to feedback are essential. This approach not only aligns products with user needs but also significantly improves resource efficiency. 𝐓𝐡𝐞 𝐈𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐜𝐞 𝐨𝐟 𝐅𝐞𝐞𝐝𝐛𝐚𝐜𝐤 𝐢𝐧 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 - MDP Creation: Start by launching a Minimal Desirable Product - this serves as your basic model to initiate user interaction. - User Observation: Monitor how users interact with the MVP. Do they find it intuitive? Are there unforeseen issues? - Feedback Collection: Actively seek user feedback through surveys, direct observations, and interviews to gather valuable insights for improvement. - Iterative Design: Refine and enhance the product based on this feedback, focusing on features that genuinely add value. - Continuous Improvement: Maintain a cycle of feedback and improvement, ensuring the product remains relevant and effective over time. 𝐀𝐛𝐨𝐮𝐭 42% 𝐨𝐟 𝐬𝐭𝐚𝐫𝐭𝐮𝐩𝐬 𝐅𝐀𝐈𝐋 𝐛𝐞𝐜𝐚𝐮𝐬𝐞 𝐨𝐟 𝐧𝐨𝐭 𝐢𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐧𝐠 𝐦𝐚𝐫𝐤𝐞𝐭 𝐟𝐢𝐭 𝐫𝐞𝐬𝐞𝐚𝐫𝐜𝐡 𝐢𝐧𝐬𝐢𝐠𝐡𝐭𝐬 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞𝐢𝐫 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 𝐝𝐞𝐬𝐢𝐠𝐧 - High Failure Rates: According to CB Insights, one of the top reasons startups fail is a lack of market need for their product. About 42% of startups cited "no market need" for their product as the primary reason for their failure. - Wasteful Spending: Harvard Business Review highlights that many companies waste money developing features that users don’t want. Studies suggest that approximately 35% of features in a typical system are never used, and around 19% are rarely used. 𝐁𝐞𝐧𝐞𝐟𝐢𝐭𝐬 𝐨𝐟 𝐚 𝐅𝐞𝐞𝐝𝐛𝐚𝐜𝐤-𝐎𝐫𝐢𝐞𝐧𝐭𝐞𝐝 𝐀𝐩𝐩𝐫𝐨𝐚𝐜𝐡 - Increased User Satisfaction: Products developed with user input are more likely to meet the actual needs and preferences of the target audience. - Cost Efficiency: Reducing time spent on unwanted features saves money and directs resources towards more impactful developments. - Enhanced Adaptability: A feedback loop facilitates quick pivots and adjustments, which is crucial in the fast-paced market environments. 𝐂𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐞𝐬 - Continuous Commitment: Integrating continuous user feedback requires dedication and can be resource-intensive. - Handling Negative Feedback: Developers must be prepared to receive and constructively use negative feedback, which can sometimes lead to significant changes in the project scope. 🔄 How do you integrate user feedback into your product development process? What lessons have you learned from observing user interaction with your products? #innovation #technology #future #management #startups

The frequency of design reviews and the speed of user feedback are the best indicators of amazing design projects. The process is less critical. It doesn't matter whether your team uses design sprints, loops, or diamonds. The goal is to align the complexity of the user journey with the design process. A design process aligns with stakeholders to create user experiences that drive the business forward. It should match the business's goals with user needs. However, this often fails when the user becomes an abstract concept in the design (it’s hard to manage this messiness). The process alone will not produce the perfect design. The success of a design reflects the team creating it and the audience it serves, considering timelines, feasibility, and project management. All these factors matter. However, after years of running design projects, the two indicators that have a disproportionate impact on design success: • Regular design reviews • Fast user research Why? Consistent design reviews offer opportunities to align: → Stakeholders with shared goals → The team collaborating and sharing ideas → Business goals with clear direction → Technical limits within available tech → Market trends with industry standards → Following laws and regulations Fast user research and feedback provide: → Understanding user needs and behaviors → Regular iteration and improvement   → Ongoing usability testing for better designs This combination keeps everyone on the same page, informed by the latest user data, and able to make quick, informed design decisions. I’ve seen it create more effective and timely design outcomes. Stakeholders are usually happier, too. While upfront user research is important to understand the problem, regular reviews and consistent testing with a targeted audience will quickly reveal gaps. #productdesign #productdiscovery #userresearch #uxresearch

"Twenty years of experience. I don't need data to tell me what works." A senior architect told me this 6 months ago. He has a portfolio full of awards and immense respect in the industry. But awards don't pay for mistakes. After move-in, his client (a tech startup) ran a performance survey because the team was struggling in the new €450k fit-out. The feedback was brutal: → Acoustic Stress: The "open collaborative" layout caused a 23% drop in focus-work productivity. → Glare Issues: His "signature" glass facade triggered a 34% increase in staff headaches. → Stress Markers: The "energizing" color palette actually spiked cortisol levels in the dev team. The Financial Damage: The client calculated a €18k monthly loss in productivity. They pushed back on the final payment, demanding a solution for the performance failures that were now costing them daily. What 20 years of experience didn't teach him: Focus vs. Collaboration:  Engineers need 80% deep-work time.  A "one-size-fits-all" open plan is a financial drain, not a design feature. Environmental Psychology: Color isn't just "vibe."  It's biology.  Overstimulating introverts in analytical roles kills their output. The 'Aesthetic' Trap:  A design that looks good in a magazine but fails the user  is a liability,  not an asset. He ended up spending weeks on retrofitting; work that evidence-based design would have solved for free during the concept stage. The Lesson:  Experience is a foundation,  but data is the insurance. Today, he doesn't just sell "creative vision." He sells Performance Discovery.  His fees reflect the extra research, but his clients pay them because he isn't guessing anymore; he’s guaranteeing a functional asset. Architecture in 2026 isn't about what looks right.  It’s about what is measurably better. Have you ever had a design "instinct" backfire once the users moved in? #Architecture #EvidenceBasedDesign #SpatialDesign #WorkplaceDesign #DesignThinking

💡SQUACK Design Critique Framework It's nearly impossible to design a solid product in a vacuum—you always need feedback from others. Yet, giving and receiving feedback are often the most challenging parts of the design process. Without a clear framework, design review sessions can easily devolve into unproductive noise or, worse, feel like a lynching. SQUACK, proposed by UX coach Julie Jensen (https://lnkd.in/dCA8CTHc), is a structured framework that helps provide constructive and organized design feedback. Each letter represents a specific type of comment: 🟠 S (Suggestion) Personal ideas or preferences that may not be backed by data but offer alternative approaches. 🟠 Q (Question) Points of confusion or requests for clarification (e.g., "Why did you decide to use this component in the first place?"). 🟠 U (User Signal) Feedback grounded in data, user research, or real user behavior. It's objective feedback, not subjective opinions. 🟠 A (Accident) Minor mistakes like typos, alignment issues, or numerical errors can cause friction or misunderstanding. 🟠 C (Critical) Major concerns that present risks (business, usability, technical). These require further attention or redesign. 🟠 K (Kudos) Praise for successful elements or well-executed design choices. This is important for morale and motivation. ✅ Benefits of using SQUACK Design critique session participants can use initials (e.g., S, Q, C) to label their comments and even combine types (e.g., "Q+S") when providing feedback. This helps improve clarity & context and leads to better outcomes: ✔ Helps categorize feedback into distinct categories and separate subjective opinions from facts. ✔ Makes critique sessions more inclusive, especially for quieter participants. ✔ Encourages actionable and balanced feedback (not just what's wrong with design but also what's good about it). 🖼️ SQUACK example by Ya-Ching #UX #uxdesign #productdesign #design

🚀 Designing a Self-Healing Chain of Responsibility – A System That Learns and Adapts “A system that does not evolve will eventually fail — the strongest architecture is not the most complex, but the most adaptable.” Over the past few days, I explored a radical take on the Chain of Responsibility (CoR) pattern — but with a twist. What if your chain could heal itself, rebalance load, and recreate failed components dynamically — without manual intervention? That’s exactly what I built: a Multi-Outcome Feedback-Driven CoR System — capable of self-adjustment through continuous monitoring and autonomous decision-making. Here’s the core architecture I designed: Handlers (M1–M4): Dynamic nodes that simulate independent processing units. LoadBalancer: Tracks real-time handler load across executions. HealthRegister (Board): Maintains system state and cell health metrics. Cache: Acts as an optimization layer to retain only high-health handlers. OutcomeManager: Drives the main execution flow by selecting optimal handlers. FeedbackManager: Observes outcomes and heals or recreates broken handlers using a factory-publisher pattern. 🧩 The result? A fully autonomous pipeline that mimics self-healing microservice architecture — one that rebalances, adapts, and regenerates in runtime. Incorporating this into Java/Spring Boot provided a fascinating perspective on low-level design meeting intelligent feedback loops. The entire code can be found here at my repo folder - https://lnkd.in/gTA7cJ2N 💡 Key Takeaways: Designed a feedback-driven, multi-outcome CoR variant. Implemented self-healing and auto-scaling inspired mechanisms. Aligned closely with SOLID and DDD principles for extensibility. Achieved functional autonomy without external orchestration. This experiment was not just a coding exercise — it was a glimpse into how autonomous systems can evolve through architecture itself. 🔍 Curious Thought: How far can we take self-healing design before architecture starts resembling biological intelligence? Would love to hear how others are exploring autonomous design patterns or self-adjusting system architectures. If you would the post useful star the repo and follow for more such weekly design components. #Java #SoftwareDesign #ChainOfResponsibility #SystemDesign #FeedbackArchitecture #AutonomousSystems #SelfHealing #EngineeringInnovation

In UX, we talk a lot about what users think, but we rarely study how their attitudes actually change over time. Most research still relies on one-time surveys like SUS, NPS, or post-test ratings. These snapshots are useful, but they tell us almost nothing about how trust grows, how frustration accumulates, or how confidence rises and collapses after a single confusing update. Attitudes are not steady states. They are trajectories shaped by experience. There are scientific ways to track those trajectories. Continuous-Time SEM lets researchers measure how satisfaction or trust evolves in real time, even if we collect feedback at irregular moments. A streaming app can trigger a question after each session and see exactly when enjoyment starts to drop, so recommendations can intervene before disengagement sets in. Latent Transition Analysis helps us understand how people move between hidden states such as novice, intermediate, competent, or stuck. Instead of guessing who needs help in onboarding, we can calculate the probability a user will progress or remain frustrated and then redesign tutorials to move them forward. Bayesian Hierarchical Models solve a common UX problem. What if we do not have huge samples like consumer apps do? With twenty or thirty enterprise users, traditional statistics break down, but Bayesian methods still model growth and decline in attitudes. They can reveal that confidence improves for new employees but decreases for experts after a redesign, a pattern that would otherwise remain invisible. Joint Modeling goes further by connecting attitude trends with real outcomes such as churn. It can show that a drop in usability or motivation predicts cancellation two weeks before users actually leave, turning measurement into prevention. One of the most powerful and practical tools is Hidden Markov Modeling. Instead of relying on surveys, it infers emotional states from behavior like hesitation, rage clicks, repeated backtracking, or abandoned tasks. It detects frustration even when people are silent, revealing emotional shifts that traditional surveys fail to capture. If you want to go deeper into these methods and see more concrete examples, I put together a full breakdown on the blog. You can read it here: https://lnkd.in/eY_Nwme2