Write a portfolio case study that shows what you learned
A portfolio learning case study explains the task, your decisions and the evidence behind the final result. State whether the work is an exercise, concept, internal project or client assignment. This guide helps beginners show useful reasoning without inventing commercial outcomes or making the screenshots carry claims they cannot support.
A portfolio learning case study explains the task, your decisions and the evidence behind the final result. State whether the work is an exercise, concept, internal project or client assignment. This guide helps beginners show useful reasoning without inventing commercial outcomes or making the screenshots carry claims they cannot support.
Key ideas
- The work is labelled as exercise, concept or actual assignment.
- Your role and other contributions are stated.
- The task has a clear user outcome.
- One decision is explained through a real constraint.
Begin with the task and your role
Explain who the imagined user is and what they should be able to do. Name your contribution: research, interface design, code or testing. If a teammate supplied part of the work, say so. A fictional restaurant website is still a legitimate exercise when it is labelled clearly. It becomes misleading when its invented context is presented as a real client or a measured business result.
Show the constraint that shaped a decision
Choose a meaningful constraint such as a small screen, long translated labels or a keyboard-only journey. Explain the options you considered and why you selected one. A before-and-after image is more useful when the reader knows what problem changed. MDN’s planning material is relevant context for making these decisions explicit. Avoid filling the case with every exploration if it obscures the final reasoning.
Attach evidence rather than an unsupported outcome
Include a reproducible task, a prototype link or a short test record. Describe what the check observed and what it did not cover. If nobody measured conversion, do not claim a conversion improvement. If your research was a conversation with a peer, do not call it a market study. GOV.UK’s interview guidance is useful methodological context; the exercise here remains a learning project with a small scope.
End with the next question
A credible case can contain an unresolved issue. Explain which assumption needs another test and what you would do with more time. Keep the final work, source credits and contribution notes accessible. Ask a second person to read the case without your explanation and identify the task, decision and evidence. If they cannot, revise the story before adding more visual polish.
Your evidence checklist
Mark only what you have checked. This records your own progress, not an independent audit or a predicted result. There is no automatic saving; download the note if you want to keep it.
0 / 6 checked
In everyday language
A strong learning case connects the task, your decision and the evidence without making the result larger than the project.
Try it yourself
Write a one-page case for a completed learning exercise. Include the task, your role, one constraint, one decision and one test. Ask a peer to identify those elements without coaching.
Expected result
A concise case with an honest project label, working evidence links and one next question. It contains no invented client, quotation or commercial result.
Check your answer: Can a concept project belong in a portfolio?
Yes, when its status and your role are clear. A concept can demonstrate decisions, craft and testing within its defined scope. Do not attach invented client names or measured performance to it. Explain what a real assignment would still need to validate.
Questions
Can a concept project belong in a portfolio?
Yes, when its status and your role are clear. A concept can demonstrate decisions, craft and testing within its defined scope. Do not attach invented client names or measured performance to it. Explain what a real assignment would still need to validate.
Do I need a success metric in every case?
Use a metric only when it was actually measured and its scope is clear. A test observation, corrected failure or well-explained decision can be useful evidence. Inventing a percentage to make the case impressive makes the reasoning less trustworthy, not more convincing.
A strong learning case connects the task, your decision and the evidence without making the result larger than the project.
Sources and further reading
- MDN — Thinking before coding ↗Sources checked:
- GOV.UK — In-depth research interviews ↗Sources checked: