Use when a group or individual is converging on a conclusion and about to commit to it — before an irreversible decision, a major bet, or locking in a plan — to deliberately construct and test the strongest case against the prevailing consensus view, rather than assuming early agreement means the view is correct.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill apply-devils-advocate-technique --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Apply Devils Advocate Technique?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-apply-devils-advocate-technique)More formats (shields.io, HTML) on the badges page.
---
name: apply-devils-advocate-technique
description: Use when a group or individual is converging on a conclusion and about to commit to it — before an irreversible decision, a major bet, or locking in a plan — to deliberately construct and test the strongest case against the prevailing consensus view, rather than assuming early agreement means the view is correct.
source: 'Irving Janis "Victims of Groupthink" (1972) and "Groupthink" 2nd ed. (1982) — case-study contrast between the Bay of Pigs decision (groupthink symptoms present, no antidotes) and the Cuban Missile Crisis ExComm process (antidotes applied — designated devil''s advocate, outside-expert consultation, independent subgroups, a second-chance meeting before final commitment); CIA "Team B" competitive analysis exercises; U.S. Intelligence Community "Structured Analytic Techniques" tradecraft standard'
tags: [critical-thinking, groupthink, decision-making, dissent, consensus, cognitive-bias, red-teaming]
related: [apply-clinamen-deviation-technique, apply-adversarial-verification, apply-constructive-dissent, apply-premortem, apply-mental-models-framework, apply-perspective-triangulation, apply-reference-class-forecasting]
---
# Apply Devil's Advocate Technique
Before committing to a conclusion the group (or you) has converged on, deliberately construct and stress-test the strongest available case against it — treating early agreement as a signal to check for groupthink, not as evidence the view is correct.
**Disclaimer:** This is a decision-making and critical-thinking technique for groups and individuals, not psychological treatment or diagnosis. If group conflict or dissent-suppression is tied to a broader pattern of workplace harassment, bullying, or psychological harm, consult a licensed mental health professional or HR/organizational specialist rather than relying on this technique alone.
## Why This Is Best Practice
**Adopted by:** Janis's own case-study pairing is the founding evidence: the Kennedy administration's Bay of Pigs planning showed classic groupthink symptoms (illusion of unanimity, self-censorship, no real dissent) and failed; the same administration's Cuban Missile Crisis ExComm process — restructured on Janis's antidotes, with Robert Kennedy explicitly assigned the devil's-advocate role, outside experts consulted, and independent subgroups deliberating before a final "second-chance" meeting — succeeded. The CIA's "Team B" competitive analysis exercises and the U.S. Intelligence Community's "Structured Analytic Techniques" tradecraft (which formally mandates devil's-advocacy and "what if I'm wrong" techniques before high-stakes assessments) both codify the same antidotes as standard practice.
**Impact:** Janis's paired case studies remain the standard cited evidence in political science and organizational-behavior curricula (widely taught in MBA and organizational-psychology programs) for the measurable difference between converged-but-untested group decisions and decisions that survived a structured internal challenge before commitment.
**Why best:** This targets a different failure mode than its closest neighbors. `apply-clinamen-deviation-technique` injects bounded randomness to escape a stale creative rut — it isn't testing a specific converged belief, and its own scope explicitly excludes high-stakes/compliance decisions, which is exactly where this technique is most needed. `apply-adversarial-verification` defends against an external party motivated to mislead you; this defends against internal premature closure on the group's or one's own belief, where no one is lying — everyone genuinely agrees, which is precisely the danger. `apply-constructive-dissent` is a standing culture built across all decisions over time; this is a discrete procedure applied at the single moment just before commitment, the same altitude as `apply-premortem`. The finance-specific contrarian skills (`apply-contrarian-sentiment-timing`, `apply-variant-perception-strategy`, `apply-non-consensus-category-conviction`) require a checkable market price or data point to diverge from; this applies to any converged belief, financial or not.
Sources: Janis, *Victims of Groupthink* (1972); Janis, *Groupthink* 2nd ed. (1982); CIA Team B exercises; U.S. Intelligence Community Structured Analytic Techniques.
## Steps
1. **Detect convergence before it hardens into commitment.** Watch for the groupthink symptoms Janis documented: an illusion of unanimity, self-censorship of doubts, direct pressure on dissenters to conform, and a shared assumption that disagreement itself would be disruptive. Convergence this fast, especially on a high-stakes or irreversible decision, is the trigger to apply this technique — not a sign the decision is already sound.
2. **Assign the devil's-advocate role explicitly, to a specific person.** Diffuse, informal "does anyone disagree?" invitations reliably produce silence per Janis's research. Name one person (rotate the role across decisions) whose explicit job is to build the strongest case against the consensus view, not just voice mild doubts.
3. **Build the actual case against the consensus, not a token objection.** The devil's advocate must construct a real, substantive argument for why the prevailing view could be wrong — what evidence is being discounted, what alternative explanation fits the same facts, what the consensus view assumes without justification.
4. **Bring in genuinely outside perspective.** Consult someone outside the group who has no stake in the group's prior discussion, per the ExComm precedent — an internal team that has spent hours converging is a poor judge of its own blind spots.
5. **Deliberate in independent subgroups before merging.** Where the decision is significant enough, split into separate subgroups that reach conclusions independently before reconvening — this prevents the first vocal opinion from anchoring the whole group's discussion.
6. **Hold a second-chance meeting before final commitment.** After apparent agreement is reached, schedule one more meeting whose sole purpose is to express any remaining doubts or reservations, per Janis's ExComm account — treat lingering silence in this meeting as more informative after this structure than it would be without it.
7. **Update the decision only if the case against holds up — don't discard it reflexively.** The goal isn't manufactured disagreement for its own sake; if the devil's-advocate case is weak once actually tested, proceed with the original consensus, but with the added confidence that it was actually tested rather than merely unopposed.
## Rules
- Assign the devil's-advocate role to a specific named person — an open invitation for dissent reliably produces silence in a group that has already converged.
- The case against consensus must be substantive, not a token objection raised and dropped — build it out enough to actually stress the prevailing view.
- Reserve this for decisions where the stakes justify it — significant, hard-to-reverse commitments — not routine low-stakes choices where the overhead isn't worth it.
## Examples
**Trigger:** A leadership team has quickly agreed on a major acquisition and momentum is building toward signing.
→ Detect the fast convergence as the signal, not reassurance. Assign one executive the explicit devil's-advocate role to build the strongest case the deal is a mistake. Bring in an outside advisor with no stake in the internal discussion. Hold a second-chance meeting after the "final" decision meeting, specifically to surface any remaining doubts before signing.
**Trigger:** An engineering team has unanimously agreed on an architecture after one meeting, with no dissent raised.
→ Fast unanimous agreement on a significant, hard-to-reverse choice (not a token check-in) is exactly the pattern this technique targets. Name someone to build the real case for the alternative architecture the team rejected, rather than accepting silence as validation.
## Common Mistakes
- **Treating "no one objected" as evidence the decision is sound.** Janis's research shows self-censorship, not absence of doubt, is what produces group silence — silence is not validation.
- **Assigning devil's advocate informally or diffusely ("anyone want to push back?").** Without a specific named owner, the role reliably goes unfilled.
- **Discarding the devil's-advocate findings as disloyalty rather than input.** If the challenge is treated as a loyalty problem rather than a genuine test, the role stops producing real dissent and becomes theater.
- **Applying this to every decision regardless of stakes.** Overuse on low-stakes, reversible choices burns goodwill and turns the technique into procedural noise rather than a signal that a decision deserves real scrutiny.
## When NOT to Use
- Low-stakes, easily reversible decisions where the cost of structured challenge exceeds the cost of occasionally being wrong.
- Genuine emergencies requiring immediate action, where the delay imposed by outside consultation and a second-chance meeting isn't available.
- As a substitute for actually building organizational psychological safety (`apply-constructive-dissent`) — this technique structures a single decision point; it doesn't fix a culture where dissent is punished the rest of the time.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!