Raw

**Markers**

| Marker | Meaning |
|---|---|
| ▲ | top / answer |
| ● | first-level group |
| ⚠ | violation (mixed kinds, unexplainable order, false grouping) |

**Text**

```
▲⚠ 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
```

**Findings**

| Location | Violation | Fix |
|---|---|---|
| Opening | Topic label instead of answer — announces the subject but makes no assertion about what to do or decide | State the answer: what the reader should believe or do regarding project teams |
| Section headings | Six first-level groups (exceeds 3–4 capacity for working memory); mixed kinds (situation, reasoning, explanation, structure, outcomes, prerequisites); order unexplainable | Consolidate to 3–4 same-kind groups; order by time, structure, or ranking |

**Score**

- Top: 0 (topic label, no answer)
- Same-kind groups: 0 (six mixed kinds)
- Order: 0 (unexplainable)
- MECE: 1 (grouping incoherent)
- Display: 1 (hierarchy not visible)

**Band: 2/10 — not structured yet**

**Three fixes that buy the most**

1. Open with the answer, not the topic — state what the reader should do or decide about implementing project teams.
2. Consolidate six headings to 3–4 same-kind groups (reasons, actions, parts, or conditions) that answer the reader's question.
3. Order the groups by an explicable principle — time (how to start), structure (what comprises the approach), or ranking (foundation to results).