Prioritizing Project Tasks

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

𝐀𝐬 𝐚 𝐂𝐎𝐎, my day is a mix of 𝐟𝐢𝐫𝐞𝐟𝐢𝐠𝐡𝐭𝐢𝐧𝐠, 𝐬𝐭𝐫𝐚𝐭𝐞𝐠𝐢𝐳𝐢𝐧𝐠, 𝐚𝐧𝐝 𝐞𝐱𝐞𝐜𝐮𝐭𝐢𝐧𝐠—all while making sure 𝐭𝐡𝐞 𝐭𝐞𝐚𝐦 𝐦𝐨𝐯𝐞𝐬 𝐟𝐨𝐫𝐰𝐚𝐫𝐝 𝐰𝐢𝐭𝐡𝐨𝐮𝐭 𝐜𝐡𝐚𝐨𝐬 𝐚𝐧𝐝 𝐰𝐢𝐭𝐡 𝐜𝐥𝐚𝐫𝐢𝐭𝐲. Early on, I realized that trying to do everything leads to doing nothing well and a messy outcome. So, I built a simple system to prioritize my time: 𝐓𝐡𝐞 3-𝐁𝐨𝐱 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤: 𝐁𝐨𝐱 1: 𝐔𝐫𝐠𝐞𝐧𝐭 & 𝐂𝐫𝐢𝐭𝐢𝐜𝐚𝐥 (𝑫𝒐 𝒊𝒕 𝑵𝑶𝑾) These are 𝐡𝐢𝐠𝐡-𝐢𝐦𝐩𝐚𝐜𝐭, 𝐭𝐢𝐦𝐞-𝐬𝐞𝐧𝐬𝐢𝐭𝐢𝐯𝐞 tasks—things that affect revenue, operations, or people immediately. ✅ A client crisis ✅ A major hiring decision ✅ A process breakdown 𝐁𝐨𝐱 2: 𝐆𝐫𝐨𝐰𝐭𝐡 & 𝐋𝐨𝐧𝐠-𝐓𝐞𝐫𝐦 𝐈𝐦𝐩𝐚𝐜𝐭 (𝑷𝒍𝒂𝒏 & 𝑬𝒙𝒆𝒄𝒖𝒕𝒆) These are 𝐭𝐡𝐞 𝐫𝐞𝐚𝐥 𝐠𝐚𝐦𝐞-𝐜𝐡𝐚𝐧𝐠𝐞𝐫𝐬—the projects that don’t scream for attention but define long-term success. ✅ Scaling a system ✅ Building leadership depth ✅ Strengthening brand & culture 𝐁𝐨𝐱 3: 𝐍𝐨𝐢𝐬𝐞 & 𝐃𝐢𝐬𝐭𝐫𝐚𝐜𝐭𝐢𝐨𝐧𝐬 (𝑬𝒍𝒊𝒎𝒊𝒏𝒂𝒕𝒆 𝒐𝒓 𝑫𝒆𝒍𝒆𝒈𝒂𝒕𝒆) These are things that seem urgent but 𝐝𝐨𝐧’𝐭 𝐫𝐞𝐚𝐥𝐥𝐲 𝐦𝐨𝐯𝐞 𝐭𝐡𝐞 𝐧𝐞𝐞𝐝𝐥𝐞. ✅ Endless status update meetings ✅ Random low-priority emails ✅ Tasks others can (and should) own 𝐓𝐡𝐞 𝐬𝐞𝐜𝐫𝐞𝐭? 𝐌𝐨𝐬𝐭 𝐥𝐞𝐚𝐝𝐞𝐫𝐬 𝐬𝐩𝐞𝐧𝐝 𝐭𝐨𝐨 𝐦𝐮𝐜𝐡 𝐭𝐢𝐦𝐞 𝐢𝐧 𝐁𝐨𝐱 1 & 3, 𝐚𝐧𝐝 𝐧𝐨𝐭 𝐞𝐧𝐨𝐮𝐠𝐡 𝐢𝐧 𝐁𝐨𝐱 2. 👉 But real impact comes when you shift your focus to Box 2—the work that builds sustainable success. 𝑰 𝒔𝒑𝒆𝒏𝒅 20% 𝒕𝒊𝒎𝒆 𝒊𝒏 𝑩𝒐𝒙 1 𝒂𝒏𝒅 3, 𝒂𝒏𝒅 60% 𝒕𝒊𝒎𝒆 𝒈𝒐𝒆𝒔 𝒕𝒐 𝑩𝒐𝒙 2. Every morning, I ask myself: 𝘞𝘩𝘪𝘤𝘩 𝘣𝘰𝘹 𝘢𝘮 𝘐 𝘴𝘱𝘦𝘯𝘥𝘪𝘯𝘨 𝘮𝘰𝘴𝘵 𝘰𝘧 𝘮𝘺 𝘵𝘪𝘮𝘦 𝘪𝘯? And that question alone changes how I work and what's the outcome of my time spent. #Leadership #COO #Execution #StartupGrowth

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

