How to write a portfolio case study that explains your decisions
A portfolio case study explains the problem, your role, important decisions, the work produced and the evidence available to assess it. It distinguishes a teaching project from paid client work and separates tested behaviour from unmeasured outcomes. The reader should understand why you chose the approach and what the result actually establishes.
The example documents the fictional workshop website used throughout the learning route. It has no paying client or revenue result. That limitation still allows a useful case study: the brief, prototype, checks and revisions can show how you approached a defined task.
Key ideas
- State the context and your actual role.
- Explain decisions using evidence and alternatives.
- Show the work in relevant states and applications.
- Label unmeasured outcomes and teaching projects honestly.
Give the problem a clear boundary
Write who the project serves, which task needed support and what your role covered. If you used a fictional brief, say so near the beginning. Identify collaborators or tools accurately without suggesting an endorsement. For the workshop, the goal is to make session information understandable and support an enquiry. This is narrower and easier to assess than claiming to transform a business or build a complete product strategy.
Select decisions that explain the process
Show a few consequential choices: the information hierarchy, the form’s states or the distinction between the offer page and a teaching guide. Explain the alternative you considered and the observation or constraint behind the selection. Avoid turning every screenshot into a chronology of tools opened. A reader learns more from a brief explanation of a changed decision than from a long gallery of nearly identical drafts with no reason attached.
Make the evidence inspectable
Include the brief, a relevant prototype view and a note of checks performed. For an implemented page, show narrow-screen behaviour and how the form responds to missing input in a test environment. Describe what these checks establish and what they leave open. A screenshot supports a claim about the displayed state; it does not establish conversion, revenue or reliable delivery. If you conducted a small research exercise, state its scope rather than manufacturing a success percentage.
Close with limits and the next question
Summarise the work completed, the strongest evidence and the unresolved part. You might have checked the layout and form states without testing delivery to a production account. Say that plainly. If you later obtain new evidence, update the case study and keep its date meaningful. A useful portfolio demonstrates judgement, including the ability to recognise a limit. Do not turn a teaching example into a client story by adding a fabricated brand, testimonial or financial result.
In everyday language
A case study is a guided explanation of work you actually did. The reader sees the problem, a decision, the artifact and the check that supports your conclusion. Honest limits make that chain easier to assess, even when the project began as a learning exercise.
Try it yourself
Write a one-page case study of the workshop project. Include the fictional context, your role, two decisions, three artifacts, completed checks and one unresolved question.
Expected result
A concise account whose statements can be matched to visible work. It labels the project’s status and does not claim a client, revenue change or user result that was never measured.
Check your answer: Can a before-and-after screenshot prove a conversion increase?
No. It shows a visual change. A conversion claim needs appropriate measurement, definitions, period and context. If those data do not exist, describe the observable design change and the checks you actually performed.
Questions
Is a teaching project suitable for a portfolio?
It can be useful when its context is clear and the work explains your reasoning. Label it as a teaching or personal project, describe the constraints and show artifacts you created. The reader can then assess the demonstrated skills without assuming there was a paying client. The case study should state what was tested and avoid turning an exercise into an invented commercial outcome.
How much process should I include?
Select the process that helps explain the important decisions. Usually the brief, an alternative, a revision and its evidence provide more value than every draft. Keep the account readable and relate each artifact to the problem. There is no required universal length; the useful amount is what lets someone understand your role, assess the result and recognise its practical limits.
Show the problem, the decision and its evidence. A portfolio becomes stronger when its claims stay close to the work.
Sources and further reading
- GOV.UK — Using in-depth interviews ↗Sources checked:
- MDN — Thinking before coding ↗Sources checked:
- W3C WAI — Accessibility curricula ↗Sources checked: