Project Title Goes Here
A concise overview of the project — the problem space, your role, and a hint at the outcome. Keep this to two or three sentences.
The problem
Describe the problem in concrete terms. Who experienced it, when, and what was the business or user impact? Avoid jargon. Write as if explaining to a smart friend outside your field.
Include any relevant context: company background, team structure, constraints, or goals that shaped the project from the start.
One-sentence framing of the core design challenge.
Specific things you owned: research, IA, visual design, prototyping, etc.
Top-line result — metric, launch milestone, or qualitative win.
Understanding the users
Describe your research approach: what methods you used, how many participants, and why you chose those methods for this problem.
What I did
Walk through the research activities — user interviews, surveys, analytics review, competitive analysis, etc. Be specific about numbers and scope.
Caption: describe what the image shows and what it revealed.
Key findings
Summarize the most important things you learned. Use specific quotes or data points.
Users struggled with X because Y, leading to Z behavior.
The biggest drop-off occurred at the [step] stage of the flow.
Mental model mismatch: users expected A, the system did B.
Framing the opportunity
Synthesize research into a clear problem statement or "How Might We" questions. Show how you moved from raw data to an actionable design brief.
Caption describing the artifact and what it communicated to the team.
Explain any prioritization decisions you made here — what you decided to tackle first and what you deliberately left out of scope, and why.
Exploring solutions
Describe your ideation process. Did you run a design sprint? Sketch solo? Facilitate a team workshop? Show range — don't just show the final direction.
Early concepts exploring different structural approaches to the problem.
Explain how you narrowed down from many ideas to a focused direction. What criteria guided the decision? What did you test or discuss with stakeholders?
The solution
Walk through the key design decisions in your final solution. Show the actual screens or interactions — don't just describe them.
Mid-fidelity wireframes showing the revised information architecture.
Decision 1: [Name the decision]
Explain a specific design decision and the reasoning behind it. Connect it back to a research insight or constraint. This is where interviewers look for critical thinking.
Final screens after two rounds of usability testing and iteration.
Decision 2: [Name the decision]
Another key design choice — perhaps a trade-off you made, a pattern you introduced, or an edge case you designed for.
Validating with users
Describe how you tested your designs. Usability testing, A/B test, beta launch? How many participants, what tasks did you give them?
What we learned
Share specific findings from testing — both confirmations and surprises. Show how results changed the design.
Users completed [task] 40% faster than with the old flow.
The label "Submit" caused confusion — we changed it to "Confirm order."
Notification settings deprioritized for v1, planned for v1.2.
Results & reflections
What happened after launch? Share metrics, qualitative feedback, or business impact. Be honest about what you'd do differently.
Task completion rate improved from 62% → 89% post-launch.
Support tickets related to [area] dropped by 35% in Q1.
NPS for the onboarding flow increased from 24 to 51.
What I'd do differently
Honest reflection: what you underestimated, what you'd invest more time in, or what you learned about your own process. This shows maturity and self-awareness.