Evidence Briefing Packet¶
Briefing artifact — instantiates Consensus Convergence
A pre-circulated dossier that fixes what evidence the group will treat as credible and puts everyone on the same factual base before deliberation begins.
An Evidence Briefing Packet is the document handed to every participant before a decision, whose job is to level the factual playing field. It states the question on the table and assembles the evidence bearing on it — data, prior analyses, options, known unknowns — under an explicit standard for what counts as credible and relevant. Its distinctive move is pre-loading a shared, admissible evidence base, so that deliberation starts from the same facts rather than becoming a contest of who read what, who remembers which study, or who can invoke the most authority. It doesn't decide anything; it decides what the group is allowed to reason from.
Example¶
A school board is deciding whether to replace a district's reading curriculum — a fight that in the past has been won by whoever brought the most emphatic anecdote to the microphone. This time the superintendent circulates an evidence briefing packet a week before the meeting.
The packet opens with the decision question stated precisely — "Should the district adopt Curriculum X for grades K–2 starting next fall?" — and then lays out the evidence under a stated standard: peer-reviewed efficacy studies and the district's own pilot data are in; vendor marketing and single-classroom testimonials are flagged as low-weight. It includes the pilot's results with their confidence caveats, a cost comparison, and an explicit list of what isn't known (long-term retention, effects on the district's specific demographics). At the meeting, the argument is noticeably different: because everyone is working from the same base and the same rules about what counts, the board spends its time on the genuine open questions rather than relitigating whose anecdote is more moving. The packet didn't tell them what to decide — it told them what they were entitled to decide it on.
How it works¶
The packet's power is in constraint, applied before anyone speaks:
- It states the evidence standard up front. What sources count, at what weight, and why — so the meeting is not a contest of volume, status, or rhetorical force, and a compelling anecdote can't outrank a weak-but-relevant study by default.
- It fixes the question the evidence answers. Framing the decision precisely at the top keeps the evidence — and the group — pointed at one target.
- It surfaces the unshared and the unknown. Deliberately including information not everyone already holds, and an explicit list of open unknowns, counters the group's pull toward rehashing what it collectively already knows.
Tuning parameters¶
- Evidence bar height — how strict the admissibility standard is (peer-reviewed only, versus anything relevant flagged by quality). A high bar raises rigor but can exclude timely, imperfect signals; a low bar is inclusive but invites noise.
- Framing neutrality — whether options are presented even-handedly or the packet leads toward a recommendation. Neutral framing builds trust; a recommended option speeds decisions but risks anchoring.
- Depth versus digestibility — exhaustive dossier versus a tight brief. Depth is defensible but goes unread; brevity is read but omits.
- Unknowns disclosure — how prominently the limits and open questions are stated. Foregrounding them keeps the group honest about what the evidence can't settle.
When it helps, and when it misleads¶
The packet is most valuable when a group's disagreements are partly factual and would otherwise be settled by rhetoric, and when levelling the base changes who wins — it directly counters the hidden-profile problem, where groups over-discuss what everyone already knows and neglect the decisive information only one person holds.[1] Its danger is that whoever writes the packet controls the frame: the selection of evidence, the weighting standard, and the framing of options can quietly pre-decide the outcome while looking neutral, which is exactly how the mechanism gets run backwards to build a case for a choice already made. The discipline is to separate authorship from advocacy — have the packet compiled (or at least reviewed) by someone without a stake, disclose the admissibility rules and the unknowns openly, and let participants add evidence that meets the standard rather than only receive it.
How it implements the components¶
The packet is the archetype's evidence-leveling artifact; it fills the two components that set the informational ground:
evidence_standard— its core function: stating what counts as credible and relevant, at what weight, so convergence rests on a shared base rather than on rhetorical force.shared_question— it fixes and circulates the precise question the evidence is meant to answer, keeping the group's reasoning pointed at one target.
It does not run the discussion (deliberation_rule, facilitation_role — Facilitated Decision Meeting), track what stays disputed after the facts are shared (disagreement_map — Disagreement Register), or declare the decision closed (closure_rule — Consensus Vote).
Related¶
- Instantiates: Consensus Convergence — the packet supplies the shared, admissible evidence base the rest of the process reasons from.
- Sibling mechanisms: Facilitated Decision Meeting · Scientific Consensus Process · Consensus Vote · Consensus Workshop · Consent Decision Rule · Delphi Process · Disagreement Register · Minority Statement Protocol · Stakeholder Alignment Session · Standards Committee Process