Raw

**Legend**

| Marker | Meaning |
|---|---|
| ▲ | top / answer |
| ● | first-level group |
| ⚠ | violation |
| ↑ | conclusion buried lower than it belongs |
| ⇄ | wrong order type |

---

▲ This memorandum describes how project teams identify and deliver significant profit improvements. ⚠ [topic label, not an answer]

It is organized in six sections:

    ● Background ○
    ● Principles of the project-team approach ⚠ [mixed kind]
    ● Definition of project work ○
    ● Organization of the program ⇄ [order unclear]
    ● Distinctive benefits and results ↑ [answer buried here]
    ● Conditions required for success ⊕ [unsupported if coordinate with others]

---

| Location | Violation | Fix |
|---|---|---|
| Opening statement | Topic label, not answer | State what the reader should conclude about project teams, not just the topic |
| Six headings | Mixed kinds: context + concepts + description + structure + benefits + prerequisites | Group by what the reader's question demands: separate why (benefits, principles) from how (organization, definition) and requirements (conditions, background) |
| Six headings | No order principle | Apply time (setup → execution → results), ranking (importance), or deduction (why → how → conditions) so the reader sees the logic |
| "Distinctive benefits and results" | Answer buried as a supporting point | Promote to the top; make it the one-sentence conclusion the sections support |
| Overall structure | Reads as a table of contents, not an argument | Reorganize into 3–4 same-kind groups under one controlling idea |

---

**Score:** 2/10 (not structured yet)
- Top: 0 | Same-kind groups: 0 | Order: 0 | MECE: 1 | Display: 1

**Three fixes that buy the most:**

1. Replace the opening with the answer: "Project teams deliver [specific benefit] because [one reason]," not a description of the memo's structure.
2. Group the six headings into 3–4 same-kind categories answering one kind of reader question: either reasons (why use teams), mechanics (how to run them), or requirements (what's needed).
3. Apply an explicit order principle and name it so the reader sees why this sequence, not another.