Skip to content
    Influence & decisionsChapter 26

    The Minto Pyramid for Technical Leaders

    SCQA, answer-first writing, logically grouped arguments, and MECE coverage for clear technical documents and messages.

    Original guideworking20 minevergreen · reviewed Aug 13, 2026
    Tech Lead
    Staff+
    Chapter outline

    Brief

    The essential idea

    The Minto Pyramid reduces cognitive load by giving the reader the answer first and supporting it with progressively detailed arguments. For RFCs, ADRs, strategy notes, status updates, and executive communication, the structure makes the conclusion visible before the reader spends time reconstructing it from evidence.

    SCQA frames the introduction as Situation, Complication, Question, and Answer. The answer becomes a concise, testable thesis, while the supporting arguments must summarize the level below, remain homogeneous in each group, follow an explicit order, and aim for MECE coverage—mutually exclusive and collectively exhaustive without forcing artificial completeness.

    Decision lens

    Key takeaways

    Lead with the answer and then provide evidence and detail.

    SCQA turns background into a focused question and makes the reason for the document clear.

    A useful thesis directly answers that question and can be confirmed or refuted.

    Each argument level should summarize the one below rather than repeat it.

    Arguments in one group should share a level of abstraction and follow chronology, priority, or another explicit logic.

    MECE is a quality check for overlaps and gaps, not a license to invent unnecessary categories.

    A technical document should finish with risks, constraints, the decision request, and the next step.

    Workplace experiment

    Apply it at work

    1. 1

      Write an SCQA introduction before the next RFC or architecture proposal.

    2. 2

      Place a one-sentence, testable thesis immediately after the introduction.

    3. 3

      Group supporting arguments by one declared logic and remove items at the wrong level of abstraction.

    4. 4

      Review the groups for overlap and missing coverage using MECE.

    5. 5

      End with the relevant risk, constraint, owner, and next action rather than leaving the reader to infer them.

    Choose one action, define the observable effect, and keep the first test small enough to reverse.

    Evidence

    Sources and further reading

    Additional sources

    Channel, aggregator, and commentary links confirm the work; they are not the primary source.

    Previous chapterCommunication Patterns — Short SummaryNext chapterEventStorming: A Practical Introduction