Empty Portfolio? Build These Three Things This Weekend
You know the loop. You cannot get work without a portfolio, and you cannot build a portfolio without work. It is the creative equivalent of needing a loan to prove you do not need a loan.
But here is the thing: an empty portfolio is almost never a talent problem. It is a definition problem. We have decided that a portfolio means a museum of paid gigs, signed off by clients, displayed in a grid. That definition is narrow, expensive, and — for anyone starting out in 2026 — mostly useless.
A portfolio is evidence of judgement. That is it. A hiring manager or a prospective client wants to see how you think, what you notice, and what you would do differently. You can demonstrate all of that without a single invoice.
Constraints help here. A blank canvas invites paralysis. A weekend and three artefacts invites decisions. So here is a sensible, low-drama plan.
Start With a Definition, Not a Panic
Write this at the top of a page: A portfolio is proof that I can make useful decisions under constraints.
That definition does two things. First, it lets you use speculative work — work you were not paid for — because the proof is in the thinking, not the purchase order. Second, it gives every piece a job: show a decision, show a trade-off, show what you would measure.
You are not trying to impress someone with the volume of your archive. You are trying to answer one question in their head: Could this person handle our problem?
Artefact One: The Teardown
Pick a brand you actually use. Not a fashionable agency brand. Something with real friction and real customers. A supermarket app. A train booking flow. A council recycling page. A gym's sign-up email.
The mistake people make is writing a rant. A teardown is not a rant. It is a structured opinion.
Use this shape:
- What it is: one line of context.
- What is working: two or three specific things, with reasons.
- What I would change: three changes, ranked by impact.
- What I would measure: one metric per change.
- The trade-off: what you might lose by making the change.
That last section is the one that separates judgement from taste. Anyone can say 'the checkout is confusing'. A useful teardown says: 'I would move delivery options above the postcode field, because the current order forces a decision before the user knows the cost. I would measure drop-off between basket and address entry. The trade-off is a longer first screen, which may hurt mobile completion.'
Title it plainly: A teardown of [brand]'s [specific surface], with three changes I would test. That framing tells the reader you are not attacking the brand. You are practising a craft.
Artefact Two: The Before-and-After Redraft
Find a real, public-facing page or email that is trying to do a job and doing it badly. A charity donation form. A local council's bin collection page. A dental surgery's appointment confirmation. A trade association's membership page.
Redact anything personal. Keep it legal and kind. Then show three things:
- Before: the original, with a short note on what it is trying to achieve.
- After: your redraft.
- Why: a 150-word rationale explaining the decisions you made.
The rationale is the portfolio piece. The redraft is just the evidence. Explain the reader you had in mind, the constraint you respected (legal, brand, technical), and the one thing you would test first.
This artefact proves something a paid case study often cannot: that you can improve someone else's work without needing a brief, a budget, or a standing invitation. That is a hireable skill.
Artefact Three: The Point-of-View Note
Write 500 words arguing one clear thing. Not a listicle. Not a round-up. One argument with a practical implication.
Examples that work for UK creatives:
- Why UK service brands keep mistaking friendliness for clarity.
- The case against 'Book a call' as the only call to action.
- What British council websites get wrong about trust.
- Why your case studies are too long and your summaries are too short.
Make the argument specific. Use one example. End with a sentence that begins: So the practical rule I would use is...
This is the piece that shows you can think beyond execution. It is also the easiest to write badly, because it tempts you into opinion without evidence. Keep it grounded in something observable: a screen, a sentence, a process.
How to Frame Each Piece So It Reads as Judgement
Use the same five-line frame for every artefact:
- Context: one line on what this is and who it is for.
- Constraint: what you could not change, or what you had to work within.
- Decision: what you did, in plain English.
- Trade-off: what you gave up, and why it was worth it.
- What this shows: one sentence on the capability being demonstrated.
That last line is not arrogant. It is helpful. A busy client should not have to infer your value from a PDF. Tell them what to notice.
For example: What this shows: I can audit a sign-up flow, prioritise fixes by likely impact, and write the rationale for a non-specialist stakeholder.
That is not filler. That is a job description with evidence attached.
The Weekend Schedule
Friday evening: choose your three artefacts. One teardown, one redraft, one point-of-view note. Do not choose the most impressive brand. Choose the one you can observe closely.
Saturday morning: research and notes. Screenshot, read, annotate. No writing yet.
Saturday afternoon: write the teardown. Keep it under 700 words.
Sunday morning: do the redraft. Keep the rationale tight.
Sunday afternoon: write the point-of-view note, add the framing lines, and publish.
Publish somewhere simple. A page on your existing site, a Carrd, a Notion page with a clean URL. You do not need a custom grid or a case-study template. You need three pieces that show a brain at work.
The Bit People Skip
Write an 80-word introduction at the top. Not 'aspiring creative'. Not 'passionate about storytelling'. Use this shape:
I help [specific UK audience] do [specific useful thing]. Before that I [relevant experience or training]. Here are three pieces that show how I think. Email me at [address].
That is it. Empty portfolio, defined properly, is not empty at all. It is a set of decisions waiting to be written down. Start with one artefact this weekend. The other two will follow.