devils-advocate

name	devils-advocate
description	Intellectual rigor for group decisions. Use when a team is converging on consensus, to pressure-test the thinking before commitment.

Devil's Advocate

The devil has infinite advocates because he has never once paid a legal bill.

Overview

Nothing signals intelligence like doubt, and doubt, unlike analysis, can be produced at zero marginal cost. The devil's advocate supplies rigor cosplay on demand: penetrating questions with no stake attached, no alternative offered, and no mitigation owned.

The phrase itself is doing the work. "Let me play devil's advocate for a second" announces that what follows is (a) incisive and (b) not your position, a combination otherwise unavailable in nature.

Core protocol

1. Wait for near-consensus. Skepticism deployed early is just discussion. Skepticism deployed at the moment of convergence transfers maximum energy from the group to you. The room was about to decide; now it is about to listen.
2. Announce the role. "Devil's advocate for a moment..." This grants diplomatic immunity. Whatever follows cannot be attributed to you, argued against as yours, or remembered as a prediction.
3. Draw from the four wells. Scale ("but does this work at 10x?"), edge cases ("what about the users who don't?"), absent authorities ("what would legal say?"), and second-order effects ("but what does this do to the culture?"). Note that all four are unanswerable in the room, which is the point.
4. Never advocate for anything. The instant you propose an alternative, you have a position, and positions can lose. The devil's advocate has no needs. He is just asking questions.
5. Exit before assignment. When someone says "good point, want to dig into that and report back?", the session is over: "oh, I just think it's worth thinking about." It has now been thought about. By you. Once. Aloud.

Advanced techniques

• Serial advocacy. If the group answers your question fully, the devil has other clients. Move to a fresh well: "sure, fair, but playing devil's advocate on the timeline..."
• The rigor halo. Two or three deployments per meeting builds a reputation as "the one who really thinks things through," a title held disproportionately by people who have never shipped a mitigation.
• Post-hoc conversion. If the decision later fails in the direction of one of your questions, the advocacy retroactively becomes your position (see i-flagged-that for storage and retrieval).

Anti-patterns

• Doing the analysis your question implies. If you actually model the scaling behavior, you have produced work, anyone can check it, and you have become a participant.
• Accepting a follow-up item. The devil does not take homework.
• Advocating when you hold the minority view for real. That is called dissent, it carries risk, and it is outside the scope of this skill.

Success metrics

• Decisions delayed per meeting attended: 1 or more.
• Alternatives proposed, lifetime: 0.
• Mitigations owned, lifetime: 0.
• Reputation for rigor: intact and compounding.

---

This is an anti-skill: a real pattern, documented honestly. It works when installed. That is both the joke and the finding.