Prioritization Frameworks for Teams

Backlog Jenga: Everyone Loses (Try Now-Next-Soon-Later-Never Instead) Many Agile teams struggle with prioritization. Backlogs bloat, scoring models get complex, and work gets lost. The Now-Next-Soon-Later-Never (NNSLN) framework simplifies prioritization by organizing work into five time-based buckets aligned with team capacity. It keeps backlogs actionable instead of overloaded. Prioritization Buckets 1) NOW - Work in Progress Highest priority items actively worked on or about to start (e.g., sprint commitments, urgent fixes, critical dependencies). Capacity Allocation: ≈ 100% of velocity (or throughput), keeping focus on the current sprint. 2) NEXT - Immediately Actionable Well-defined, top-priority backlog items expected to start next. No blockers, fully refined. Capacity Allocation: 100-200% of velocity, making short-term work manageable. 3) SOON - Awaiting Refinement Important but needs refinement, dependencies cleared, or alignment. Provides mid-term visibility without overloading the backlog. Capacity Allocation: 300-500% of velocity, preventing mid-term overload. 4) LATER - Future Considerations Low-priority ideas that might be valuable but aren’t urgent. Reviewed periodically to check relevance. Capacity Allocation: 5-10x velocity, maintaining long-term visibility. 5) NEVER - Out of Scope / Deprioritized Misaligned, outdated, or indefinitely deprioritized work. Not expected to be worked on. Capacity Allocation: Unbounded, but should be reviewed regularly to remove irrelevant work. Why This Model Works This model actively manages work rather than hoarding it, preventing backlog bloat and keeping priorities realistic. By focusing on actionable work, it encourages flow-based prioritization instead of letting tasks pile up. It also limits backlog expansion, so teams don’t get lost in overplanning. Whether you're working at the team level, across an ART, or managing a portfolio, the approach scales easily, keeping workflows aligned and efficient. Implementation by Framework Kanban: Use Now, Next, Soon, and Later swimlanes like classes of service, and set WIP limits to keep backlogs lean. Scrum: Organize the Backlog into these categories for structured Sprint Planning. Keep Next limited to refined work that can be pulled into upcoming sprints. SAFe & LPM: Classify Features, Enablers, and Epics to improve strategic alignment. Cap work in Next and Soon to prevent portfolio overload. Balancing Priorities with Capacity Allocation Most teams overload their backlogs with more work than they can complete. This framework ties prioritization directly to throughput, keeping backlog growth controlled. This simple structure prioritizes what truly matters while preventing unnecessary work expansion. Workflow Clarity, Focus, And Efficiency Prioritization methods fail when they’re too rigid or vague. The NNSLN framework strikes a balance between structure and flexibility, helping teams stay focused and avoiding backlog bloat.

How I Prioritize as a Program Manager at Amazon One of the toughest parts of being a program manager is deciding what gets attention when everything feels important. At Amazon, where the pace is fast and the stakes are high, I’ve learned that effective prioritization isn’t just a skill—it’s a necessity. Here are three approaches that help me stay focused and move the needle: 1️⃣ Impact vs. Effort Matrix When juggling multiple projects, I map tasks based on how much impact they’ll have versus how much effort they’ll take. High-impact, low-effort items? Those are no-brainers. Low-impact, high-effort tasks? They often end up on the backlog or get re-evaluated. This simple framework keeps me and my teams working smarter. 2️⃣ Customer Obsession At Amazon, the customer always comes first. Before prioritizing, I ask myself: How will this improve the customer experience? If an idea doesn’t bring clear value to the customer, it’s either deprioritized or reconsidered. It’s a principle that keeps us grounded in what really matters. 3️⃣ Time for Big-Picture Thinking Amid the daily fire drills, it’s easy to let long-term planning slip. I’ve started blocking time on my calendar specifically for strategic thinking. This helps me step back, focus on the bigger picture, and ensure we’re not just putting out fires but also building for the future. Prioritization is messy, and it’s not always perfect. But these methods have helped me find clarity in the chaos and deliver meaningful results. How do you decide what deserves your attention when everything feels important? #Leadership #Prioritization #CustomerObsessed #ProgramManagement

