A polished screen gives someone a reason to pause. The explanation around it helps them understand what you can contribute to a team.
The challenge is choosing how much process to show. Include every workshop and wireframe, and the project becomes hard to follow. Show only the final interface, and the decisions disappear.
A useful case study follows the problem through a few meaningful choices to an honest outcome.
Open with the project in plain language
Before the first large image, give the reader a compact introduction:
- What were you designing, and who was it for?
- What problem were you trying to solve?
- What was your role, and who else was involved?
- Did the work ship, reach a prototype, or remain a concept?
Here's a fictional example: "I redesigned the booking flow for a community sports centre. Working with a product manager and two engineers, I owned interaction design and usability testing. The new flow shipped; the membership redesign stayed outside our scope."
That opening establishes the boundaries. The rest of the case study can explain the work within them.
Build the story around turning points
You don't need to prove that you followed every stage of a design process. Choose two or three moments when evidence or constraints changed your direction.
Perhaps you discovered that people compared dates before choosing a class. Perhaps a payment integration limited what could appear on one screen. Perhaps testing exposed a label that your team had assumed was clear.
For each moment, connect the observation to the decision: "Participants kept returning to the timetable to compare availability, so we moved date selection earlier in the prototype."
Then show the relevant artifact. A cropped flow or annotated screen can support that explanation better than an entire workshop board.
Give every image a job
Before adding an image, finish this sentence: "This helps the reader understand…"
If you can't finish it, consider removing the image. If the answer is important, put it in the caption.
Useful captions explain a change, comparison, or limitation. "Earlier concept" is a label. "This concept hid availability until the final step, so we dropped it after the first test round" tells the reader something about your judgment.
Make labels readable at the size they'll appear on the page. Include a text explanation so the point survives even when a diagram is difficult to inspect on a phone.
Explain tradeoffs without rewriting history
Real projects include constraints: time, existing components, engineering capacity, incomplete research, and competing needs.
Choose a tradeoff you can explain clearly. What did you prioritize? What did you leave unresolved? Why was that acceptable for this version?
If you're revisiting an old project, distinguish what you knew then from what you would change now. A retrospective improvement is useful, but don't present it as part of the original shipped work.
The same applies to concept projects. Label assumptions and simulated briefs. You can demonstrate careful thinking without inventing customers, research participants, or a launch.
Match outcome claims to your evidence
If you have product measurements, explain the period and the scope. Avoid attributing a whole business result to a visual change when pricing, traffic, or other features changed too.
If you only tested a prototype, report what you observed in that test. A handful of participants completing a task is useful feedback; it isn't proof of a site-wide conversion increase.
If you couldn't measure the outcome, say what shipped and what you would want to evaluate next. This gives the reader a clear boundary between evidence and expectation.
For client or employer work, include only approved material. If you create a simplified reconstruction, identify it and remove confidential details.
Make the short version work first
Read only your opening, headings, captions, and conclusion. Can someone still understand the problem, your contribution, and the result?
If so, the longer explanation can reward a closer read. If not, reorganize the story before adding more visuals.
For a broader look at selecting work, see portfolio website examples and what makes them work.
Create your Curvit profile to bring your experience and selected design work together in one place.