How to write design portfolio case studies people finish reading
The final screens are the least interesting part of your work. A good case study shows the brief, the decisions and what changed because of them.
A gallery of polished screens tells a reviewer that you can make things look good. It does not tell them how you got there, which is what they are hiring for. Design leads, recruiters and clients want to see how you think: how you understood the problem, which options you rejected, how you worked with other people and whether the result made a difference.
A case study is the format for that. Done well, it is the most persuasive thing in a design portfolio. Done badly, it is a wall of process photos that nobody scrolls through.
Why case studies beat a gallery of screens
Screens show the output. A case study shows the judgement behind it, and judgement is what separates a designer someone wants to hire from one who can follow a brief. It also answers the questions a reviewer would otherwise have to ask in an interview: what was your role, what were the constraints, and how do you know it worked?
Keep the gallery too, if your work is strongly visual. But lead with two or three case studies, and let the gallery support them rather than replace them.
The structure that works
Use the same order for every case study. Reviewers learn where to look after the first one, and a consistent shape makes it obvious when something is missing.
- The problemWho was affected, what was going wrong and why it mattered to the business or the people using it. Two or three sentences.
- Your roleYour title, the team around you and which parts were yours. Name the collaborators by role, such as a product manager and two engineers.
- The processThe few decisions that shaped the outcome: research that changed your mind, options you tested, constraints you designed around. Not every workshop.
- Your solutionWhat you designed and why it answers the problem. This is where the best screens belong.
- The resultWhat happened after launch: behaviour that changed, feedback, adoption, or what you learned if it did not ship.
- The numbers that matteredOne to three measures you can stand behind, with what they were measured against. Leave this out rather than guess.
- Screenshots with captionsEach image with a line saying what it shows and why it matters. An uncaptioned image makes the reader do the work.
Writing each part well
Open with the stakes
The first lines decide whether anyone reads the rest. Start with the problem in plain language, not the company's history or your design philosophy. "New customers were abandoning sign-up at the identity check" gets attention. "I was excited to join the team in spring" does not.
Be precise about your role
Most design happens in teams, and reviewers know it. Saying exactly what you did, and what others did, reads as confidence. Vague "we" language reads as either modesty or inflation, and the reader cannot tell which.
Show decisions, not activities
Sticky notes on a wall prove a workshop happened, not that anything was learned from it. For each process image, say what it changed. If a stage did not change anything, leave it out.
Use only numbers you can defend
A real number with context is powerful. A guessed or borrowed one is a liability in an interview. If you do not have figures, describe the result in words: what users could do afterwards, what support stopped hearing about, what the team adopted.
Handling work under NDA
Much of the best design work is confidential. You still have options, roughly in order of preference:
- Ask. Many clients and employers will approve a case study if you show them the draft and remove anything sensitive.
- Anonymise. Remove the company name, change identifying copy and blur or redraw data, while keeping the problem and the decisions intact.
- Describe without visuals. Tell the story of the problem and your approach, with your own sketches or diagrams in place of real screens.
- Share privately. Keep the full case study off the public site and show it only to the people evaluating you, behind a password or in a PDF sent on request. PDF portfolio or portfolio website? weighs the two.
Whatever you choose, follow the agreement you signed. If you are unsure, ask the client before you publish, not after.
On Introfio, the private option is a password-protected page, which is a Pro feature. You set a password for a page in the editor's Publish tool under Page passwords, and visitors see a password prompt instead of the content. A protected page is hidden from search engines, its content is not sent to the browser until the password is checked, and once someone enters it the page stays open on their device for 12 hours. Share the password only with the people who need it, and change it when the process is over. Publish your site covers the details.
How many case studies to show
Three is a good target, and two strong ones beat five thin ones. Choose the ones closest to the work you want next, and make sure between them they show range: perhaps one research-heavy project, one where you shipped under tight constraints and one with a clear measured result.
Below the case studies, a short list or gallery of other work can show breadth without asking anyone to read more. Feature your strongest case study first; many reviewers only open one.
Presenting them on the page
Give each case study a cover image and a one-line summary on your main page, so a reviewer can pick the one most relevant to them. Keep the full write-up scannable: short paragraphs, clear headings for each stage, and images placed next to the words that explain them.
Introfio's Work section has fields for exactly this structure: The problem, My role, Process, What I did, The result, Key numbers and up to eight Screenshots, each with a caption. Set an entry's type to Case study and fill in only the fields you have; a template draws only what is filled in. The Designer template, on Pro, is built around image-led case studies, and because every template shares the same sections, switching layouts later keeps what you wrote. If you want each case study on its own page, multiple pages are also on Pro; pages and navigation explains how they work.
Before you share it
Read each case study as a stranger would, ideally on a phone. Can you tell what the problem was within the first few lines? Is it clear what you did? Does every image have a reason to be there? Then ask someone outside design to read one and tell you what you did. If they cannot, rewrite the role section first.
When the work is ready, publish your site explains going live and setting page passwords, and what to put on a personal website covers the sections around your case studies. The designers page shows how Introfio is set up for this kind of portfolio.
Common questions
How long should a design case study be?
Long enough to cover the problem, your role, the key decisions and the result, and no longer. Most readers skim, so clear headings and captioned images matter more than length.
Can I show work I did under an NDA?
Only as far as the agreement allows. Ask permission, anonymise the work, describe it without visuals, or share it privately with the people evaluating you.
What if my project never launched?
It can still be a strong case study. Explain what you designed, why it did not ship and what you learned, which shows judgement as clearly as a launch does.
Can I password-protect a case study on Introfio?
Yes, on Pro. Set a password for the page in the Publish tool, and only people with the password can see it. Protected pages are hidden from search engines.
Keep reading
- Publishing your site: going live, updating it and taking it offlineHow publishing works in Introfio: Draft, Live and Changes pending, the Before you publish checklist, unpublishing, and password-protected pages on Pro.Guides
- Pages and navigation: add pages and reuse sections across themAdd, rename, hide, reorder and delete pages on your Introfio site, how page addresses work, plan limits, and how to reuse or sync a section across pages.Guides
- What to put on a personal website (and what to leave off)The sections a personal website needs, in the order visitors read them: intro, about, work, experience, services, testimonials and contact, plus a checklist.
Build your site on Introfio
Pick a template, fill it in, and publish on your own link. Free to start, no card needed.