When to use it
Use when the team is too aligned, when a high-stakes decision is difficult to reverse, or when an idea has survived internal review but hasn't faced genuinely critical perspective.
Essential in The Test when you need to know if your proposal can survive real scrutiny.
How it works in The Studio
Here's how a session works with WAiDE:
Sample output
Here's what a Devil's Advocate session looks like in practice:
What you get
Set of sharpest objections — each either reveals a genuine weakness to address, or (if rebutted convincingly) strengthens confidence. Goal: more robust idea, not defeated one.
Foundation
Formalised in the Catholic Church's canonisation process in the 13th century by Pope Gregory IX. Widely used as a strategy and military red-team technique. Taught at Harvard Business School, INSEAD, and the US Department of Defense.
Why it works
The Devil's Advocate role was formalised by the Catholic Church in the 13th century as the Advocatus Diaboli — a designated official whose job was to argue against canonisation, regardless of personal belief. The insight behind the role is profound: institutions make better decisions when someone is structurally required to oppose, not merely permitted to. Without a formal challenger, groups drift toward confirmation bias and social pressure to agree.
In business contexts, the framework addresses what psychologists call motivated reasoning — the tendency to evaluate evidence in ways that confirm existing preferences. When everyone in a room wants the plan to work, the brain unconsciously filters out disconfirming signals. A designated Devil's Advocate creates a permission structure that makes critique socially safe, separating the act of challenging from the person doing it.
Amazon's "Disagree and Commit" culture, the US military's Red Team doctrine, and McKinsey's "obligation to dissent" all descend from the same insight: structured adversarialism produces better outcomes than polite consensus. The protocol works because it externalises the challenge — the Devil's Advocate isn't being negative, they're performing a structural role. This frees others to engage with the criticism rather than defend against the person raising it.
The mechanism: Devil's Advocate doesn't destroy good ideas — it stress-tests them. An idea that survives rigorous challenge is stronger for having survived. An idea that collapses under challenge needed to collapse before it cost you anything real.
Frequently asked questions
Won't this just produce a demoralising attack on our idea?
Only if done wrong. The key distinction is that the Devil's Advocate role is explicitly temporary and structural — it's a protocol, not a person's opinion. WAiDE frames the session as stress-testing rather than attacking, and the second phase always asks which objections are genuine weaknesses versus which can be confidently rebutted. The goal is a stronger idea, not a defeated team.
What's the difference between Devil's Advocate and Pre-Mortem?
Pre-Mortem imagines a future failure and asks what caused it — it's primarily about identifying operational risks. Devil's Advocate challenges the logic and assumptions of the strategy itself, asking whether the reasoning holds up under scrutiny. Pre-Mortem is execution-focused; Devil's Advocate is strategically focused. They work powerfully in sequence: Devil's Advocate first to stress-test the plan, Pre-Mortem second to anticipate implementation failures.
What if the Devil's Advocate finds a flaw we can't answer?
That's the best possible outcome of the session — far better than discovering the flaw after commitment. An unanswerable objection either reveals a genuine weakness that needs addressing before proceeding, or it identifies an assumption that needs testing. WAiDE will help you distinguish between a fatal flaw and a solvable problem, and translate the finding into a specific next action.
Can I use this on a decision that's already been made?
Yes — and it's often most valuable then. If a decision has been made but not yet fully acted on, a Devil's Advocate session can surface implementation risks and assumption gaps before resources are deployed. It requires psychological safety to challenge a plan with existing momentum, which is exactly why the formal role structure helps: it's the protocol challenging the plan, not a dissenting individual.