A portfolio case study should explain the problem, your contribution, the decisions you made and what actually happened. It is not a diary of every step or a story in which the first idea always succeeds. Give readers enough evidence to assess your judgement, including constraints and limitations that affected the result.

Build the evidence before polishing the presentation

Begin with a compact project summary: setting, task, role and current status. Then describe the problem in terms a newcomer can understand. Separate the original request from the need you investigated. Explain which evidence was available and which assumptions remained uncertain.

Choose a small number of consequential decisions for the main narrative. Show an alternative, the reason you selected or rejected it and how feedback changed the work. A screenshot becomes useful when its caption explains the decision it illustrates. End with the actual outcome: a delivered artefact, a tested prototype, an observed use or a measured result, whichever the evidence supports. Do not convert completion into proof of business impact.

Practical decisions and checks for this task
Area Useful approach What to check
Problem Explain the task and why it mattered in its actual context Do not assume the reader knows the brief
Decision Show an alternative and the evidence or constraint behind the choice Do not present every step as inevitable
Outcome State what was delivered, observed or measured Do not equate a finished prototype with proven business success

A fictional worked example

Fictional example: a student redesigned a library booking flow as a self-initiated exercise. Her first case study lists five design stages with decorative diagrams. The revision explains that users needed to compare time slots before entering details, shows two layout alternatives and records a small consented observation that led her to change the sequence.

She identifies the study’s limits and states that the prototype was not implemented by the library. The outcome is a revised practice prototype, not a proven reduction in real booking errors. The case study becomes more useful because the reader can follow the reasoning and distinguish observed evidence from the student’s interpretation.

Make each decision inspectable

Problem

Show: Explain the task and why it mattered in its actual context

Check: Do not assume the reader knows the brief

Decision

Show: Show an alternative and the evidence or constraint behind the choice

Check: Do not present every step as inevitable

Outcome

Show: State what was delivered, observed or measured

Check: Do not equate a finished prototype with proven business success

Apply the process to your own material

  1. Frame: Summarise the setting, task, role and status before describing the process.
  2. Select: Choose the decisions that best reveal your judgement and contribution.
  3. Explain: Connect evidence, alternatives, revisions and the actual result.
  4. Review: Check that a newcomer can distinguish facts, assumptions and limitations throughout the story.

Use an actual piece of your own work for this exercise, or create a clearly labelled practice example. Keep the original and revised versions so you can explain what changed. Ask a reviewer to identify the main contribution without additional explanation, then note where their interpretation differs from what you intended. Revise the evidence or wording that caused the mismatch rather than adding an unsupported claim to make the result sound stronger.

From first draft to shareable evidence
  1. Frame

    Summarise the setting, task, role and status before describing the process.

  2. Select

    Choose the decisions that best reveal your judgement and contribution.

  3. Explain

    Connect evidence, alternatives, revisions and the actual result.

  4. Review

    Check that a newcomer can distinguish facts, assumptions and limitations throughout the story.

Move forward only when the previous step is clear enough to explain. A finished-looking file still needs a content and usability review.

Review the result before sharing

Ask a reviewer to explain the problem, your role and one important decision after reading the page. If they remember only the final image, strengthen the reasoning and captions. Remove process sections that add no evidence. Check that project status, team contribution and outcome wording remain consistent across the portfolio card, case study and resume.

A closer check that strengthens the evidence

Read the case study once with the final result temporarily hidden. The reasoning should still make sense: the problem, evidence and alternatives should explain why the chosen direction was plausible. If the narrative only works because the reader is told the final design is successful, strengthen the missing links. Then restore the outcome and check whether its wording matches the evaluation actually performed. This separates a clear account of judgement from a retrospective success story in which every decision is made to look obvious. A credible case study can include uncertainty without becoming vague or apologetic.

Common questions

Does every case study need the same headings?

A consistent structure can help, but the headings should fit the work. Do not force a research stage or business metric into a project that did not contain it. The essential questions concern context, contribution, decisions and outcome. Adapt the narrative while preserving enough clarity for a reader to evaluate those elements.

Should I include every draft and screenshot?

No. Select artefacts that explain a meaningful decision or change. Too many images can make the reasoning harder to follow. Give each selected image a useful caption and ensure important information also appears in text. A private archive can preserve the full process without making the public case study a complete diary.

What if the project had no measurable business outcome?

State the actual outcome, such as a prototype, analysis, document or tested feature. Explain what was evaluated and what remains unknown. A learning project can demonstrate judgement without commercial metrics. Do not invent revenue, conversion or time-saving claims simply because another portfolio template includes an impact section.

Can I discuss a rejected idea?

Yes, when it reveals useful reasoning. Explain why the alternative was plausible and what evidence or constraint led you away from it. Avoid making the rejected option artificially foolish to make your final choice look obvious. A credible case study shows a real tradeoff rather than a predetermined success story.

How much background is enough?

Provide the context needed to understand the task, audience, constraints and your role. Remove organisational history that does not affect the decisions. A reader should not need specialist knowledge of your class or workplace to follow the project. Use concise explanations and define unfamiliar terms where they matter.

How do I separate observation from interpretation?

State what was seen or recorded first, then explain the meaning you inferred and any uncertainty. For example, a participant paused at a label; your interpretation may be that the wording was unclear. Do not report the interpretation as a directly observed fact without acknowledging the reasoning between them.

What should the outcome section include?

Describe the final artefact or state, how it was reviewed and the limits of the evidence. Include measured results only when their method and scope are defensible. A useful reflection can identify the next question or improvement. Avoid turning reflection into a generic statement that you learned teamwork without showing how.

How do I know the case study is too long?

Look for repeated claims, uncaptioned images and process sections that do not change the reader’s understanding. Ask a reviewer where they lost the main thread. Keep deeper detail available when it supports inspection, but make the central contribution and decisions easy to follow without reading an exhaustive chronology.

Sources and further reading

Reviewed 7 November 2026. Examples and exercises are original editorial guidance. University advice reflects its own context; employer instructions and local requirements take priority.