What is a UX case study?

What a case study is really for

Hiring managers rarely hire you for your layouts alone. They hire you for judgment: how you pick a problem, deal with messy information, work with other people and know when something is good enough.

A case study is where that judgment becomes visible. Pretty final screens say little about it, because anyone can polish an interface. The story of how you got there says a lot.

That is why most portfolios lean on a small number of deeper case studies rather than a long gallery of thumbnails.

The shape of a good one

There is no single required template, but most strong write-ups walk through the same beats:

• The context: what the product was, who it was for, and what your role was.
• The problem: what was actually going wrong, ideally backed by something you observed.
• The process: the research, ideas and tests that shaped your thinking, including dead ends.
• The solution: the final design, with a few screens that matter rather than all of them.
• The outcome: what changed, and what you would do differently.

Keep your own part clear. If you worked in a team of six, say what was yours.

How to write one without it taking a month

Start with the story, not the layout. Write rough notes answering one question per beat, then pick the five or six images that support them.

Aim for something a busy reader can skim in two or three minutes and a curious one can read properly in ten. Short headings, one idea per paragraph, and captions that explain why an image is there.

Show work in progress. A photo of a messy whiteboard or an early sketch is more convincing than a perfect mockup, since it proves the thinking happened.

When results are not measurable, describe what you learned or what the team decided because of your work. Honest and modest beats invented numbers every time.

Mistakes that make readers close the tab

The usual problem is a case study that is secretly a gallery: twenty screens, no explanation. Close behind is the opposite, a wall of text about process with no sense of the result.

Other pitfalls include claiming credit for the whole team's work, hiding the failures (they are the interesting part), and burying the problem under a long company introduction.

If you signed an NDA, you can still show the thinking. Blur names, change the data, or rebuild a similar example, and say that you did.

Who needs one, and how many

Anyone entering or moving within UX will benefit, from students to senior designers pitching for a new role. Two or three strong case studies usually outperform a dozen thin ones.

Choose projects that show different strengths: one research-heavy, one focused on visual craft, one showing collaboration. Then tailor which you highlight to the job you are applying for.