think-pyramid-principlelisted

<!-- thinking-framework-skills | https://github.com/product-on-purpose/thinking-framework-skills | Apache-2.0 --> # Pyramid Principle Most recommendations are delivered in the order they were discovered - context, then analysis, then, eventually, the point - forcing the reader to hold a pile of facts in mind and guess where they lead. The pyramid principle inverts that: the conclusion (the **governing thought**, the one thing the reader should do or believe) goes first; beneath it sit a small set of **MECE key arguments** that together justify it; beneath each sits its **supporting evidence**. The reader descends only as far as their trust requires and can stop at the top with the recommendation in hand. The output is a structured **pyramid** (governing thought + ordered key lines + support), not a flowing essay. It composes a clear case; it does not check whether the case is sound. ## When to Use - A conclusion or recommendation already exists and must be communicated to a busy or senior reader who needs the headline first. - Findings, analysis, or a memo need to be ordered into a tight top-down case instead of a chronological narrative. - A draft buries its point under context and reasons, and needs restructuring so the answer leads. - Preparing an executive summary, a decision memo, or the spine of a recommendation deck. ## When NOT to Use - **Early exploratory thinking, before a conclusion exists.** Answer-first structure forces a premature headline; do the thinking