The gate, restated
VERIDEX Gate 22 reads, in its canonical form: the Decision-Maker Briefing is separated from the analysis it summarises. The note exists because that sentence does more work than its length suggests.
Why the separation matters
A briefing that lives inside the analysis is, structurally, a summary. The reader treats it as a paragraph in a longer document; the briefing’s recommendations sit alongside the analysis’s hedges; the boundary between what the analyst found and what the principal should do dissolves.
A briefing that lives separately from the analysis is, structurally, a decision artefact. It is a document the principal can take into the room where the decision is made, refer to during the conversation, and return to later as the auditable record of what was recommended on what evidence.
The two artefacts are different objects. The gate enforces the separation.
What the separation produces, in practice
Three behaviours flow from the separation.
- The Briefing is finite. A separated Decision-Maker Briefing typically runs one to three pages. The constraint forces the firm to identify the load-bearing recommendation rather than letting it diffuse across the analysis.
- The Briefing names the question. Because the Briefing is a stand-alone artefact, it must restate the development question that the analysis answered. The principal reading the Briefing two months later does not have to find the analysis to remember what was being asked.
- The Briefing names the counterfactual. Per Gate 16, every recommendation pairs with at least two named alternatives that were rejected. In a separated Briefing the alternatives are explicit; in an embedded summary they tend to dissolve.
What the separation does not produce
The separation does not produce a Briefing that disagrees with the analysis. Per Gate 14, Impact ↔ Risk consistent, the Briefing must be quantitatively reconcilable with the analysis it summarises. The separation is structural, not editorial.
The shape of a Decision-Maker Briefing
A separated Decision-Maker Briefing has, in the firm’s working form, six fields. The fields are visible inline in the Ghana case at /case-studies/ghana-market-entry/interactive/.
| Field | What it carries |
|---|---|
| The question | The development question, restated. |
| The recommendation | The recommended pathway, with its scoring. |
| The counterfactual | The alternative paths, costed. |
| The constraints | The binding regulatory or capital constraints. |
| The integrity stack | The gates the analysis cleared. |
| The reference | The path back to the full analysis. |
The six fields are not an editorial template. They are the minimum set that lets the principal use the artefact as an audit-defensible decision artefact.
Why the gate exists at all
Most analytical work, in the firm’s reading of the field, suffers the same pathology: the analyst’s recommendation is buried inside a long document, hedged with caveats that protect the analyst more than they inform the principal. The reader leaves the document unsure what they were told to do.
Gate 22 exists to refuse that pathology by structural means. A separated Decision-Maker Briefing cannot hedge into oblivion because its length forbids it.
Cross-references
- The full gate enumeration. /methodology/validation/
- A reader’s guide to all twenty-two gates. /library/twenty-two-gates/
- A working Decision-Maker Briefing, embedded. /case-studies/ghana-market-entry/interactive/#s08