How to Write a Design Portfolio Case Study People Can Follow

Choose a project for the role you want

Select work that gives evidence for the skills in the roles you are pursuing. A portfolio can include client work, internal work, class projects, or self-directed work. Be candid about the setting and constraints; a self-initiated concept should not be presented as a shipped product or a client engagement.

UConn’s portfolio guide recommends selecting strong work and tailoring how it is presented. For UX and interface work, it specifically calls out the process behind the result—such as research, user journeys, wireframes, and iterations—when those details help explain the project.

University of Connecticut Center for Career Readiness: Portfolio Guide

Use a story structure, not a list of deliverables

• Context: who the work was for, the problem, and any important constraints.
• Your role: what you owned, who you worked with, and what decisions you could make.
• Evidence: what you learned from users, support requests, analytics, or existing research—and what that evidence could not tell you.
• Decision: the key alternatives you considered and why you chose one direction.
• Delivery: what you made, how it was tested or handed off, and what changed during the work.
• Outcome and reflection: what happened after release, what remains unknown, and what you would investigate next.

Show the decision with one useful piece of evidence

Suppose you redesigned a fictional appointment-request flow. Instead of showing ten polished screens in order, show the point where people could not tell whether a time was available, the evidence that led you to examine that question, two directions you considered, and the chosen design with a short explanation. A wireframe or a small annotated comparison may teach more than another full-screen mockup.

Do not invent participant quotes, test outcomes, or conversion lifts to make the story persuasive. If you have no measured result, say what was delivered and what you would measure next. If a metric is confidential, describe the directional learning only when you have permission and can do so without exposing protected information.

Illustrative limitation statement — adapt to the facts of your project

“The updated flow was handed off for implementation. I did not have access to post-release completion data, so I cannot claim that the change increased bookings. I would compare request completion and validation errors before and after launch.”

Clear limits build trust and show how you connect a design decision to a measurable question.

Edit for the person reading between meetings

Lead with a short summary of the problem and your role. Give diagrams a caption that states what the reader should notice. Expand specialized terms once, crop images to the detail that matters, and keep the main story readable without requiring a click through every artifact. Put supporting material later in the page.

Check that names and contributions are credited, client permissions are respected, and the site remains usable on a phone. A strong case study earns its length by answering questions a hiring reader is likely to have; it is not a record of every activity you completed.