Designer portfolio review: what to look for
The first three minutes decide everything
According to statistics, a recruiter or client spends no more than three minutes reviewing a portfolio. The first project in the list actually determines whether the others will be opened. If it is weak, unstructured, or lacks an explanation of the task — the person closes the tab, even before getting to truly strong works. Hence a simple practical conclusion: put not the most recent project at the beginning, but the most convincing one.
How many projects there should be — and why quantity harms
The average designer level is usually confirmed by at least six projects, but this does not mean one should strive for the maximum. A portfolio with fifty weak cases makes a worse impression than a selection of five to seven strong ones. Each extra weak project lowers the overall rating — the client subconsciously averages the level across the entire sample, not choosing the best from what is shown.
- 3-7 projects — a comfortable volume for quick review without losing the quality of perception
- each case should cover a separate competence, not repeat the previous one
- if you are in doubt whether to include a project or not — do not include it
Why beautiful visuals are not the main argument
In 2025 year 82% of customers choose a performer based on their ability to explain the solution, not on the aesthetics of the layouts. This breaks the stereotype that a portfolio is a competition for the most stylish design. Beauty is needed, but it is secondary: it confirms taste, not competence in solving business tasks. It is important for the customer to understand why a particular layout was chosen, not just to see that it is neat. A designer who can explain the logic through the task and result looks like a more reliable performer — even if their visual style is more modest than the competitor's.
How to correctly analyze one case
The optimal length of a quality case is 7-9 screens. This is not a random number: such volume creates a feeling of careful elaboration without overload with details. The structure should lead the reader through a clear logic, rather than be a set of images with captions.
- Context and task — what the client requested, what the limitations were
- The role of a designer in a team — a solo project or a team member, for what the author was specifically responsible
- The process is research, drafts, variants, hypotheses
- The final decision — with an explanation of why this particular option was chosen
- The result is specific figures: conversion, traffic, reach, and load time
- Retrospective — what worked, what did not work, and what would be different now
A case without numbers in the results section is usually ignored — the client needs specific metrics such as 'conversion increased by 34%' or 'traffic +250%', not abstract 'the project was successful'.
Why the process is more important than the outcome
The final mockup shows the result, but not the thinking behind it. Drafts, rejected variants, research notes — these are what prove the point: the solution was not pulled out of thin air randomly, but derived from an analysis of the task. A designer who shows only a glossy final result leaves the question open — whether there was actually a choice at all, or whether it's simply the only variant he knows how to make. Live mockups in context — product photos in hand, interfaces in real use — work stronger than dry mockups, because they confirm that the solution has been tested by reality, not just stayed on the screen.
Red flags and green flags: what an experienced eye looks at
| Green flags | Red flags |
|---|---|
| Clear structure task → solution → result | Only final screenshots without task context |
| Author's role in the team is explicitly indicated | It's unclear what exactly the designer did by themselves |
| There is a retrospective and error analysis | The result is presented as an unconditional success without nuances |
| Live prototypes in real usage context | Only ideal mockups without signs of real usage |
| Specific metrics and numbers of the result | Abstract formulations like 'the project was liked by the client' |
Portfolio for hiring, clients and contests — these are different documents
Error of many designers — keeping one universal portfolio for all cases. But the evaluation criteria differ fundamentally.
- Job search: A recruiter is interested in your role in the team, your ability to work according to the brief and on time, and your capacity to explain your solution to colleagues with different expertise
- Attracting clients: The client values business results and metrics — it is precisely cases with proven effectiveness that allow raising the cost of services by 30-40%
- Participation in competitions: The jury evaluates the originality and visual boldness of the solution even without commercial confirmation — conceptual, experimental works are acceptable here
A portfolio assembled under one goal often fails in another context — a strong competitive case without metrics may leave the client indifferent, while a pragmatic business case without visual elegance will not impress the jury. It is worth keeping 2-3 versions of the selection, changing the emphasis to suit the audience rather than relying on one universal set of projects
The first three minutes decide everything
According to statistics, a recruiter or client spends no more than three minutes reviewing a portfolio. The first project in the list actually determines whether the others will be opened. If it is weak, unstructured, or lacks an explanation of the task — the person closes the tab, even before getting to truly strong works. Hence a simple practical conclusion: put not the most recent project at the beginning, but the most convincing one.
How many projects there should be — and why quantity harms
The average designer level is usually confirmed by at least six projects, but this does not mean one should strive for the maximum. A portfolio with fifty weak cases makes a worse impression than a selection of five to seven strong ones. Each extra weak project lowers the overall rating — the client subconsciously averages the level across the entire sample, not choosing the best from what is shown.
- 3-7 projects — a comfortable volume for quick review without losing the quality of perception
- each case should cover a separate competence, not repeat the previous one
- if you are in doubt whether to include a project or not — do not include it
Why beautiful visuals are not the main argument
In 2025 year 82% of customers choose a performer based on their ability to explain the solution, not on the aesthetics of the layouts. This breaks the stereotype that a portfolio is a competition for the most stylish design. Beauty is needed, but it is secondary: it confirms taste, not competence in solving business tasks. It is important for the customer to understand why a particular layout was chosen, not just to see that it is neat. A designer who can explain the logic through the task and result looks like a more reliable performer — even if their visual style is more modest than the competitor's.
How to correctly analyze one case
The optimal length of a quality case is 7-9 screens. This is not a random number: such volume creates a feeling of careful elaboration without overload with details. The structure should lead the reader through a clear logic, rather than be a set of images with captions.
- Context and task — what the client requested, what the limitations were
- The role of a designer in a team — a solo project or a team member, for what the author was specifically responsible
- The process is research, drafts, variants, hypotheses
- The final decision — with an explanation of why this particular option was chosen
- The result is specific figures: conversion, traffic, reach, and load time
- Retrospective — what worked, what did not work, and what would be different now
A case without numbers in the results section is usually ignored — the client needs specific metrics such as 'conversion increased by 34%' or 'traffic +250%', not abstract 'the project was successful'.
Why the process is more important than the outcome
The final mockup shows the result, but not the thinking behind it. Drafts, rejected variants, research notes — these are what prove the point: the solution was not pulled out of thin air randomly, but derived from an analysis of the task. A designer who shows only a glossy final result leaves the question open — whether there was actually a choice at all, or whether it's simply the only variant he knows how to make. Live mockups in context — product photos in hand, interfaces in real use — work stronger than dry mockups, because they confirm that the solution has been tested by reality, not just stayed on the screen.
Red flags and green flags: what an experienced eye looks at
| Green flags | Red flags |
|---|---|
| Clear structure task → solution → result | Only final screenshots without task context |
| Author's role in the team is explicitly indicated | It's unclear what exactly the designer did by themselves |
| There is a retrospective and error analysis | The result is presented as an unconditional success without nuances |
| Live prototypes in real usage context | Only ideal mockups without signs of real usage |
| Specific metrics and numbers of the result | Abstract formulations like 'the project was liked by the client' |
Portfolio for hiring, clients and contests — these are different documents
Error of many designers — keeping one universal portfolio for all cases. But the evaluation criteria differ fundamentally.
- Job search: A recruiter is interested in your role in the team, your ability to work according to the brief and on time, and your capacity to explain your solution to colleagues with different expertise
- Attracting clients: The client values business results and metrics — it is precisely cases with proven effectiveness that allow raising the cost of services by 30-40%
- Participation in competitions: The jury evaluates the originality and visual boldness of the solution even without commercial confirmation — conceptual, experimental works are acceptable here
A portfolio assembled under one goal often fails in another context — a strong competitive case without metrics may leave the client indifferent, while a pragmatic business case without visual elegance will not impress the jury. It is worth keeping 2-3 versions of the selection, changing the emphasis to suit the audience rather than relying on one universal set of projects
Recent articles
MegaFon, BMW, VTB and more 240+ companies. See how it looks in the showcase reel:
Our branding agency is approached to order:
Branding agency services
