Product Manager Portfolio Under NDA: How to Show Work You Can't Name

Almost every PM hits this wall: the strongest project of your career is also the one you signed the most paperwork about. The instinct is to either skip it entirely or write around it so vaguely the case study says nothing. Neither is necessary. An NDA restricts what you disclose, not whether you can describe the problem, the process, and the result — and a well-anonymized case study often reads as more credible than one with the company name attached, because it forces you to lead with substance instead of the logo.

1. Know what your NDA actually restricts

Most standard NDAs protect three things: confidential business information (roadmaps, unreleased features, internal metrics), trade secrets, and sometimes the fact of the engagement itself. They almost never prohibit you from describing your own role, the type of problem you solved, or the shape of the outcome in relative terms. Re-read the actual agreement — or the standard confidentiality clause in your offer letter — before you assume the whole project is off-limits. Most of the time, 80% of what makes a case study compelling was never covered.

2. Anonymize the company, not the substance

Replace the company name with a category descriptor: "a Series C fintech lending platform" or "a 200-person B2B logistics SaaS company" gives a reviewer everything they need to judge scale and context without naming names. Do the same for product names and internal codenames. What you keep specific is the work: the hypothesis, the constraint, the decision you made, and the measurable result. A reviewer evaluating you for a PM role is judging your thinking, not fact-checking your employer history — LinkedIn already tells them where you worked.

3. Convert absolute numbers to relative ones

"Grew signups from 40,000 to 58,000/month" might be the exact figure an NDA prohibits, but "grew monthly signups 45% over two quarters" usually is not — it's a rate, not a disclosed business metric. When in doubt, convert every hard number in a case study to a percentage, a ratio, or a range ("high six figures in ARR impact"). This is standard practice at companies with strict confidentiality cultures, and hiring panels are used to reading numbers this way.

4. Get explicit sign-off for anything borderline

If a project genuinely mattered and you're unsure whether a detail crosses the line, ask. A two-line email to a former manager — "I'd like to reference this project in my portfolio, described at a high level with no company name or specific metrics, is that okay?" — takes five minutes and removes the risk entirely. Most managers say yes immediately, because a former report describing work at a peer-review level of detail with no proprietary specifics is not the kind of disclosure NDAs exist to prevent.

5. Lead the case study with the problem, not the credential

An anonymized case study actually reads better when you stop trying to compensate for the missing company name. Open with the problem and constraint — "A subscription product was losing 30% of new users in the first session, with a hard technical constraint that ruled out the obvious fix" — and let the thinking carry the case study. Reviewers who scan portfolios all day are pattern-matching for judgment and rigor, not brand names; a sharp anonymized case study often outperforms a name-dropped one that's thin on reasoning.

6. Say it's anonymized, once, briefly

Add a single line at the top or bottom of the case study — "Company and product names withheld per NDA; all metrics are directional" — and move on. Don't apologize for it repeatedly or explain the NDA in detail; one clear line signals professionalism and closes the question so the reviewer can focus on the work itself.

Bottom line

An NDA is a reason to anonymize a case study, not a reason to cut it. Strip the company name, convert hard numbers to rates and ranges, get quick sign-off on anything borderline, and lead with the problem and your reasoning instead of the logo. For the structure every case study — anonymized or not — should follow, see how to write a PM case study, and for how to decide which metrics belong in the story at all, see what metrics to put in a PM portfolio.

Product Leader builds this structure — case studies, metrics, and a video intro — from your CV or LinkedIn in under a minute. Start your portfolio here, free, no credit card.