Portfolio Advice That Actually Reflects How They Are Reviewed
Portfolios are assembled as comprehensive records and reviewed as rapid filters. Understanding the gap between those two things explains most of what is wrong with the average portfolio.
The first pass is under two minutes
A reviewer with forty applications gives each one a brief scan before deciding whether to look properly. During that scan they are answering one question: is this person’s work good enough to spend more time on? Everything that does not contribute to answering it is dead weight.
Lead with the strongest piece, without exception
Chronological ordering, category grouping and building toward a climax all fail against a two-minute scan. The best work goes first. If the reviewer stops after one project, that project should be the one you would have chosen.
Fewer projects, shown properly
Four strong projects outperform eleven mixed ones, because a portfolio is judged substantially by its weakest inclusion. Every mediocre piece invites the question of why it was included, and the honest answer — that there was not enough strong work — is exactly the impression to avoid.
Show the reasoning, briefly
Reviewers want to know what the problem was, what you decided and why. Three sentences of context transform an attractive image into evidence of thinking. Six paragraphs of process documentation will not be read. The common failure is either no context at all or an enormous case study nobody finishes.
Be explicit about your contribution
Team projects are fine and expected. Ambiguity about what you personally did is not — reviewers assume the least flattering interpretation. One line stating your role resolves it.
The presentation is itself a work sample
A slow site, broken images, inconsistent typography or a confusing navigation is being evaluated as design work, whether or not it was intended as such. This is the most common self-inflicted failure in the entire category.
Assume ninety seconds, one project, and a reviewer looking for a reason to continue. Build for that and the longer read takes care of itself.
