Murder-boarding the brief: anticipating the questions

Ask yourself the hard questions before the room does — and know, honestly, which one you can’t answer yet.

The idea

A murder board is a friendly firing squad: colleagues who grill your brief the way the real decision-maker will, so nothing lands as a surprise. The questions aren’t random — they cluster on stable axes: cost, risk, implementation, politics, what the opponents would say, and why now.

Prepare an answer plus evidence for each axis. Then tune for the specific leader — a CFO drills cost, a chief of staff drills politics. And where you genuinely don’t know yet, prepare an honest holding line: name the gap and how you’ll close it. That beats bluffing every time.

the interactive · prep, then get grilled

Your brief: consolidate three regional warehouses into one automated hub. Prep each axis, pick who’s in the room, then run the grilling.

skip nothing prepared · claim an assertion, no proof · proof claim backed by evidence · hold an honest holding line for a real unknown

prep time

0 / 9

against this leader

Choose a prep level for each axis. The gauge is your expected coverage — the share of questions you’ll field well.

In the room:

not started

Press run the grilling — or step through one question at a time.

Set your prep above. The gauge already forecasts how you’ll do against the CFO — then run the grilling to watch it play out, question by question.

How it works

Coverage on an axis is how solid your answer is; the leader’s angle is how often they press each axis. Readiness is just the two multiplied and summed — your expected share of questions handled. Your weak point is the axis they press hardest where you’re thinnest.

coverage:  skip 0.0  ·  claim 0.4  ·  hold 0.7  ·  proof 1.0

readiness = SUM( leader_weight[axis] x coverage[axis] )

Example vs the CFO  (weights: cost .32, risk .22, impl .16,
                     politics .08, opponents .10, why-now .12)
  cost      proof 1.0 x .32 = .320
  risk      proof 1.0 x .22 = .220
  impl      proof 1.0 x .16 = .160
  politics  skip  0.0 x .08 = .000   <- nothing prepared here
  opponents claim 0.4 x .10 = .040
  why-now   hold  0.7 x .12 = .084
  ------------------------------------------
  readiness = 0.82

exposure = axis with the largest  weight x (1 - coverage)
  politics   .08 x 1.0 = .080   (largest -> your weak point)
  opponents  .10 x 0.6 = .060
  why-now    .12 x 0.3 = .036
  -> politics is the neglected axis this leader will find

When to use it

Reach for a murder board when…	The trade-off
You’re briefing up: a decision review, board paper, launch go/no-go.	It costs colleagues’ time — reserve it for high-stakes rooms, not routine updates.
The decision is contested or the audience is skeptical.	A friendly board can be too friendly; recruit someone who will actually attack it.
You have time to prepare evidence, not just talking points.	Prep time is finite — the budget above forces you to choose where to go deep.

Watch out for

Prepping only your favorite axis. Engineers over-prep implementation; strategists over-prep the vision. The room finds the axis you find boring — usually cost or politics.
Assertions without evidence. “It’ll save money” invites “how much, by when, versus what baseline?” A claim you can’t back is worse than one you didn’t make.
Bluffing a gap. Inventing an answer on the spot is how credibility dies. A prepared holding line — “we don’t have that yet; here’s how we’ll know by Friday” — keeps trust intact.
Ignoring ‘what would opponents say.’ If you can’t state the strongest case against your brief, you haven’t pressure-tested it — and someone in the room has.
A too-gentle board. If the mock grilling was comfortable, it failed. Pick reviewers who’ll channel the actual decision-maker’s meanest question.

Worked example

An interviewer says: “You’re presenting the warehouse consolidation to the exec team tomorrow. How do you prepare?” A strong answer names the six axes and then tunes: “The CFO chairs this, so I’d go deepest on cost — all-in capex, payback, and the sensitivity if volumes drop — with a one-page model as evidence. Risk and implementation next. But the axis I’d normally under-prep is politics: three regions each lose a warehouse and some headcount, so I’d name who loses, how loud they’ll be, and my mitigation. On the data-migration cutover I don’t yet have a tested rollback, so I’d say that plainly and commit to a dry-run date — a holding line, not a bluff.” That answer shows the interviewer you red-team yourself, not just your slides.

Check yourself

The leader asks about a number you genuinely don’t have yet. Best move?

You have limited prep time and a CFO-chaired review. Where should the last hour go?