Product Managers: Turn Questions into Board Decisions

Who This Helps

You're a product manager who gets asked big questions in meetings. "When do we run out of cash?" "What happens if growth slows?" "Should we hire now or wait?"

These aren't just product questions. They're board questions. And if you can't answer them with numbers, you lose trust.

The Board Finance & Runway Narrative course is built for exactly this moment. It gives you a repeatable way to turn any product question into a measurable decision your board will approve.

Mini Case

Meet Viktor. He's a product manager at a SaaS startup with 18 months of runway. His CEO asks: "What's our hiring plan for the next quarter?"

Viktor doesn't guess. He builds a runway trigger tree. He defines three scenarios: growth (12% monthly), flat (2%), and decline (-5%). For each, he sets a trigger: if growth drops below 5% for two months, hiring freezes. If cash dips below 9 months, they cut one contractor.

Result? The board approves his hiring plan in 15 minutes. No pushback. No "let's discuss later."

Do This Now (5 Steps)

1. Pick one product question you're avoiding. Write it down. Example: "Should we launch feature X or fix churn first?"

1. Define your runway trigger tree. List 3 scenarios: best case, base case, worst case. For each, write one trigger (like "if churn hits 8%" or "if revenue drops 10%").

1. Add an action branch. For each trigger, write one concrete action. Example: "If churn hits 8%, pause all new features for 2 weeks and run a retention sprint."

1. Run the numbers. Use your current cash, burn rate, and growth rate. Calculate how many months of runway each scenario gives you. Keep it simple: 3 numbers max.

1. Write a one-page board memo. Use the Board Signal Alignment mission from the course. List your top signal, your trigger tree, and your recommended action. Keep it to 5 bullet points.

Avoid These Traps

• Don't use vague triggers. "If growth slows" is useless. Use a number: "If growth drops below 5%."
• Don't skip the worst case. Boards love when you show you've thought about the bad stuff. It builds trust.
• Don't overcomplicate. Three scenarios. Three triggers. Three actions. That's it.
• Don't present without a recommendation. Always end with: "I recommend we do X because Y."
• Don't forget to update. Run your trigger tree every month. It takes 10 minutes.

Your Win by Friday

By Friday, you'll have one board-ready decision on your desk. Pick any product question, run it through the trigger tree, and write a one-page memo. Show it to your CEO or a peer. Get a yes or a clear next step.

You'll feel like a superhero. And honestly, that's a pretty fun feeling for a product manager.