case-study-story-maplisted

# Case Study Story Map Turn evidence into an outcome arc. The user or operator is the protagonist; the product, designer, and AI agent are supporting forces. Read `references/outcome-arc.md`. ## Workflow 1. Extract the protagonist, starting state, goal, trigger, constraints, actions, pivotal decision, changed state, and outcome evidence. 2. Arrange evidence on the eight-part Outcome Arc. 3. Identify the actual climax: the moment value or learning becomes visible, not the launch date. 4. Find cliffhangers: drop-offs, unresolved errors, abandoned paths, missing measurements, or outcomes without causes. 5. Test the arc against qualitative and quantitative evidence. 6. Collapse process steps that do not change the decision or outcome. 7. Draft section headings that make the arc scannable without dramatic exaggeration. ## Rules - Use conflict to explain real constraints, not manufacture theater. - Keep project chronology subordinate to causal logic. - Show how evidence changed the work. - Preserve branching, failure, and iteration when the real journey was non-linear. - Mark hypotheses and unknown causes instead of forcing a neat ending. ## Output Return: 1. a one-sentence case-study thesis; 2. the eight-part Outcome Arc; 3. the three strongest evidence anchors; 4. the pivotal decision; 5. unresolved evidence or cliffhangers; 6. recommended section headings.