Feedback Prioritization Methods

How do you and your teams synthesise and select which customer needs or pains to progress in your #product, #design, or #innovation projects? Imagine you've just completed some great customer discovery research, including observing, interviewing and being the customer. You've built some good empathy for who your customers are, what is important to them, what pains them, and what delights them. Then you unpack your findings into some form of empathy map, and you've got 100s of sticky notes everywhere. You've then started to narrow them down to the most promising and interesting observations, but this still leaves you with a sizeable collection and you want to add some rigour to your intuition on which ones to take forward first. Well, here are 3 different methods that I’ve used and iterated over the years: Number One – The Opportunity Scale This first one is the simplest and is inspired by how Alexander Osterwalder et al rank jobs, pains and gains in their book Value Proposition Design, 2014. As a team, you take your short list of observations from your empathy map and rank them from how insignificant/moderate to how important/extreme the need/pain is for the customer with the most important/extreme being prioritised to explore further first. Number two – The Opportunity Matrix A The opportunity matrix increases the rigour and confidence of your prioritizing by adding ‘strength of evidence’ as another dimension. Strength of evidence at this stage of journey can be determined by the number and type of data points. For example, if you heard from several customers that a pain point was extremely painful then you could be more confident this was worth solving than one highlighted by only one customer. Likewise, observing customers do something provides stronger evidence than customers saying they do something. Here you prioritise the most important needs with the strongest evidence first. Something to watch out for is when your team selects an observation that has strong evidence but isn’t that important of a need or pain to customers. Teams can be blinkered by numbers and end up over-investing in time wasting-opportunities. Number three – The Opportunity Matrix B The third method swaps out evidence for fulfilment of the need - how satisfied are customers with their ability to fulfil the need/solve the pain with the solutions they use today? By matching this with the importance of the need/pain we can select those observations that we understand to be the most important and unmet for our customers. You can then overlay the strength of evidence across this ranking to make your final selection even more robust. And to take it to a whole new level and really de-risk your selection you can test your prioritised observations, written as need statements, in quantitative research with customers. This is something that Antony Ulwick shares in his book Jobs To Be Done, 2016. I hope you find these methods useful. #designthinking #humancentreddesign

Most teams guess what to build. We talk to 100s of prospects a month and let them tell us exactly what’s broken. In the early days of Salesforge, we knew one thing: The company that talks to the most customers the fastest… wins. That’s why we book 10–20 meetings a day not just to sell, but to learn faster than anyone else in our category. Every single day, we hear what prospects hate, where their current stack fails, what gets them excited, and what they wish existed. That learning compiles. It compounds. And over time, it becomes your strategic edge. Here are 4 lessons we’ve learned by doing this at volume and how it’s shaped how we build: 1. Feedback isn’t optional Most teams try to prioritize based on opinions, roadmaps, or investor pressure. We don’t. We let volume of feedback decide what gets built and what doesn’t. When you’re on 100+ calls a week, patterns become undeniable. If 6 out of 10 people mention the same workflow friction — we tag it, push it to product, and ship fast. Sometimes within a week. Without this level of signal clarity, you risk overbuilding, building in the wrong direction, or even worse — building something nobody wants. Velocity of feedback → velocity of learning → velocity of execution. 2. The best ideas don’t live on a whiteboard We’ve never treated the roadmap as a fixed blueprint. It’s a living document that adapts with every conversation. Some of our biggest wins started out as throwaway questions from prospects: “Can you guys do this?” “What if your agent could also handle that?” When you hear something like that three, four, five times in a single week, it’s no longer a fluke. It’s a market pull. We’ve built entire products like Warmforge and Leadsforge based on patterns that showed up first in conversations. Too many teams fall in love with their own ideas. We fall in love with patterns. 3. Repetition forces clarity or it exposes fluff If you’ve ever delivered the same pitch 50+ times in a week, you know one thing: you can’t fake it. If your messaging isn’t sharp, people will tune out. That’s the beauty of repetition. It either breaks your narrative or forces you to tighten it. Every meeting becomes a stress test for your story. 4. Geography matters more than you think One of the most underappreciated lessons we’ve learned from talking to prospects globally is just how different buyer behavior is by region. → Southeast Asia and LATAM? WhatsApp. → US? Email + cold call + LinkedIn → Europe? Email + cold call + LinkedIn + Whatsapp Without the conversations, we’d be shipping the wrong thing into the wrong market. TAKEAWAY Most teams optimize for pipeline. We optimize for learning velocity. That’s how you ship products people want. That’s how you write copy that converts. That’s how you build an agent that actually works in the wild. And the only way to do it? Listen harder. Track everything. Move fast. It’s messy. It’s unscalable. And it’s the reason we’re winning.

Most product managers prioritize features the wrong way. AI can fix that. Here are 3 powerful AI prompts to revolutionize your workflow. Here are 3 AI prompts that will change how you rank features based on user needs and business impact: 1️⃣ Comprehensive Feature Analysis: A deep dive into each feature's potential impact and alignment with goals. 💡 Prompt: "Analyze the following features: {feature_list}. For each feature, provide a detailed assessment of its potential impact on user satisfaction, retention, and revenue growth. Consider our current user base demographics, market trends, and competitive landscape. Prioritize these features based on their alignment with our Q4 goal of improving user retention by 15%. Finally, rank the features in order of priority and explain the rationale behind this ranking." 2️⃣ User Feedback Synthesizer: AI powered analysis of user pain points and feature requests. 💡 Prompt: "Aggregate and analyze customer feedback from the following sources: {feedback_sources} (e.g., app store reviews, customer support tickets, user interviews, NPS surveys). Identify the top 5 recurring themes or pain points mentioned by users. For each theme, provide specific examples of user quotes or data points. Rank these themes based on frequency of mention and severity of impact on user experience. Then, map each theme to potential feature improvements or new feature ideas. Prioritize these feature ideas based on their potential to address user pain points, estimated development effort, and alignment with our product strategy. Share a detailed rationale for your prioritization, including any potential risks or trade-offs to consider." 3️⃣ Development Effort Estimator: A comprehensive analysis of resource requirements. 💡 Prompt: "Estimate the development effort for implementing {feature_name} in our {product_type}, considering our team of 10 engineers and 8-week timeline. Break down the implementation into key components or stages (e.g., design, frontend development, backend development, testing, deployment). For each component, estimate the number of engineer-days required, potential technical challenges, and any dependencies on other systems or third-party integrations. Consider our team's expertise and any learning curve associated with new technologies. Identify any potential bottlenecks or risks that could impact the timeline. Suggest strategies to mitigate these risks, such as parallel development tracks or phased rollout approaches. Provide a confidence level (low, medium, high) for each estimate and explain the reasoning. Finally, give a range estimate for the total development time (best case, expected case, worst case) and suggest any features or scope that could be adjusted to fit within the 8-week timeline if necessary." Product Managers, these AI prompts are designed to enhance your decision making, not replace it. Use them to gain data-driven insights, then apply your expertise to make the final call.

