LightDark

A complete guide of how to write a compelling case study – defination, process and example

A case study is an in-depth, detailed examination of a particular case or cases within a real-world context.

It tells the story of how a problem was identified and solved, using visuals to bring the design journey to life for potential employers, clients, or team members

A compelling case study is presented like a story, walking the reader through your design thinking process.

The structure generally includes:

  • Project Overview: A brief introduction explaining the project’s background, your role, and the project’s scope.
  • Problem Statement: A clear and concise definition of the problem or challenge you set out to solve and why it was important.
  • User Research and Discovery: An explanation of your research methods (e.g., interviews, surveys, competitive analysis) and the key insights you gained. Visuals like user personas and journey maps can add depth here.
  • Design Process: A walk-through of your process, including ideation, sketching, wireframing, and prototyping. It should highlight the decisions you made and the rationale behind them.
  • Challenges and Iterations: A transparent section discussing unexpected roadblocks, what didn’t work, and how you iterated and adapted your design based on feedback.
  • Final Solution: A presentation of the final design, including high-fidelity mockups, prototypes, or other visual assets. Clearly show how your solution addresses the initial problem.
  • Results and Impact: The outcome of your work. This should include measurable data or key performance indicators (KPIs) and qualitative feedback to prove your design’s success.
  • Learnings and Next Steps: A reflective summary of what you learned from the project and potential future improvements or opportunities

Example of a case study-

  • Project: Redesigning a pharmacy delivery app
  • Problem: A pharmacy delivery app experiences a high user churn rate of over 35%. User research revealed that the account overview page was confusing and navigation was not intuitive.
  • Role: Lead Product Designer, collaborating with a Product Manager, two engineers, and a content strategist
  • Research:
  1. User Interviews: Conducted interviews with five regular users and two users who recently churned.
  2. Surveys: Sent a survey to 100 recent app users to gauge their experience with the account page.
  3. Usability Testing: Performed usability tests on the existing app, observing users struggle to find specific information on their account page. 

Key Findings:

  • The checkout process felt clunky and required too many steps.
  • Users found the layout of the account page cluttered, with crucial information like prescription refill status buried in sub-menus.

Design Process and Iteration:

  1. Initial explorations: Started with low-fidelity sketches and whiteboarding sessions to map out a cleaner information hierarchy for the account page.
  2. Wireframing: Created medium-fidelity wireframes that prioritized prescription status and upcoming delivery information at the top of the account screen.
  3. Prototype testing: Developed a clickable prototype and conducted further usability testing. Initial feedback showed users still struggled with some of the new icons.
  4. Refinement: Based on testing, the team simplified the iconography and improved the contrast and readability of the text

Solution:
The final design featured a new, intuitive account overview. The redesigned page includes:

  • A clear, prominent section for prescription status and refill requests.
  • An integrated delivery tracker visible directly on the account page.
  • A simplified, single-page checkout flow.

Impact:

  • Reduced Churn: The churn rate for new users dropped by 18% in the first two months after launch.
  • Increased Engagement: Users spent 30% less time navigating the account page, indicating improved usability.
  • Positive Feedback: Qualitative feedback from users highlighted their appreciation for the new, streamlined interface. 

Learnings:

  • Iterate Based on Feedback: The initial prototype was not perfect, emphasizing the importance of user testing to refine and improve the design.
  • Data-Driven Decisions: The initial user research data helped focus the redesign on the most critical pain points, ensuring the final solution had a measurable impact
Share this

Leave a comment: