How to Build a UX Portfolio From Scratch (With No Experience)

Most career-changers who want to move into UX design hit the same wall at some point. They understand what UX is. They have done their research. They are motivated. And then they realise: you need a portfolio to apply for jobs, and they do not have one.

This post is not about why you should build a portfolio. You already know that. It is about the practical question most resources skip over: how do you build a UX portfolio from scratch when you have never worked in UX before?

The portfolio paradox — and why it is false

You have probably encountered the circular logic: you need a portfolio to get a UX job, but you need a UX job to build a portfolio. It feels like a closed loop.

It is not. The premise is wrong.

Employers are not looking for a CV of prior employers. They are looking for evidence that you can do the work — that you can identify a real problem, understand the people who have it, explore solutions, test them, and iterate. That process does not require a client relationship or a salary. It requires rigour and documentation.

A well-executed personal project, where you spoke to five real users and made visible decisions based on what they told you, is more revealing to a hiring manager than a case study that says "I worked on a mobile banking app" with no process shown. The first tells them how you think. The second tells them nothing.

What you cannot fake

Before getting into the how, it is worth being clear about what you cannot shortcut. Three things separate a credible portfolio project from a design exercise:

Real users. You have to speak to people who actually use (or would use) the thing you are designing. Five conversations is a legitimate sample for a portfolio project. Zero is not research — it is speculation.

Documented findings. What did users tell you that was unexpected? What did you assume going in that turned out to be wrong? If your research section says "I spoke to five people and found that usability is important," that is not insight. Quote specific things people said. Show an affinity map. Explain what surprised you.

Decisions made for reasons. Every design decision in your case study should have a "because" attached to it. "I moved the navigation to the bottom because every user I spoke to was holding their phone one-handed and could not reach the top bar." That sentence shows UX thinking. "I moved the navigation because it looked cleaner" does not.

Three types of projects that work for a starter portfolio

Type 1: Personal briefs

Pick a product you genuinely use and care about — an app, a website, a physical service. The fact that you know it well is an advantage, not a cop-out. Treat it as a real design brief: what problem does it have? Who are the users? What is causing the friction?

The critical step that most people skip is research. A portfolio project based on a product you redesigned without speaking to anyone is, in the industry, called a "concept project." They are common and they are mostly ignored. To make yours count, you need to speak to real users of that product — five people, recruited through your own network, a subreddit, a local community group, wherever you can find them.

The strength of a personal brief is that you chose something you already understand deeply. The limitation is that there are no real constraints, no stakeholder pressure, and no one to push back on your assumptions. Document the constraints you set yourself to compensate.

Type 2: Volunteer work

This is the strongest type of project you can add to a starter portfolio. Local charities, community organisations, small businesses, and early-stage start-ups regularly need UX help and have no budget for it. Offering your time pro bono gives you a real client, a real brief, real constraints, and real people to interview.

How to find opportunities: reach out directly to organisations whose work you care about. Be transparent that you are training and will do the work pro bono in exchange for the experience. Catchafire and Idealist list volunteer roles in the UK, some of which are specifically UX-related. Local council community groups, mutual aid networks, and small-business owners you already know are also good places to start.

What makes volunteer work valuable in a portfolio is the same thing that makes any real project valuable: you had to navigate a relationship, explain your decisions to a non-designer, and deliver something to an actual standard. That shows more than a self-directed exercise, and hiring managers can usually tell the difference.

Type 3: Course projects

A well-structured UX course gives you a real client brief, experienced instructor feedback, and a peer group whose work you can learn from. The best course projects are not made-up scenarios — they involve real companies with real design problems, and they require you to conduct genuine research rather than just work through a set of design templates.

The advantage over self-directed projects is the feedback loop. When you do not know what "good" looks like yet, working with an experienced UX practitioner who reviews your case study at each stage accelerates your development faster than anything else. You can see examples of the kind of projects UX Academy students produce on the student work page.

What every portfolio case study must include

A case study is not a design showcase. It is a written account of your process — the decisions you made, why you made them, and what happened when you tested them. Here is the structure that works:

The problem. What were you trying to solve, and for whom? Be specific. "Improving the checkout experience for first-time buyers on a small e-commerce site" is more credible than "redesigning an e-commerce app."

Research. Who did you speak to? How did you recruit them? What did you find that mattered? This section should not summarise your method — it should tell the reader what changed in your understanding because of what you heard.

Insights and decisions. What did the research tell you? Which problems did you decide to prioritise, and why? Show your reasoning. An insight is not "users found it confusing" — it is "three of five users did not realise the checkout required an account until they had already entered their payment details, which caused two of them to abandon."

Process. Show the work in progress: rough wireframes, explorations, discarded directions. Hiring managers want to see that you explore before you land on a solution. A case study that goes straight from research to polished screens skips the most interesting part.