One of the most critical contributions of a Business Analyst in any project is ensuring that the right features are delivered at the right time—balancing business value, technical feasibility, and user expectations. 👉 Enter the MoSCoW Prioritization Technique — a tried-and-true method I’ve used recently while working with Product Owners, Marketing, Customer Support, and Tech teams for a freelancing project. 🔍 𝐂𝐚𝐬𝐞: Enhancing the Checkout Experience of an eCommerce Platform The goal? Boost conversions, reduce cart abandonment, and improve user experience. Here’s how we applied MoSCoW to prioritize requirements during the workshop: ✅ 𝐌𝐔𝐒𝐓-𝐇𝐀𝐕𝐄 (𝐂𝐫𝐢𝐭𝐢𝐜𝐚𝐥 𝐟𝐨𝐫 𝐥𝐚𝐮𝐧𝐜𝐡): ➡️ Implement Guest Checkout to avoid forcing account creation. ➡️ Add Multiple Payment Options (Credit Card, UPI, PayPal) for inclusivity. ➡️ Ensure Order Summary with Real-time Price Updates. 📌 These were non-negotiable. Without them, the release would fail user expectations and business KPIs. ✅ 𝐒𝐇𝐎𝐔𝐋𝐃-𝐇𝐀𝐕𝐄 (𝐈𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐭, 𝐛𝐮𝐭 𝐧𝐨𝐭 𝐯𝐢𝐭𝐚𝐥 𝐚𝐭 𝐥𝐚𝐮𝐧𝐜𝐡): ➡️ Auto-apply Coupons during checkout. ➡️ Add Progress Bar to visually indicate checkout steps. ➡️ Provide Delivery Date Estimator based on pincode. 📌 These enhance user experience but can wait until Phase 2. ✅ 𝐂𝐎𝐔𝐋𝐃-𝐇𝐀𝐕𝐄 (𝐍𝐢𝐜𝐞-𝐭𝐨-𝐡𝐚𝐯𝐞, 𝐨𝐧𝐥𝐲 𝐢𝐟 𝐭𝐢𝐦𝐞/𝐫𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 𝐩𝐞𝐫𝐦𝐢𝐭): ➡️ Add Gift Wrapping Option. ➡️ Enable One-click Repeat Orders. ➡️ Allow Delivery Instructions for Courier. 📌 These create differentiation but don’t impact core functionality. ✅ 𝐖𝐎𝐍’𝐓-𝐇𝐀𝐕𝐄 (𝐎𝐮𝐭 𝐨𝐟 𝐬𝐜𝐨𝐩𝐞 𝐟𝐨𝐫 𝐭𝐡𝐢𝐬 𝐫𝐞𝐥𝐞𝐚𝐬𝐞): ➡️ Integration with Crypto Payment Gateway. ➡️ Launching a Voice-Activated Checkout experience. 📌 Innovative ideas, but postponed based on current ROI and technical constraints. 💬 𝐀𝐬 𝐚 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐀𝐧𝐚𝐥𝐲𝐬𝐭, 𝐦𝐲 𝐫𝐨𝐥𝐞 𝐰𝐚𝐬 𝐭𝐨: 👉 Facilitate the MoSCoW session with cross-functional stakeholders. 👉 Capture business value vs. effort trade-offs. 👉 Document the priorities in JIRA for sprint planning. 👉 Ensure Product Owner and Tech Leads were aligned on scope. 🎯 The result? Clear alignment, reduced scope creep, and focused development sprints. 💡 𝐓𝐢𝐩 𝐟𝐨𝐫 𝐅𝐞𝐥𝐥𝐨𝐰 𝐁𝐀𝐬: MoSCoW isn’t just a matrix—it’s a conversation starter to uncover what truly matters for both users and the business. BA Helpline

Unclear and conflicting priorities can disrupt your timeline and cause product delays. If you want to do everything at once, you won’t be able to do anything. Instead, focus on the most critical items and add everything else in the backlog to consider later. There are many prioritization frameworks available to help you. Pick one of the frameworks, define your criteria, and score and rank all the items. Let’s dive in, 1. MoSCoW Method The MoSCoW method helps you categorize tasks into Must Have, Should Have, Could Have, and Won’t Have. This framework is crucial because it ensures you focus on the most critical features first. To use this method, list all your tasks and classify them into these four categories to prioritize essential features and address less critical ones later. 2. RICE Scoring Model The RICE model evaluates tasks based on Reach, Impact, Confidence, and Effort. (Reach * Impact * Confidence) / Effort = RICE Score List all the features and assign scores to each criterion, then calculate the RICE score to rank them. This method is effective because it quantifies the potential value (impact) and effort required for each feature. 3. Kano Model The Kano model differentiates between basic features, performance features, and delighters. Researcher Noraki Kano developed it to help product managers prioritize features and updates based on customer needs. This framework is important because it helps you understand what features will meet basic user needs and which ones will exceed expectations. 4. Value vs. Effort Matrix The Value vs. Effort Matrix helps you plot features on a 2x2 grid based on their value and the effort required. This visualization makes it easy to identify high-value, low-effort items. Plot each feature on the matrix and focus on those in the high-value, low-effort quadrant. This ensures that you’re investing your resources in the most efficient way possible. 5. Weighted Scoring Weighted Scoring involves assigning weights to different criteria based on their importance and scoring each feature accordingly. Define your criteria, assign weights, and score each feature to prioritize those that score the highest. 6. Cost of Delay The cost of Delay evaluates the economic impact of delaying each feature. This approach helps you prioritize features that, if delayed, would result in significant financial loss. Calculate the cost of delay for each feature and prioritize those with the highest cost to minimize financial impact. 7. Opportunity Scoring Opportunity Scoring focuses on identifying opportunities based on customer needs and the difficulty of meeting those needs. By following these frameworks, you’ll be well on your way to effective prioritization in product development. Work on the highest priority items and avoid spending efforts on less important work. This will help you stay focused, avoid unnecessary work, and ensure timely product launches.

