30 Requests. No Framework. Sprint Planning Is Tomorrow.
Everyone has an opinion about what's most important. The CEO has a pet project. The VP of Sales has five "urgent" customer requests. Engineering is begging for tech debt time. You have no defensible way to choose. This course gives you a prioritization system that survives contact with real stakeholders. Not a theoretical framework you'll abandon by Wednesday. A system that makes the decision visible, repeatable, and politically survivable.
The Problem This Course Solves
You're not bad at prioritizing. You're bad at saying no. There's a difference.
Most PMs can rank a list of features on a whiteboard. The hard part is what happens after. The VP who doesn't like where their project landed. The CEO who asks "why isn't my thing at the top?" The sales team that forwards you the Slack message from a prospect who "needs this by end of quarter."
So you do what most PMs do. You say yes to everything. You overcommit. Sprint planning becomes a negotiation instead of a decision. Your team delivers 60% of what you promised, and nobody trusts the roadmap anymore.
The root problem is that you don't have a system that makes the reasoning visible. When the reasoning is invisible, every decision looks arbitrary. And arbitrary decisions invite political override.
This course fixes that. You'll build a prioritization system where every request gets scored against business impact, not squeaky-wheel volume. Where trade-offs are explicit. Where saying no doesn't cost you political capital because the framework said no, not you.
What You'll Learn
8 modules. Self-paced. Each one gives you a tool you can use in your next sprint planning session.
Why prioritization frameworks fail
RICE, MoSCoW, weighted scoring. They all work on paper. They all collapse when a VP walks in with "just one more thing." You'll learn why, and what to build instead.
The Business Impact Scorecard
A scoring model that evaluates every request against revenue impact, strategic alignment, cost of delay, and effort. Not theoretical. Calibrated from real product teams that actually use it.
The "three solutions, never one" technique
When someone brings you a demand, you bring back three options at different investment levels. This reframes the conversation from "yes or no" to "how much." It changes the power dynamic.
Saying no without losing political capital
Scripts and frameworks for declining requests from leadership without damaging the relationship. The key: make the trade-off visible. "We can do X, but it means not doing Y. Which matters more?"
The Sprint Trade-Off Matrix
A visual tool that shows your team's capacity, current commitments, and what gets displaced by every new request. When the CEO sees that their pet project pushes the Q3 revenue feature to Q4, the conversation changes.
Handling the CEO/VP pet project
The request that doesn't score well but comes from someone who controls your career. A step-by-step approach for escalating gracefully: validate the intent, quantify the trade-off, offer alternatives, and document the decision.
Capacity allocation model
How to split your team's capacity across new features, tech debt, bugs, and exploration. A formula that prevents the "we never have time for tech debt" death spiral.
Building consistency across your team
For PMs and product leads managing multiple PMs. How to roll this system out so every PM on your team uses the same criteria. Stops the "my PM says yes, your PM says no" problem.
Who This Is For
This is for you if:
- You're a PM drowning in requests with no defensible way to prioritize. Sprint planning feels like a negotiation, not a decision.
- You say yes to everything and consistently under-deliver. Your roadmap changes weekly. Your team is frustrated.
- You can prioritize features logically but can't hold the line when a senior stakeholder pushes back.
- You're a product lead trying to build consistent prioritization across multiple PMs on your team.
This is NOT for:
PMs with a single focused product where sequencing is clear and stakeholder pressure is low. Or PMs in very early-stage startups where the founder decides everything and prioritization is a one-person conversation.
What's Included
Total perceived value: $427. You pay $59.
What Others Say
"I walked into sprint planning with the scorecard and for the first time, nobody argued. The numbers spoke. We cut 12 requests down to 4 in twenty minutes."PM, B2B SaaS (coached by Brennan Collins)
"The three solutions technique changed my relationship with our VP of Sales. He used to bring me demands. Now he brings me problems and asks for options."Senior PM, Enterprise Software
"My team was shipping 55% of what we committed to each sprint. After implementing the capacity allocation model, we hit 90% for three straight sprints. The trust came back."Product Lead, Fintech
Frequently Asked Questions
Ready to get started?
Everyone has an opinion about what's most important. The CEO has a pet project. The VP of Sales has five "urgent" customer requests. Engineering is begging for tech debt time. You have no defensible way to choose. This course gives you a prioritization system that survives contact with real stakeholders. Not a theoretical framework you'll abandon by Wednesday. A system that makes the decision visible, repeatable, and politically survivable.