Handling NDAs in Design Case Studies: How to Show Secret Work Without Legal Panic

We've all been there: you spent over a year spearheading a mission-critical fraud engine, a stealth crypto trading desk, or a confidential zero-to-one health app. The work is easily your best craft yet — but you legally cannot publish a single production screenshot.

Most designers panic and do one of two bad things: they either hide their best work and put an old junior project on their portfolio, or they put the entire site behind a clunky password that recruiters immediately skip.

Good news: hiring leaders don't care about your company's confidential customer database. They care about your product judgment, your systems thinking, and how you untangle chaos. By decoupling your design rationale from proprietary IP, you can show off your best work in 100% compliance.

1. Convert raw numbers into relative multipliers. If your checkout overhaul grew quarterly revenue from $12M to $16.5M, don't post the balance sheet. Write "+37.5% checkout completion lift" or "1.38x checkout velocity". It's more impressive and 100% legal.

2. Swap real client logos for clear archetypes. Replace "Citigroup Trading Portal" with "Global Tier-1 Investment Bank", or "Figma Enterprise" with "Leading Design Systems SaaS". Recruiters instantly understand the scale.

3. Generalize internal code names. If your machine learning team called their secret tool "Project Cerberus", just call it "the automated risk triage queue". You explain the mechanics without leaking trademarks.

When screenshots contain confidential data, please don't slap a messy Photoshop blur over the screen. Blurs look lazy, unreadable, and frustrate reviewers who want to inspect typography and layout hierarchy.

Instead, reconstruct the key screen states as high-fidelity abstracted wireframes. Use crisp neutral cards, structural typographic bars, and clearly labeled navigational nodes. This forces the reviewer to focus on what actually matters: your information architecture, state machines, and task efficiency.

In a 45-minute portfolio walkthrough, a design director will ask: "What was your core hypothesis?", "How did engineering constraints change your initial prototype?", and "How did you validate the interaction model with real operators?".

Notice how none of those questions require leaking trade secrets. By structuring your case study around the 7 core sections — Context, Problem, Role, Process, Solution, Impact, and Reflection — you stand out as an executive product thinker.