Before you commit · 6 min read

How to build a career-change portfolio when you have no clients

Three complete practice briefs, an annotated case-study structure and a way to show your work honestly, even before you have a client.

Written by Nivaan, founder of OffLadder · Last reviewed 10 October 2026 · Sources listed at the foot of this page

The blank page can feel circular. You need a job to get experience and experience to get a job, while everyone advises you to “show your work.” What work? For whom? At what standard?

Begin with one small brief that has enough constraints to force decisions. You do not need a pretend global client, a personal brand launch and six case studies before showing someone how you think.

Decide what the portfolio has to prove

Choose a narrow target. A content-design portfolio should not merely prove that you write fluently. An operations sample should not merely prove that you can format a spreadsheet. Read relevant adverts and identify the decisions or outputs the employer expects.

Nielsen Norman Group’s research on UX portfolios emphasises showing process and explaining your own contribution, rather than relying only on finished visuals. Its findings concern UX hiring, not a universal rule for every profession, but the distinction is useful: a polished object can hide weak reasoning, and a modest-looking object can contain strong work.

Ask what format a reviewer can realistically inspect. A short PDF, document or repository may be more appropriate than a website. Do not build an elaborate presentation layer before the work deserves one.

Brief one: make a confusing service understandable

This fictional community workshop offers a ninety-minute session for adults. It costs £8, includes materials and takes place on Saturdays at 10 a.m. People must request a place by Wednesday. A booking is confirmed only when staff reply. Cancellations before Thursday noon receive a refund. The room has step-free access, but there is no hearing loop.

Your task is to produce a 250-word information page and a short confirmation email. Do not invent a payment method, extra access provision or a phone number. Mark missing operational details as questions for the fictional service owner.

A strong case study explains the order of information, how the reader knows whether a place is confirmed and what they need before booking. Test comprehension with a consenting adult: ask when a place becomes confirmed and what happens after a late cancellation. Record what actually happened. Do not report a conversion increase because the page looks clearer.

This brief can show writing, information design and responsible handling of missing facts. It does not show that you have worked for a real service.

Brief two: make a messy operation visible

A fictional repair club has six open requests: A, received Monday, parts available, standard; B, Monday, waiting for parts, standard; C, Tuesday, parts available, urgent; D, Tuesday, parts available, standard; E, Wednesday, waiting for a customer reply, urgent; F, Wednesday, parts available, standard.

The supplied rule is to handle urgent requests first when they are ready, then standard requests by received date. Blocked requests should remain visible with an owner and next check. Assume the letters resolve ties within a day.

Build a one-page queue and handover note. The ready order is C, A, D, F. B and E should not silently disappear: record the blocker and what needs to happen next. Do not invent a completion date without capacity information.

Then introduce a change: only two requests can be handled tomorrow. Explain what you would do, what would remain and whom you would update. This sample can reveal whether you understand priorities and exceptions, not just colour coding.

Use the fictional workshop dataset in article 11. Produce a short recommendation on whether to investigate an additional Saturday session. Include the cleaned table, your treatment of the duplicate and missing attendance, a chart and the limits of the conclusion.

The case study should say why you selected a particular comparison and why you did not fill missing attendance with zero. Retain the original data so the cleaning decisions can be checked.

Make the recommendation proportionate: “Investigate demand and operating constraints for another Saturday” is not the same claim as “Saturday sessions will increase revenue by 40%.” There is no evidence for the latter. A portfolio becomes less credible, not more commercial, when it adds impressive numbers without a measurement basis.

Turn the work into a case someone can follow

Use this structure and keep it compact: context, task, contribution, decisions, output, feedback, limits, next step. Here is an annotated example for the operations brief.

“Context: Self-directed practice using a fictional repair-club queue.” This establishes provenance before a reader mistakes it for client work.

“Contribution: I designed the queue and wrote the handover note; no team or real organisation was involved.” This prevents an impressive “we” from obscuring what you did.

“Decision: I separated blocked work from ready work without removing it from the view.” This explains a choice and its consequence.

“Feedback: A reviewer could identify the next two jobs but could not tell who would check the blocked requests. I added an owner and next-check field.” Use this only if that review actually happened. Otherwise write “Feedback not yet obtained.”

“Limit: The exercise does not test whether the queue works with real demand or multiple staff.” That is an honest boundary, not an apology.

Get feedback on the work, not encouragement about your future

Ask one specific question: “Could you decide what to do next from this handover?” or “Which claim is not supported by the data?” It is easier to answer than “Do you think I could work in this field?”

Seek feedback from someone familiar with the work where possible, but respect their time. Share a short sample, explain that it is practice and request a bounded review. Do not demand unpaid mentoring or present yourself as a client offering future work.

Keep a before-and-after example. The change may be more revealing than the final output because it shows whether you can respond thoughtfully rather than defend everything you originally made.

Keep the evidence clean

Do not publish former employers’ materials, customer records or confidential processes without appropriate permission. Removing a company name may not be enough. Rebuild a genuinely fictional example when necessary and state that it is fictional.

Label AI assistance where it materially shaped the work, and make sure you can explain and verify the result. Credit collaborators and distinguish your own contribution. A practice project does not become commercial experience because you put a real company’s logo on it.

How many pieces do I need? Start with one strong, relevant case and learn from its review. Add a second when it demonstrates a different capability rather than repeating the first in another colour.

Can I use these briefs? Yes, as practice, with clear acknowledgement that the supplied scenarios and data are fictional. Your decisions, execution and any real feedback are the evidence you contribute.

Let the portfolio help you choose, too

OffLadder is not only a place to find a direction. Explore suggests work to test, Laddie helps you make sense of the response, and You keeps the experiments and reflections together. Bring in the sample you most wanted to improve, not just the prettiest one. Build evidence about your next direction. A good practice project can tell an employer how you think and tell you whether you want more of this work.