The Role of Feedback in Product Development

That’s the thing about feedback—you can’t just ask for it once and call it a day. I learned this the hard way. Early on, I’d send out surveys after product launches, thinking I was doing enough. But here’s what happened: responses trickled in, and the insights felt either outdated or too general by the time we acted on them. It hit me: feedback isn’t a one-time event—it’s an ongoing process, and that’s where feedback loops come into play. A feedback loop is a system where you consistently collect, analyze, and act on customer insights. It’s not just about gathering input but creating an ongoing dialogue that shapes your product, service, or messaging architecture in real-time. When done right, feedback loops build emotional resonance with your audience. They show customers you’re not just listening—you’re evolving based on what they need. How can you build effective feedback loops? → Embed feedback opportunities into the customer journey: Don’t wait until the end of a cycle to ask for input. Include feedback points within key moments—like after onboarding, post-purchase, or following customer support interactions. These micro-moments keep the loop alive and relevant. → Leverage multiple channels for input: People share feedback differently. Use a mix of surveys, live chat, community polls, and social media listening to capture diverse perspectives. This enriches your feedback loop with varied insights. → Automate small, actionable nudges: Implement automated follow-ups asking users to rate their experience or suggest improvements. This not only gathers real-time data but also fosters a culture of continuous improvement. But here’s the challenge—feedback loops can easily become overwhelming. When you’re swimming in data, it’s tough to decide what to act on, and there’s always the risk of analysis paralysis. Here’s how you manage it: → Define the building blocks of useful feedback: Prioritize feedback that aligns with your brand’s goals or messaging architecture. Not every suggestion needs action—focus on trends that impact customer experience or growth. → Close the loop publicly: When customers see their input being acted upon, they feel heard. Announce product improvements or service changes driven by customer feedback. It builds trust and strengthens emotional resonance. → Involve your team in the loop: Feedback isn’t just for customer support or marketing—it’s a company-wide asset. Use feedback loops to align cross-functional teams, ensuring insights flow seamlessly between product, marketing, and operations. When feedback becomes a living system, it shifts from being a reactive task to a proactive strategy. It’s not just about gathering opinions—it’s about creating a continuous conversation that shapes your brand in real-time. And as we’ve learned, that’s where real value lies—building something dynamic, adaptive, and truly connected to your audience. #storytelling #marketing #customermarketing

When a founder recently asked me, "What's the secret ingredient for nailing feature updates and iterations?", I didn't hesitate. My answer? User feedback. Always. This question got me thinking about the broader impact of user insights on MVP development. Let me share why I believe this is critical: 👉 A staggering 42% of startups fail due to lack of market need - a fate often avoidable by truly listening to users. 👉 Take Airbnb's early days: user feedback led to a simple photography initiative that doubled bookings almost overnight. 👉 Or consider Instagram's pivot from a check-in app to a photo-sharing platform - a move entirely driven by user behavior analysis. These examples underscore a crucial point: user feedback isn't just a tool, it's the compass that guides product evolution. But here's the catch - implementing feedback effectively is an art. It requires discernment, prioritization, and the courage to challenge our own assumptions. I've delved deeper into this topic in my latest newsletter, exploring strategies for gathering insights, overcoming common pitfalls, and leveraging feedback for sustainable growth. What's your experience with user feedback in product development? Has it ever led you to pivot in unexpected ways? #ProductStrategy #UserExperience #StartupInnovation Let's continue this conversation in the comments. What questions do you have about integrating user feedback into your MVP process?

