Start with the question a reader needs answered
A portfolio case study should help a potential client or collaborator understand what you can do. When a project involved several people, a polished final image rarely answers that question on its own. Readers need to know which decisions you made, what you produced, and how your work fit into the wider effort. Clear attribution makes your contribution easier to assess; it does not make it smaller.
Near the beginning of each case study, add a compact project summary. Include the project type, your role, the team or collaborators involved, and the scope of your work. For example: “Role: visual designer. I developed the page layouts and component styles using a content structure supplied by the client. A developer built the site.” This gives readers a reliable frame before they see the finished work.
Describe actions, not just job titles
Titles such as “designer” or “creative lead” can mean different things on different projects. Follow a title with specific actions: “I explored three layout directions, refined the chosen direction, and prepared responsive screens for handoff.” If you joined after the concept was approved, say so. If you guided the whole project but another person made the illustrations, distinguish your direction from their execution.
Use “I” for decisions and deliverables you owned, and “we” for shared work. This small choice can prevent a case study from quietly claiming a group achievement as an individual one. Where responsibilities overlapped, describe the process rather than forcing a sharp boundary: “The writer and I shaped the page hierarchy together; I handled the visual layout, while they drafted and revised the copy.”
Make collaborator credits visible and specific
Place credits where a reader can find them without searching. A short list beside the project summary or at the end of the case study often works well. Identify people by name and contribution when they are comfortable being named: photography, research, copy, development, illustration, motion, or creative direction. If naming someone is not appropriate, a role-based credit such as “Photography: client team” still helps explain the work.
Credit should match the material you show. If a striking illustration is central to the page, identify its creator near the image or in a clearly connected credit list. The same applies to photographs, writing, and other contributions that might otherwise be mistaken for yours. Keep the wording straightforward rather than treating credits as fine print. If someone’s preferred name or credit wording is uncertain, ask before publishing.
Handle sensitive or mixed-ownership projects carefully
Before publishing a client or team project, check what you are permitted to show. A project may include unpublished concepts, private information, licensed assets, or work created under an agreement that limits public use. If you are unsure, seek permission or show a narrower selection. You can still explain your process without exposing private details: describe the design problem in general terms, show material cleared for display, and state what you contributed.
Be equally careful with explorations that did not become the final product. Label an unused concept as a concept, not as the launched design. If a case study combines your independent sketches with a team-produced result, separate those stages in the narrative. Honest labels let readers appreciate your thinking without confusing it with the final team decision.
Give your contribution evidence and keep credits current
Once roles are clear, use the case study to demonstrate your work. Show a relevant sketch, layout iteration, component, or handoff example where you can, and explain the decision behind it. A brief account of a constraint and your response is often more useful than a long list of tasks. Be measured when discussing outcomes: describe what changed or what the team delivered without implying that your work alone caused an outcome you cannot verify.
Before a case study goes live, read it as someone unfamiliar with the project. Could they identify what you made, what others made, and which images represent final work? Then invite collaborators to flag inaccurate credits when practical. Revisit older entries after a redesign or team change so that captions, names, and links remain consistent. A portfolio is both a showcase and a record of working relationships; maintaining that record well is part of presenting your work professionally.
