Structuring a UI/UX Case Study

1. What is a Case Study?

At its core, a UX case study is a story that walks a potential client or employer through your design process on a specific project. It’s your single most important tool for demonstrating not just your visual skills, but your critical thinking, problem-solving abilities, and ability to create business impact.

Let's start with a clear definition and some common pitfalls to avoid.

The key mistakes to avoid are:

• Only showing the final, polished screens. This is like presenting only the final balance sheet without the supporting statements. The value is in the process.
• Forgetting the problem statement. Every project must start with a "why." Without a clear problem, your solution has no context.
• Poor presentation. Typos, misaligned elements, and blurry images suggest a lack of attention to detail—a red flag for any client.

2. The Classic Case Study Framework

Most successful case studies follow a simple, logical narrative structure. The most common is the Problem-Process-Solution-Outcome framework. It’s effective because it’s easy for anyone to follow, from a fellow designer to a non-technical business owner.

Let's break down each component:

1. Problem: This sets the stage. It defines the challenge from both a business and a user perspective. A great problem statement is concise and compelling. It answers:

   • What was the business goal or challenge? (e.g., "To increase freelance efficiency...")
   • What user pain point were you trying to solve? (e.g., "...by reducing the time spent recreating common UI elements.")
   • What were your specific role and responsibilities on the project?

2. Process: This is the "how." It's a curated walkthrough of the key steps you took to get from the problem to the solution. This section should showcase your skills and thinking. You don't need to show every single thing you did. Instead, highlight 2-3 pivotal moments or decisions. For example:

   • Research: Competitor analysis, user interviews.
   • Ideation: Sketches, user flows, information architecture.
   • Design: Wireframes, building components, defining styles.
   • Validation: Usability testing, feedback sessions.

3. Solution: This is the "what." Here, you present your final, polished designs. But don't just show them—explain them. Use annotated mockups to connect specific design decisions back to the original problem. For example: "The button component includes variants for hover, focused, and disabled states to improve accessibility and provide clear user feedback, directly addressing a gap found during competitor analysis."

4. Outcome: This is the "so what?" It demonstrates the impact of your work. Your background in commerce makes this section your secret weapon. Whenever possible, use quantifiable metrics.

   • Business Impact: Did it save time? Increase revenue? Improve conversion? (e.g., "The design system is projected to reduce UI development time by 30% on future projects.")
   • User Impact: Was the experience improved? (e.g., "Usability testing showed a 50% decrease in task completion time.")
   • Learnings: What did you learn? What would you do differently next time? This shows humility and a growth mindset.

3. A Business-Focused Alternative: The Minto Pyramid Principle

Given your background, you'll appreciate this alternative structure. The Minto Pyramid Principle, developed at McKinsey for executive communication, flips the classic narrative. Instead of building up to the conclusion, you start with it.

It's structured in three layers:

1. Top: The Answer. Start with your single most impressive, quantifiable outcome.
2. Middle: Key Arguments. Provide 2-3 key findings or decisions that led to that outcome.
3. Bottom: Supporting Evidence. Show the data, research, and process details that prove your arguments.

This "answer-first" approach is incredibly effective for busy stakeholders who want the bottom line upfront.

While you'll likely write your portfolio case study using the classic narrative, keeping the Minto Pyramid in mind is invaluable for live portfolio presentations, where you might only have 5 minutes to impress a CEO.

4. Deconstructing a Real-World Example

Let's see how this structure plays out in a real portfolio presentation. In this video, a designer walks through a case study for a project at Amplitude. Notice how he clearly establishes the problem, details his process, and presents a solution with measured outcomes.

As you watch, you can clearly map his story to the Problem-Process-Solution-Outcome framework. This is the structure you will now apply to your own project.

5. Your Turn: Outline Your Design System Case Study

Now it's time to apply what you've learned. You will create an outline for a case study based on the design system you built in Module 10. Open a document and use the following structure as a template. Be concise—use bullet points for now. The goal is to create a strong skeleton for the narrative you will write later.

Project Title: Building a Scalable Design System for [Your Freelance Brand Name]

1. Problem

• Business Problem: As a freelance designer, I need to deliver high-quality, consistent work efficiently. Without a system, each project starts from scratch, leading to wasted hours and potential brand inconsistencies across client projects.
• User/Designer Problem: Time is wasted on repetitive tasks like creating buttons and forms. Manually ensuring consistency in spacing, color, and typography is tedious and prone to error.
• My Role: Product Designer (leading the project from conception to execution).
• Project Goal: To create a single source of truth—a reusable component and style library—to accelerate my design workflow and ensure professional-grade consistency for all future projects.

2. Process
(List the key stages you went through. Think back to the lessons in Module 10.)

• Audit & Strategy: Deconstructed an existing, mature design system (like Material Design) to understand its structure (tokens, components, patterns).
• Foundation Definition: Defined design tokens in Figma for colors, typography, spacing, and elevation to serve as the system's core variables.
• Component Construction: Built a core set of versatile, multi-state components using variants and Auto Layout, including:
  • Buttons (Primary, Secondary, etc.)
  • Form Inputs (with labels, error states)
  • Cards (for content display)
  • Modals (using a 'slot' pattern)
• Documentation: Wrote concise usage guidelines for each component, including do's, don'ts, and accessibility considerations.
• Publication: Structured the Figma file for collaboration and published it as a team library for use across projects.

3. Solution
(Describe the final deliverable and highlight its key features.)

• A Published Figma Library: A professional, centralized library of styles and components.
• Key Feature 1: Token-Based Styles: All colors and fonts are managed through styles, allowing for easy global updates.
• Key Feature 2: Variant-Powered Components: Components like buttons and inputs have all their states (e.g., hover, disabled, error) built-in as variants for easy use.
• Key Feature 3: Clear Documentation: A dedicated page in the Figma file explains how and when to use each component.
  (You would include screenshots here: your organized Figma file pages, your button component variants, etc.)

4. Outcome & Learnings

• Impact on Efficiency: This system is projected to reduce the time for designing standard UI screens by over 40%, allowing for more focus on complex UX problems.
• Impact on Quality: Guarantees 100% consistency in visual design, elevating the professionalism of client deliverables.
• Impact on Handoff: Provides a clear, inspectable system for developers, reducing ambiguity and development time.
• Key Learning: The importance of a robust variant structure. I learned that planning component properties upfront is crucial for creating a truly flexible and scalable system.
• Next Steps: I plan to expand the library with more complex components like data tables and navigation patterns as client needs arise.

Spend about 15-20 minutes filling this out. This outline is the blueprint for your first portfolio piece.

Conclusion

In this lesson, you've learned how to transform a project from a series of tasks into a compelling narrative. You now have a solid, structured outline that demonstrates not just what you can do, but how and why you do it—a crucial differentiator in the freelance market.

Key Takeaways:

• A case study is a story of how you solved a problem.
• The Problem-Process-Solution-Outcome framework is a reliable structure for telling that story.
• Focus on highlighting key decisions and connecting your design work to tangible business impact.
• Your background in finance and auditing gives you a natural advantage in creating logical, detailed, and business-focused case studies.

Preview of the Next Lesson:

With this strong outline in place, our next step will be to flesh it out. In the next lesson, we will focus on writing a compelling design narrative that connects business goals to design decisions and user needs. You'll learn how to turn your bullet points into engaging prose that captures a client's attention from the first sentence to the last.