Many UX designers already have real project experience — but hesitate to use it in their portfolio.
The reasons are familiar:
- NDA restrictions,
- internal tools,
- confidential data,
- enterprise clients,
- unfinished or sensitive projects.
As a result, designers often hide their strongest work and replace it with weaker, fictional case studies.
This article shows how to anonymize real UX projects ethically and professionally, so you can showcase your experience without breaking trust, contracts, or credibility.
Why Anonymization Is a Professional Skill (Not a Hack)
Anonymization is often misunderstood as “hiding logos.”
In reality, it is about:
- protecting confidentiality,
- abstracting sensitive context,
- preserving decision-making,
- demonstrating judgment.
Senior designers anonymize work all the time — not to deceive, but to focus on transferable skills.
This approach builds directly on
Enterprise UX Portfolio: Designing Complex Systems
👉 https://zofiaszuca.com/articles/enterprise-ux-portfolio
Enterprise experience often requires discretion.
What You Can Safely Show in an Anonymized Case Study
Even under strict NDA, you can usually show:
- problem framing,
- user roles (abstracted),
- constraints,
- flows and logic,
- trade-offs,
- lessons learned.
What you must protect:
- company names,
- internal metrics,
- proprietary terminology,
- screenshots with real data,
- identifiable architecture.
Anonymization is about removing identity, not removing substance.
Step 1: Abstract the Domain Without Losing Realism
Start by replacing the specific company with a domain description.
Examples:
- “A global financial institution”
- “An enterprise SaaS platform for internal operations”
- “A regulated data-heavy system with role-based access”
This keeps the context realistic while protecting identity.
This technique is especially effective when combined with the portfolio structure from
UX Portfolio Without Clients: Real Case Studies with AI
👉 https://zofiaszuca.com/articles/ux-portfolio-without-clients
Step 2: Rename Roles, Not Responsibilities
Job titles and role names can often identify an organization.
Instead:
- rename roles generically,
- keep responsibilities intact.
For example:
- “Compliance Officer” → “Risk Reviewer”
- “Internal Admin Tool” → “System Management Interface”
Hiring managers care about what the role does, not what it’s called.
Step 3: Rebuild Screens as Diagrams or Neutral Wireframes
Never upload real screenshots from internal tools.
Instead:
- recreate flows as diagrams,
- redraw screens as low-fidelity wireframes,
- remove branding and proprietary UI elements.
This aligns with enterprise portfolio best practices discussed in
Enterprise UX Portfolio: Designing Complex Systems
👉 https://zofiaszuca.com/articles/enterprise-ux-portfolio
Recruiters value clarity of logic more than visual fidelity.
Step 4: Use AI to Help Abstract Without Inventing
AI is useful in anonymization — if used carefully.
Good uses include:
- rewriting descriptions to remove identifiers,
- generalizing domain language,
- checking for accidental disclosures,
- improving clarity after abstraction.
Bad uses include:
- inventing new problems,
- changing decisions,
- adding features you didn’t design.
This follows the system mindset from
Prompt Generator vs Prompt System: What UX Designers Need
👉 https://zofiaszuca.com/articles/prompt-generator-vs-prompt-system
AI assists editing — not rewriting history.
Step 5: Clearly State That the Project Is Anonymized
Transparency builds trust.
Include a short note such as:
“This project is anonymized to respect confidentiality. Details have been abstracted while preserving the design process and decisions.”
Hiring managers appreciate honesty far more than false realism.
Step 6: Focus the Narrative on Decisions and Trade-Offs
Anonymized projects work best when the narrative emphasizes:
- constraints,
- risks,
- rejected options,
- compromises.
This mirrors the thinking-focused approach explained in
UX Portfolio Prompts: How to Design Case Studies Step by Step
👉 https://zofiaszuca.com/articles/ux-portfolio-prompts-case-studies
The less you rely on visuals, the stronger anonymization becomes.
Step 7: Ethically “Upgrade” the Project (Optional)
In some cases, you may want to show growth.
This can be done ethically by:
- adding a clearly marked “What I would improve today” section,
- exploring alternative solutions,
- reflecting on limitations at the time.
AI can help structure this reflection — but the insight must be yours.
This avoids the pitfalls described in
Why Most UX Prompts Fail (And How Designers Can Fix Them)
👉 https://zofiaszuca.com/articles/why-most-ux-prompts-fail
Reflection signals maturity.
Common Anonymization Mistakes to Avoid
Avoid:
- keeping real data with blurred text,
- leaving recognizable layouts intact,
- copying internal terminology,
- inventing outcomes to “improve” the story,
- pretending the project is fictional when it’s not.
These mistakes hurt credibility more than not showing the project at all.
Why Recruiters Respect Anonymized Work
Experienced recruiters know:
- real UX work is often confidential,
- strong designers protect trust,
- NDAs are common in enterprise roles.
An anonymized, well-explained case study signals:
- professionalism,
- ethical awareness,
- real-world experience.
It is often seen as more credible than polished fake projects.
Where This Fits in the Larger UX AI System
Anonymization is part of a mature UX AI workflow where:
- AI supports abstraction,
- designers own decisions,
- portfolios stay ethical,
- credibility is preserved.
This system is explained in full in
The Designer’s AI Playbook.
👉 https://zofiaszuca.com/designers-ai-playbook
The book shows how to:
- work with real constraints,
- use AI responsibly,
- build senior-level portfolios,
- and grow without burning bridges.
Final Thought
You don’t need to choose between honesty and opportunity.
You can:
- protect confidentiality,
- show real thinking,
- respect past employers,
- and still build a strong portfolio.
Anonymization done well is not hiding.
It is professional storytelling with integrity.
AI can help — but only if the designer leads.