There is only one type of company that will survive in the future. And no, this has nothing to do with AI. It’s the companies that collect, manage, and act on customer feedback. A few years ago, I was preparing to roll out a new program focused on enablement, education, and engagement. Instead of building it in a vacuum, I interviewed 20 different customers to get their feedback on what I was planning. Not only did this shape the final design, but when I rolled it out, I shared back with the broader customer base how their peers’ voices had directly influenced what we built. That one decision did three things instantly: 1️⃣ Showed we cared. 2️⃣ Illustrated that we listen. 3️⃣ Encouraged even more customers to share in the future. And the program? It became one of our most successful launches. Feedback isn’t just “nice to have.” It’s your survival strategy. Because when customers tell you what’s working and what’s not they’re giving you a free roadmap to: ❗ Fix broken experiences before they become deal breakers. ❗ Double down on what’s driving loyalty and expansion. ❗ Spot emerging needs before your competitors do. But here’s the part most leaders miss: every team in the business can tap into customer feedback and act on it. ✅ Marketing can refine messaging by listening to how customers describe their wins and struggles. ✅ Sales can tailor discovery questions based on feedback about what attracted (or repelled) prospects. ✅ Support sees trends in recurring tickets that point to product or education gaps. ✅ Services hears firsthand how onboarding and implementation shape customer confidence. ✅ Product can prioritize the features that customers say would truly move the needle. ✅ Customer Success uncovers both risks and expansion opportunities through ongoing conversations. ✅ Finance can better forecast retention and growth by understanding feedback-driven health signals. The insights are everywhere. The real power comes when companies can connect the dots across all teams and turn feedback into coordinated action. And this is where I see the biggest roadblock: Companies struggle to manage feedback across the business in a meaningful way. It’s siloed, scattered, and often disconnected from strategy. So let me ask: Is this a challenge you’re seeing in your organization too?

If you say you care about user feedback… but you don’t act on user feedback… you don’t care about user feedback. You just care about collecting data. CEO’s have a vision for their company, which is important. But that vision can become a roadblock when it prevents the company from adapting to meet the needs of users. Feedback from users needs to be the force that guides strategy if the company wants to stay relevant. Here’s a real-world example: I’m working with a company focused on a specific population. They care so much about understanding their user, they’ve partnered with a large nonprofit that’s helping us refine the product for them. We didn’t just whip up a survey and call it good. Before we go national with the survey, we’re interviewing individuals from this population to test it out. We’re asking follow-up questions and digging into their feedback. We’re using science to refine our tools so that when the survey is distributed, the data we collect will be meaningful and actionable. Compare that to what I see too often, which is companies making minor tweaks that don’t go deep enough or skipping the feedback altogether. If you just guess instead of truly understanding, you end up with a product that doesn’t meet user needs. This user feedback process takes time and resources, but the payoff is a product that is built with users, not just for them. It’s an ongoing cycle—listen, learn, adapt, and grow. That’s how you stay competitive. #userfeedback #sciencestrategy #fractionalcso

User feedback is not a product roadmap. Let that sink in for a moment. In today's world, that statement might sound like sacrilege. We live and breathe user-centricity. Our sprints revolve around user interviews. We A/B test relentlessly. "Listen to your users" is the first commandment of product development. And yet... The best product leaders understand intuitively when they should look in the other direction. Don't get me wrong — user feedback is invaluable. It highlights pain points, reveals critical behavioral patterns, and keeps us honest with ourselves. But treating it as the sole guide for product decisions is a recipe for missed opportunities. Here's why: 1. Users don't always know what's possible. They're constrained by their current experiences and mental models. 2. Feedback often focuses on surface-level issues, not underlying needs. You might hear complaints about a specific feature when the real problem is a fundamentally flawed workflow. . 3. The loudest voices aren't always representative. Power users and vocal minorities can drown out the silent majority. 4. Short-term satisfaction doesn't always align with long-term value. Sometimes, the right decision might initially frustrate users but lead to better outcomes over time. So, when should you consider ignoring user feedback? ↳ When you have deep insights into emerging tech or market trends that they might not be aware of ↳ When user requests conflict with your core product vision or long-term strategy ↳ When you identify a bigger opportunity by solving an adjacent problem — The key is to balance listening to users with trusting your vision. It's about synthesizing feedback, market insights, technological trends, and your unique perspective to chart a course that might not be obvious to users themselves. This isn't easy. It requires confidence, a deep understanding of your users and market, and the ability to communicate your rationale clearly to both your team and your customers. But the payoff can be enormous. Some of the most impactful products and features in tech history came from leaders who knew when to listen to users — and when to respectfully disagree in pursuit of something fundamentally better. So the next time you're reviewing user feedback, remember: Your job isn't just to give users what they ask for. It's to deliver what they need, even if they don't know how to ask for it yet. That's not ignoring your users. That's truly serving them. #UX #userfeedback #userinterviews #innovation

