Structured business recommendations and persuasion
The Elegant Pitch Summary: Build a Recommendation People Can Assess
The Elegant Pitch teaches a structured process for turning a business question into a clear recommendation, testing its logic and evidence, and communicating it in a form stakeholders can evaluate.
One-Sentence Answer
The Elegant Pitch teaches a structured process for turning a business question into a clear recommendation, testing its logic and evidence, and communicating it in a form stakeholders can evaluate.
What The Book Is About
Mike Figliuolo's book addresses a familiar problem: a team performs extensive analysis, builds an impressive deck and discovers that the audience cannot identify the recommendation or why it matters. The publisher's record confirms the title, Career Press imprint and 2016 publication. The author's training description links the book to his Structured Thought and Communication program.
The approach gives shape to the work before the final presentation. Its vocabulary includes a core idea, an architecture and a story, followed by the facts and analysis needed to test the case. Story here concerns the narrative of a recommendation; it does not mean inventing a customer anecdote to decorate a slide. This guide follows a fictional equipment-reservation proposal to show how the distinctions can change the thinking, not just the wording.
Who Should Read It
Read this when you have a recommendation to develop and several people need to understand or approve it. Analysts can use it to avoid collecting data without a question. Managers can use it to examine a proposal before their team spends weeks polishing a presentation. Project leads may find the stakeholder conversations useful when different departments define success differently.
It is less directly useful for someone whose immediate need is delivering a ceremonial speech or overcoming presentation nerves. Its structured approach also takes judgment: a preliminary recommendation is a hypothesis to examine, not a verdict that evidence must be forced to support. For high-consequence decisions, use the appropriate analytical and subject-matter expertise alongside communication guidance. A beautifully ordered proposal can still recommend the wrong thing.
Main Summary
The Elegant Pitch treats persuasion as a process of clarifying the question, building a recommendation and testing the case before presenting it. Figliuolo's structured thought approach asks the communicator to identify what the audience needs to decide and why the issue matters. A core idea connects the proposed action with a result stakeholders care about. That connection gives the subsequent work a purpose.
The architecture organizes the logic supporting the core idea. Rather than assembling every available fact into a deck, the writer first considers what would have to be true for the recommendation to make sense. A story then expresses that reasoning in a comprehensible narrative. Feedback from people outside the immediate team can reveal missing context, unsupported assumptions or competing priorities before the final communication is produced.
A distinctive feature is the attention to analysis after the question and logical structure have been clarified. This does not mean that facts are optional. It means the writer identifies the evidence required to examine the recommendation rather than doing every possible calculation. Figliuolo explicitly includes disproving hypotheses. If the evidence fails, the idea must change; the objective is a sound answer rather than vindication of the first proposal.
The original case in this guide follows Leila, a manager at a fictional shared fabrication studio. She considers a trial reservation system for equipment because members report difficulty coordinating access. A large survey, a new software purchase and a persuasive presentation are all possible activities, but none should begin without a clearer decision question. The case illustrates the method without claiming that the proposed system actually reduces waiting or that the book contains this example.
The final communication can take different forms, including a memo, email or presentation. Its format should serve the decision and the audience. Read the book when you need a disciplined route from an initial idea to an assessable recommendation, with enough openness to abandon or revise that idea when the reasoning does not hold.
Key Ideas
1. Define the decision question before polishing the proposed answer
The book begins its structured thought process by defining the question. An issue can sound obvious while different stakeholders understand it differently. One person may be asking how to reduce delays, another how to use equipment fairly and another whether new software is worth its administrative cost. A recommendation designed for only one of those questions can look unresponsive to the others.
Leila initially frames her proposal as buying a reservation tool. Before choosing a product, she asks what decision the studio actually needs to make. Is the immediate problem insufficient machine capacity, unclear booking expectations or poor visibility of availability? Those possibilities call for different responses. Her preliminary question becomes whether a limited reservation trial would help the team understand coordination problems without committing to a full purchase. That remains a question for investigation, not proof that the trial is worthwhile.
For your own proposal, write the decision question and why answering it matters to the person responsible. Ask that person to correct the wording. Then draft a core idea that connects an action with the result the audience cares about. Mark any claim about the result as provisional until evidence supports it.
This matters because a strong presentation cannot repair a mismatch about the task. Agreement on the question gives later analysis a target and makes disagreement more specific. A stakeholder can challenge the proposed action while still agreeing that the underlying issue deserves attention. That is a better starting point for reasoning than defending a solution whose purpose remains unclear.
2. Build an architecture that exposes the logic of the recommendation
Figliuolo uses architecture for the logical structure supporting a core idea. It is not a decorative outline added after the research. The authorized chapter preview warns against starting by gathering miscellaneous facts and attempting to fit them together. The supporting logic should follow from the idea and the audience's information needs.
For the fictional studio, Leila identifies several propositions her trial would depend on. Members must be able to understand and use the reservation process. The trial must produce information relevant to the coordination question. Running it must not create an unacceptable burden for staff or exclude members who need another way to book. These are original case-specific tests, not an official three-part model from the book. Each proposition shows what she would need to investigate.
Draw your recommendation at the top of a page and place the supporting claims beneath it. Read downward and ask whether each claim helps establish the recommendation. Read upward and ask whether the support is sufficient. If two branches repeat the same idea in different words, combine them. If the argument depends on an unstated assumption, bring it into view.
This matters because an orderly set of headings can conceal a missing connection. A chart showing existing demand, for example, does not by itself show that a booking system is the right response. Architecture makes it easier for both the writer and the audience to identify that gap before a final deck makes the proposal feel more settled than it is.
3. Draft the story early enough for other people to improve it
The book distinguishes a logical architecture from the story that communicates the recommendation. A written narrative lets the author test how the reasoning will travel from one person to another. It also creates something concrete for stakeholders to respond to. Asking whether people like an idea can produce polite approval; asking them to follow a short draft can reveal where understanding breaks down.
Leila writes a plain-language account of the current coordination concern, the proposed trial, what it would help the studio learn and what remains uncertain. She shares it with a staff member and a regular equipment user. The staff member notices that administering cancellations is absent from the plan. The member asks whether a reservation will prevent someone from using an otherwise idle machine. Those responses change the proposal before she selects software or prepares slides.
Choose feedback readers who possess relevant knowledge and at least one person who lacks your background context. Ask them to identify the recommendation, the reasoning they find weakest and the information needed to decide. Keep their objections in the working draft until you have addressed them. A polite conversation should not be recorded as support when the person actually raised an unresolved condition.
This matters because writers routinely supply context in their own minds that never reaches the page. Stakeholders also know constraints the writer may have missed. Early review helps locate both kinds of gap. Treat it as an opportunity to improve the decision, rather than a campaign to obtain endorsements before anyone sees the evidence.
4. Gather the facts that can challenge the hypothesis as well as support it
The Elegant Pitch includes identifying required facts and proving or disproving hypotheses. This is an essential qualification to its recommendation-first approach. An initial core idea helps focus inquiry; it must not become a conclusion protected from inquiry. The authorized preview on hypotheses explicitly emphasizes openness to an initial idea being disproved.
Leila lists evidence that would matter to the studio's decision. She needs to understand when coordination problems occur, whether members can use the proposed booking channels and how much work staff would have to perform. She also writes down what would count against the trial. If the main obstacle turns out to be equipment maintenance rather than scheduling, a reservation system may miss the problem. If the trial prevents informal use without improving coordination, its design may need to change.
For your proposal, attach an evidence question to each important claim. Specify what observation could weaken it. Keep measured results separate from estimates and assumptions. If a calculation depends on information you do not possess, show the uncertainty instead of filling the gap with a convenient number.
This matters because selective analysis can make almost any preferred idea look attractive. The useful output is a recommendation whose strength matches the evidence, including a revised recommendation when necessary. Sometimes the result will be that a smaller experiment is justified. Sometimes it will be that no action should proceed. Both are legitimate outcomes of a process intended to improve judgment rather than merely win approval.
5. Choose the communication vehicle after the recommendation becomes clear
The author's training description includes packaging the story in a presentation, memo, email or another suitable form. That flexibility is important. A recommendation is not automatically a slide deck, and a slide deck is not the underlying analysis. The final vehicle should let the audience inspect the decision, its support and the action being requested without having to reconstruct your entire working process.
For Leila, a brief decision memo may be enough to explain the trial and invite written questions before a meeting. A small supporting diagram can show how members would reserve equipment. Detailed observations and administrative estimates belong in an accessible attachment. She should not create a dramatic presentation merely because substantial effort went into the proposal. The audience needs the argument in a usable form, not proof that the author worked hard.
Before producing the final version, ask how the decision will actually be made. Will people read in advance, discuss together or approve within a documented process? Identify what they need to see immediately and what they may need to inspect afterward. Put the recommendation and requested action where they can find them. Check that a reader can distinguish the current proposal from a decision already taken.
This matters because format can change what an audience is able to evaluate. A fast spoken explanation may hide a complicated assumption that deserves careful reading. Conversely, a long document can obscure a simple choice. Select the vehicle that supports understanding and questions, and be prepared to revise the recommendation when that evaluation exposes a weakness.
Practical Takeaways
- Write the decision question and its importance before choosing a presentation format.
- Ask the responsible stakeholder to correct your understanding of the problem.
- Express the core idea as a proposed action linked to an audience-relevant result, then mark unsupported claims as hypotheses.
- Map the claims that must hold for the recommendation to make sense.
- Draft a short narrative before building a polished deck, and ask a reader to restate the recommendation.
- Record conditions and objections raised during stakeholder conversations; do not count conditional support as unconditional approval.
- For every major claim, identify evidence that could weaken or overturn it.
- Choose a memo, meeting or presentation according to how people need to evaluate and decide.
How To Apply It
An original proposal-development worksheet
Start with a real recommendation whose scale is manageable. State the question, the person or group deciding and the consequence of leaving it unresolved. For Leila, the question concerns whether and how to investigate equipment coordination, not which software has the most attractive features. Keeping that distinction visible prevents procurement from replacing problem definition.
Write a preliminary core idea and sketch its logical support. Create a short prose draft using ordinary language. Ask two relevant readers to identify a missing assumption and a reason the proposal might fail. If their concerns change the question, return to the beginning rather than disguising the change as a minor wording adjustment.
Next, prepare an evidence list. Identify the observation or analysis required for each important claim and what you will do if it contradicts the proposal. In the studio example, evidence of a maintenance bottleneck would redirect the investigation. No outcome is assumed merely to make the exercise end neatly.
Only then decide how to communicate the result. Include the requested decision, the reasoning, material limits and the next action. After the decision, compare the questions stakeholders actually asked with those you anticipated. That comparison can improve the next recommendation without requiring a new template for every situation.
Notable Ideas, Paraphrased
These are editorial paraphrases: know the question before defending the answer; make the support visible before decorating the communication; obtain feedback while revision is still inexpensive; and allow evidence to change the recommendation you hoped to make.
Best Related Books
- The Pyramid Principle is useful for deeper attention to the hierarchy and grouping of business arguments. The Elegant Pitch adds an accessible route through development, feedback and testing of a recommendation.
- HBR Guide to Persuasive Presentations is a useful companion when the final vehicle is a presentation and you need to work on audience-facing structure and delivery.
- Brief addresses the practical problem of communicating with less unnecessary material. It is a lighter starting point when the decision logic is already sound and the immediate problem is length.