𝗠𝗼𝘀𝘁 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝘀 𝗳𝗮𝗶𝗹 𝗳𝗿𝗼𝗺 𝗱𝗼𝗶𝗻𝗴 𝘁𝗼𝗼 𝗺𝘂𝗰𝗵, 𝗻𝗼𝘁 𝘁𝗼𝗼 𝗹𝗶𝘁𝘁𝗹𝗲. The difference between good PMs and the great ones lies in their ability to say "no" with conviction.  Prioritization isn’t about task management, it’s about strategic sacrifice. The frameworks you use determine whether you:   - Multiply impact (or spread teams thin)   - Build what moves the needle (or what’s loudest)   - Create category-defining products (or bloated ones)  𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 𝘁𝗵𝗲 7 𝗺𝗼𝘀𝘁 𝗽𝗼𝘄𝗲𝗿𝗳𝘂𝗹 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸𝘀 𝗱𝗲𝗰𝗼𝗱𝗲𝗱:  1️⃣ RICE – When you need to quantify "gut feel" (Score Reach, Impact, Confidence, Effort)   2️⃣ MoSCoW – For ruthless trade-offs (Must-have, Should-have, Could-have, Won’t-have)   3️⃣ Kano Model – To separate "delighters" from "basics" (Before competitors copy them)   4️⃣ Opportunity Scoring – When user pain points > feature ideas   5️⃣ Weighted Scoring – For stakeholder battles (Math beats opinions)   6️⃣ User Story Mapping – To prioritize features based on the user journey   7️⃣ Value vs Effort Matrix – The 2x2 that kills pet projects  Swipe for the breakdown on each framework! Your turn: Which framework has saved you from a disaster? (Or which one needs a funeral?) 👇  

📊 𝗧𝗵𝗲 𝗕𝗲𝘀𝘁 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸𝘀 & 𝗪𝗵𝗲𝗻 𝘁𝗼 𝗨𝘀𝗲 𝗧𝗵𝗲𝗺 One of the biggest challenges in 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 is deciding 𝘄𝗵𝗮𝘁 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝗻𝗲𝘅𝘁. With countless ideas, competing priorities, and limited resources, having a structured 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 can make all the difference. Here are some of the 𝗺𝗼𝘀𝘁 𝗽𝗼𝗽𝘂𝗹𝗮𝗿 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸𝘀, when to use them, and their 𝗽𝗿𝗼𝘀 & 𝗰𝗼𝗻𝘀. 1️⃣ 𝗥𝗜𝗖𝗘 𝗦𝗰𝗼𝗿𝗶𝗻𝗴 📌 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗶𝘀: Prioritize features based on Reach, Impact, Confidence, and Effort to assign a score. ✅ 𝗕𝗲𝘀𝘁 𝗳𝗼𝗿: Data-driven teams balancing effort vs. impact. ➕ 𝗣𝗿𝗼𝘀: Helps remove bias, quantifies decisions. ➖ 𝗖𝗼𝗻𝘀: Requires accurate estimates, time-consuming. 2️⃣ 𝗠𝗼𝗦𝗖𝗼𝗪 𝗠𝗲𝘁𝗵𝗼𝗱 📌 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗶𝘀: Categorizes initiatives into Must-have, Should-have, Could-have, and Won’t-have priorities. ✅ 𝗕𝗲𝘀𝘁 𝗳𝗼𝗿: Aligning stakeholders on critical vs. optional features. ➕ 𝗣𝗿𝗼𝘀: Simple, effective for MVP planning. ➖ 𝗖𝗼𝗻𝘀: Can be subjective, lacks clear scoring. 3️⃣ 𝗞𝗮𝗻𝗼 𝗠𝗼𝗱𝗲𝗹 📌 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗶𝘀: Classifies features as Basic Needs, Performance Needs, and Delightful Extras based on customer expectations. ✅ 𝗕𝗲𝘀𝘁 𝗳𝗼𝗿: Optimizing customer experience. ➕ 𝗣𝗿𝗼𝘀: Helps focus on features that create differentiation. ➖ 𝗖𝗼𝗻𝘀: Requires detailed user research, hard to quantify impact. 4️⃣ 𝗘𝗶𝘀𝗲𝗻𝗵𝗼𝘄𝗲𝗿 𝗠𝗮𝘁𝗿𝗶𝘅 📌 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗶𝘀: Prioritizes tasks/features based on Urgency vs. Importance. ✅ 𝗕𝗲𝘀𝘁 𝗳𝗼𝗿: Time-sensitive decisions and backlog cleanup. ➕ 𝗣𝗿𝗼𝘀: Quick, easy to use. ➖ 𝗖𝗼𝗻𝘀: Doesn't account for effort or long-term strategy. 5️⃣ 𝗖𝗼𝘀𝘁 𝗼𝗳 𝗗𝗲𝗹𝗮𝘆 (𝗖𝗗𝟯) 📌 What it is: Weighs how much revenue, efficiency, or opportunity is lost by delaying a feature. ✅ 𝗕𝗲𝘀𝘁 𝗳𝗼𝗿: Revenue-driven decision-making. ➕ 𝗣𝗿𝗼𝘀: Helps prioritize features that drive business growth. ➖ 𝗖𝗼𝗻𝘀: Requires accurate financial forecasting. 6️⃣ 𝗢𝗽𝗽𝗼𝗿𝘁𝘂𝗻𝗶𝘁𝘆 𝗦𝗰𝗼𝗿𝗶𝗻𝗴 📌 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗶𝘀: Prioritizes features by comparing customer importance vs. current satisfaction. ✅ 𝗕𝗲𝘀𝘁 𝗳𝗼𝗿: Customer-driven product teams. ➕ 𝗣𝗿𝗼𝘀: Helps identify high-impact gaps. ➖ 𝗖𝗼𝗻𝘀: Needs strong customer feedback data. 𝗖𝗵𝗼𝗼𝘀𝗶𝗻𝗴 𝘁𝗵𝗲 𝗥𝗶𝗴𝗵𝘁 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 There’s 𝗻𝗼 𝗼𝗻𝗲-𝘀𝗶𝘇𝗲-𝗳𝗶𝘁𝘀-𝗮𝗹𝗹 approach. The best framework depends on 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗱𝘂𝗰𝘁, 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗴𝗼𝗮𝗹𝘀, 𝗮𝗻𝗱 𝘁𝗲𝗮𝗺 𝗱𝘆𝗻𝗮𝗺𝗶𝗰𝘀. 💬 𝗪𝗵𝗶𝗰𝗵 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗺𝗲𝘁𝗵𝗼𝗱 𝗱𝗼 𝘆𝗼𝘂 𝘂𝘀𝗲? Drop your thoughts below👇 💡 If you’re looking to refine your 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆, visit www.productdiscipline.io or reach out—I’d love to help! #ProductManagement #Prioritization #DigitalProductDiscipline #BuildRightProducts #Agile #ProductStrategy #Innovation #Leadership

