How to review a UX case study in 10 minutes

You can review a UX case study well in ten minutes if you read it in the same order a hiring manager does: orientation, decisions, evidence, outcome and then craft. This guide gives a timed method for reviewers and a way for designers to test their own case studies.

How does a hiring manager read a case study?

Most readers skim first and read closely only if something earns it. They want quick answers to four questions: What was the problem? What was your part? What did you decide, and why? What changed because of it? A case study that answers those near the top buys a close read.

The 10-minute method

1. Minutes 0-2: orient. Read the title, the first paragraph and the headings only. Write down the problem, the role and the result as you understand them. If you cannot, note where you got lost.
2. Minutes 2-5: find the decisions. Look for moments where the designer chose between options. Mark each decision, the alternatives and the reason. Case studies that only list steps ("we did research, then wireframes") show activity, not judgement.
3. Minutes 5-7: check the evidence. For each claim, find proof: a quote, a test result, a metric, a before-and-after. Mark claims with no evidence.
4. Minutes 7-9: read the outcome. Is the result stated and believable? Is there honest reflection on what did not work?
5. Minute 9-10: craft and form. Scan for readability, image quality, length and layout. Then write your reply.

What are the most common problems?

• The role is missing, so you cannot tell what the designer did.
• Process is shown as a tidy sequence, with no dead ends or trade-offs.
• Outcomes are vague ("improved the experience").
• Screens are shown without explanation of why they look that way.

How should you write the review?

Use the three-part reply: one strength, one unclear spot and one change to try. Quote the exact section you mean. Link back to the 15-point checklist for the craft items, and to what good feedback sounds like for wording.

FAQ

How long should it take to review a UX case study?

Ten minutes is enough for a useful review if you follow a fixed order: orient, find decisions, check evidence, read the outcome and then judge craft. Longer reviews are fine, but a focused ten minutes beats an unfocused hour.

What should a UX case study include?

It should state the problem, your role and the team, the key decisions with their reasons, the evidence behind them and the outcome. Process artefacts like sketches or research notes help when they explain a decision.

How do I show impact if I do not have metrics?

Describe the observable change: what the team could do afterwards that they could not before, what users stopped struggling with, or what decision the work unblocked. Be honest about what you do not know.

Why do recruiters skim case studies?

They read many in a short time, so they use headings, the opening paragraph and the outcome to decide whether to read closely. Make those parts do the most work.