Who This Helps
You're a Product Manager who needs to turn product questions into measurable decisions. You've got a board meeting coming up, and your CEO wants a clear finance narrative. The Board Finance & Runway Narrative course is built for exactly this moment.
Mini Case
Meet Viktor, a PM at a growth-stage startup. His board asked: "What happens if revenue drops 12% next quarter?" Viktor used the Runway Trigger Tree from the course to map out three action branches: cut hiring by 20%, pause a feature launch, or extend runway by 7 days. The board approved his plan in one meeting.
Do This Now (5 Steps)
- Pick one board-level signal. What single number matters most this cycle? For Viktor, it was monthly recurring revenue growth.
- Build your scenario envelope. Write down three scenarios: best case, base case, worst case. Assign explicit assumptions to each.
- Define runway triggers. At what revenue drop do you act? Viktor set a 12% drop as his trigger.
- Create action branches. For each trigger, list one concrete action. Example: if revenue drops 12%, freeze hiring for 30 days.
- Test with your team. Walk through each branch with your finance lead. Make sure everyone agrees on the next step.
Avoid These Traps
- Too many triggers. Stick to three max. More than that and you'll freeze when it's time to act.
- Vague actions. "Cut costs" isn't a branch. Say "reduce contractor spend by 15%."
- Ignoring the board's context. Your board cares about runway, not feature specs. Keep your narrative focused on capital decisions.
- No owner for each branch. Assign a person to each action. Viktor's VP of Engineering owned the hiring freeze branch.
Your Win by Friday
By Friday, you'll have a one-page board finance memo that turns your product questions into approved execution. You'll walk into your next board meeting with a clear runway trigger tree, three scenarios, and a capital allocation tradeoff your team already bought into. And honestly, that feels way better than guessing what the board wants.