Many highly-skilled PMMs can't figure out strategy. Many less-skilled PMMs already have. Why? Because it's not about raw talent. It's about one thing: connecting your daily to-do list to the company's goals. For a lot of PMMs, somewhere between "company strategy" and "what I'm doing today," things start to get muddy. They end up doing a lot of busy work that leads nowhere. What PMMs need is the mental scaffolding to connect the highest-level business goals to their nitty-gritty daily work. Here's a quick breakdown of the 6-level planning framework I recommend. It divides everything down by time. 1) Annual: know your company OKRs → Know top company goals  → Sanity-check projects against them → Use them to filter what matters 2) Quarterly: rocks, pebbles, and sand Translate company OKRs into personal (or team) priorities: → Pick 1 major “rock” → Add 2–3 supporting “pebbles” → Keep “sand” tightly limited If you don't size your work upfront, sand will eat your entire quarter. 3) Monthly: break your rock into milestones → Define clear monthly outcomes → Turn projects into checkpoints → Track visible progress 4) Weekly: pick ONE key deliverable → Choose 1 main output for the week → Limit to 1–2 priorities max → Use it to triage requests 5) Daily: focus on ONE task → Pick 1 task tied to your weekly goal → Avoid context switching too much → Measure real progress, not activity 6) Hourly:  protect your peak hours → Identify your best thinking hours → Block them for deep work → Push meetings outside One note on annual planning: company direction can shift fast. But with this framework, you can review your annual anchors quarterly and adjust. The framework doesn't make chaos disappear but it will make you faster at reorienting when things do change. 👉 Which level of this framework is the hardest for you? P.S. I've helped 300+ PMMs land and thrive in their dream jobs to become more strategic without burning out. If this resonated, share it with a PMM in your network who needs it, and follow for more frameworks like this. :) ♻️ #productmarketing #strategy #coaching

I've managed 5 high-performing product marketing teams at startups and public companies, and there are 2 commonalities I've noticed at each: 1) it's easy for PMMs to get overwhelmed by the sheer volume of tasks on their plates, and 2) teams are rarely recognized for their true effort or impact by upper management. That's why I want to share my prioritization matrix 👇 It’s been a game-changer in how my teams approach projects and focus on what truly drives results. I’m curious—does this framework resonate with your approach to prioritizing tasks? Here's the concept: Rack up the wins by focusing on projects that offer high visibility and impact for lower effort and avoid those that drain your energy and don’t align with company goals. (Note: you could replace visibility with impact on this scale, but it's important that what you're working on is actually on the radar of those in upper management). Here’s how to prioritize: Quick Wins: These are the golden opportunities! High visibility, low difficulty — they bring great returns with minimal effort. Look for ways to get a few of these in your quarter. Strategic Initiatives: Aim for ONE strategic initiative per quarter. These are high-visibility, high-difficulty tasks that are aligned with your long-term goals. Go deep, plan ahead, and focus on the impact. You will be the most proud of these, but you need to be realistic about them. Routine Tasks: You’ve got to keep up with these, but don't let them consume too much of your time. Find a system to manage them efficiently. Avoid: Stay clear of high-difficulty, low-visibility tasks. These projects often don't yield the results you need, and they’re energy-draining. They don't align with your values or long-term success. 💡 Action Step: Review your current or upcoming projects. Classify them into high or low reward, and high or low effort. What projects are you spending too much time on that aren’t worth the effort? Time to realign and focus on what truly matters! #Productivity #TimeManagement #Prioritization #WorkSmart #StrategicFocus #CareerGrowth #Leadership How do you manage your / your team’s workload?

