My strongest design project launched internally, but I cannot share adoption metrics or screenshots publicly.
2 Answers
-
Describe the problem, constraints, decisions, and internal outcome without claiming impact; the missing fact is whether your confidentiality agreement permits anonymized artifacts.
-
Your strongest project can still earn a portfolio spot, but it needs evidence of your design thinking, not just a claim that it launched.
- I’d disagree with treating anonymized artifacts as the main solution. If screenshots, flows, or even the domain are confidential, heavy anonymization can still expose internal information.
- Show work you are authorized to recreate: a simplified wireframe, a redrawn component, or a fictionalized version of one interaction. Label it clearly as a reconstruction.
- Example: instead of showing an internal operations dashboard, explain how you reduced a multi-step approval flow into two states, then use invented labels and sample data.
- Be precise about what you cannot verify publicly: say it launched internally, avoid adoption or performance claims, and focus on your role, tradeoffs, and review process.Ask your manager or legal contact what level of reconstruction and attribution is permitted before publishing anything.
Want to answer?
Log in or create an account to post answers, vote, and build your professional profile.
Log in or registerHow thoughtful discussions stay useful
How we moderate answers
We review contributions for clear, actionable, professionally relevant guidance. Duplicate, promotional, low-quality, or unsupported content may be removed.
What makes a high-quality answer
Strong answers directly address the question, explain the reasoning, and include specific steps, examples, tools, or frameworks when they add value.
Expert participation rules
Professional expertise should be grounded in real experience and presented objectively. Answers must stay career-focused and avoid undisclosed promotion.