Building a Portfolio That Actually Works
Tips for designers who want to stand out đž

This article pairs nicely with my previous post, âA Comprehensive Guide to Game UXâ. If you havenât read that one, I suggest checking it out.
Every now and then I get messages from designers asking me to review their portfolio or share tips for building one. My first reaction isnât great, since it reminds me how neglected my own portfolio is, but after that moment of guilt I usually share the same advice. So letâs make it easier for both sides and put everything into this article.
Why is it so difficult? đŤ
If youâve ever built a portfolio, you know itâs harder than it looks.
Designing for others is easy, designing yourself is chaos.
Your portfolio can summarize your journey even if youâre not looking for a new job. But for this post, letâs assume your portfolio is the interface between you and your next opportunity.
My advice boils down to two principles:
Use a what / why / how structure to explain your thinking.
Quality beats quantity. Three great projects are better than ten âokayâ ones.
Letâs unpack these and a few more tips so you can take action right now.
1. Treat it like a product đŽ
Your portfolio solves a user problem.
User: recruiter or hiring manager
Goal: understand who you are, what you do, and how you think
Success metric: getting the next conversation
Approach it like any design challenge. Keep it clear, focused, and easy to explore.
2. Tell a story, not just show screens âď¸
People donât hire pixels, they hire thinkers. Each project should explain:
The problem
Your role
The process
The impact
Whenever possible, back up your work with numbers (e.g. âreduced drop-off by 15%â), but even qualitative outcomes count. What matters most is showing how you think and the impact of your actions, not just what you built.
3. Make it a workshop, not a museum đ ď¸
Skip static galleries. Show thinking in motion with sketches, wireframes or prototypes.
For UX/UI designers, balance visuals with reasoning. Explain why something looks the way it does, thatâs what turns âprettyâ into âpurposeful.â
And please, keep it curated. Nobody needs to see every project youâve ever done.
4. Write like a human đŹ
Avoid things like âleveraged insights to enhance experiences.â Say what really happened: âPlayers were confused by X, so I simplified Y.â
Your writing reflects your design maturity. In a sea of AI-generated text, your own tone and honesty make a difference. Donât forget that this is where people check for fit, your words give a sense of who you are. The idea is simple: good writing = good UX.
5. Keep it short, not shallow âąď¸
Focus on quality, not a minimum number of projects. Make sure each one follows a clear what / how / why structure so readers instantly understand your reasoning.
If youâre new to the industry, itâs fine to make your own briefs or redesign an existing game as a case study. Personal projects are also fine, as long as you know what theyâre meant to communicate, whether itâs UI creation, prototyping, or implementation skills.
If youâre more focused on UX than UI, include visuals from the team when needed, just credit your collaborators and clarify your role. That transparency shows collaboration skills, something that adds a lot of value.
6. Choose the right format đ
Early career? Notion, Medium, ArtStation, or Behance will work well.
More senior? A simple website feels more professional.
Whatever you use:
Keep navigation simple
Make it mobile-friendly
Add contact info
Tailor your top projects to each role. Match your platform to your craft. ArtStation suits visual-heavy work, while Notion or personal sites fit UX or research cases better.
đ Final Notes
A strong portfolio isnât about showing everything, itâs about showing how you think.
If someone closes your page and says, âI get how this person solves problems,â youâve done your job. For my part, I hope this gives me the push to finally update my own portfolio so I can stop feeling like an impostor when I talk about this topic đ
Got a great portfolio or an extra tip to share? Drop it in the comments.

