Quick Start

Start with the essential framework:

# [Project Name] Case Study

Product: [Name and type] Role: [Your specific contribution] Timeline: [Duration] Platform: [Mobile app/web/etc.]

Brief description of what you designed and why.

[Specific design challenge - what wasn't working and for whom]

[High-level approach and key improvements]

# Workflow

Progress:

• Project Summary - Product name, your role, timeline, platform
• Context - Background, users, market situation
• Problem Statement - Specific design challenge
• Goals & Objectives - What success looks like
• Role & Responsibilities - Your specific contributions
• Research/Discovery - How you understood the problem
• Key Insights - 3-5 findings that shaped design
• Design Strategy - 3-4 guiding principles
• Information Architecture - User flows and organization
• Design Exploration - Iterations and rejected concepts
• Solution Breakdown - Feature-by-feature analysis
• Visual System - UI decisions and components
• Prototype/Interactions - How it behaves
• Validation - Testing and feedback
• Outcome - Results and improvements
• Learnings - Reflection and growth

For each major feature:

### [Feature Name]

**Challenge:** What problem this solved
**Design Decision:** What you created
**Rationale:** Why this approach worked
**Impact:** How it improved the experience

Progress:

• Project Summary
• Context & Problem
• Goals & Role
• Research/Discovery
• Design Strategy
• Solution Breakdown
• Outcome & Learnings

Examples

Example 1: Problem Statement Input: "The app was confusing" Output: "Although the product had useful financial features, the interface lacked visual hierarchy and consistency, making important actions harder to find and reducing user confidence in transaction security."

Example 2: Solution Feature Input: Need to explain dashboard redesign Output:

### Dashboard Overview

**Challenge:** Users couldn't quickly scan their financial status
**Design Decision:** Created a card-based layout with visual hierarchy
**Rationale:** Cards separate information types while maintaining scannable layout
**Impact:** Reduced time to find key information from 45 seconds to 8 seconds

Example 3: Key Insight Input: Research showed users were confused Output: "Users need financial information to be scannable at a glance - they check balances during brief moments throughout their day, not during dedicated review sessions."

Best Practices

• Lead with user problems, not features
• Include specific metrics when available
• Show process, not just polished results
• Use "Challenge/Decision/Rationale/Impact" structure consistently

• Break up text with clear section headers
• Include progress checklists for complex workflows
• Use consistent formatting for repeated elements
• Balance screenshots with explanatory text

• Include research methodology, even if brief
• Show design iterations and what didn't work
• Quantify improvements when possible
• Be specific about your individual contributions

• Start with project context, not your process
• Connect each design decision to user needs
• End with measurable outcomes or clear improvements
• Include honest reflection on challenges and learnings

Common Pitfalls

• Avoiding the template mindset - Don't list every portfolio piece identically
• Skipping the problem definition - Don't jump straight to solutions
• Focusing only on final designs - Show exploration and iteration
• Being vague about your role - Clearly state what you personally did
• Ignoring outcomes - Always include results, even if qualitative
• Over-explaining basic concepts - Assume design literacy in your audience
• Making it about the product - Keep focus on your design process and decisions