Start with the decision, not the archive
A case study is a guided explanation of a project, not a complete record of everything you made. Sketches, screenshots, meeting notes and rejected drafts can all be useful, but only when they help a reader understand a decision. Before selecting images, write down the central question your case study should answer. For example: How did you turn a broad brief into a usable identity? Or how did you simplify a complicated sign-up flow?
Give readers enough context to judge the work: the goal, your role, the audience, the main constraints and the final deliverable. Keep this introduction short. A freelance designer might explain that a client needed packaging that remained legible at small sizes. A student might note that a classroom assignment required a concept to work across print and screen. These details make the process meaningful without forcing readers through the entire brief.
Choose a few moments that changed the work
Look through your project files for turning points rather than a fixed number of artifacts. A useful process item shows a problem, an option you considered, feedback you received or a change you made. For a website project, that might mean showing an early page structure, one round of usability notes and the revised navigation. Ten nearly identical wireframes are less informative than two versions with a clear explanation of what changed between them.
For each item, ask: What can a reader learn from this that the final image cannot show? If the answer is unclear, leave it out or combine it with another item. You can mention that you explored additional directions without displaying every variation. This keeps the case study honest about the work involved while protecting its main story from clutter.
Pair evidence with concise explanations
Process images should do more than decorate the page. Give each sketch, draft or screenshot a caption that identifies its purpose and explains the decision it informed. Instead of “Early concepts,” try “The first layouts put all three actions on one screen; the revised version gave the primary action more space.” The second caption tells readers what to notice and why the artifact belongs in the case study.
Separate observation from interpretation. You may know that a change made the design feel clearer, but a reader cannot see that reasoning unless you state what you adjusted. Describe the specific choice, such as reducing competing type sizes or moving instructions closer to a form field. If a decision came from feedback, say what kind of feedback it was and how you responded. Do not imply that a design was tested with users if it was only discussed with a teammate or instructor.
Make the page easy to scan
A reader should be able to follow the project at two speeds: by scanning the headings and key visuals, or by reading the full account. A simple sequence works well: brief, challenge, selected process, outcome and reflection. Place the strongest final image near the beginning so readers know where the story leads, then use process examples to explain how you arrived there. Short captions and consistent labels help more than long blocks of commentary beside every image.
Treat selection and presentation as part of the edit. Crop screenshots so the relevant change is visible, while retaining enough context to understand it. If you show two versions for comparison, present them at similar sizes and label them clearly. Add descriptive text for important images when publishing online; readers should not have to rely on a visual alone to understand your point. A small team can use the same approach while identifying which decisions were shared and which work each contributor owned.
Close with an outcome and a useful reflection
Finish by showing what was delivered and how it addressed the original goal. If you have a concrete outcome you can verify, describe it accurately. If you do not, explain what the final deliverable was designed to do rather than claiming that it succeeded. For example, you can show how a set of templates accommodates different content lengths without inventing performance results.
A brief reflection adds depth when it names a lesson rather than offering a generic success statement. What constraint shaped your best decision? What would you revisit with more time? For a personal concept project, distinguish your proposed solution from something that was launched. The strongest case study leaves readers with a clear view of the finished work and enough selected evidence to understand your judgment, without asking them to sort through your entire project folder.
