Saving.Careers
All writing

What a portfolio proves that a CV cannot

A CV is a claim and a portfolio is evidence. The two objections people raise are both real, and neither is actually a blocker.

Nikhil SharmaOctober 6, 20263 min read

A CV is a claim. A portfolio is evidence. That is the whole difference and it is larger than it sounds.

Everything on a CV is a sentence about yourself, written by you, that the reader has to take on trust. Eleven years. Led a team. Grew the account. All of it might be true and none of it can be checked in the ninety seconds your reader is giving you. So the reader does what anybody does with unverifiable claims — discounts them heavily, and looks for something they can actually see.

A portfolio removes the trust step. Here is the thing. Look at it.

The two objections

"My work is not visual." Most work is not. A portfolio does not have to be pictures.

It can be a page explaining a decision you made and why you made it instead of the obvious alternative. A teardown of somebody else's work, done properly. A short write-up of a problem in your industry that most people get wrong, with the correction. None of these are pretty and all of them prove the thing that matters.

"It is all confidential." Then write about the shape of the problem rather than the client. Nobody needs the account name to see that you understood what was actually being asked.

Both objections are usually real and neither is actually a blocker. What stops most people is that a portfolio is work, and it is work with no deadline and no boss, which makes it the easiest thing in the world to postpone.

What a portfolio is really demonstrating

Not skill. Skill is increasingly cheap and increasingly assumed.

Judgement. The reader is trying to find out whether you can be trusted with an ambiguous problem and no supervision. Every piece of evidence you put in front of them is answering that question whether you meant it to or not — which is why a small finished thing with a clear decision explained beats a large unfinished thing with impressive ambition.

The useful constraint

Build something this week that needs nobody's approval.

Not your employer's, not a client's, not a platform's. The constraint matters because waiting for permission is the most common way a portfolio never gets made, and because the pieces you can publish without asking are usually the ones that show judgement most plainly.

One page. One decision. One reason it was not the obvious choice.

Comments

Nothing here yet.

Sign in to join Saving.Careers and comment.