Common Portfolio Mistakes

Most portfolios fail in the same handful of ways. That is oddly reassuring: a mistake that is common is a mistake with a known fix, and simply knowing the list puts you ahead of most applicants. The failures fall into three families - curation, craft, and honesty - and we will take them in turn, with the fix for each, before assembling a checklist you can run before you ever hit send.

The first and most damaging family is curation - and its headline error is too much. The instinct to include everything, to show range, to not waste work you slaved over, produces bloated portfolios of fifteen or twenty projects where six would have been stronger. The problem is not just that a busy reader will not look at all of it; it is that a portfolio is judged by its weakest included piece. One flat, half-finished, badly-shot project sitting among strong ones does not read as 'and also this' - it reads as evidence that you cannot tell your good work from your bad. It plants a doubt that colours everything around it.

The fix: cut hard. For most people a main portfolio is four to eight genuinely strong, well-presented projects, and a job application often fewer. Rank everything honestly, draw a cut line, and remove anything below it - including good work that does not serve the argument to this particular reader. If it took you ages but it is not strong, it still goes; effort is not a reason to include something.

The close cousin of too-much is no clear opener. Readers scan in seconds and form a first impression they rarely revise, so burying your best project on page nine is a self-inflicted wound. Lead with your strongest, most relevant work. The weak-piece rule cuts both ways: as your first piece makes your best impression, your worst piece caps your ceiling. Fix both ends and you have solved most of what sinks portfolios before craft even enters the picture. Curation is not the glamorous part of portfolio-making, but it is the part that decides more outcomes than any other single thing.

The second family is craft - the failures of the portfolio as a designed object, which are especially damaging for us because the document is itself a demonstration of design ability. Three recur.

Tiny, unreadable text. Captions set at six or eight points, low-contrast grey on white, or text crammed to the edges - all of it costs you in exactly the seconds you cannot spare. If your reader has to squint, they will not read; they will move on. Set body and captions at a genuinely readable size (roughly nine to eleven point in print, larger on screen), with real contrast and margins, and test it by printing a page or viewing it at actual size on a phone. If you cannot read it at arm's length, neither can they.

No visual hierarchy. A spread where everything is the same size shouts equally and therefore says nothing. The reader cannot tell the hero image from a supporting sketch, or the title from a caption. Establish a clear hierarchy - one dominant hero per spread, a clear title, supporting images visibly subordinate - so the eye knows where to land first and how to move. Hierarchy is what lets a page be understood in the six-second scan.

Over-design. The opposite failure, and just as fatal: restless layouts, trendy graphics, heavy filters, five typefaces and decorative clutter that fight the work for attention. Over-design reads as insecurity - as if the work cannot stand on its own. The discipline is restraint: a quiet, consistent grid and one or two typefaces that frame the work and never upstage it, like a good gallery where you notice the art, not the walls. When in doubt, take something out. The most common upgrade to a student portfolio is not adding polish but removing noise - more white space, fewer fonts, a calmer grid - until the work itself is finally allowed to speak. Craft mistakes are the easiest to fix and the most visible, which means fixing them buys an immediate, disproportionate lift in how seriously your work is taken.

The third family is the quietest and the most serious: story and honesty.

No story. A project shown as a data dump - a wall of drawings and renders with no framing - forces the reader to reconstruct your thinking, and most will not bother. Every project needs a spine: the problem or brief, the idea, how it developed, and how it resolved. A single line of framing - what this was, what was hard, what you did about it - turns a pile of images into an argument for how you think, which is what readers are actually assessing. You do not need many words; you need the right few, in the right order.

Dishonesty about authorship. This is the mistake that can end a career, not just cost a job. Presenting team or office work as if it were solely yours, implying you led what you assisted on, or quietly claiming a studio project's collective effort - experienced reviewers detect it easily, often with a single question in an interview you cannot answer, and the moment they do, trust collapses completely. Credit honestly and specifically. Naming your real role does not diminish you; it signals maturity and makes the parts that were yours believable. A precise credit reads as confidence, not weakness.

Weak (vague / over-claiming):  "Designed a 40-storey mixed-use tower."
Strong (honest / specific):    "Project team of six. My role: facade
                               studies, bay detailing, and the physical
                               model. Studio X, project lead: A. Rao."

Not being straight about AI. As AI tools enter the workflow, the same principle extends to them: be honest about what was AI-assisted. You do not need to annotate every keystroke, but passing off AI-generated imagery as hand-craft, or hiding tool use you would be embarrassed to explain in an interview, is the same integrity failure in a new form. Honest, thoughtful use of tools is fine and increasingly expected; misrepresenting it is not. In a field this small, your reputation for honesty outlasts any single portfolio - and it is the one asset you cannot rebuild once it is spent.

Knowing the mistakes only helps if you catch them in your own work, which is harder than catching them in someone else's - you are too close, and too fond of pieces for reasons your reader does not share. The remedy is a deliberate, cold review before every send. Run this checklist as a stranger would, ideally after a day away from the file:

PRE-SEND CHECKLIST
[ ] Fewer than ~8 projects? Every one genuinely strong?
[ ] Weakest piece: does it still earn its place, or cut it?
[ ] Strongest, most relevant project first?
[ ] Can I read every caption at actual size, on a phone?
[ ] One clear hero per spread? Obvious hierarchy?
[ ] Restraint: 1-2 typefaces, quiet grid, no clutter?
[ ] Each project: problem - idea - development - resolution?
[ ] Credits honest and specific? AI use straight?
[ ] File named + sized to email? Opens on their machine?
[ ] Six-second scan: is it obvious what I do and that I am good?

Two habits make the checklist far more powerful. First, get outside eyes. You cannot see your own portfolio the way a stranger does, so ask someone honest - ideally someone in the field, ideally someone who will actually tell you the truth - to give it the six-second scan and then a proper read, and to point at the weakest thing. It will sting; it is the most valuable feedback you will get.

Second, sleep on it. The mistakes you make under deadline pressure are exactly the ones a day's distance reveals, which is one more reason the living-portfolio habit from Lesson 10.1 matters: a portfolio kept current is never sent in a panic, so it is never sent full of the errors that panic produces.

None of these mistakes are exotic. They are ordinary, repeated, and entirely fixable - and a portfolio free of them already outperforms most of the pile. You do not need a trick or a flourish to stand out; you need to reliably not make the six mistakes that everyone else does. That is a lower bar than it sounds, and clearing it is almost entirely within your control.