What Makes a UX Portfolio Get Replies
Beautiful portfolios get ignored every day. The ones that get replies answer a question the pretty ones never address: what did you decide, and why.
I have been on both sides of this. I have sent portfolios and heard nothing, and I have looked at portfolios while deciding who to work with. The gap between a portfolio that looks good and one that gets a reply is not visual quality. It is almost never visual quality.
What is missing is evidence of thinking. Anyone can produce a clean artboard now. Far fewer can explain why the interface is shaped that way.
Show the decision, not the artboard
A screenshot of a finished screen tells me you can use Figma. It tells me nothing about whether you can be trusted with a problem.
What I want to see is one hard decision, and the reasoning: two approaches you considered, why you picked one, what you gave up. A single paragraph of that is worth more than ten screens of polish, because it is the thing that cannot be copied from a template.
The case study structure that actually works
- The problem, stated as the business felt it, not as a design brief.
- The constraint. Budget, legacy system, a client who insisted on something. This is the most interesting part and it is almost always omitted.
- What you did, with one or two decisions explained properly rather than every screen shown.
- What happened. A number if you have one, an honest note if you do not.
- What you would do differently. This one sentence does more for credibility than everything above it.
That last point makes people uncomfortable and it is exactly why it works. Everyone knows no project goes perfectly. A portfolio where nothing went wrong reads as marketing.
Numbers, if you have them
Conversion moved, support tickets dropped, the form completion rate went up. If you have a number, use it. If you do not, say what changed qualitatively rather than inventing something. Anyone who has run a project can smell a made-up metric.
You can also count your own work honestly. "Designed 30+ pages for an enterprise compliance application" tells a hiring manager the scale you can operate at, which is a real signal even without a conversion number attached.
Cut the weak work
A portfolio is judged by its weakest piece more than its strongest. Three strong cases beat eight of mixed quality, every time. The student project from four years ago is costing you.
Make it survivable on a phone, in a hurry
Whoever opens your portfolio is doing it between two meetings, possibly on a phone. If the first screen is a full-viewport animation and the case studies are inside a PDF, you have lost before you started.
- The first screen should say who you are and what you do, in text.
- Case studies as web pages, not downloads.
- It should load in under three seconds on mobile.
- Contact details visible without hunting.
One thing that separates the top of the pile
Show that you know what happens after the design is handed over. Whether it got built as designed, what broke in development, what you changed because of a technical constraint.
Designers who understand the build are rare and everybody who has ever managed a project knows it. It is the fastest way to move from "nice work" to "let's talk".
Related
See how I document work in the portfolio. Interface shifts worth planning around: UX/UI design trends.
Другие записи
Most test suites are thorough about the wrong things. Fifteen variations of an empty field, nothing about what happens when the session expires halfway through checkout.
The tools moved from autocomplete to agents that plan and execute across files. That is a real shift. It also moves the bottleneck somewhere most teams have not staffed.
I pay for more than one of these, which tells you the comparison is not as simple as picking a winner. Where each model is genuinely better, from daily use rather than benchmarks.
Every model is best at something and mediocre at something else. This is which one I open for which task, based on using all of them inside real client work rather than on benchmarks.
AI can write a WordPress plugin in a minute. Whether you should put that plugin on a live site is the part nobody covers. From someone who reviews this code for a living.
Most slow WordPress sites are slow for two or three specific reasons. Here is how to find which ones, in the order that gives you the biggest drop in load time for the least work.
AI напишет тест-кейсы за секунды. Найдут ли эти кейсы хоть что-нибудь, вопрос отдельный. Что на самом деле изменил год работы с AI внутри реальной QA-задачи.
AI пишет код за секунды. Проверять, работает ли он, всё равно приходится человеку. Сколько на самом деле стоит vibe coding и как пользоваться AI, не выпуская его ошибки в прод.
Десять UX/UI трендов, отсортированных по другому принципу: меняют ли они то, что вы реально строите, или только то, как в этом году выглядят дизайн-блоги.
Рабочий чек-лист для защиты сайта на WordPress: вход, файлы, база, хостинг и мониторинг. Не теория, а то, что реально ломается на живых сайтах.
AI разложит экран, прочитает поведенческие данные и прогонит юзабилити-проверки. Решить, каким должен быть продукт, он не может. Практический взгляд на то, где проходит граница.