As Product Managers it’s so easy to loose trust if features on the roadmap are not prioritised correctly. Here are 5 prioritization frameworks and when to actually use them: 1. RICE (Reach, Impact, Confidence, Effort) ✅ Use when: You have multiple ideas/features and want to prioritize based on expected impact. 📌 Best for: Growth experiments, new features, MVP ideas 💡Tip: Confidence % is often biased calibrate with data! 2. MoSCoW (Must have, Should have, Could have, Won’t have) ✅ Use when: You’re working with tight deadlines and multiple stakeholders. 📌 Best for: Sprint planning, product launches 💡Tip: Don’t let every stakeholder label everything as “Must have.” 3. Kano Model ✅ Use when: You want to balance delight with functionality. 📌 Best for: Customer-facing products 💡Tip: A feature that delights today might be expected tomorrow. 4. ICE (Impact, Confidence, Ease) ✅ Use when: You want a quicker version of RICE for fast decision-making. 📌 Best for: Rapid prototyping, early-stage prioritization 💡Tip: Use ICE when you don’t have a ton of data but still need to move. 5. Value vs. Effort Matrix ✅ Use when: You want to visualize trade-offs with stakeholders. 📌 Best for: Roadmap discussions, stakeholder alignment 💡Tip: Plot features on a 2×2: * Quick Wins (High value, low effort) * Strategic Bets (High value, high effort) * Time Wasters (Low value, high effort) * Fillers (Low value, low effort) So which one should you pick? Use RICE when you’re in a data-driven company. Use MoSCoW when time is tight and alignment is tough. Use ICE when you need speed > accuracy. Use Kano when delight matters. Use the Value/Effort Matrix when people keep asking, “Why this first?” 📌 Save this for your next prioritization war. 💬 Tried any of these at work? Drop your go-to framework in comments! #productmanager #job #PMjobs #learning #frameworks

🪢 The MoSCoW Method: Prioritization with Purpose (Not Panic) Ever felt like your backlog is a never-ending buffet—and your team’s trying to eat everything at once? Welcome to the chaos of poor prioritization. But don’t worry—there’s a secret sauce that separates the chaotic teams from the confident ones. 👉 It’s called the MoSCoW Framework. Let’s break it down, without the corporate jargon overdose. _______________________________________ 💡 What is the MoSCoW Method? It’s not about Russia (sorry, geography fans). MoSCoW is a prioritization technique that helps you decide what truly matters in your projects—especially when time, budget, or sanity is tight. MoSCoW = ✅ Must Have ✅ Should Have ✅ Could Have ❌ Won’t Have (this time) ___________________________________ 📌 Why It Works Like a Charm Let’s be real: Not all features are equal. Not all stakeholder asks are sacred. And not everything can ship in the same sprint. The MoSCoW method forces clarity. It kills feature creep. And it brings focus back to value. ______________________________________ 🔆 The Four Buckets of Brilliance 1️⃣ Must Have 🚨 Non-negotiable. If these don’t make it, your product breaks or fails. Think: security login, checkout system, core workflows. Without these? Game over. 2️⃣ Should Have 🔥 Important, but not vital for launch. Think: error messages, mobile responsiveness, dark mode (maybe). You want them. Users want them. But the ship still sails without them. 3️⃣ Could Have ✨ Nice-to-haves. Think: animations, visual polish, integrations that look good in a demo. They delight—but don’t define—your product. 4️⃣ Won’t Have (this time) 🚫 Just say no. This doesn’t mean never, just not now. You’re buying focus by parking distractions. ___________________________________________ 💡 How to Use MoSCoW Like a Pro ✔️ Do it collaboratively—include stakeholders, devs, and end users. ✔️ Tie items back to business value and customer impact. ✔️ Revisit regularly—priorities shift, and so should your MoSCoW. ______________________________________________________ 🛠️ Real Talk for Scrum Masters & Product Owners Stop treating every item as a top priority. Use MoSCoW to run better refinement sessions. Apply it during PI Planning and Sprint Planning to manage scope creep like a boss. It’s a game-changer when balancing tech debt vs new features. ________________________________________________ 🔁 TL;DR: MoSCoW = Prioritize with Power You can't do it all—and you shouldn't. Use MoSCoW to deliver the right things, not everything. Because success isn't about doing more. It's about doing what matters. _____________________________________________ 🫵 Over to You: How do you prioritize under pressure? Tried MoSCoW before? Share your wins (or war stories) 👇 And hey—follow me Kamal for more Agile tips that actually work in the real world. #Agile #ScrumMaster #ProductManagement #MoSCoWMethod #Prioritization #AgileCoaching #SprintPlanning #ProjectManagement #LeadershipInTech

