Study Notes by Niladri & AI

ch10-reflecting-pyramid-on-page

11 min read

Chapter 10: Reflecting the Pyramid on the Page

tpp pyramid-principle presentation formatting headings page-layout

Status: Notes complete

Overview

Chapter 10 addresses how to translate the logical hierarchy of a pyramid structure into visible, physical formatting on the written page. The goal is for readers to grasp the entire thinking — Introduction, Main Point, and Key Line points — within the first 30 seconds of reading, and to clearly see how subordinate groups of ideas relate to each other.

Minto presents five principal formatting devices for long reports: (a) hierarchical headings, (b) numbered and underlined points, (c) decimal numbering, (d) indented display, and (e) dot-dash outlines. While she personally favors hierarchical headings, she acknowledges strong arguments for each approach and explains the rules for applying all of them correctly.

Beyond structure, the chapter covers how to write transitions between major sections — either by “telling a story” (a mini Situation-Complication-Question narrative) or by “referencing backward” (picking up a key word or phrase from the previous section). It concludes with guidance on summarizing long sections and on writing effective conclusions, including a special section on “Next Steps.”

Core Concepts

Hierarchical Headings: A formatting system where increasingly subordinate ideas are placed progressively further to the right of the page, and ideas at the same level receive the same visual treatment (type size, style, indentation).

Underlined Points: An approach that underlines the entire statement of each support point, distinguishing levels by indentation and numbering, allowing the reader to “zip through” the document reading only major points.

Decimal Numbering: A system using numbers like 1, 1.1, 1.1.1 to indicate the hierarchical level of each paragraph or section, common in government and technical documents.

Indented Display: Setting groups of supporting ideas off visually as a block, expressed in grammatically parallel form, to make them “jump out” at the reader.

Dot-Dash Outline: A variation of indented display used in consulting progress reviews (“lap visuals”), designed for slow reading and discussion; rules are looser than for other forms.

Transitionary Phrases: Language used to move the reader smoothly from one grouping of ideas to the next, relating what sections say (their major ideas), not merely what they do.

Referencing Backward: A transition technique where you pick up a key word or phrase from the preceding section and carry it forward into your opening sentence for the next section.

Highlight the Structure

Formatting choices depend on document length:

  • Short documents (few paragraphs per Key Line point): Underline the Key Line points — they literally “jump out” at the eye. (Exhibit 54 example: numbered and underlined points make three concerns immediately visible in a memo.)
  • Longer documents: Introduce the Key Line points in the opening, then use section headings to reflect each one. (Exhibit 55 example: a field sales meeting memo uses bold headings like “SELECTING THE CHAIN” to mark each section.)

Exhibit 53 (Headings reflect divisions of thought): A pyramid diagram showing how each level of the hierarchy maps to a formatting level:

  • Title or Chapter heading → Major thought (apex)
  • Section headings → first level below apex (e.g., “1.”)
  • Subsection headings → second level (e.g., “1.1.”)
  • Numbered paragraphs → third level (e.g., “1.1.1.”)
  • Dash points → lowest level

Hierarchical Headings

The technique: place signs for increasingly subordinate ideas further right on the page; treat ideas at the same level with identical visual form (Exhibit 56).

Six rules for hierarchical headings:

  1. Never use only one of any element. A heading signals membership in a group; you cannot have a group of one. This applies at every level — no single major section, no single subsection, no single numbered paragraph.

  2. Show parallel ideas in parallel form. Since all ideas at a level are the same kind, express their headings with the same grammatical structure. Parallelism holds within a group, not between groups.

  3. Limit the wording to the essence of the thought. Headings remind, not dominate. Keep them concise — the heading “Appoint a Full-Time Chief Executive” is better than “Appoint a Full-Time Chief Executive to Provide Clear Central Authority.”

  4. Regard headings as outside the text. Headings are read by the eye, not deeply processed by the mind. Your text must flow smoothly without them; your opening sentence under each heading should indicate a new topic. (Exception: numbered paragraphs, which are meant to be read as part of the text.)

  5. Introduce each group of headings. Before a section begins, state the main point the grouping will explain or defend. Never have a major section heading begin immediately after the title, nor a subsection heading immediately after a section heading.

  6. Don’t overdo it. Use headings only where they genuinely help clarify your message and keep subdivisions in the reader’s mind. Often it is not necessary to go below the major section heading level.

Properly worded headings serve as a table of contents precis. A bad table of contents (“Introduction 1, Background 2, Findings 3, Conclusions 15, Recommendations 23”) communicates nothing. Real ideas in headings allow the reader to get the gist immediately.

Underlined Points

Exhibit 57 illustrates the system: underline the full statement of each major point, indent lower-level points and underline those too. The levels are distinguished by numbering style (uppercase/margin; parenthesized numbers/indented; lowercase/further indented) and by dots and dashes at the lowest levels.

Three strict rules for this format:

  1. Absolute discipline with question/answer logic. Every sub-point must directly answer the question raised by the point above it — nothing else. No room for graceful liaison language or amplification within the structure itself.

  2. State points as sparsely as possible. More than a dozen words, or more than one subject-and-predicate, is a warning sign. Brevity is essential.

  3. Be totally ruthless about the deductive or inductive outline. You must truly follow either deduction (max four points in a chain) or induction (max five in a group). If you have more, you have missed a grouping opportunity.

Decimal Numbering

Common in government and many companies, decimal numbering (1, 1.1, 1.1.1; or I, 1, a, i) signals subdivisions precisely and enables easy cross-reference.