During my time as a Principal TPM in the Oracle Cloud Infrastructure team, I learned firsthand that knowing what to de-prioritize is equally crucial as prioritization. Prioritization is a delicate dance every Technical Program Manager performs daily. It's not just about crafting a to-do list; it's about making strategic choices that propel your projects and teams forward. Mastering this art can mean the difference between smooth sailing and utter chaos in the whirlwind of technical program management. It's all about feeling empowered by the decisions you make. Imagine your workload as a juggling act – not every ball is the same size, and not every ball needs to be caught immediately. 🤹♂️ Early in my career, I was juggling a major product launch, a team restructure, and a handful of smaller projects. Trying to do everything at once was a recipe for disaster. After a near-miss with a critical deadline, I started each day by listing my tasks and categorizing them into "urgent and impactful," "can be done later," and "delegate." The change was immediate and profound. Not only did I meet my deadlines, but my team also became more cohesive and efficient. 🎯💪 Some popular prioritization strategies that have helped me and many others include: Eisenhower Matrix, which categorizes tasks into four quadrants based on urgency and importance(Do First, Schedule, Delegate, and Don't Do). 📊  The MoSCoW method (Must have, Should have, Could have, and Won't have) is another excellent approach, especially for managing project requirements. 📝  Ivy Lee method, where you list the six most important tasks to complete the next day and focus on them in order of priority. Each method can provide a clear framework for deciding what needs immediate attention and what can wait. Understanding the power of saying "No" can be transformative, allowing you to focus on what truly matters and avoid unnecessary stress. So, the next time you're feeling overwhelmed, remember: it's not just about what you do, but also about what you choose not to do. Share your prioritization hacks, challenges or stories in the comments! 👇💬

🚨 𝗦𝘁𝗿𝘂𝗴𝗴𝗹𝗶𝗻𝗴 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝗼𝗳𝘁𝗲𝗻 𝘁𝗿𝗮𝗰𝗲 𝗯𝗮𝗰𝗸 𝘁𝗼 𝗮 𝗰𝗼𝗺𝗺𝗼𝗻 𝗿𝗼𝗼𝘁 𝗰𝗮𝘂𝘀𝗲: 𝗪𝗲𝗮𝗸 (𝗼𝗿 𝗮𝗯𝘀𝗲𝗻𝘁) 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗿𝘂𝗹𝗲𝘀. When 𝘦𝘷𝘦𝘳𝘺𝘵𝘩𝘪𝘯𝘨 feels urgent, nothing moves forward with clarity or logic. That’s why strong programs and PMOs anchor around a 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗿𝘂𝗯𝗿𝗶𝗰, built early, not reactively. A clear rubric gives you: ✅ Consistency in chaos ✅ Fact-based decision-making ✅ Faster, defensible tradeoffs when pressure hits Here’s how to build one that sticks 📈 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗶𝗺𝗽𝗮𝗰𝘁, 𝗺𝗮𝗴𝗻𝗶𝘁𝘂𝗱𝗲, 𝗮𝗻𝗱 𝗽𝗿𝗼𝗯𝗮𝗯𝗶𝗹𝗶𝘁𝘆. • Does it affect multiple business units? • Can you quantify the financial or operational impact? • Is there a feasible workaround?    ♻️ 𝗥𝗲𝘃𝗶𝘀𝗶𝘁 𝗰𝗼𝗻𝘀𝘁𝗮𝗻𝘁𝗹𝘆. 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗻𝗼𝘁 𝗮 𝗼𝗻𝗲-𝗮𝗻𝗱-𝗱𝗼𝗻𝗲 𝗲𝘅𝗲𝗿𝗰𝗶𝘀𝗲. • When markets shift, priorities shift. • When new information is presented, reassess the severity. • Force rank within each prioritization level.    ⚓ 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 𝘁𝗵𝗲 𝗯𝗹𝗶𝗻𝗱 𝘀𝗽𝗼𝘁𝘀. 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗼𝗻𝗹𝘆 𝗮𝘀 𝘀𝘁𝗿𝗼𝗻𝗴 𝗮𝘀 𝘁𝗵𝗲 𝗱𝗲𝗯𝗮𝘁𝗲 𝗯𝗲𝗵𝗶𝗻𝗱 𝗶𝘁. • Map upstream/downstream impacts. • Recommend tradeoffs, not just surface issues. • Document the decision 𝘢𝘯𝘥 the why behind it.    Projects don’t fail because teams don’t care. They fail because they care about 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 equally. Build your rubric. Anchor your focus. Deliver with purpose. 👉 If your projects feel like they’re spinning, start by redefining what truly matters. Build your prioritization rubric before you need it.

90% of projects fail because of mental blind spots. Senior Program Management is a game of systems, not speed. If you’re focused on a 'To-Do' list, you’ve hit your ceiling. 8 frameworks to stay ahead: 1. The Cynefin Check Categorize the environment first. Management styles that work for clear tasks fail in chaotic ones. Match your approach to the domain. 2. Pareto Analysis (80/20) Audit your friction. A small group of stakeholders or a specific technical debt usually generates most of the noise. Focus your energy there. 3. The Pre-Mortem Imagine the project collapsed six months from now. Trace the specific risks that caused it. Address those "hidden" killers while you still have lead time. 4. Second-Order Thinking Evaluate decisions by their downstream effects. Every "quick fix" carries a future cost. Ask: "And then what happens?" 5. Parkinson’s Law Work expands to fill the time you give it. Tighten internal milestones to flush out unknowns earlier in the cycle. 6. The O’Toole Effect People clear easy emails to avoid high-friction tasks. Move the "hardest rock" before your first meeting. 7. Cost of Delay (CoD) Translate time into dollars. Quantify exactly what is lost for every week a milestone is missed. It turns a schedule debate into a business decision. 8. The Bus Factor If a project stops because one lead is unavailable, you have a single point of failure. Cross-train the team. Move knowledge into shared systems. Which one is your team missing? Drop a comment below. 👇

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 to Evaluate Bets Quickly Without Sacrificing Confidence (Moving fast shouldn’t mean moving blindly.) Over the past decade, one question has remained constant with any Product Leader I talk to: How do you drive product growth consistently? In my experience, the answer lies in building a team practice that prioritizes confidence and iteration. It’s not just about speed—it’s about being decisive with confidence. Here’s the challenge: many frameworks for prioritizing growth features fall short. Why? 🚫 They rely heavily on subjective opinions (e.g., “effort” or “impact”) with little numerical grounding. 🚫 They lack a structured way to prioritize initiatives that deliver real, measurable business impact. Take RICE (Reach, Impact, Confidence, Effort), for example. It assigns a 1-3 scale to “impact” but leans heavily on “reach” as the deciding factor. While helpful, it often leads to decisions that feel more like gambling than placing well-informed bets. So what’s the alternative? Successful growth teams prioritize speed, confidence, and iteration by treating each initiative like a well-placed bet—with just enough structure to guide decisions without overcomplicating the process. 💡 Introducing the Litmus Framework The Litmus Prioritization Framework expands beyond confidence and effort to deliver a more comprehensive approach to prioritization. It evaluates initiatives based on four critical factors: 1️⃣ Estimate: The Napkin Math estimate for KPI impact, often shared in $$ terms. 2️⃣ Resourcing Impact: Considers not just dev effort but the larger stakeholder impact, rated on a 0-100% scale. 3️⃣ Risk to Existing Revenue: Accounts for the potential risk an initiative poses to current revenue streams, also rated on a 0-100% scale. 4️⃣ Exec Buy-In Prediction: Assesses how well decision-makers are likely to receive the idea, rated on a 0-100% scale. The formula: [Napkin Math Estimate] X [1 - % Resourcing Impact] X [1 - % Risk to Existing Revenue] X [% Exec Buy-In Prediction] This calculation produces a Litmus Value—a single number to prioritize and stack rank initiatives, projects, or features with confidence. 💡 It can even work in highly regulated industries like healthcare Where the stakes are higher and lives are literally at stake, the Litmus Framework’s "Risk to Existing Revenue" should include risk to long term revenue, to ensure that growth initiatives protect trust, stability, and ethical standards. The goal isn’t to move fast for the sake of it—it’s to move fast with confidence. By aligning your team on a methodology that blends decisiveness with structured evaluation, you unlock consistent growth and reduce the risk of spinning wheels on low-impact initiatives. What’s your go-to method for evaluating bets quickly? P.S. Building confidence in your growth bets can be a game-changer for your team. If you’ve experienced this, I’d love to hear your thoughts!