← Back to blog

Team Lead · Board Finance & Runway Narrative

Team Leads: Prioritize Your Next Move with a Runway Trigger Tree

Stop guessing what to do next. Build a simple trigger system to focus your team's effort on the highest-impact experiment.

Who This Helps

This is for team leads who feel stuck in endless planning cycles. If your team has a dozen good ideas but can't decide which one to run next, this helps. It's a core part of the Board Finance & Runway Narrative program, designed to turn financial discipline into clear team action.

Mini Case

Viktor's team had 8 potential growth experiments. They debated for weeks. He built a simple trigger tree: if monthly active users grew by less than 5%, they'd run experiment A. If cash runway dipped below 9 months, they'd pause hiring and run experiment B for margin improvement. In 7 days, they had a clear rule. The next month, user growth slowed to 3%—they instantly launched experiment A without a meeting. It saved them 15 hours of debate.

Do This Now (5 Steps)

  1. List your top 3-5 experiments or projects your team could tackle.
  2. For each one, ask: "What specific company signal tells us to run THIS one NOW?"
  3. Define that signal with a number. Think: revenue growth rate, cash runway months, or a key metric.
  4. Write the simple rule: "If [Signal] is [above/below] [Number], we start [Experiment]."
  5. Share this one-page trigger tree with your team this week. Boom, decision framework done.

Avoid These Traps

  • Don't create triggers for everything. Start with the 2-3 most critical business outcomes.
  • Avoid vague signals like "if engagement is low." Low compared to what? Use a clear percentage or count.
  • Don't let the perfect be the enemy of the good. Your first version will be 80% right, and that's 100% better than no system.
  • Skipping the "defend expected impact" step. For each trigger, know roughly what success looks like (e.g., "This should improve retention by 2%").

Your Win by Friday

By Friday, you'll have a one-page document that answers Viktor's problem: defining runway triggers and action branches. No more weekly "what should we do" debates. Your team will know the playbook, so you can all focus on execution. It’s like giving your team a compass instead of just a map.