SKILL.md
Case Study Writing
Structure
The Honest Arc
- Context — Company, timeline, your role, team size. No fluff. Just facts.
- Problem — What was broken, missing, or failing. Be specific with metrics if you have them.
- Constraints — What made this hard. Budget, timeline, technical limits, organizational politics. Constraints make the story real.
- Process — What you actually did. Not a waterfall diagram. The real, messy process including dead ends.
- Key decisions — The 2-3 decisions that mattered most. What were the options? Why did you choose what you chose?
- What failed — What didn't work. What you tried and abandoned. This is where credibility lives.
- Outcome — Measurable results. Revenue, conversion, engagement, adoption, time saved. Numbers beat adjectives.
- Reflection — What you'd do differently. What you learned.
Common Mistakes
- Starting with "I was tasked with..." (passive, boring)
- Showing only the happy path (nobody believes it)
- Screenshot galleries with no explanation
- Process diagrams that describe methodology, not actual work
- Focusing on deliverables instead of decisions
- No metrics (words like "improved" and "enhanced" mean nothing alone)
- Writing for other designers instead of the intended audience
Writing Quality
Lead with the Outcome
Don't make people read 2000 words to find out what happened. State the result upfront, then explain how you got there.
Bad opening: "In Q3 2024, the team identified an opportunity to improve the onboarding experience..."
Good opening: "We cut onboarding drop-off by 34% in six weeks. Here's the decision that made the difference."
Show Your Thinking
Screenshots of final designs are the least interesting part. Show:
- The whiteboard sketch that unlocked the solution
- The comparison of 3 approaches you considered
- The data that changed your mind
- The prototype that users rejected (and why)
Write for Your Audience
- For hiring managers: emphasize process, collaboration, impact
- For founders: emphasize speed, business outcomes, constraints handled
- For peers: emphasize craft decisions, technical tradeoffs, methodology