Install a narrative OS. Align boards in weeks.
Your data moves faster than the story. A stable narrative turns evidence into decisions—and tension into trust.
What makes a narrative OS stick?
Own one page
Hypothesis, data, decision, next proof—no fluff, no drift.
Expose assumptions
Publish priors and confidence. Disarm debate before it starts.
Expose assumptions
Publish priors and confidence. Disarm debate before it starts.
Tag decisions
Reversible vs. irreversible calls guide speed and proof.
Keep the trail
Linked artifacts and change logs smooth diligence and filings.
Keep the trail
Linked artifacts and change logs smooth diligence and filings.
Install your board‑ready narrative OS
When Board Meetings Become Board Marathons
Slides multiply. Decks balloon to 60+ pages. Reviews stretch to 2+ hours. And somehow, you still leave without clear decisions on what matters most.
The problem isn't the board—it's that context fragments across too many slides, making it hard to separate signal from noise.
The Pattern: Data Without Decisions
Most board decks are structured around what happened (experiment results, milestone updates, budget actuals) rather than what needs to be decided (go/no-go calls, resource allocation, strategic pivots).
What this looks like:
20 slides on assay results, 1 slide on whether to advance the candidate
Detailed manufacturing timelines, but no clear "are we ready to scale?" decision
Hours of presenting, 15 minutes of actual decision-making
Is this your situation?
Ask yourself: In your last board meeting, how many explicit decisions were made and documented? (Not "we discussed X" but "we decided Y based on Z")
If the answer is fewer than 2-3 clear decisions per meeting, you're updating the board, not using them to make decisions.
What Works: Decision-First Board Updates
The teams with the most effective boards flip the structure: decisions first, context second.
Instead of building up to a decision through 30 slides of background, they start with:
What needs to be decided (go/no-go, resource allocation, strategic pivot)
What evidence informs it (the key data points, not every experiment)
What we're recommending and why
What we need from the board (approval, input, connections)
Everything else—the detailed timelines, budget actuals, org updates—goes in an appendix that board members can review if they want more detail.
Why this works:
Board members can focus their limited attention on the handful of decisions that actually matter, rather than trying to absorb 60 slides of context to figure out what you're asking them.
The One-Page Decision Log
The simplest tool the most effective teams use: a one-page decision log that tracks major program decisions over time.
What it contains:
Decision made: "Advance Compound A to IND-enabling studies"
Key evidence: "Target engagement >80% at 10nM, clean tox profile in 28-day study"
Confidence level: High / Medium / Low
Reversibility: Can we change course later if we learn something new?
Next proof point: "GLP tox complete by Q2"
Why this matters:
Six months later, when someone asks "Why did we choose Compound A over B?" you can answer in 30 seconds, not reconstruct three board meetings worth of discussion.
It also prevents relitigating decisions—the board can see what was decided, what evidence drove it, and what the next milestone is.
Evidence: What This Looks Like in Practice
A Phase 2 rare disease company was drowning in board prep—60-slide decks taking their leadership team 2-3 days to prepare every quarter.
What they changed:
Started each board meeting with a one-page summary:
3-4 decisions needing board input this quarter
Key evidence for each
Recommendation and rationale
What they needed from the board (approve, advise, connect)
The detailed slides went into an appendix. Board members could dive in if they wanted, but the meeting focused on the decisions.
What happened:
Board meetings went from 3 hours to 90 minutes. More importantly, the board started asking better questions—not "walk me through this assay" but "if this readout is inconclusive, what's your pivot plan?"
Their lead investor told them: "This is the first time I feel like I'm seeing the actual strategic choices, not just the highlight reel."
Two Other Shifts That Help
1. Pre-define what "good" looks like before you spend the money
Most teams share results without sharing the thresholds they were expecting to hit. This leads to debates like "is 60% target engagement good enough?" after the money's already spent.
What works better:
Before starting a study: "We need >70% target engagement at <50nM to advance. Below that, we pivot to backup compound."
After the study: "We hit 82% at 30nM. Decision: advance to next stage."
No debate needed—the threshold was agreed upfront.
2. Tag decisions as reversible vs. irreversible
Not all decisions deserve the same scrutiny. Some you can change later (choosing a CRO, adjusting trial site mix). Others you can't (dosing first patients, selecting lead candidate).
What this looks like:
Reversible decisions (Type 2): Make them fast with the core team, document in decision log, inform board after
Irreversible decisions (Type 1): Bring to board for input before committing, document thoroughly
Why this matters:
Type 2 decisions get bogged down in board meetings when they should be made quickly by the team. Type 1 decisions get rushed when they deserve more scrutiny.
Tagging them forces clarity about what actually needs board time.
How to Actually Do This
Step 1: Start with your next board meeting (2-3 weeks before)
Instead of starting with "what slides do we need?" ask:
What decisions do we need the board to make or bless?
What evidence do they need to feel comfortable with those decisions?
What can go in an appendix vs. needs to be discussed live?
Step 2: Create a simple decision log (1-2 hours)
For your lead program, document the last 3-4 major decisions:
What was decided
What evidence drove it
How confident were we
What's the next proof point
This becomes your template going forward.
Step 3: Test the new format at one board meeting
Lead with the decision log. Put detailed updates in appendix. See if the conversation improves.
What to watch for:
If board members keep asking for more detail that's in the appendix, you haven't given them enough context in the summary. If they're making decisions without needing to reference the appendix, you've nailed it.
What Good Looks Like
You'll know this is working when:
Board meetings get shorter (90-120 minutes instead of 3 hours)
More actual decisions get made and documented
Board members ask strategic questions instead of requesting more data
You spend less time on board prep because you're not rebuilding context from scratch each quarter
Most reliable signal: A board member says something like "This is the clearest picture I've had of where we are and what you need from us."
When This Doesn't Help
This approach works best for:
Phase 1+ companies (clear programs with decision points)
Boards that are engaged and want to add value
Teams drowning in board prep time
It's probably overkill if:
You're pre-IND with an advisory board (informal updates work fine)
Your board is already efficient and decision-focused
You only meet with your board 1-2 times per year
What Are You Seeing?
Are your board meetings productive decision forums, or update marathons? And if they feel like marathons, what's driving that—board dynamics, deck structure, something else?
Worth comparing notes.
—Roop
Run your first narrative review before quarter‑end