Tell a Credible Portfolio Story

Choose the capability the case study should demonstrate before selecting the project images. You might want to show how you clarify an ambiguous brief, create a visual system or coordinate a careful production. That purpose helps you decide which parts of the project deserve space. Write the context and your responsibility early, including who else contributed. A reader should not need to infer whether you led the whole project, completed one specialist part or joined after major decisions had already been made.

Draft the introduction in two sentences and check every claim against your actual involvement. Name the assignment, the relevant constraint and the part you were responsible for. Avoid turning the opening into a list of software or a broad statement about creative passion. Then select the material that supports the capability you chose. A beautiful image can stay if it helps explain the work, but it should not displace the decisions that make the case study meaningful for someone evaluating how you think and contribute.

Practice: Write a two-sentence introduction naming the context, your responsibility and the capability you want to show.

Build each main section around a decision rather than around a generic stage label. Explain the constraint, the alternatives you considered and the reason for the chosen direction. A process image should help the reader inspect that reasoning. Instead of showing several layouts as exploration, describe what changed between them and which problem the change addressed. This approach lets you include only the material that reveals judgment, rather than reproducing the entire project history in the order it happened to be saved.

Write the three decision paragraphs from the exercise and read them without the images. Check whether each paragraph contains a real tradeoff or only describes an action you took. Then add the minimum image and caption needed to make the choice understandable. Include uncertainty or a rejected option when it explains the final result. A case study does not become weaker because a first attempt needed revision; a clear account of how you recognized a problem and changed direction can make your contribution easier to assess.

Practice: Draft three decision paragraphs, each with a constraint, a choice and an explanation.

Create an evidence table before writing an outcome headline. For each proposed claim, record the source, the period or scope it covers and whether you have permission to share it. Distinguish a measured result from a client's opinion, your own observation or a deliverable that was completed. These are different kinds of evidence and should be described accordingly. Do not imply that your work caused a business change merely because the change happened around the same time as the project was released.

If no measured result is available, describe what can be supported. You can explain what was delivered, which constraint was resolved, how feedback changed the work or what you learned from the process. Use specific language and keep the limits visible. Remove a metric when its source or meaning cannot be checked, even if it would make the page look more impressive. The exercise should leave you with fewer unsupported statements and a clearer understanding of which evidence genuinely helps a reader evaluate the project.

Practice: Create an evidence table with claim, source, publication permission and any limitation.

Design the case study for a quick scan and a more careful read without telling two different stories. The title, introduction, section headings and captions should communicate the assignment and your contribution at a glance. The body can then explain the decisions and evidence in more detail. A reader who stops after one minute should retain the same central claim that the longer version supports. Avoid an ambitious opening that the actual project material cannot substantiate once someone reads beyond the first screen.

Write the short overview and compare it with the full draft. Remove repeated context, shorten headings that describe process without meaning, and check whether each image earns its place. Ask another person to state your role and the most important decision after a quick read. Then ask what they understood differently after reading carefully. Use the gaps to adjust hierarchy or explanation. This final pass is about making the story easier to navigate, not compressing every part into a slogan or hiding complexity that matters to the work.

Practice: Produce a one-minute overview and a longer version, then ask whether they communicate the same contribution.