Neil Patel

Walks through common product launch mistakes like building for yourself, waiting too long, or trying to do too much at once. Useful when planning a launch and you want a quick check on the easy ways things go wrong.

Paulo Caroli

A one-week structured workshop that aligns a team on key features, customers, and an MVP canvas before building. Useful when kicking off a new product and stakeholders are not aligned yet.

Konstantin Valiotti

Lays out three times to consider freemium (retention, expanding fit, hitting competition) and warns that it requires real engineering, marketing, and ops investment. Useful when leadership is debating whether a free tier makes sense for the business.

Riya Gayasen

Walks PMs through what to consider before bolting AI onto a product, drawing on a PayPal PM talk about feature fit, data, and risk. Useful when leadership is pushing for AI features and you need a clear filter for which to build.

Billy Sweetman

Billy Sweetman covers where design debt comes from and how to manage it before it slows the team. Useful when a design team needs a clear plan to start paying down debt.

Marty Cagan

Marty Cagan explains the opportunity backlog: a list of problems to solve, not features to build. Useful when a team's roadmap is jammed with feature requests and missing real opportunities.

Sophia Barron

HubSpot's Sophia Bernazzani Barron lists tested retention tactics like clear expectations, customer roadmaps, and feedback loops. Useful when a customer success team is rebuilding its retention playbook with examples.

Steve Denning

Lays out a five-step shift from red ocean fighting to blue ocean creation, including spotting hidden pain points and testing new value. Useful when a team has decided to pivot and needs a step-by-step path to make the move.

Sovita Chander

Lays out four elements to find the right beachhead market: brainstorm options, evaluate adjacent markets, do hands-on customer discovery, and budget for the search. Useful when a startup founder is choosing where to start small and needs a step-by-step.

Artkai

Explains the 3 Horizons model for product teams using core business, emerging tech, and long-term transformation lenses. Useful when a product team is deciding how to split effort between today's product and bigger bets.

Relab Studios and Alvin Hermanto

Relab Studios with Alvin Hermanto walks through the Value vs Effort prioritization method as a fast way to pick which to-do tackles first. Useful when a small team needs a quick whiteboard exercise to align on what matters.

Francesca Cortesi

Argues you should sort the prioritization matrix by time-to-ROI rather than just impact and effort. Useful when leadership cares about how fast value lands, not just how big it is.

Rameez Kakodker

Quick explainer of McKinsey's 3 Horizons Model with the 70-20-10 split between core, transform, and innovate work. Useful when a product team needs a framework to balance current bets against future ones.

Mike Kulakov

Founder of Everhour shares lessons from growing a bootstrapped SaaS to $130K MRR, including launch hacks like Beta List and team scaling tips. Useful when a small SaaS team is figuring out when to hire, launch, and scale.

Anthony Murphy

Anthony Murphy explains how to use RICE with examples and traps to avoid. Useful when a team is starting RICE and wants to dodge common mistakes.

Alyssa Zacharias

Alyssa Zacharias shows how to streamline projects in Notion using RICE prioritization. Useful when a team uses Notion for project planning and wants RICE built in.

Airfocus

Airfocus video explaining the RICE scoring framework with examples. Useful for teams that learn faster from video walkthroughs.

Joe Cotellese

Joe Cotellese walks through cooking up a backlog using RICE step by step. Useful for a PM who wants a recipe-style intro to RICE.

Mile Živković

Mile Zivkovic surveys seven popular prioritization frameworks for PMs. Useful when a PM is shopping for a prioritization method that fits the team.

Waleed Elaghil

Waleed Elaghil shows a hands-on way to put RICE into practice. Useful when a team has read about RICE but hasn't actually scored anything yet.

Kasey Kaplan

Kasey Kaplan tweaks RICE into BRICE to add a missing 'B' factor. Useful when teams find RICE oversimplifies tradeoffs in their backlog.

Roman Pichler

Roman Pichler offers ways to prioritize a backlog when stakeholders say everything is important. Useful when a PM is stuck between competing must-haves.

Azer Aliyev

Azer Aliyev explains the WSJF prioritization framework for product backlogs. Useful when an agile team needs a way to weigh urgency and effort together.

Anup Sheshadri

Anup Sheshadri introduces SU-RICE as a SaaS-focused twist on the RICE framework. Useful when a SaaS team finds plain RICE missing key signals.

Meenakshi Uniyal (she,her)

Meenakshi Uniyal applies the Kano model to backlog prioritization. Useful when a team needs to balance must-have, performance, and delight features.

Moataz Samy

Moataz Samy challenges teams to ask if they are solving real problems or just adding features. Useful when a backlog is full of feature ideas and no clear customer outcomes.

Itamar Gilad

Itamar Gilad argues the Impact/Effort matrix fails because we are bad at predicting impact and effort, and proposes adding Confidence to the formula. Useful when a team picks bad winners using a 2x2 and needs a smarter approach.

airfocus

Airfocus's video defines the Value vs Effort model and shows how to plot features to find quick wins and skip thankless work. Useful when a team is building a roadmap and needs a fast prioritization sketch.

Gaurav Nukala

Gaurav Nukala shares a decision framework for product portfolio management that decides which items get worked on, in what order, and for how long. Useful when a leadership team has too many bets and needs a repeatable way to sequence them.

Matt Hicks

Matt Hicks shares strategies for managing multiple product lines, including the 70-20-10 portfolio split between core, adjacent, and transformational bets. Useful when a leader needs a simple lens to balance current revenue and future growth.

