Structured thinking and communication using Minto Pyramid (SCQA), BLUF, MECE issue trees, Six Thinking Hats, first principles, steel manning, OODA loop, and Socratic questioning. Adapts to context: writing memos uses Minto/BLUF, decomposing problems uses MECE/issue trees, making decisions uses OODA/Eisenhower, evaluating arguments uses steel manning/Socratic method. Use when organizing thoughts, writing proposals, decomposing problems, or making decisions.
Each framework here is a tool, not a religion. The point is to catch what unstructured thinking misses. Pick the framework that fits the problem. Combine them when useful. Drop them when they get in the way.
Barbara Minto developed this at McKinsey in the 1960s. The core insight: readers absorb information top-down, so communication should be structured answer-first, with supporting logic beneath.
Situation — Establish shared context. What does the audience already know and agree with? Non-controversial setup. Keep it short.
Complication — What changed? What went wrong? What tension exists? The complication is why you're communicating at all.
Question — The complication raises a natural question in the reader's mind. Sometimes explicit, sometimes implied. It bridges from "here's the problem" to "here's what to do."
Answer — The recommendation or key message. This goes at the top of the actual document, even though it comes last in the narrative logic. SCQA is for developing the argument; the pyramid is for it.
[Answer / Key Message]
/ | \
[Argument 1] [Argument 2] [Argument 3]
/ \ / \ / \
[Evidence] [Evidence] [Evidence] [Evidence]
Each level answers "why?" or "how?" for the level above. Arguments at the same level must be:
From U.S. military communication doctrine (AR 25-50). Messages get interrupted, radios cut out, people get pulled away. The most important information comes first because it might be the only thing read.
Bottom Line — The single most important thing the reader needs to know. One to two sentences. The decision, finding, or request.
Background — Enough context for the bottom line to be intelligible. Not a history lesson.
Supporting Details — Evidence, analysis, data, caveats. Readers who need it will read it. Readers who trust the bottom line can stop.
Action Required — What needs to happen, by whom, by when. If no action is required, say so explicitly. Ambiguity about next steps is the most common failure mode in professional communication.
Complementary, not competing. BLUF is a communication habit — lead with the conclusion. Minto is a structure for building the logic beneath that conclusion.
MECE (Mutually Exclusive, Collectively Exhaustive) is a decomposition principle. Parts should not overlap (mutually exclusive) and should cover everything (collectively exhaustive). Nothing falls through cracks, nothing gets double-counted.
Start with the core question. Frame it precisely. "Why is revenue declining?" is better than "What's wrong with the business?"
Decompose into MECE branches. At each node: do these branches overlap? Is anything missing? Each branch should be testable or answerable independently.
Go deep enough to be actionable. A branch is done when it points to something you can investigate, measure, or act on. If it's still abstract ("improve operations"), decompose further.
Well-known decompositions that are MECE by construction:
Edward de Bono's framework for parallel thinking. Most group discussions fail because people argue from different modes simultaneously — one person is creative while another is critical. The hats force everyone into the same mode at the same time.
White Hat — Facts and Information. What data do we have? What do we need? Neutral, objective. No interpretation, no opinion.
Red Hat — Feelings and Intuition. Gut reactions, legitimized without requiring justification. "This feels risky" is valid. The point is surfacing intuitions that get suppressed in "rational" discussion.
Black Hat — Caution and Critical Judgment. What could go wrong? Risks, weaknesses, flaws. The most natural hat for many people and the most overused. Valuable, but only as one mode among six.
Yellow Hat — Optimism and Benefits. Advantages, upside, best case. Counterweight to black hat. Forces consideration of opportunity, which critical thinkers often skip.
Green Hat — Creativity and Alternatives. Unconventional options, new ideas. Quantity over quality. No criticism allowed — that's what black hat is for.
Blue Hat — Process and Meta-thinking. What are we trying to accomplish? What hat next? Are we making progress? Manages the thinking process itself. Typically worn by the facilitator.
For evaluating a proposal:
Flexible: for creative problems, start with green. For risk-heavy decisions, spend more time in black and yellow.
Reasoning from fundamental truths rather than by analogy. Most thinking is analogical: "this worked before" or "everyone does it this way." First principles strips away assumptions to find what's actually true, then builds up from there.
Step 1: Identify assumptions. What do you believe about the problem? Be explicit. "We need a database" is an assumption. "Users want a mobile app" is an assumption. Most assumptions are invisible until deliberately surfaced.
Step 2: Break down with "why?" chains. For each assumption: why do we believe this? Evidence or convention? Keep asking until you hit something demonstrably true or clearly unexamined.
Example:
Now the problem is reframed: maybe the answer isn't hiring but paying down debt.
Step 3: Separate real constraints from assumed constraints. Real: laws of physics, legal requirements, available budget. Assumed: "we've always done it this way," "the team won't accept that." Challenge every assumed constraint.
Step 4: Reconstruct from fundamentals. Starting from only what's demonstrably true and actually constrained, what's the best solution? This often looks nothing like the conventional approach.
Analogy is faster and usually good enough for well-understood problems. First principles is expensive. Reserve it for when the conventional approach seems wrong, stakes justify the effort, or genuinely novel solutions are needed.
The opposite of straw manning. Instead of weakening an opposing argument, strengthen it to make it as hard as possible to defeat.
Step 1: Understand the opposing position thoroughly. Read the strongest advocates, not the weakest defenders. Arguing against microservices? Read the best case for them, not a regret blog post.
Step 2: Identify the strongest version. Best evidence, most compelling logic, strongest examples. Construct it as the most capable proponent would — including preemptive responses to obvious objections.
Step 3: Apply the endorsement test. Would a thoughtful advocate recognize and endorse your characterization? If they'd say "that's not what I mean," the steel man isn't strong enough. Refine until they'd say "yes, exactly — maybe better than I'd put it myself."
Step 4: Respond to the strongest version. If you can defeat the steel man, you've addressed the real argument. If you can't, you've learned something valuable.
It forces genuine engagement instead of performative refutation. It often reveals the opposing position has merit. It builds credibility. It prevents the false confidence of defeating a straw man.
Colonel John Boyd developed this for fighter pilot decision-making. It applies broadly to any competitive or fast-changing environment.
Observe — Gather raw information. What's happening? What signals are present? Observe broadly before narrowing focus.
Orient — The critical phase. Raw observations become understanding, shaped by:
Boyd considered orientation most important because it determines how you interpret observations and what options you consider. Two people can observe the same facts and orient completely differently.
Decide — Select a course of action. This is a hypothesis: "given our understanding, this action should produce this result."
Act — Execute. Then immediately begin observing results, feeding back into the next loop.
Orientation is where biases live, where mental models help or hinder. The most common failure: observing new information but orienting with old models — seeing evidence the plan isn't working but interpreting it as "we just need more time."
Boyd's insight: the fighter who cycles through OODA faster gains a compounding advantage. Each action creates a situation the slower opponent hasn't oriented to. In non-combat contexts: iterate quickly. Small decisions made and tested rapidly beat large decisions made slowly.
"What is important is seldom urgent, and what is urgent is seldom important." Prioritization along two axes: urgency and importance.
URGENT NOT URGENT
+-----------------+-----------------+
IMPORTANT | Q1: DO | Q2: SCHEDULE |
| Crises | Strategy |
| Deadlines | Planning |
| Emergencies | Prevention |
+-----------------+-----------------+
NOT | Q3: DELEGATE | Q4: ELIMINATE |
IMPORTANT | Interruptions | Time wasters |
| Some meetings | Busywork |
| Some emails | |
+-----------------+-----------------+
Q1 (Urgent + Important): Do immediately. Genuine crises and hard deadlines. The goal isn't to eliminate Q1 but to minimize it through better Q2 investment.
Q2 (Not Urgent + Important): Schedule deliberately. This is where leverage lives. Strategic planning, skill development, system improvement, prevention. Q2 reduces future Q1. It's sacrificed most often because it never screams for attention.
Q3 (Urgent + Not Important): Delegate or minimize. Feels pressing but doesn't matter much. The urgency is often someone else's priority.
Q4 (Not Urgent + Not Important): Eliminate. Some Q4 is fine for rest, but don't confuse it with productive work.
Most people spend too much time in Q1 and Q3. The result is perpetual