Back to all ArticlesI noticed something frustrating.
Every time I talked about my work during interviews, people got it.
They understood the complexity. The decisions. The trade-offs.
But when they looked at my portfolio?
Silence.
No questions. No depth. Just polite acknowledgment.
At first, I thought maybe my work wasn’t strong enough.
It wasn’t that.
The real problem wasn’t my work
It was how I was showing it.
Like many designers working on complex systems, I had one big project.
A full application. Multiple modules. Dozens of screens.
So I did what seemed logical:
I shared Figma.
A full file. Structured. Clean. Thought through.
Everything was there.
And that was exactly the problem.
Nobody clicks your Figma
Let’s be honest.
Recruiters don’t explore your files.
They don’t click through flows.
They don’t try to “understand the system”.
They scan.
They look for signals:
- Do you understand problems?
- Do you make decisions?
- Can you simplify complexity?
A Figma file answers none of those questions.
It shows output — not thinking.
Big systems break portfolios
The bigger your project, the worse it performs in a traditional portfolio.
Because:
- It requires context
- It requires time
- It requires effort
And no one gives you that upfront.
So instead of showing depth, you show overwhelm.
Instead of clarity, you show volume.
I was showing everything — and explaining nothing
My mistake was simple:
I treated my portfolio like documentation.
I showed:
- navigation
- dashboards
- settings
- notifications
- flows
Everything existed.
But nothing was explained.
There was no entry point.
No hierarchy.
No story.
What I changed
I stopped thinking in terms of “project”.
And started thinking in terms of problems.
Instead of:
“This is my application”
I shifted to:
“These are the problems I solved inside this system”
From one big case to focused decisions
I broke the system into smaller, meaningful parts:
- Dashboard builder → how users start using the product
- Notification system → how the system communicates state
- Navigation → how users stay oriented in complexity
Each of them became a clear, self-contained story.
Not a screen.
Not a feature.
A decision.
I stopped relying on Figma
Figma didn’t disappear.
It just changed role.
Before:
- main way to show my work
Now:
- backup
- deep dive
- something I show only when someone asks
The portfolio itself became:
- curated
- structured
- intentional
The shift that made the difference
The biggest change wasn’t visual.
It was conceptual.
I stopped trying to show everything.
And started making my thinking visible.
What I learned
Your portfolio is not a product demo.
It’s not a playground.
It’s not a place to prove how much you’ve done.
It’s a place to show:
- how you see problems
- how you make decisions
- how you handle complexity
Final thought
If your work only makes sense when you explain it —
your portfolio is hiding your value.
And that’s the real problem.
