Learn pattern
Governing Thought
The single overarching idea that unifies all supporting points
- Category
- Block
- Source
- Barbara Minto, The Pyramid Principle (1987)
Found in 149 slides across 110 decks in our corpus.
Learn pattern
The single overarching idea that unifies all supporting points
Long-form treatment of this canon entry. A compact, operational version exists as the skill companion — what the agent reads when calling this tool.
One sentence. One verb. One position the entire deck is prepared to die on. If you can write it, the work is finished. If you can't, it isn't — and no amount of additional slides will hide that from the reader on the other side of the table.
The governing thought is Barbara Minto's term for the apex of a Minto pyramid. It lives inside the Pyramid Principle she codified at McKinsey, but it deserves its own entry — it is the single most demanding moment of the entire method, the line where a writer commits in public.
Minto joined McKinsey in 1963 in Cleveland as the firm's first female MBA hire. Three years later the partners shipped her to London, where she spent 1966 to 1973 teaching European consultants how to write. Her diagnosis, repeated decades later in her McKinsey alumni oral history, was always the same: the consultants weren't bad writers, they were bad committers. Their documents climbed slowly toward a conclusion that was usually right but always buried — the reader had to mine for the answer through twenty pages of methodology.
Her fix was structural, not stylistic: put the answer at the top of the page, in one declarative sentence, and let everything else work to defend it. That sentence became the governing thought — the idea that governs the structure beneath. She left McKinsey in 1973 to found Minto International, self-published the first edition in 1981, and released the canonical Pyramid Principle: Logic in Writing and Thinking in 1985. The term migrated from London training rooms into McKinsey's internal style guide, then into the bloodstream of strategy consulting. BCG calls it the "main message". Bain, the "key takeaway". Investment banks, the "thesis". The name varies; the object doesn't.
A governing thought has three properties, and a sentence that fails any of them isn't one.
It is declarative. Not a topic, not a question, not a theme. "Strategic options for European expansion" is a topic. "What should we do about Europe?" is a question. "Enter Germany via the Bayer JV in Q3 to capture €120M of TAM before Sanofi consolidates" is a governing thought. Mechanical test: the sentence has a verb that does work. If the verb is "to be" pretending to mean something, the sentence isn't committing.
It is the answer to a specific question. Minto's SCQA opening — Situation, Complication, Question, Answer — makes this explicit; the governing thought is the A. If you can't say what question it answers, the document hasn't found its reader.
It summarises everything beneath it. Strip the apex away, read only the supports, and ask: is this what they collectively claim? If not, either the apex overclaims or the supports underdeliver. This is the discipline that catches fake governing thoughts — confident-sounding sentences the analysis can't defend.
Field test: write the apex, then write each of your three to five supports as a single sentence. Read them in order. They should sound like because-clauses for the apex. If they don't, the pyramid leaks at the top.
Writing a governing thought is the single hardest sentence in executive communication, and forcing it surfaces every weakness in the underlying analysis at once.
Most decks are vague at the top because the analyst is vague at the top. They have data, charts, observations, hypotheses — what they don't have is a position. Topic-style titles ("Considerations for the European market") are the linguistic hiding place for unfinished thinking; as long as the title is a topic, the analyst doesn't have to commit. The apex is so much harder to write than to identify that most analysts cope by writing supports first and hoping the apex assembles itself. It almost never does. A pyramid built bottom-up has a topic at the top because the analyst couldn't bring themselves to commit on the way up.
The second reason is reader cognition. Senior readers read the headline first and decide in four to six seconds whether to keep reading. If it's a topic, those seconds yield no information; if it's a governing thought, the entire answer lands in the first cognitive beat. The pyramid is, at root, a tool for progressive disclosure — maximum conviction per unit of reader effort, packed into one sentence.
A governing thought is the right tool whenever there is a recommendation, a decision, or a position the document is meant to advance — virtually all consulting deliverables, board memos, investment committee papers, partner communications, strategy decks. If the deck has a because, it has a governing thought.
It is the wrong tool for genuinely exploratory work: workshop discovery decks, hypothesis trees, problem framings, regulatory disclosures where the writer must enumerate without recommending. Forcing a governing thought onto unfinished analysis produces dishonest documents — confident sentences the work can't yet support. Better to label the deck "working document" and use topic titles than to fake an apex.
Diagnostic: can you write the governing thought in the form "[VERB] [OBJECT] because [REASON]"? If yes, the analysis is done and the pyramid is structurable. If no, either the recommendation hasn't crystallised or the reasoning hasn't — or both.
A strategy team has spent eight weeks evaluating three acquisition targets for a mid-cap industrials client. The board meets next Tuesday. There are 47 slides of analysis in the back. The only question that matters tonight is what slide 1 says.
The wrong shape (topic):
Acquisition opportunities — strategic and financial analysis
The title of a textbook chapter. The board reads it, learns nothing about what they're being asked to do, and starts hunting for the answer in the appendix while someone else presents.
The wrong shape (multi-sentence apex):
We evaluated three targets. Each has merits. Target B emerged as our preferred candidate based on strategic fit, financial profile, and integration risk. We recommend further diligence.
Four sentences. Two hedges ("emerged as", "further diligence"). No verb that commits. The board reads this as we don't actually know yet.
The right shape (governing thought):
Acquire Target B for €340M in Q3 to lock in the European service-network gap before Schaeffler closes its own deal.
One sentence. One verb (acquire). One object (Target B). One price band (€340M). One window (Q3). One because (before Schaeffler closes). The board reads it once and knows the answer, then reads the three supports — strategic fit, financial returns, execution window — to decide whether to trust it.
The discipline that produced that sentence is brutal: the team had to choose B over A and C out loud, commit to a price band, commit to a quarter, and commit to the because. Each of those is the kind of thing analysts prefer to hedge inside a topic title. The governing thought refuses the hedge.
When diligence three weeks later flags worse-than-expected integration risk, the team rewrites the apex — not the deck. "Pause Target B and pivot to A as the lower-risk path" is now the governing thought. The architecture beneath doesn't change; the sentence at the top does. That is the method working as designed.
The topic disguised as an answer. "Path forward for the EU portfolio" sounds executive and commits to nothing. Every "path forward", "considerations for", "options around", "view on" is the same hedge in different costume. Force a verb.
The multi-sentence apex. A governing thought is one sentence. Two means the writer couldn't decide which was the answer; three or more means the supports are leaking up. If the headline takes a paragraph, the analysis isn't done.
The qualifier-laden apex. "We believe Target B may emerge as the most likely candidate, subject to further analysis." Every qualifier marks a place the writer is hedging. Strip ruthlessly; if the analysis genuinely warrants "may", finish the work first.
The orphaned apex. A governing thought floating free of an SCQA opening lands in a vacuum — the reader can't tell whether it's a good answer because they don't know what question it answers. Anchor every apex with SCQA.
The fake apex. A confident sentence the supports don't defend. The reader scans, notices the gap, and silently downgrades the writer — worse than a topic, because it broadcasts overconfidence the analysis can't back. Test by reading only the supports.
The buried verb. "Recommendation: acquisition of Target B." A noun phrase pretending to be a sentence. Verbs do work nouns can't. "Acquire Target B for €340M before Schaeffler closes" is the finished form.
pyramid-principle — the
structure the governing thought sits on top of. The pyramid is
the building; the governing thought is the apex stone.scqa-framework — the
four-beat opening that lands the reader at the governing
thought. Situation, Complication, Question, Answer — the
Answer is the governing thought.action-titles — the
slide-level application of the same discipline. Every slide
title is a mini governing thought defending one support of the
deck's apex.big-idea-formula — Nancy
Duarte's narrative-deck cousin. Same demand for one declarative
sentence; different rhetorical register.overview
The single declarative sentence at the apex of a Minto pyramid that summarises and is supported by everything beneath it — the answer the deck exists to defend.
When the deck makes a recommendation, decision, or argues a position; when defining the top of a pyramid before structuring supports; when an SCQA opening needs an Answer; when stripping topic-style titles in favour of action titles.
Forces the writer to commit to a position before structuring the case — exposes muddled thinking that hides safely inside topic-style headings. Gives busy readers the answer in the first cognitive beat and enables progressive disclosure of the supporting case.
Anchor the document in one defensible claim with a working verb, so the audience knows the answer before they read the proof and the entire structure ladders up to it.
Topic-style headings ('Strategic options for growth', 'Considerations for Europe') instead of declarative claims with verbs. Multi-sentence apex statements. Qualifier-laden hedges. Noun-phrase labels ('Recommendation: acquisition of Target B') pretending to be sentences. Fake governing thoughts — confident apex the supports don't actually force.
Examples