Who This Helps
This is for founders and operators who see a key number drop and need to know why—fast. It pulls directly from the Product Portfolio Strategy course, turning a messy situation into a clear, actionable diagnosis.
Mini Case
Your weekly active users dropped 15% last month. The team is debating: Is it the new feature? The pricing page? A competitor? You spend 3 days in meetings, but the root cause is still a mystery. Time and focus are leaking.
Do This Now (5 Steps)
- Grab your one-page portfolio artifact. If you don't have one, list every active product, feature, and experiment on a single page. This is your Portfolio Map.
- Circle the three biggest bets. Look at your list. Which items have the most team time or customer promise? Mark them.
- Check your guardrails. For each circled bet, ask: Did any core metric we promised not to get worse actually get worse? (Think: page load speed, sign-up completion). This is your 'Define what must not get worse' moment.
- Note the launch dates. When did the last change for each big bet ship? Write it down. A drop 7 days after a launch is a giant clue.
- Isolate the signal. You now have a focused list of 1-3 possible culprits linked to your KPI drop. You've turned 20 possibilities into 3.
Avoid These Traps
- Don't jump into deep data analysis before you look at your portfolio map. You'll waste hours on irrelevant metrics.
- Don't let the team argue about every possible cause. Use the map to constrain the conversation to your active bets.
- Don't forget to look at what you didn't change. Sometimes the cause is a neglected part of the product that stopped performing.
- Avoid diagnosing in a vacuum. Share your one-page map with one other leader to pressure-test your logic.
Your Win by Friday
By Friday, you'll have a single, clear hypothesis for your KPI drop, backed by your actual product bets. No more endless debate. You'll know if it's Bet A, B, or something you stopped paying attention to. Then you can actually fix it. Pretty neat, right?