The Pyramid Principle: the book that teaches FDEs to write so client executives get it from the first sentence
At consulting firms, a draft can come back with a single instruction: "make it Minto". Forward deployed engineers, who write for client leadership, would do well to pick up the same habit.
In brief
- Barbara Minto is an executive communication specialist with a Harvard MBA who has taught the pyramid method for more than 30 years
- Three ideas worth keeping: put the conclusion first, group only ideas that are logically comparable, and start from the question the reader already has
- For FDEs, this is a book about how to think before writing emails, pilot reports and proposals for client leadership
- The reader's questionWhat the client executive is asking, e.g. will the pilot make go-live?
- Main point at the topThe answer goes on the first line and summarises everything beneath it
- Supporting groupsIdeas of the same kind, logically comparable, summarisable in one sentence
- Detailed evidenceFigures, technical errors, test-run results, placed at the bottom
The conclusion sits at the top; every layer below exists only to support the one above it.
Graphic: FDE Times
The phrase is so common that Barbara Minto’s method has become part of the profession’s shared vocabulary.
FDEs are not consultants, but consider what an FDE may have to write: an update email to a VP on the client side, a post-pilot report, a proposal to expand a deployment. The safe assumption is that the recipient reads the first few lines carefully and only then decides whether to keep going.
That is why a project can still be stopped when the code works but the email is a mess, and why The Pyramid Principle deserves a place on the desk of any engineer who works directly with customers.
A book about thinking, not just prose
Barbara Minto is an American author and consultant specialising in executive communication, with an MBA from Harvard Business School. Her course distils more than 30 years of teaching in many countries.
The book first appeared in 1985. The 1996 edition, published by the author herself as The Minto Pyramid Principle: Logic in Writing, Thinking and Problem Solving, has four parts, 12 chapters and three appendices, and is sold directly through barbaraminto.com. The easier edition to find is Pearson Education’s third edition, The Pyramid Principle: Logic in Writing and Thinking.
Newcomers should start with the Pearson edition; the author’s own edition suits the moment you want to go deeper into the problem-solving material.
The book helps you organise your thinking on any subject so you can present it clearly to others, and teaches you to use the pyramid structure itself to develop ideas. The order matters: the ideas must be arranged in your head before the first word is typed.
Why does the answer belong at the top?
The first principle is simple: state the general idea first, then move down to the supporting points. This is top-down communication, in which the main point is a high-level summary of the ideas below it.
Picture yourself in the second week of a pilot that uses an agent to process invoices for a logistics company.
A draft written out of developer habit tends to run chronologically: integrated the ERP API, hit timeout errors, fixed them, test-ran 500 invoices, found that foreign invoices had formatting errors. Only in the last sentence comes the proposal to push go-live back by a week.
If the client’s VP only has time for the first two lines, all they learn is that the team is busy. Written the Minto way, the first line reads: “We propose delaying go-live by one week to fix foreign invoices; everything else is ready.” The technical details are still in the email, but only as evidence for that proposal.
Which ideas belong in the same group?
The second rule is that ideas grouped together must be logically comparable, and each level must summarise the ideas directly beneath it.
In the example above, three good supporting points would be: the ERP integration is done, domestic invoices meet the required accuracy, foreign invoices still have errors. All three answer the same question: how ready is the system?
By contrast, a group made up of “we are using model X”, “the client hasn’t granted access yet” and “we should add a dashboard” mixes three different kinds of information, and the reader will not know what to conclude. A quick test: if you cannot write one sentence that sums up the group, the group is wrong.
What is the reader asking?
The third rule is to start from the question the reader already has. This is the foundation of the Situation–Complication–Question framework.
Applied to the pilot above, the Situation is that the agent has been running for two weeks. The Complication is that one group of invoices is failing. The VP’s natural question is “will we make go-live?”, and the answer to that question is the top of the pyramid.
This rule connects directly to customer discovery. If you do not know what the client’s leadership is worried about, however tight your pyramid is, it will answer the wrong question.
Learn by fixing your own emails
A sensible order is to read Antoine Buteau’s summary “Lessons from Barbara Minto” first to get the rules, then read the book. While reading, rewrite one real email a day using the method rather than just underlining passages.
For developers, including those in Vietnam, looking to move into FDE roles, this is a skill you can show to others. Prepare a design doc or project report written in pyramid structure, with the conclusion on the first line, to bring to interviews for customer-facing positions.
A first exercise: take the muddled group from the earlier section, “we are using model X”, “the client hasn’t granted access yet” and “we should add a dashboard”, and rewrite it yourself before reading on.
Three questions to check your work. What does the VP want to know about the pilot right now? Which of the three points actually answers that question and deserves the top spot? Which is merely evidence, and which belongs in a different email altogether?
Employers can test your coding with an exercise. Getting a client executive to nod after the first sentence is something you have to demonstrate yourself.