Who This Helps
You’re a Junior Analyst who just finished a deep dive. Now you need to present it so stakeholders nod and say yes. This is for you if your last deck got more questions than approvals.
Mini Case
Sofia, a Junior Analyst at a mid-size SaaS company, ran a portfolio review. She found 12 active projects, but only 3 had clear success metrics. Stakeholders kept asking, “Why are we doing this?” Sofia used the Product Portfolio Strategy course’s Kill Criteria mission to flag the 9 unclear bets. She showed that cutting them freed up 40% of engineering capacity. Her recommendation was approved in one meeting.
Do This Now (5 Steps)
- List every active project in your portfolio. Include rough cost and confidence level.
- Define your guardrails – what must not get worse (e.g., uptime, customer satisfaction).
- Apply kill criteria from the course. If a project doesn’t meet a guardrail, flag it.
- Size the impact – calculate capacity saved (like Sofia’s 40%) and show it in one number.
- Write one recommendation per project: keep, pause, or kill. No more than 3 sentences each.
Avoid These Traps
- Hiding bad news – stakeholders smell it. Show risks early.
- Too many slides – one-page portfolio artifact wins. Use the Portfolio Map mission.
- Vague language – replace “might improve” with “saves 12% cost.”
Your Win by Friday
By Friday, you’ll have a one-page portfolio map with clear guardrails and kill criteria. Your next stakeholder meeting? They’ll approve your recommendations. And you’ll feel like the analyst who actually gets things done.