Raw

**Legend:** `▲` top/answer · `●` first-level group · `⚠` violation · `⊗` overlap · `⊕` gap · `✂` cut

```text
▲⚠ This memorandum describes how project teams identify and deliver significant
   profit improvements. [topic label — states the subject, answers nothing]
✂ It is organized in six sections: [statement of purpose / table of contents,
   not a Situation and not an Answer]

    ● Background                                  ⚠ context, not a claim
    ● Principles of the project-team approach     ⚠ concepts  ⊗ with Definition
    ● Definition of project work                  ⚠ concepts  ⊗ with Principles
    ● Organization of the program                 ⚠ mechanics ⊗ with Principles
    ● Distinctive benefits and results            ⚠ payoffs — the only branch of
                                                     the kind the reader needs
    ● Conditions required for success             ⚠ prerequisites
    ⊕ [no reader question stated anywhere; no SCQ; six groups, no order]
```

| Location | Violation | Fix |
|---|---|---|
| Opening sentence | No answer anywhere in the visible text — the document has a subject, not a controlling idea. Reader deciding whether to adopt project teams needs what it is worth, not what the memo covers | Replace with one sentence asserting the answer, e.g. the reader's payoff from adopting the approach |
| Whole setout | Six headings of six different kinds (context, concepts, definition, mechanics, payoffs, prerequisites) — no plural noun fits them | Re-derive the kind from the reader's question, refill the groups with one kind |
| Six sections | Count exceeds working memory; nothing signals which matter most | Collapse to 3–4 first-level groups |
| Sections 2, 3, 4 | Overlap: principles, definition and organization all describe what the approach is and how it runs | Merge into supports under the payoff they produce |
| Section 5 vs 1–4 | Wrong level: "Benefits and results" is the answer to the reader's question, buried as the fifth of six items | Promote the benefits to the first level; demote mechanics beneath them |
| Entire opening | No SCQ: no Situation the reader accepts, no Complication forcing a choice, no Question — so no way to tell what the memo closes | Open with the situation and what changed, then the question, then the answer |
| All six headings | Topic words, not claims — the skeleton cannot be read at a glance | Restate every heading as an assertion |

**Score: 2/10** — Top 0 · Same-kind groups 0 · Order 0 · MECE 1 · Display 1. Band: *not structured yet.*

**Three fixes that buy the most**

1. State the answer in the first sentence — what the reader gains from project teams.
2. Promote "benefits and results" to the first level and hang principles, definition and organization under it as support.
3. Rewrite the six topic labels as three or four same-kind assertions, ordered by ranking.

Say the word and I'll run `write` on it once the body is available.