Disadvantages:

  • Frequent index numbers interrupt the reader’s concentration on content
  • Any amendment may require renumbering all subsequent paragraphs
  • Best used in conjunction with, rather than as a replacement for, hierarchical headings

When to use: Number the paragraphs only where they represent actual divisions of thought — not in initial introductions, concluding summaries, linking comments, or introductions to subpoints.

Exhibit 58 shows an excerpt from Antony Jay’s Effective Presentation (Chapter 5) combining decimal numbering with descriptive headings — a hybrid approach that provides both precise referencing and contextual meaning.

Indented Display

For documents too short for headings or decimal numbers, indented display makes logical groupings visible.

The key rule: Express ideas at the same level in the same grammatical form (parallel construction). This both saves words and reveals whether you have actually stated a clear message.

Exhibit comparing two versions of a memo: The first version is dense prose; the second sets four numbered, bold points off as an indented block. The second makes the structure “jump out.”

For longer or shorter memos alike: One set of indented groupings per memo is enough; using more diminishes the visual effect.

Dot-Dash Outlines (Lap Visuals)

Used by consulting firms for progress reviews read around a table. Format rules:

  • Make short, direct statements at each level (omit grace notes and liaisons)
  • Limit each level to one statement only
  • Use parallel construction for ideas at the same level where possible
  • Ensure ideas at each level relate directly to the level above (explaining or supporting it)
  • Do not bother to use this format unless you intend to obey the rules

Show Transitions Between Groups

Once the initial introduction is written and the body begun, write a short introduction to each Key Line point. In longer documents, pause periodically to orient the reader — at either the end or beginning of each major grouping.

Guiding principle: Relate what sections say (their major ideas), not what they do (“This chapter has looked at X. The next chapter looks at Y”). Make progress seem smooth and nonmechanical.

Telling a Story

Introduce each Key Line point with a mini Situation-Complication-Question story that leads naturally to the Key Line point as the Answer.

  • The same SCQ structure from the overall introduction, but reduced in scope to match where the reader stands as each new section begins
  • The introductory story should contain only information the reader already knows or will agree is true
  • This technique is illustrated in Exhibit 59 (TQM/Benchmarking/Activity-Based Management example), where each section (Benchmarking, Activity-Based Management, Total Quality Management) gets its own SCQ mini-introduction

Referencing Backward

Pick up a key word or phrase — the main idea of the preceding portion of the pyramid — and use it in the opening sentence of the new section or set of support points.

Example (Exhibit 60, Ritz-Ryan hotel chain):

  • Between two sections: “The current top executive and board structure suffers from two major shortcomings that severely limit the degree to which Ritz-Ryan can take advantage of its combined resources.”
  • Between subsections: “In addition to appointing a Group Managing Director, Ritz-Ryan should make a number of changes in the executive structure…”
  • Between support points: “Just as only a full-time Chief Executive can coordinate line and staff activities effectively, so only a full-time Chief Executive can provide the steady, strong, and relentless pressure needed…”

The technique carries the major point of the next section forward — a section already briefly introduced in the “explanation” part of the original introduction. Thus no new SCQ story is needed.

Summarizing Sections

For extremely long or complicated chapters/sections, pause at the end and summarize completely before continuing.

  • Restate the principal matter and tone of the preceding text as adroitly as possible
  • Since the pyramid already has all major points in front of you, summarizing is simply pulling them together again for the reader
  • Example: “In summary, the top-level executive structure recommended in this chapter consists of the Ritz-Ryan Board and Chairman, a Group Managing Director, and three key executives reporting to him…”

Making Full Conclusions

Technically, a well-structured pyramid document does not need a concluding statement — the question was asked and answered with impeccable logic. In practice, however, writers often feel a psychological need to end gracefully.

Options:

  • Signal the end with a line of asterisks (“sunset”) and begin the last paragraph with “In conclusion…”
  • Avoid lame restatements; find compelling words that sum up while producing “an appropriate emotion” in the reader
  • The appropriate emotion for business: a need and desire to act; give the reader some indication of what he should think about or what he is able to do with his new knowledge

Stating Next Steps

A legitimate concluding section arises when dealing with actions the reader will definitely take in the immediate future:

  • Create a “Next Steps” section only for logically obvious, self-evident actions the reader will not question
  • These are actions the reader would not debate (“Call the man who owns the company and ask him to lunch”)
  • If an action would raise questions, it belongs in the body of the document, tied into the vertical and horizontal logic of the pyramid

Key Takeaways

  1. The goal of formatting is to make the hierarchy of ideas visually obvious so the reader can grasp the main point and Key Line in under 30 seconds.
  2. Hierarchical headings are Minto’s preferred approach: place each level’s ideas further right, and treat same-level ideas with identical visual form.
  3. Never use only one element at any level — a heading signals group membership, and a group requires at least two members.
  4. All headings at a level must be expressed in parallel grammatical form, reflecting the logical sameness of the ideas.
  5. Headings are for the eye, not the mind — your text must flow without them; always introduce each group of headings with a paragraph that states the main point.
  6. Underlined points require absolute discipline: question/answer logic, sparse wording, and strict adherence to deductive or inductive structure.
  7. Transitions between sections should relate what sections say, not what they do — use either a mini-SCQ story or backward referencing.
  8. Backward referencing picks up a key word from the preceding section and carries it into the opening sentence of the next.
  9. Summaries at the end of long sections restate the principal matter adroitly; use the pyramid to pull points together efficiently.
  10. A “Next Steps” concluding section is appropriate only for logically obvious actions the reader will not question.

Graph View

Backlinks