Unlocking Focus: A Simple Framework To Prioritise The Initiatives That Matter I facilitated a workshop with the leadership team of one of my technology clients yesterday, where we focused on a critical challenge: how do we prioritise outcomes over hours to maximise effectiveness? The solution? A simple but powerful tool I've relied on for years, which I learned during my time at General Electric (GE) - the Ease/Impact Matrix. Here's why it works so brilliantly: We often gravitate toward quick wins without considering their actual value. This matrix forces the team to evaluate everything through two critical lenses: ✅ High Impact + High Ease = Quick Wins (do immediately, gain momentum) ✅ High Impact + Low Ease = Long-term Bets (worth the investment) ❌ Low Impact + Low Ease = Avoid at All Costs ❓ Low Impact + High Ease = Question Why (just because we can, should we?) By reorienting around impact, we focused on what will truly benefit their business both immediately and in the long run. Sometimes the simplest tools create the most profound shifts. What frameworks have you found most valuable for prioritisation? #OutcomesOverHours

Your prioritization process is broken. Most product teams rely on RICE to decide what to build. But here’s the problem: RICE ignores strategy. So why do so many teams still use it? Because it’s easy. But easy doesn’t mean effective. The Problem with RICE: ❌ A feature can score high on reach and impact but still be a terrible idea if it doesn’t align with strategy. ❌ High-confidence, low-effort work can still waste resources if it doesn’t move the business forward. ❌ It optimizes for individual features, not the bigger picture. 💡 The Fix: RICEs (with a critical ‘S’—Strategic Alignment). Before prioritizing, ask: ✅ Does this fit our long-term vision? ✅ Will this move us toward our strategic goals? ✅ Will it strengthen our core differentiation? ✅ Is it solving problems for the right customers? If a feature doesn’t align with strategy, it doesn’t matter how well it scores—it’s a distraction. Great product teams don’t just choose what to build. They choose what to ignore. 🔔 Next time your team runs a prioritization exercise, don’t just use RICE. Use RICEs. --- 👋 I'm Ron Yang, a product leader and advisor. Follow me for insights on product leadership and building better products.