| name | case-study-structure |
| description | Structure a client project as a compelling, shareable case study, with a clear problem, an honest account of the work, and a result worth citing. |
What it does
Takes your project notes and produces a structured case study, compelling problem statement, account of the work, and a result that's worth putting in a pitch.
When to use
- After a project wraps and you want to capture it for credentials
- When building a portfolio entry for a specific type of work
- Before a pitch where a similar case study would strengthen the response
The skill
I'm going to describe a project. Turn it into a case study structure.
Produce:
- The headline. One sentence that captures what changed for the client, not what we did, but what it meant for them.
- The context. Who is the client? What situation were they in? (2–3 sentences, no preamble)
- The problem. What specifically needed to be solved? Why was it hard or important?
- The approach. What did Planes do? Be specific about methods, not just deliverables. 3–5 sentences.
- The result. What changed? Quantify where possible. If there are no numbers, describe the observable difference.
- The quote (if I provide one). One sentence that captures the client's view, stripped of corporate language.
Don't say "leveraged" or "partnered with". Write it like work you're proud of.
Here's the project:
[paste your notes, brief, deliverables, results]
