Choose a project with a story to tell
You do not need a commercial client to create a credible case study. You do need enough material to explain a problem, the choices you made and what those choices produced. An assignment with a modest final deliverable but clear constraints may be more useful than a polished image you cannot explain. Look for work where you can show a brief, sketches or drafts, feedback, revisions and a finished result.
Start by separating the assignment from your own ambitions. What did the course ask you to make, for whom and under what constraints? Then identify the part you chose to explore. For example, a class brief might require a mobile app prototype, while your particular goal was to make its navigation understandable to first-time users. That distinction gives readers a way to assess your decisions without mistaking a classroom exercise for a commissioned product.
Give readers the context before showing the solution
Open the case study with a short summary: the type of project, its purpose, the deliverable, your role and whether it was an individual or group assignment. State plainly that it was student work. If the brief used a fictional organization, say so. These details do not weaken the project; they help a potential collaborator understand the conditions in which you worked.
Next, describe the constraints that shaped the outcome. You might have had a fixed format, a limited set of tools or a requirement to address a particular audience. Include only constraints that affected your decisions. A sentence such as “The prototype had to work within five screens, so I prioritized the main booking path over account settings” explains more than a long list of software and course requirements.
Show decisions, not just a timeline
A credible case study does not need to document every step. Select two or three decisions that reveal how you approached the work. For each one, describe the problem you noticed, the options you considered and why you chose a direction. Pair the explanation with relevant evidence when available: an early layout beside a revised one, a short excerpt from a content outline or a screenshot of a prototype flow.
Be precise about feedback and testing. If classmates commented on a draft, call it peer feedback rather than user research. If you asked someone to try a prototype, explain what you asked them to do and what you observed; avoid claiming that a small informal check proved the design works for everyone. You can also show how a critique changed your work: “Readers missed the primary action in the first layout, so I moved it above the supporting details.”
For group assignments, mark your contribution clearly. Say which parts you created, which decisions were shared and how the team coordinated. If you are displaying a shared final artifact, captions can identify your specific work. Give teammates appropriate credit, and check any course or team expectations before publishing shared files.
Present the outcome honestly
Show the finished work in a form a visitor can understand without opening a project file. Use a small set of legible images or excerpts, each with a caption explaining what it demonstrates. A website project might show the home page, a key interaction and a responsive layout. A writing project might include the content structure and a short before-and-after passage. Choose evidence that supports the story rather than filling the page with every screen or draft.
Explain what was delivered and what happened next, if anything. A course submission, working prototype and published product are different outcomes. Do not add performance figures or claim audience impact unless you measured it and can explain how. When there was no launch, discuss what the work achieved within the assignment: perhaps it met the brief, incorporated critique or produced a usable demonstration of an idea.
End with a brief reflection that stays specific. Name one thing you would keep and one thing you would change with more time. For instance, you might retain a simplified navigation structure but seek feedback from people outside the class before developing it further. This shows judgment without pretending the project had opportunities it did not.
Make the case study easy to review
Before publishing, check that the page answers five questions quickly: What was the assignment? What did you do? Why did you make those choices? What did you deliver? What did you learn? Put the strongest final example near the top, then let interested readers explore the process below. Keep captions readable, explain unfamiliar course terms and provide text that conveys the meaning of important visuals.
Finally, review what you have permission to share. Remove private feedback, personal details and material you do not have the right to publish. A focused, accurate account is more persuasive than an inflated one. The purpose of a student case study is not to make an assignment look like client work; it is to show how you think, make and improve.
