Raw

⚠ | violation (mixed kinds, unexplainable order, false grouping)
✂ | cut, or move to an appendix

⚠ 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 |
|---|---|---|
| First line | Top is a topic label ("describes how"), not an answer to the reader's question. | State the controlling idea answering the reader's question in one sentence. |
| First line | No SCQ intro; text announces content rather than telling the story. | Replace with Situation → Complication → Question → Answer in story form. |
| List | Six groups exceed working memory capacity; cognitive load too high. | Consolidate into 3–4 first-level groups. |
| List | Mixed kinds: topics, principles, definitions, outcomes, and requirements are grouped together. | Split into same-kind classes (e.g., all reasons, all actions, or all parts). |
| List | Order follows report convention/recall, not a logical principle. | Assign an explicit order type (time, structure, ranking, deduction, or induction). |
| Second line | Meta-text ("It is organized in...") is apparatus that buries structure. | Delete; reveal structure via key lines, headings, and numbering. |

**Score:** 0 / 10 · `not structured yet`

**Top:** 0 · No answer.
**Same-kind groups:** 0 · Full mix.
**Order:** 0 · Unexplainable.
**MECE:** 0 · Clear gaps and overlaps.
**Display:** 0 · Solid prose.

**Three fixes that buy the most:**
1. Replace the opening sentence with a one-sentence answer derived from the reader's question.
2. Merge the six headings into three or four groups of the same kind.
3. Delete the meta-intro and make the hierarchy visible through key lines and numbering.