Raw

▲ top / answer | ● first-level group | ○ supporting detail | ⚠ violation | ↑ buried conclusion | ⇄ wrong order | ⊗ overlap | ⊕ gap | ✂ cut/appended

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

| location → violation → fix |
|---|
| Opening sentence → Topic label instead of answer → Replace with a single-sentence answer to the reader’s decision question |
| Entire intro → Missing SCQ story → Add Situation (current profit baseline) and Complication (blocker/change) leading to the Question |
| Section list → Mixed kinds & unexplainable order → Collapse into 3–4 same-kind branches (e.g., reasons, steps, criteria) with explicit ordering |
| Structure → Table-of-contents format → Restructure as argument-first hierarchy with clear key lines under each branch |
| Scope → Six items exceed working-memory limit → Consolidate to three or four core points; move remaining details to supports or appendix |

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

**Three highest-impact fixes**
1. Replace the opening description with a one-sentence answer that directly resolves the reader’s profit-improvement question.
2. Draft a concise SCQ intro that states what the reader already accepts and what specifically forces a choice now.
3. Group the six report sections into three or four same-kind branches ordered by time, structure, or ranking, and promote the real recommendation to the top.