Say the flaw out loud
A portfolio that shows only wins is not a portfolio. It is an advertisement, and everyone reading it knows.
Kiefer Likens · · 4 min
There is an unspoken agreement in this industry that portfolio work is presented at its best and its problems are never mentioned. Everyone participates. Everyone knows everyone else is participating. The result is that a portfolio carries almost no information — a reader cannot distinguish between work that went well and work that was rescued, because both are presented identically.
Which means the whole format has quietly stopped functioning as evidence. It functions as a competence signal, roughly equivalent to a clean shirt.
What naming a flaw actually signals
When a case study says the animated statistics band renders as zero for anyone without JavaScript, several things become legible at once that no amount of praise could establish.
- That the person writing it went back and looked, after delivery, when nobody was paying them to.
- That they understand the failure mode well enough to describe it precisely rather than vaguely.
- That the rest of the document is probably also true, because someone willing to write that down has no obvious motive to inflate what sits next to it.
That third one is the whole return. Credibility is not built by claims. It is built by the reader’s growing sense that you are not managing them.
Truth beats positioning. It costs something. It costs less than being caught.
Where the line is
This is not an argument for performative self-criticism, which is its own kind of marketing and reads as such immediately. There is a real distinction, and it is worth stating precisely.
Name flaws that are specific, technical, and fixable, and name them because they are the most useful thing you learned. What stays out is anything that breaks a confidence, or that blames a person who cannot answer. A recommendation you would happily make to the client’s face is fair game. A grievance is not.
A workable rule: before publishing a critical observation about a project, send it to the client first, as a fix recommendation. If it is worth writing about, it is worth them having. If you are not willing to send it, the point was never honesty — it was being interesting.