“Startups don't starve. They drown...” They drown in too much information, too much analysis, too much conflicting feedback, too much "important" work. Where do you start? Even mantras like "right action, right time," I espouse, run up against practical ground realities. Most people simply guess or vibe their way, but here’s the expensive reality: When you don’t have a systematic way to prioritize and pick what feels most urgent or what the loudest customer complained about, you end up burning time, cash, and momentum. In this week's YouTube video, I outline a 4-step prioritization framework I use for picking where to focus. It combines a popular product priorization framework, RICE, with Fermi Estimations. RICE stands for: • Reach: How many customers will this impact? • Impact: What's the value per customer? • Confidence: How certain are we? • Effort: What's the cost to build? The formula: (Reach × Impact × Confidence) ÷ Effort But here's the problem most people face: How do you score objectively without fooling yourself? Should onboarding be a 7 or an 8? Is that feature worth $5,000 or $7,500? This is where Fermi estimation comes in... Instead of false precision, I use order-of-magnitude scales: • Reach: 1, 10, 100, 1,000, 10,000, 100,000 • Impact: $100, $1K, $10K, $100K • Confidence: 20%, 50%, 80% • Effort: 2 hours, 2 days, 2 weeks, 2 months You go from fudging numbers to justify the thing you want to build to prioritizing the right work. More in the full video...

I talked with 100+ product over the last months They all had the same set of problems Here's the solution (5 steps) Every product leader told me at least one of the following: "Our feedback is all over the place" "PMs have no single source of truth for feedback" "We'd like to back our prioritization with customer feedback" Here's a step-by-step guide to fix this 1/ Where is your most qualitative feedback coming from? What sources do you need to consolidate? - Make an exhaustive list of your feedback sources - Rank them by quality & importance - Find a way to access that data (API, Zapier, Make, scraping, csv exports, ...) 2/ Route all that feedback to a "database-like" tool, a table of records Multiple options here: Airtable, Notion, Google sheets and of course Cycle App -Tag feedback with their related properties: source, product area customer id or email, etc - Match customer properties to the feedback based on customer unique id or email 3/ Calibrate an AI model Teach the AI the following: - What do you want to extract from your raw feedback? - What type of feedback is the AI looking at and how should it process it? (an NPS survey should be treated differently than a user interview) - What features can be mapped to the relevant quotes inside the raw feedback Typically, this won't work out of the box. You need to give your model enough human-verified examples (calibrate it), so it can actually become accurate in finding the right features/discoveries to map. This part is tricky, but without this you'll never be able to process large volumes of feedback and unstructured data. 4/ Plug a BI tool like Google data studio or other on your feedback database - Start by listing your business questions and build charts answering them - Include customer attributes as filters in the dashboard so you can filter on specific customer segments. Every feedback is not equal. - Make sure these dashboards are shared/accessible to the entire product team 5/ Plug your product delivery on top of this At this point, you have a big database full of customer insights and a customer voice dashboard. But it's not actionable. - You want to convert discoveries into actual Jira epics or Linear projects & issues. - You need to have some notion of "status" sync, otherwise your feedback database won't clean itself and you won't be able to close feedback loops The diagram below gives you a clear overview of how to build your own system. Build or buy? Your choice