Brady Simpson

LinkedIn PM Brady Simpson runs a webinar on identifying product opportunities using a UI-ME framework, real problems, and cross-functional partners. Useful when PMs want a structured way to walk a team from goal to opportunity list.

Susan Stavitzski

Susan Stavitzski shares three steps to break down product opportunities so teams stop drowning in ideas and start picking. Useful when a PM has a backlog of suggestions and needs a sharper way to choose what to pursue.

Alexander Fandén

Alexander Fanden's Notion resource sheet collects templates and references for prioritizing design systems. Useful when a team is setting up its own prioritization process and wants ready-made templates to start from.

Alexander Fandén

Alexander Fanden explains how to prioritize design-system work — by value, frequency, and risk — so small teams can ship the right components first. Useful when a design-system backlog feels endless and the team needs a way to pick what to do next.

Filip Stollár

Hacker News thread on building a design system at a startup — covering trade-offs, when to bother, and what to skip when small. Useful when a startup designer is wondering if they are too early for a system and wants outside opinion before investing.

Reddit, Inc.

Reddit thread of practitioner tips for creating a design system at a single company — covering scope, governance, and how to start small. Useful when a designer is asked to start a system and wants real-world advice before committing to a tool or structure.

Samer S

Samer S explains how to prioritize among competing stakeholders — by mapping power, interest, and impact — so teams know who to listen to first. Useful when too many voices are pulling on a project and a leader needs a way to pick which voices win this round.

Mike Cohn

Mike Cohn argues that 'not now' is a stronger answer than 'no' when paired with medium-term goals — it keeps options open and ties prioritization to a horizon. Useful when a team keeps killing ideas hard and stakeholders feel unheard because there is no roadmap context.

Russell Bourne

Russell Bourne shares how a CSM can ruthlessly prioritize a packed account list — by tier, risk, and growth opportunity — instead of reacting to whoever shouted last. Useful when a CSM is overwhelmed by inbox chaos and needs a way to spend the day on accounts that matter most.

Christian Watson

Christian Watson shares a lightweight prioritization framework anyone on a product team can use — score by impact, effort, and confidence, then talk through the top items together. Useful when a small team wants prioritization to be a shared act, not a leader's solo call.

Alyona Nikolaieva

Walks through seven feature prioritization frameworks — RICE, MoSCoW, Kano, Value vs. Effort, and more — with notes on when each one fits. Useful when a PM is staring at a long backlog and needs to pick a method to rank items, not just argue about them.

Krys Higgins

Five resolutions for better onboarding — write less copy, cut steps, show real value early, test with new users, and keep iterating. Useful when an onboarding flow has grown bloated and the team needs a simple checklist to trim it back.

Ameet Ranadive

Pushes PMs to think critically before chasing any opportunity, since time is limited. Useful when leaders need to say no to weak product ideas.

Eduardo Mignot Escalada

Pushes beyond impact-vs-effort to weigh confidence, dependencies, and timing in prioritization. Useful when you want richer prioritization than a 2x2 grid.

Ted Goas

Practical guide on understanding users, business, and market, then plotting projects on impact vs effort. Useful when a product designer wants to start owning strategy without leaving design behind.

Andrew Dillon

Three-step framework for early CEOs: prioritize, estimate with t-shirt sizes, and roadmap themes by quarter. Useful when you are an early founder doing PM work and need a simple way to plan.

Jason Yip

Defines UX debt as the gap between current and target UX quality, then offers three strategies: incremental fixes, fixed capacity, and quantifying impact. Useful when you need a clean way to define UX debt and pick a payback approach.

Mariia Kasym

Step-by-step guide for product owners to find UX debt through audits and usability testing, then prioritize and resolve it. Useful when you suspect UX debt is piling up and need a way to inventory and tackle it.

Jason Brush

Argues that journey maps are wasted unless they directly inform strategy or actions that change customers' lives. Useful when teams plan a journey mapping exercise and you want to challenge whether the work will actually pay off.

Cori Widen

Describes a three-step approach: hold a stakeholder kickoff, define the prioritization elements that fit your org, and score each request numerically. Useful when you want to defend a research roadmap with explicit criteria instead of gut feel.

Ilse Blom

Suggests using stakeholder willingness to pivot, clarity on insight use, and team alignment as filters to skip research that won't change anything. Useful when triaging incoming requests and you want to avoid spending weeks on a study that nobody will act on.

Nikki Anderson

Lays out a nine-step checklist for sorting an overflowing research backlog by priority, impact, team support, and readiness to act. Useful when you have more research requests than time and need a repeatable way to decide what to run next.

Productboard

Productboard names five common feature-prioritization mistakes - loud voices, scattered insights, feature-not-outcome focus, saying yes too often, and gut-feel data. Useful when teams notice their roadmap is feature-stuffed and missing impact.

Rosie Mangiarotti

Rosie Mangiarotti shares lessons from three years of physical-product development before her first sale - manufacturing complexity, multi-year timelines, and the value of advisors. Useful when first-time founders underestimate hardware product timelines.

Mprakash

Mprakash explains how dashboard design services turn complex data into clear actionable insights and lists what to consider when picking a vendor. Useful when leaders are evaluating whether to build, buy, or contract dashboard work.

Anna Kaley

Defines UX debt as accumulated shortcut decisions and shows how to identify, prioritize, and resolve it inside agile sprints. Useful when leaders need a structured way to decide which UX issues to tackle first.