One of the most common misconceptions in early-stage startups is that if you build something technically extraordinary with a talented team, success will naturally follow. The reality is far more nuanced. Yes, building a complex product under tight resource constraints is challenging. The trade-offs alone can feel insurmountable. But the most critical—and often overlooked—challenge at this stage is constructing a feedback loop while the product is being developed. For engineers-turned-founders, this is especially dangerous. The instinct to focus solely on technical execution, what I call “engineering in the closet,” can doom even the most innovative startups. Without input from potential users or customers, you risk building a product that solves a problem no one has—or in a way no one values. The truth: 👉 Building doesn’t truly begin until the feedback loop is in place. 👉 Early validation ensures you’re creating the right solution, not just a technically impressive one. 👉 Regular feedback forces you to align your product with real-world needs—long before it’s too late. A practical approach: Create a simple demo to gather feedback early. This doesn’t require a fully functioning product—mocked or simulated backends are perfectly fine. A demo not only highlights your value proposition and product experience but also compels you to practice articulating its benefits. These early iterations are invaluable. They help you refine your direction, strengthen your messaging, and ensure that your efforts are aligned with real demand. Founder-led sales are critical through the seed stage, and this process builds the muscle of selling early and often. By the time the product is ready for market, founders will already have a head start, both in refining the pitch and in building relationships that can drive adoption. #Startups #EngineeringLeadership #ProductDevelopment #FounderInsights

𝗜𝗳 𝘆𝗼𝘂’𝗿𝗲 𝗻𝗼𝘁 𝘁𝗮𝗹𝗸𝗶𝗻𝗴 𝘁𝗼 𝘆𝗼𝘂𝗿 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀, 𝘆𝗼𝘂’𝗿𝗲 𝗷𝘂𝘀𝘁 𝗴𝘂𝗲𝘀𝘀𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗮 𝗯𝘂𝗱𝗴𝗲𝘁. 𝗦𝗧𝗢𝗣 Assuming. 𝗦𝗧𝗔𝗥𝗧 Listening. Customer surveys, paid panels, and focus groups aren’t just checkboxes. They’re your reality check. Real user feedback is the heartbeat of 𝗴𝗿𝗲𝗮𝘁 product strategy. It’s what separates teams that build for themselves from those that build for their customers. Every interview, every piece of data, positive or negative, is a chance to test your hypothesis. To validate what’s true, fix what’s broken, and double down on what actually drives value. You can’t shortcut this.  You can’t guess your way into customer loyalty. 𝗦𝗧𝗢𝗣 𝘢𝘴𝘴𝘶𝘮𝘪𝘯𝘨 𝘺𝘰𝘶 𝘬𝘯𝘰𝘸 𝘸𝘩𝘢𝘵 𝘤𝘶𝘴𝘵𝘰𝘮𝘦𝘳𝘴 𝘸𝘢𝘯𝘵. 𝗦𝗧𝗔𝗥𝗧 𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘢𝘯𝘥𝘪𝘯𝘨 𝘵𝘩𝘦 𝘳𝘦𝘢𝘭 𝘥𝘢𝘵𝘢, 𝘯𝘰𝘵 𝘷𝘢𝘯𝘪𝘵𝘺 𝘮𝘦𝘵𝘳𝘪𝘤𝘴 𝘰𝘳 𝘪𝘯𝘵𝘦𝘳𝘯𝘢𝘭 𝘣𝘪𝘢𝘴.  • Set value-based KPIs that measure impact, not activity  • Build, test, learn, and repeat, continuously  • Document your process and close your feedback loops  • Let customer sentiment shape smarter decisions, not reactive ones 𝗧𝗵𝗶𝘀 𝗶𝘀 𝘄𝗵𝘆 𝗱𝗮𝘁𝗮 𝗺𝗮𝘁𝘁𝗲𝗿𝘀. 𝗧𝗵𝗶𝘀 𝗶𝘀 𝘄𝗵𝘆 𝗹𝗶𝘀𝘁𝗲𝗻𝗶𝗻𝗴 𝗺𝗮𝘁𝘁𝗲𝗿𝘀. When your process works and you actually validate your ideas, you don’t just get happy customers. You earn repeat ones. And please, stop nickel-and-diming customers for every new feature. It’s grimy, short-sighted, and kills trust faster than any bug ever could. The best products aren’t built in meetings. They’re built through conversations. What’s one customer insight that completely changed how you built your product? #ProductLeadership #CustomerExperience #DataDrivenProduct #VoiceOfCustomer

