Start with what you are allowed to share
A strong portfolio makes your work understandable, but it should not come at a client’s expense. Before preparing a case study, review the agreements and project communications that govern what you can disclose. Check for restrictions on the client’s name, unreleased designs, internal processes, data, screenshots, and results. Work that appears publicly may still include details you were not given permission to publish.
If the boundaries are unclear, ask the client for written permission to show specific materials in a specific way. A short request is easier to assess than a broad request to “feature the project.” You might describe the proposed images, text, attribution, and where the case study will appear. Keep a record of the response, and be prepared to revise or omit the work if permission is not granted. When an agreement is difficult to interpret, seek appropriate professional guidance rather than relying on a guess.
Choose a format that fits the restriction
Confidentiality does not always mean you must leave the project out. Sometimes you can discuss the type of challenge and your approach without naming the client or displaying the deliverable. For example, you might explain how you organized a complex set of requirements, tested a navigation structure, or prepared a handoff for a development team. The description should be general enough that someone cannot easily identify the client or recover private information from context.
Other options include showing a public portion of the work, creating a simplified diagram of your process, or making a new illustrative example based on the skill involved. Label any reconstruction clearly as an illustration, not a client-approved screen or an actual project artifact. Removing a logo alone is rarely sufficient: interface text, unusual workflows, file names, background details, and even the combination of industry and project scope can reveal more than intended.
Make your contribution clear without revealing the brief
A useful case study answers three questions: what problem were you trying to solve, what did you personally do, and how did you decide what to do next? You can answer those questions at an appropriate level of abstraction. Instead of reproducing a private brief, describe the broad design challenge. Instead of showing internal research notes, explain the method you used to turn feedback into decisions.
Be precise about your role, especially on a team project. Identify whether you led the design, contributed a particular component, facilitated a workshop, or prepared production files. Explain one or two meaningful decisions and the tradeoffs behind them. This gives a prospective client evidence of how you think, even when the finished work cannot be shown. Avoid implying that you created work done by teammates or that an illustrative example was delivered to the client.
Handle outcomes and access with care
Results can make a case study persuasive, but private figures should not be included simply because they make the story stronger. Use approved outcomes when available. Otherwise, describe what the team completed or learned without inventing numbers or implying a business impact you cannot substantiate. Phrases such as “prepared a reusable component library for handoff” are often more informative than a vague claim that the project was a success.
Some makers offer a private case study to prospective clients. Limited access can help with presentation, but a password or unlisted link does not replace permission to share. Confirm that the intended audience and materials are allowed, then share only what that audience needs to evaluate your work. If a client prefers that the project remain entirely private, respect that decision and choose a different example.
Build a portfolio that does not depend on one secret project
Confidential projects are easier to manage when your portfolio includes other ways to demonstrate your abilities. A personal project can show your design process from start to finish. A clearly labeled concept exercise can demonstrate a particular skill. Public or permissioned client work can provide evidence of collaboration and delivery. Together, these examples can give visitors a fuller picture without putting pressure on a restricted project to reveal more than it should.
For each confidential project you do include, perform a final review from an outsider’s perspective. Could a reader identify the client from scattered clues? Does any image contain private data? Is every claim about your role and the outcome accurate? Can you explain exactly what was approved for publication? A portfolio earns trust not only by showing capable work, but by showing that you know how to handle someone else’s work responsibly.
