Who This Helps
This is for Product Managers who have done the work—like running a Unit Economics Snapshot from the Finance Basics for Operators course—but now need to get everyone else on the same page. You're translating numbers into a clear story for your boss, finance, or the exec team.
Mini Case
Viktor saw his product's contribution margin was 35%, but one feature line had a -5% margin, dragging the whole average down. Instead of just showing the spreadsheet, he framed it: "Our core product is strong at 35%, but Feature X is costing us 5% on every sale. Pausing it for one quarter could lift our total margin to 38%." He got approval to deprioritize it in 15 minutes.
Do This Now (5 Steps)
- Start with the one number that matters. Lead with your key finding, like "Our contribution margin is 35%."
- Show the 'so what' immediately. Add the context: "...which is 7 points above our target, but one line is pulling us back."
- Use the mission problem as your script. Remember Viktor's task: "identify one weak line." Name it clearly.
- Present exactly one choice. Offer a single, clear recommendation, like "Let's pause the weak feature for 90 days and monitor."
- Define the next check-in. Propose a specific date to review the decision: "Let's revisit this next sprint review."
Avoid These Traps
- The Data Dump: Don't forward the raw spreadsheet. Your stakeholders don't have time to be analysts.
- Presenting Problems Without Options: Never just highlight an issue. Always pair it with a proposed next step.
- Using Jargon: Words like "variable cost allocation" can confuse. Say "the cost for each new customer" instead.
- Asking for Open-Ended Feedback: "What do you think?" leads to circles. Ask for a yes/no on your specific proposal.
- Forgetting the Win: Every analysis should connect to a business goal, like extending runway or hitting a margin target. Connect those dots.
Your Win by Friday
Your goal isn't just to share insights—it's to get a decision that moves the work forward. By framing your Unit Economics Snapshot around a single, clear recommendation, you turn a weekly analysis into an approved action. You'll spend less time in meetings explaining and more time executing. That’s the operator’s flywheel. Now go get that 'yes.'