Duolingo didn’t always have Product Review, but it’s one of the best processes we’ve implemented. Here’s why: When we were a small company (maybe 25 employees) the process for getting something in the product was pretty informal: walk up to Luis von Ahn or Tyler Murphy (our head designer), sit with them at their desks, show them the design, get approved. This was okay, until we noticed something: the designers who sat closest to Tyler, and the PMs who sat closest to Luis, were developing much faster than their peers. They got more feedback more often, and so could learn and iterate much faster than others. We also noticed that our engineers, who rarely interfaced with Tyler and Luis, were developing much more quickly across the board. Why was this? Engineers always reviewed each other’s code before going into production. They were constantly learning from each other thanks to a defined and consistent process. Product Review was a game-changer for talent development and product quality, because it created a process for documenting and reviewing changes. People weren’t just showing a spec at a desk—they were using a template to explain the change and the impact. And we had a system for evaluating those changes—the stakeholders were aligned and discussion happened in one meeting rather than at a desk/via Slack/in the hallway/in a fishtank… etc. Because we shared notes after PRs, PMs and designers started to improve much faster, because they got consistent feedback and could learn from each other’s reviews. Start-ups are often scared of process—they think it adds bureaucracy and slows things down. But in some cases, a good process is essential to growing the people and the product. We wouldn’t be where we are today without it. The team has iterated a lot on Product Review since our early days (I rarely join a PR anymore) but here’s the initial template I shared for PMs/designers to fill out back in 2015:

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.

We just issued our 3rd course refund in 7 years. The feedback, “I couldn’t find anything actionable in the first 25% of the course materials.” Most student feedback tells us the exact opposite. It’s a common product management challenge. There are always conflicting signals in customer feedback. A product manager’s job is to manage the ambiguity and implement improvements that prevent this from happening again. No matter what kind of product you’re building, outlier feedback could be the leading indicator of a much larger problem. Anyone who shares feedback is giving you gold. Use it to improve. In our case, the problem is either the course content or the marketing. If our marketing is connecting with the wrong customer segments, that will lead to the wrong people taking my courses. If the content isn’t actionable for every segment that can get value from the course, we need to fix that. That means reevaluating each video and ensuring the actionable components are clearly stated. What we’ve learned from several course reviewers is that “actionable” often means more granularity, templates, and more specific action plans. With a self-paced course on strategy, that’s difficult to deliver. Every company is different, and the strategy must adapt to fit. That means customizing and flexing the frameworks, often implementing frameworks partially on the road to doing things the right way. In a self-paced course, I can only deliver the why and how. In the instructor-led version, I can get context from students to explain the what and when. There’s a gap, and it’s obviously not called out. We’re not clarifying the differences between the self-paced and instructor-led courses or explaining the limitations in the free introduction to the self-paced course. We’ll be fixing that in the coming days. I’m also evaluating how to deliver more of the what and when in the self-paced course. What templates and action plans can I provide? How do I explain when the templates work without modification and when they must be modified? I built the office hours to manage complex questions from the self-paced courses, but not everyone can attend or ask their questions in a public forum. It’s time to reevaluate that solution as well. Contradictory feedback shouldn’t cause dramatic product changes, but small updates and improvements can generate significant value. Ignoring outlier feedback misses the opportunity to deliver it.