CH-04 Team A and Team B
Has two teams each build the best case for a competing view and debate before a jury of peers, and produces competing papers and debate findings.
What it does
Two teams each build the best case for a competing view, then debate before a jury of peers. Artefact: competing papers and debate findings; read where the teams disagree on assumptions or evidence.
When to use it
Use when a long-standing dispute has two strongly held views and each needs a full, separate case.
When it does not fit
The issue is not significant enough to justify the resources.
Result format
The result has one paper from each team setting out the best case for its competing view, and the findings of the debate. It names the points where the teams disagree on assumptions or evidence.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Unit of analysis | Always applies | requires=claim |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Structure, Content type, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | Two or more strongly held competing views, two teams and a jury of peers. |
|---|---|
| Additional sources needed | comparator |
| Not for (rules) | stakes_tier=exploratory :: The issue is not significant enough to justify the resources |
| Not for (text) | The dispute is minor or recent, so that two teams and a jury cost more than the decision is worth. |
Choosing and ordering
| Kind of technique | Challenge technique, runs in step 6 |
|---|---|
| Phase tag | validate |
| Other phase tags | analyse |
| Kind of finding | contradiction; difference |
| Question answered | why; what |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | proceed with limit stated |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | assumption and limitation statement | none | no |
| decision-informing | assumption and limitation statement | none | no |
| decision-informing | independent review | needed; left out below high stakes | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | independent review | needed | no |
| high-stakes | expert review | needed | no |
| high-stakes | second technique with different assumptions | none | conditional |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Simulates both teams with one model so the two cases share the same assumptions and the debate adds no independent view. |
| Error sources | input data; coder or rater judgement; language model |
| Certainty limits | No effectiveness evidence found; the result depends on the jury and on the teams having separate evidence, and shared team assumptions lower certainty by risk of bias. |
Related techniques
- substitutes for CH-03 Devil's advocacy: Use when stakes_tier is high-stakes and both sides need a full case and not one adversary
- pairs with CH-10 Rapoport's rules (fair restatement of an opposing position) Also serves: Compare.: Fair restatement of the opposing position keeps the debate on the real disagreement
Evidence and tag basis
Documented. The CIA primer reserves it for long-standing disputes and distinguishes it from devil's advocacy; no effectiveness evidence found. (CIA Tradecraft Primer (2009))
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.