The Design Portfolio Is Broken. Here Is What I Would Show Instead.
I have reviewed a lot of portfolios. Hiring for teams, mentoring, and lately just being sent them by people who found my site. They have converged on a single format and that format has stopped working.
You know the one. A hero image of an app on a floating phone. A paragraph about the challenge. Four personas. A user journey map. Some wireframes. A section titled "The Solution". Final screens on a gradient. A line at the end saying engagement increased by some percentage that nobody can verify.
Every one of them looks competent. Almost none of them tell you whether the person can design.
The format hides the only interesting part
What I want to know is how you think when the problem does not cooperate. The standard case study is written backwards from a known answer, which removes exactly that.
Nothing in it is wrong. It just describes a process that went smoothly, and no project goes smoothly. The version where the research said something inconvenient, or engineering said no, or the first three ideas failed, is the version that would tell me something. It gets edited out because it looks like weakness.
It is the opposite of weakness. It is the entire job.
What I would put in instead
One decision, in detail. Pick a single real fork in the project. Show what the options were, what you knew at the time, what you chose, and what it cost. One well explained decision beats a full process walkthrough, because process is a template and decisions are yours.
The thing you got wrong. Genuinely. What shipped, what happened, what you changed. Anybody who has built real products will trust you more, not less. The people who would hold it against you are the people you do not want to work for.
Work that was not precious. The rough version, the ugly test, the sketch that unlocked it. Polished finals tell me you can render. The middle of the work tells me you can think.
Numbers you can actually defend. If you say conversion went up eleven percent, be ready to say over what period, against what baseline, and what else changed at the same time. If you cannot, do not use the number. An honest "we did not measure this properly" is worth more than a figure you cannot stand behind, and experienced interviewers spot the difference immediately.
The part nobody wants to hear
Your case study is probably too long and your best work is probably buried on page three.
Reviewers are giving you somewhere between forty seconds and two minutes on the first pass. Not because they are lazy, because there are sixty portfolios. Whatever you most want them to see needs to be visible in that window without scrolling and without a preamble about your design philosophy.
Three strong projects with real depth beats nine that are fine. The weakest thing in your portfolio sets your level, not the strongest, because the reviewer is asking what your floor looks like.
What is replacing it
The most convincing portfolios I have seen lately are not portfolios. They are things that exist.
A small app in the App Store. A tool that solves an annoying problem, used by two hundred people. A site you built and shipped. Something with a URL that a stranger can open right now.
That is not a fashion. It is that the barrier to making something real has collapsed. If you can design and you can now build, then a shipped thing is available to you in a weekend, and a shipped thing answers every question a case study is trying to argue.
Show me something that works. Then tell me why it looks like that.