Writing Case Studies

Tell the Story of a Decision

A case study is a story about solving a problem. It is not a diary of everything you did, and it is not a slideshow of final screens. Good case studies read like a short, well-edited article: a clear problem, meaningful choices, and a result.

Remember that reviewers skim. Structure your case study so someone can understand it in 60 seconds from headings and images alone, then go deeper if they are interested.

---

The Problem → Process → Solution → Impact Format

0. The overview (at the top)

A short summary card:

• Project: Savings feature for market traders
• Role: Product designer (solo designer, with 1 PM and 2 engineers)
• Timeline: 6 weeks, 2025
• Tools: Figma, Maze, WhatsApp for interviews
• Outcome: 38% of pilot traders saved weekly for 2 months

Many reviewers read only this, so make it count.

1. Problem

What was wrong and for whom? Why did it matter to the users and to the business?

Traders in Ariaria Market wanted to save, but 7 out of 8 we interviewed had stopped using savings apps within a month because deposits took too long between customers.

Include constraints: deadline, budget, technical limits, regulation (for example CBN KYC tiers).

2. Process

Show the key moments of your process, not every step.

• The research you did and the insight it revealed
• Ideas you explored and why you rejected some
• Tests you ran and what changed because of them

Show sketches, journey maps and early wireframes. Messy artefacts prove the process was real.

3. Solution

The final design, presented clearly:

• Key screens, with short annotations explaining decisions
• A prototype link or short video of the flow
• How it handles edge cases, such as being offline

4. Impact

What happened because of your work?

• Metrics: "Deposit time fell from 90 seconds to 12 seconds", "Task success in testing rose from 3/5 to 5/5"
• Qualitative: quotes from users or stakeholders
• If it did not launch or you do not have data, share usability test results and be honest

5. Reflection

What did you learn? What would you do differently? Reflection shows maturity and self-awareness, which hiring managers value highly.

---

Writing Tips

• Be specific about your role. Use "I" for what you did and "we" for team work. Never take credit for others' work.
• Lead with the insight, not the method. "Traders serve several customers at once, so every extra tap costs a sale" beats "I conducted 8 interviews".
• Use numbers wherever you can.
• Keep it scannable: short paragraphs, clear headings, captions on images.
• Aim for about a 5 to 8 minute read. Cut anything that does not support the story.
• Protect confidentiality. If you are under NDA, blur data, change names or describe the work without showing sensitive screens. Ask permission when unsure.

---

Nigerian and Global Readers

If you are applying to global companies, add context that a reader outside Nigeria needs: what a POS agent is, why USSD matters, or what NUBAN account numbers are. That context also shows you design for real markets, which is a strength for any company targeting Africa.

---

Try It in the Lab

The case study builder guides you through each section with prompts and examples. As you write, the quality meter checks for common signals reviewers look for: a clear role, numbers, an insight, rejected alternatives and reflection. The live preview shows how it will read.