The problem with showing your best work
The projects you are proudest of are sometimes the ones you are least free to show. Internal tools, unreleased products, client strategy documents and anything involving customer data usually belong to someone else, and the people involved may have expected it to stay private.
Portfolio confidentiality is the practice of showing enough to demonstrate your skill without breaking those expectations. Getting it wrong can damage client trust, may breach a contract, and could create legal or employment problems. This article gives general guidance, not legal advice, and the rules vary by agreement, employer and country.
Start by finding out what you agreed to
Before deciding what to show, look at the paperwork you already have.
- Contracts and written agreements. Freelance and employment agreements often include confidentiality clauses, ownership terms and sometimes a section on whether you can display the work. Written agreements are most useful here because they replace guesswork.
- Employer policies. Many workplaces have rules about sharing work, even work you created. Policies may also cover mentioning the employer’s name.
- Non-disclosure agreements. An NDA may cover more than you assume, including the existence of the project or the client.
- Informal understandings. Even without a signed document, a client may reasonably expect discretion.
If the terms are unclear, ask. A short, polite email can resolve a question that would otherwise hang over your portfolio for years. For anything complicated, a qualified professional can read the agreement and explain it.
Ask permission the right way
When you request approval, make it easy to say yes. Describe exactly what you want to show: which pages, screenshots, text or numbers, and where it will appear. Offer to remove names, blur details or share a draft for review. Ask for approval in writing and keep a copy.
Timing helps too. Raising portfolio rights while a project is underway, or when you negotiate scope, is easier than asking years later when contacts have moved on. Keep client expectations in mind: some will happily agree, others will not, and either answer should be respected.
What counts as confidential
Confidential information is not limited to obvious secrets. Think about:
- Names of clients, partners and unannounced products.
- Revenue, pricing, margins, traffic and other internal numbers.
- Customer or user data, including names, emails, photos and messages.
- Internal documents, source code, process diagrams and strategy.
- Screenshots that accidentally show browser tabs, account names, folders or notes.
- Metadata in files, such as author names, comments, tracked changes or hidden layers.
It is worth checking each sample line by line before it goes live, including images and PDFs, since small background details are easy to miss.
Options when you cannot show the real thing
You often have alternatives that still demonstrate what you can do.
Anonymize. Replace the client name with a general description such as “a regional retailer,” remove identifying logos and change or round sensitive figures. Make sure the remaining details do not make the client easy to identify, because a few specifics can be enough.
Recreate. Build a similar sample from scratch using made-up content. Label it plainly as a mock-up or example so nobody mistakes it for client work. Do not copy proprietary text, layouts or code.
Describe in general terms. A short case summary can cover the problem, your approach and the type of result without revealing sensitive information. Keep your claims accurate, since vague wording is not a reason to inflate your role.
Use a private portfolio. Some people keep a public selection and share a more detailed version only with a specific interviewer or prospective client, with the owner’s permission. Password protection is not a guarantee of confidentiality, so it does not replace permission.
Show process, not product. Sketches, wireframes you created yourself or an explanation of your method can show your thinking without exposing the final deliverable.
Offer references instead. When you cannot show the work, a former client who agrees to speak about it may help. Get their consent first.
Personal data deserves extra care
Projects involving customers, patients, students or members may include information about real people. Even if the client says you can show the project, consider whether those individuals would expect their details to appear in your portfolio. Removing or replacing personal data is generally a safer practice, and in some regions, privacy laws apply. If you are uncertain, treat the data as off limits.
Be honest about what you leave out
Hiding details is acceptable. Misleading people is not. If a case study is anonymized, say so, so that no one assumes the client is fictional or the results invented. A short note such as “Client details have been changed at their request” is straightforward.
The same honesty applies to credit, because collaborators may also have an opinion about being named. These are the same concerns that run through branding ethics generally.
If you already published something you should not have
Act quickly. Take the item down, check whether search results or caches still show it, and contact the affected party to explain what happened and what you removed. Cleaning up old posts is a normal part of managing your reputation, and a prompt, honest response is usually received better than silence. If a formal complaint or legal threat follows, seek professional advice rather than improvising.
No approach eliminates every risk, and it is better to show slightly less than to expose something that is not yours. A smaller portfolio that you are free to share will serve you better than a polished one that causes a problem.