Speak-Truth-to-Power Escalation Rule
Escalate consequential bad ideas before institutional momentum protects them
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 98%
The Speak-Truth-to-Power Escalation Rule starts from a hard institutional lesson: obviously bad proposals do not always die naturally. A professional who identifies material harm first tests the evidence, understands the decision path, and formulates both a clear objection and a workable alternative. The concern should be delivered directly to the person with authority, using language calibrated to be heard without softening the underlying truth. If normal channels fail and the potential damage is severe, the professional escalates more forcefully rather than mistaking initial disagreement for completed responsibility. Seniority increases this duty because experienced people better understand consequences and possess greater access. The output is timely, proportionate, documented dissent that improves the decision and protects the institution from avoidable momentum.
Origin
Jack Divine drew this rule from regretting that he did not oppose the Iran-Contra proposal more forcefully when normal expectations suggested the bad idea would die. Extracted from Masters in Business.
Core principles
- 01Bad ideas can survive despite appearing obviously flawed
- 02Seniority creates a duty to voice consequential dissent
- 03The intensity of escalation should match the potential harm
- 04Candor is more effective when phrased for the recipient to hear
- 05Responsible dissent can strengthen rather than destroy a career
How to run it
- 1
Assess the stakes
Identify the likely harm, reversibility, affected parties, and urgency. Distinguish consequential risk from ordinary disagreement.
Pro tip Write the feared outcome in one testable sentence.
Watch out Constant escalation over minor issues weakens credibility when a serious warning is needed.
- 2
Verify the objection
Check facts, assumptions, policies, and relevant history. Seek informed challenge so personal preference is not mistaken for institutional danger.
Pro tip Ask a trusted skeptic to attack your reasoning before you escalate.
Watch out Do not delay indefinitely in search of perfect evidence when the decision is imminent.
- 3
Offer an alternative
Pair the warning with a safer path that still addresses the decision-maker's objective. Explain trade-offs candidly.
Pro tip Make the alternative easier to adopt than simply rejecting the proposal.
Watch out An objection without a viable path forward may be dismissed as obstruction.
- 4
Speak directly and carefully
Tell the responsible leader what is wrong, why it matters, and what should change. Phrase the message so the recipient can absorb it without losing the substance.
Pro tip Lead with the shared mission and concrete consequence, not an attack on judgment.
Watch out Excessive politeness can make a critical warning sound optional.
- 5
Escalate proportionately
If the idea survives and the potential harm is serious, use the next appropriate channel and increase the clarity of the warning. Match persistence to stakes.
Pro tip Decide your escalation ladder before pressure peaks.
Watch out Assuming someone else will stop the proposal repeats the original failure mode.
- 6
Document and remain accountable
Record the evidence, warning, response, and final decision. Continue supporting lawful institutional work while remaining honest about unresolved risk.
Pro tip Update the record when new evidence changes your assessment.
Watch out Documentation should preserve accountability, not become a tool for retaliation or self-protection alone.
In the wild
Divine believed the Iran-Contra proposal was a bad idea and did object, but later concluded that he should have escalated much more forcefully. His earlier career experience had taught him that most bad ideas died naturally; this one did not.
→ The episode became his lasting lesson that recognizing danger is insufficient when the stakes require stronger escalation.
A senior engineer finds that a planned launch could expose customer data. After verifying the flaw, she proposes a short delay and a contained migration, briefs the product leader directly, and escalates to the risk committee when the launch remains scheduled.
→ The release is paused, the vulnerability is fixed, and the warning includes a practical route to launch safely.
Common mistakes
Assuming the system will stop it
Normal reviews eliminate many weak proposals, but relying on that pattern can allow one consequential exception to proceed.
Making dissent personal
Attacking the proposer triggers defensiveness and obscures the institutional risk. Focus on evidence, consequences, and alternatives.
Treating one warning as enough
A quiet objection may not discharge the responsibility created by seniority and severe foreseeable harm.
Is it for you?
Best for
It is best for experienced professionals confronting high-consequence proposals inside hierarchical organizations.
Not ideal for
It is not a license to escalate every preference dispute or bypass routine collaboration over low-stakes decisions.
From the transcript
“no bad idea dice and washing.”
“when you see a bad idea, stand up.”
“It's a responsibility at a certain level in in all institutions to uh speak truth to power.”
From the episode
Jack Devine Talks About the FBI and CIA