| name | studio-thinking-case-study |
| description | Case-study narrative plugin for Studio. Use when the brief is really about one company, customer, transformation, rollout, or before/after story and should not default to a strategy memo. |
Studio Thinking Mode: Case Study
Use this as a light thinking plugin, not as a separate pipeline.
When to use
- The brief is framed as a case study, company story, customer story, implementation story, or before/after transformation.
- The deck should explain what happened, what changed, and what the lesson is.
Page grammar
- Use context / challenge / intervention / outcome / lesson grammar.
- Let one page carry one move in the case.
- Preserve sequence and causality so the audience can follow the narrative without memo-like headers everywhere.
Guardrails
- Do not turn the deck into an executive recommendation report unless the brief explicitly asks for that lens.
- Keep the story concrete. Use evidence, artifacts, and outcomes rather than abstract strategic filler.
- When page count is fixed, cut side commentary before mixing the intervention and lesson into the same page.
