What to put in a UI/UX case study

A UI/UX case study explains the problem, how you reached the solution and whether it works in practice. It is not a gallery of screens: it’s an explanation of your thinking, and the person reading it, whether that’s a client or a hiring manager, wants to know whether they can trust that thinking.

Here’s the structure I’d use.

1. Start with the problem

Say what the problem was in a few sentences. Who had it, what wasn’t working, and why it mattered. If the reader doesn’t understand the problem, they can’t judge your solution.

Add one line on your role and the project’s scope, so it’s clear which part of the work was yours.

2. Explain how you reached the solution

This is the part most case studies skip, and it’s the most important. Don’t jump from the problem to the finished design. Show how you came to the solution: what you looked at, what options you considered, and why you chose the one you did.

Someone should be able to follow your reasoning and see that the final design wasn’t a lucky guess.

3. Show the solution

Now show the design. Use the best few screens rather than all of them, and say what each one is solving. Tie every screen back to the problem you described at the start.

4. Show that it works in practice

A solution can sound good in theory and fail in practice, so show which one yours is. Explain how you checked that it was practical: what you tested, what you learned, and what you changed because of it.

If you have real results, include them. If you don’t, don’t make any up. A clear account of how you tested the idea is more convincing than a number the reader can’t trust.

5. Finish with what you learned

Close with a short reflection: what worked, what you’d do differently, and what you’d try next. It shows you can look at your own work honestly.

What to leave out

• Most of your projects. Show only the ones that represent your skills well. The biggest mistake I see in other designers’ portfolios is showing too many projects at once. A few strong case studies make a better impression than a long list.
• Every screen you made. Keep the ones that explain your thinking.
• Decoration without information. If a section doesn’t help answer the problem, the solution or the proof, cut it.
• Results you can’t support. Claim only what you can show.

A copy-and-paste outline

1. The problem: who had it and why it mattered
2. My role: what I was responsible for
3. How I got to the solution: what I looked at, what I considered, why I chose this option
4. The solution: the best few screens, each tied to the problem
5. Does it work in practice: what I tested, what I learned, what I changed
6. What I learned: what worked and what I’d do differently

Where to put it

Each case study can live in a CMS collection on your portfolio site, with one reusable page that shows every project. If you use Framer, my guide to building a portfolio in Framer in a weekend walks through the setup.