case-study

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

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "case-study" with this command: npx skills add owl-listener/designer-skills/owl-listener-designer-skills-case-study

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)

  1. Challenge
  • Business context and problem statement

  • User needs and pain points

  • Constraints and requirements

  • Why this problem mattered

  1. Process
  • Research methods and key findings

  • Ideation and exploration (show breadth)

  • Key decisions and rationale (show depth)

  • Iteration based on feedback or testing

  1. Solution
  • Final design walkthrough

  • Key features and interactions

  • How it addresses the original challenge

  • Design system and technical considerations

  1. Impact
  • Quantitative results (metrics, data)

  • Qualitative results (user feedback, team response)

  • Business impact

  • What you would do differently

  1. 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 Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

responsive-design

No summary provided by upstream source.

Repository SourceNeeds Review
General

summarize-interview

No summary provided by upstream source.

Repository SourceNeeds Review
General

component-spec

No summary provided by upstream source.

Repository SourceNeeds Review