UX/UI portfolio: case studies that show how you think

Why screens alone are not enough

Anyone can imitate a pretty screen. What a studio or product team wants to know: do you understand the problem, can you research, can you justify decisions and do you work iteratively? You cannot see that in a final screen; you see it in the road towards it.

Three to four case studies

Depth beats breadth. Choose:

• One project with real research — interviews, observation, a test with users.

• One project with a clear interface decision — navigation, form, onboarding.

• One project with a measurable effect — faster, fewer errors, higher conversion, or a concrete reaction from users.

• Optional: one free or speculative project that shows what you make when nobody asks.

The structure of a UX case study

1. Problem — for whom, what goes wrong, how do you know? One paragraph.

2. Research — what you did (and with how many people), what you learned, what surprised you.

3. Directions — two or three concepts, sketches or wireframes, and why you chose.

4. Iterations — what you tested, what did not work, what you changed. This is the heart.

5. Interface — the final screens, large, in context (phone, desktop).

6. Effect — numbers if you have them; otherwise reactions, a pilot, what the client did with it.

7. Reflection — what you would do differently now.

This is a specialised version of the general [case-study structure](/en/guides/how-to-write-a-case-study).

Images

• Wireframes and sketches may be rough; they prove process.

• Final screens sharp, in a device frame, at full width.

• One image that puts "before and after" side by side says more than three paragraphs.

• Short videos or loops of interactions work well; keep them under ten seconds.

Pitfalls

• A gallery of thirty screens. Nobody reads it.

• Research that leads nowhere. If you did interviews, show which decision changed because of them.

• "We" without "I". Name your role, especially in team projects.

• Only success. A test that failed and what you did next is more convincing than a flawless story.

• Jargon. A double diamond on every page does not replace content.

Presentation

A UX portfolio may itself be a well-designed product: clear navigation, fast loading, readable on a phone. Choose a calm setting in which the screens stand out. In Folyra the Studio engine works well for interface work; the Frame engine (black, video as the hero) if you have many moving prototypes. See the example portfolio of [Milo Vermeer](/en/examples/milo-vermeer), a fictional maker of titles, 3D and motion identities.