The board meeting is one of the most high-stakes communication contexts in a VP or executive's professional life, and for most leaders it's also the one with the least practice. A typical VP presents to the board three or four times per year. Each session is different. The feedback afterward, if it exists at all, is filtered through the CEO and tends to be general. There is almost no mechanism for a VP to develop board-level communication as a deliberate skill.
The board challenge simulation is Coachvyne's most-used scenario, and the design choices behind it are worth explaining in detail — both what we built and why, and what the data from the first set of sessions tells us about where VP-level leaders most consistently break down.
The Design Intent: Replicating Real Pressure, Not a Friendly Q&A
A board Q&A has several characteristics that make it genuinely difficult as a communication context. The questioner typically has more contextual authority than the person presenting, even if they have less operational knowledge. The questions often contain embedded assumptions or frames that, if accepted uncritically, put the presenter in a weak position. The data in the room is incomplete by design — boards see a curated view of the business, not the full operational picture. And the stakes of appearing uncertain or evasive are high in a way that peer-level conversations are not.
We built the board challenge simulation to replicate each of these characteristics. The simulated board member does not ask softball questions. They challenge the strategic rationale of the plan being presented. They point to apparent inconsistencies in the numbers. They ask "why not the alternative approach?" in ways that make clear they've considered it seriously. They push back when an answer seems incomplete.
This is intentionally uncomfortable, and some leaders find the first session jarring. We've had VPs tell us that the simulation felt more adversarial than their actual board interactions. In a few cases that's probably true — some boards are genuinely collegial. But in our view, preparing for the harder version is the right calibration. A VP who can perform well in the simulation will find the real board meeting easier by comparison, not harder.
The Scenario Structure
A standard board challenge session runs 18–22 minutes and includes three phases.
The first phase is a brief setup: the VP is given a one-page brief describing the strategic or operational situation they're presenting on. This might be a Q2 results review with a revenue miss, a request to approve a new market entry investment, or a post-mortem on a product launch that underperformed. The brief is intentionally incomplete — it provides the key numbers and context but leaves some questions unanswered, mimicking the real experience of walking into a board meeting having prepared as well as possible but knowing that questions will surface things you didn't anticipate.
The second phase is the presentation itself, which the VP delivers in whatever format they choose. There's no slide deck in the simulation — the VP has to structure and deliver the narrative verbally. This is a deliberate design choice. Visual aids can mask narrative gaps. A VP who relies on well-designed slides to do the organizational work of their presentation will often discover in a verbal format that the underlying logical structure is weaker than they realized.
The third phase is the Q&A challenge. The simulated board member asks five to seven questions in sequence, each one following from the VP's previous answer. The questions are generated dynamically based on what the VP said — they're not a fixed script. This is where most of the scoring signal comes from.
What We Score in the Challenge Phase
The board challenge scenario is a high-signal context for six of the twelve dimensions: Narrative Coherence, Accountability Framing, Decision Under Uncertainty, Directness Under Social Pressure, Emotional Regulation, and Prioritization Logic.
Narrative Coherence is the most broadly informative. The board challenge is one of the few scenarios where narrative gaps become immediately apparent — a board member who follows up with "wait, but you said X in your opening statement, which seems inconsistent with the number you just cited" puts the VP in a position where they have to either hold the coherence of their position or acknowledge and repair the gap. Both are valid responses; incoherence is not.
Accountability Framing shows up consistently in board challenge scenarios involving financial or operational misses. The scoring signal is whether the VP articulates a clear causal chain: what decision led to what outcome, who owned that decision, and what changes as a result. The failure mode is the passive voice — "revenue was below target because of market conditions" gives a board member almost no useful information and no confidence that the situation is being managed.
Decision Under Uncertainty becomes a scoring dimension when the board member asks the VP to defend a strategic direction with incomplete data. High-scoring responses acknowledge the uncertainty explicitly, identify what data would change the decision, and make a defensible call given what's known. Low-scoring responses either overclaim certainty or defer entirely — "we'll have better data next quarter" is not an answer to "why are we making this investment now."
Where VP-Level Narrative Breaks Down
The pattern we see most often in the first session is what we'd call the authority collapse: a VP who presents with confidence and clarity in the opening phase but whose narrative begins to fragment under sustained challenge. The fragmentation typically follows a predictable sequence. The board member asks a challenging question. The VP gives a clear initial answer. The board member follows up with a sharper version of the same challenge. The VP's answer becomes longer and less structured. By the third iteration, the VP is providing a lot of information but no coherent position.
This isn't a knowledge problem — the VP usually has the information needed to answer well. It's a structural problem: the VP hasn't internalized a clear enough narrative architecture to defend their position under pressure without the scaffolding of slides or bullet points. They know what they believe, but they haven't practiced articulating it in a form that holds together when challenged three times in a row.
A specific pattern we saw in early sessions: a VP at a mid-size technology company presenting Q3 results in a simulation where revenue had missed target by 11%. Their opening narrative was solid — clear on what happened, clear on the cause, clear on what had changed operationally as a result. But when the simulated board member challenged the adequacy of the operational changes ("that sounds like a patch, not a fix to the underlying problem"), the VP's response became defensive and increasingly granular. Four minutes of detailed explanation of the sales process changes, without ever returning to the high-level frame of why the changes were sufficient. The board member's concern — is this actually fixed? — was never directly addressed.
The debrief on that session pointed to one specific repair: when challenged on the adequacy of a response, acknowledge the challenge first, then restate your position explicitly, then support it. Don't lead with the support. That ordering difference sounds small but changes the way the response lands significantly.
What the Data Has Taught Us About Board Readiness
After running a meaningful number of board challenge simulations, a few findings stand out. First, the correlation between a VP's confidence rating of their board communication skills (self-assessed before the session) and their actual simulation scores is low. Leaders who rate themselves highly tend to have done enough real board work that they've stopped noticing their weak patterns — they've adapted around them. The simulation surfaces what adaptation has concealed.
Second, Emotional Regulation and Narrative Coherence are the most divergent dimensions in board challenge scenarios — meaning it's very common to score well on one and poorly on the other. A VP who stays calm under pressure but loses structural clarity in their answers is a different coaching target than a VP who maintains perfect logical structure but whose visible anxiety gives the board less confidence than the content warrants. The development work for these two profiles is completely different, which is exactly why dimension-level scoring matters more than an aggregate rating.
Third, and perhaps most importantly for L&D directors designing development programs: board readiness is not a C-suite-only skill. The VPs we see in board challenge simulations are typically not presenting to boards regularly — but they will be, as they're promoted or as their companies grow. The gap between their current capability and what a board context requires is often larger than they realize, and the time to develop it is before they're in the room, not during.
We're not suggesting every VP needs to master board communication to be effective. Many VP roles have limited board exposure. But for leaders who are on a path toward the C-suite or toward roles at smaller companies where board interaction is regular, the board challenge simulation is one of the clearest indicators of readiness — and the gaps it surfaces are highly specific and developable with targeted practice.