Raw

[Legend: ▲ top/answer | ● first-level group | ○ support | ⚠ violation | ↑ buried conclusion | ⇄ wrong order | ⊗ overlap | ⊕ gap | ✂ cut/move]

✂ This memorandum describes how project teams identify and deliver significant
profit improvements. It is organized in six sections:

    ⚠ Background
    ⚠ Principles of the project-team approach
    ⚠ Definition of project work
    ⚠ Organization of the program
    ⚠ Distinctive benefits and results
    ⚠ Conditions required for success

| Location | Violation | Fix |
|---|---|---|
| Opening sentence | Top does not answer reader question; states topic instead | Replace with a single-sentence answer addressing the reader’s decision or action |
| Heading list | Mixed kinds & unexplainable order; background, principles, definitions, organization, benefits, conditions do not share one plural noun | Group into 3–4 same-kind branches (reasons, actions, or criteria) and apply explicit ordering (time/ranking/structure) |
| Structure | No vertical summary; headings are topics, not claims summarizing supports | Convert headings to claim-based statements that directly answer the reader’s question |
| Display | Skeleton hidden behind generic intro and flat list | Use indentation, numbering, and a key line to make hierarchy readable at a glance |

**Score**
Top: 0 · Same-kind groups: 0 · Order: 0 · MECE: 0 · Display: 0
Band: 0–3 not structured yet

**Three fixes that buy the most**
1. Delete the introductory sentence and replace it with one direct answer to the reader’s question.
2. Collapse the six topic headings into three or four same-kind groups and assign a clear ordering principle.
3. Rewrite each group heading as a claim rather than a topic word, and use indentation/numbering to show the hierarchy.