Testing. Did you put the design in front of real users? What did they do that you did not expect? What did you change as a result? Even a lightweight usability test with three people, documented honestly, adds significant credibility.

Outcome. What did you deliver? If you were doing it again, what would you do differently? Showing self-awareness about the limitations of your own work is a mark of maturity, not weakness.

A case study that takes five to seven minutes to read is about right. Longer and readers drop off before they reach the outcome.

What to leave out

The temptation when building a portfolio from scratch is to include everything you have ever touched, to bulk out the work. Resist it.

Leave out: projects you cannot explain confidently. If you cannot articulate why you made a specific decision, do not include that project — you will be asked about it in an interview and the gap will show.

Leave out: purely visual work with no UX process behind it. Illustration, graphic design, and UI styling belong in an art portfolio, not a UX one. What you include should demonstrate research, analysis, and problem-solving — not just taste.

Leave out: more than three or four projects. Depth beats volume. A portfolio with two deeply documented projects is stronger than one with six thin ones.

Leave out: the generic Twitter or Airbnb redesign with no research. Every UX portfolio course in existence prompts students to redesign one of these apps. If yours does not have research behind it, it blends in with the noise rather than standing out from it.

Choosing a portfolio platform

The platform you choose matters far less than the quality of what you put on it. A clear, scannable Notion portfolio beats a complicated Webflow one every time. That said, here are the realistic options:

Notion is the fastest to build and completely free. It produces clean, readable pages and is widely accepted across the industry. For a career-changer building a first portfolio, it is the most sensible place to start.

Squarespace offers polished templates and requires no technical knowledge. At around £12-16 per month, it is a reasonable step up if you want a more designed feel without a learning curve.

Adobe Portfolio is included with Creative Cloud subscriptions. If you are already paying for CC, this is a no-cost option with reasonable templates.

Webflow gives you significant design control and produces impressive results, but it has a steeper learning curve. Worth considering once you have one version of your portfolio live and want to invest more in the presentation layer.

Figma — some designers present case studies as scrollable Figma files, linked from a simple landing page. This works particularly well for audiences who are themselves designers or work closely with design teams.

Writing case studies that people actually read

The writing in your case studies matters. A few principles that make the difference:

Write as if you are explaining your process to a smart person who was not in the room with you. Do not assume they know what decisions you faced or why certain things were difficult. Make it explicit.

Lead with the problem, not the solution. The most common mistake in case study writing is front-loading the final design. Start with the context and the problem — earn the solution by showing the path you took to reach it.

Describe decisions as choices made for reasons, not as inevitable steps. "I used card sorting because..." is more interesting than "I used card sorting." The because is where your thinking becomes visible.

Keep it scannable. Short paragraphs, clear section headers, annotated images. Hiring managers are reading multiple portfolios. Make it easy to move through yours at speed and still grasp the essentials.

Show real artefacts. Interview notes, affinity maps, rough wireframes, sticky-note photos — these signal that the process was real, not retrospectively tidied up to look like a process. See UX research methods for guidance on which artefacts to generate and document at each stage.

Getting your portfolio seen

A portfolio that no one sees is not a portfolio. Once you have at least two case studies documented:

LinkedIn is the primary channel for UX roles in the UK. Put your portfolio URL in your headline and in the Featured section. Update your headline to reflect that you are actively looking — "UX Designer | Open to Junior Roles" signals availability.

Share one case study breakdown as a LinkedIn post — a short walkthrough of your process, the problem you solved, and what you learned. This signals activity and gives people a reason to click through to your portfolio.

Direct outreach works. Find UX designers and hiring managers at companies you want to join. Send a short, specific message — not a generic "I would love to work at your company" but something that shows you know their product and have relevant thinking to offer. Include your portfolio link. Personal messages with a specific hook get read.

For more on the job search side, see how to get a UX job with no experience and the UX portfolio review checklist.

The fastest path to a strong portfolio

The single biggest accelerant for a starter portfolio is working on a real design brief with experienced feedback at each stage. When you are new to UX, the hardest thing is not doing the work — it is knowing whether the work is good, and understanding why it is or is not.

On the Beginner UX Design course at UX Academy, you work on a real client brief with a real design problem over eight weeks of live instruction. Every stage of your process — research, synthesis, wireframing, testing — gets reviewed by a working UX practitioner before you move forward. The case study you produce becomes the strongest piece in your portfolio.

If you are targeting a full career transition and want interview prep and job search support alongside the design work, the UX Career Track covers the complete journey from first brief to first role.

You can also look at UX design portfolio examples and the UX portfolio guide to see what strong early-career portfolios look like before you start building your own.

The portfolio is not the obstacle. It is the first piece of work.