Create an Honest Portfolio Case Study from a Small Project
A portfolio case study should help a reader understand how you think and what you actually made. It does not need a famous client or a dramatic performance graph. A small, clearly explained project can show planning, judgement and delivery more convincingly than a beautiful image with no context. This guide covers commissioned work and self-initiated samples, with a simple structure that keeps claims, permissions and your personal contribution visible.

Photo: ANTONI SHKRABA production · License. Illustrative stock photography.
Choose a project that answers a buyer's question
Select a project related to the service you want to offer. If you edit workshop materials, a carefully organised handout shows more relevant judgement than an unrelated fantasy poster. Ask what the viewer needs to know: can you improve information order, handle supplied copy or produce usable files? Choose two or three decisions you can explain from evidence. A project does not need to prove everything. Remove private information before gathering screenshots, and confirm whether the client permits public presentation at all.
State the context and your exact role
Open with the assignment, audience, constraints and your contribution. Example: self-initiated practice project; I wrote and designed a four-page guide for an invented neighbourhood repair workshop. For commissioned work, identify any collaborators and distinguish your tasks from theirs. Do not describe an entire campaign as your own when you only produced the captions. If the client must remain unnamed, explain the type of organisation without revealing identifying details. Readers should not have to guess whether the project was real, speculative or a team effort.
Show a few meaningful process decisions
A useful sequence is initial problem, explored approach and selected solution. For a dense handout, show how you grouped the materials list, changed heading order and separated actions from background notes. Explain why each change suits the reader. Include rough work only when it adds understanding; an arbitrary wall of thumbnails does not prove a process. If the first version contains client information that cannot be shown, create a clearly labelled reconstruction with invented details rather than publishing the confidential file.
Handle assets and permission carefully
Keep a record of photographs, illustrations, fonts and collaborators used in the display. Permission to use an asset in a client deliverable does not automatically describe every possible portfolio use, so review the actual arrangement. The Copyright Office explains that copyright can protect photographs and other original works. Credit contributors accurately, and ask for clarification when a licence or client approval is unclear. A screenshot taken from a public website is not automatically yours to reuse in promotional material merely because it is visible online.
Report outcomes at the level you can support
Separate what you delivered from what happened afterward. Delivered one approved handout and editable source file is a claim you can verify. Increased attendance by forty percent needs reliable measurements and a basis for connecting the change to your work. If you have no performance data, discuss practical completion, review feedback that you have permission to quote, or what you would test next. Never invent testimonials or turn a friendly private message into an endorsement without agreement. Honest limits strengthen the usefulness of the case study.
Make the case study easy to scan
Use a short overview, three decision sections, a compact final gallery and a closing note about deliverables. Write image descriptions that explain what matters in the screenshot. Check text readability on a phone; tiny mockup screens often hide the very work you want people to inspect. End with the relevant service and a straightforward enquiry route. Keep the page updated when permissions change or the example no longer reflects your current skill. A concise case study should feel like an explanation, not a fictional success story.
Your working checklist
Checkmarks stay in this browser when storage is available. They do not submit a form or complete a booking.
Put it into practice
- Choose one relevant project and identify three decisions that demonstrate your service. Confirm the display permissions before preparing a public page or social post.
- Write the context, constraints and your precise contribution. Label practice work or reconstructed examples clearly so the reader can interpret the evidence correctly.
- Pair selected images with explanations of the problem and the solution. Include readable details and remove private information from every file, screenshot and filename.
- Check all outcome claims, collaborator credits and image descriptions. Publish only what you can support, then retain a copy of the permission and evidence records.
Before you finish
- Practice projects are not presented as paid commissions.
- Team contributions and third-party assets are credited accurately.
- Confidential information is absent from images and file metadata.
- Outcome claims have evidence rather than attractive invented numbers.
- The actual work remains legible on a small screen.
Common questions
Can I show a project with no measured results?
Yes. Explain the brief, constraints and finished deliverables. Show the decisions you made and identify what you would evaluate later instead of manufacturing sales or audience figures.
Can I use a client's private feedback as a quote?
Ask for explicit permission and confirm the wording and attribution. A useful internal comment is not automatically an authorised public testimonial.
Should I include every project?
A few relevant, well-explained examples are easier to assess than a large unrelated gallery. Choose work that shows the service you offer and the decisions you can discuss honestly.