Raw

Legend: ▲ top/answer · ● first-level group · ○ supporting detail · ⚠ violation · ↑ promote buried conclusion · ⇄ wrong order · ⊗ overlap · ⊕ gap · ✂ cut/move appendix

Annotated opening (visible text only):
```text
This memorandum describes how project teams identify and deliver significant
profit improvements. [⊕ no answer; ⚠ topic/purpose statement; ⊕ no SCQ] It is organized in six sections: [⚠ six first-level sections; mixed kinds; ⇄ order not explicable]

    Background [● ⚠ context, not a first-level argument element]
    Principles of the project-team approach [● ⚠ mixed kind]
    Definition of project work [● ⚠ mixed kind]
    Organization of the program [● ⚠ mixed kind]
    Distinctive benefits and results [● ↑ payoff appears late]
    Conditions required for success [● ⚠ mixed kind]
```

Findings:

| Location | Violation | Fix |
|---|---|---|
| First line | The top is a topic/purpose statement, not an answer; the visible opening contains no controlling idea. | Put a one-sentence claim/recommendation first that closes the reader’s question, not a description of the memo. |
| Opening | No SCQ: the situation, complication, and literal question are absent. | Add a short story-form intro that makes the reader’s question live before the answer. |
| Section list | Six first-level sections are presented where 3–4 grouped branches are needed. | Regroup the sections under 3–4 same-kind branches. |
| Headings | Mixed kinds: context, principles, definition, organization, benefits, and conditions sit at the same level. | Recast first-level headings as one kind of claim matching the reader’s question. |
| Order | The sequence is not explicable as time, structure, ranking, deduction, or induction. | Choose one order type and arrange the branches by it. |
| “Distinctive benefits and results” | The payoff/result material is scheduled after the mechanics; if it carries the answer, it is buried. | Promote the key benefit/result to the top or first branch. |
| Display | The opening reads as a table of contents, not an answer-first skeleton. | Show the hierarchy with a key line and grouped supports. |

Score:

| Axis | Score |
|---|---:|
| Top | 0 |
| Same-kind groups | 0 |
| Order | 1 |
| MECE | 1 |
| Display | 1 |

Total: 3/10 — not structured yet.

Three fixes that buy the most:
1. Replace the descriptive first line with a one-sentence answer that closes the reader’s question.
2. Add a short SCQ intro so the situation, complication, and question are visible before the answer.
3. Collapse the six sections into 3–4 same-kind branches under one order type, promoting the benefit/result if it carries the answer.

Next: I can run `write` to restructure the opening.