AI Guides › Career & Work
The Difference Between A Portfolio And A Pile Of Projects
By Nigel Guy · 2 min read
The natural instinct, especially once AI makes it cheap to produce more
work, is to keep adding: another project, another case study, another link
in the list. More items feels like more evidence. To the person reviewing
it, a long undifferentiated list usually reads as less impressive, not more
— it asks them to do the work of figuring out what actually matters.
The rule: a portfolio makes the case for you before anyone reads the
details — a pile of projects makes the reviewer do that work themselves, and
most won't bother.
The mechanism: the Portfolio Filter
- Cut to the three or four pieces that best show range or depth,
whichever your target role actually needs. Not your favourite projects —
the ones that answer the specific question a reviewer has about you.
- Lead each piece with the decision, not the deliverable. What was hard
about it, what you chose to do, why — the artifact itself is evidence for
that story, not the story.
- Cut anything that needs a caveat to be impressive. "This one's not
finished, but…" or "the client changed scope so…" — if it needs a defence
before it can land, it's weakening the portfolio, not strengthening it.
- Order by relevance to the reviewer, not by chronology. The most
recent thing you made is rarely the most relevant thing to lead with.
- Ask what one thing you want them to conclude after looking, and check
whether the current selection actually gets them there — if it doesn't,
the selection needs to change, not the write-up.
Where AI genuinely helps
Drafting the "why" behind each piece — the decision and the reasoning — from
your own notes is a good use of AI, especially if you're bad at
self-narration. It's also useful for stress-testing whether a piece belongs:
describe it and ask what conclusion a stranger would draw. If the answer
doesn't match what you wanted, that's a real signal.
What to skip
Skip including something because it took a long time to make — effort isn't
the axis a reviewer judges on. Skip a portfolio that tries to demonstrate
everything you can do; a scattered "I can do all of this" reads as less
credible than a focused "here's what I'm actually good at."
Guardrails
- What counts as a strong portfolio varies significantly by field and by
what the specific reviewer is screening for — this is a general filter,
not a template to fill in identically every time.
- Don't let a draft description overstate your role in a piece you didn't
lead alone — a reviewer who asks a follow-up question will find the gap.
- A tight portfolio still needs the work behind it to be genuinely good;
curation makes weak work look worse by contrast, not better.
All 751 AI guides · JulieMango plans from £17/mo