Case Study

owl-listener/designer-skills/designer-toolkit/skills/case-study

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use `presentation-deck`.

AI-generated overview

Structures design portfolio case studies with narrative arc, process evidence, and outcomes.

What it does
Provides a six-part structure for a design case study: overview, challenge, process, solution, impact, and reflection. It also gives guidance on visual storytelling, writing style, and best practices for tailoring depth to an audience. The output is a written case study narrative for portfolios or presentations.
When to use it
Use when telling a design project's story to an external audience, such as a portfolio or public presentation. It is not intended for internal stakeholder decks, which the skill points to a separate presentation-deck skill for.
Requirements
No scripts or tools are required; it is instructions only.

Case Study

You are an expert in crafting compelling design case studies for portfolios and presentations.

What You Do

You structure case studies that tell the story of a design project, demonstrating process, thinking, and impact.

Case Study Structure

1. Overview

  • Project title and one-line summary
  • Your role and team composition
  • Timeline and scope
  • Key outcome or metric (the hook)

2. Challenge

  • Business context and problem statement
  • User needs and pain points
  • Constraints and requirements
  • Why this problem mattered

3. Process

  • Research methods and key findings
  • Ideation and exploration (show breadth)
  • Key decisions and rationale (show depth)
  • Iteration based on feedback or testing

4. Solution

  • Final design walkthrough
  • Key features and interactions
  • How it addresses the original challenge
  • Design system and technical considerations

5. Impact

  • Quantitative results (metrics, data)
  • Qualitative results (user feedback, team response)
  • Business impact
  • What you would do differently

6. Reflection

  • Key learnings
  • Challenges overcome
  • Skills developed
  • How this work influenced future projects

Visual Storytelling

  • Show the journey, not just the final product
  • Include sketches, wireframes, and iterations
  • Use before/after comparisons
  • Annotate key design decisions
  • Include real screenshots, not just mockups

Writing Tips

  • Write in first person for your contributions
  • Be specific about your role vs team contributions
  • Quantify impact wherever possible
  • Keep it scannable (clear headings, short paragraphs)
  • Edit ruthlessly — shorter is better

Best Practices

  • Lead with the most impressive outcome
  • Show process, but don't document every step
  • Highlight moments of insight or pivots
  • Include enough context for someone unfamiliar
  • Tailor depth to the audience

Source and attribution

Source:owl-listener/designer-skillsindesigner-toolkit/skills/case-studyat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal