Your First UX Portfolio: Start with evidence, not polish

Start with the work you want next

Your first portfolio is not supposed to prove that you have already done every kind of UX work. Its job is to help the right reader see a credible connection between the work you have and the work you want to do next.

Collect a small set of role descriptions that genuinely interest you. Look for repeated expectations—not every phrase in every job post. Then translate those expectations into evidence a project could show.

Build the minimum portfolio that makes a case

Do not wait until you have a magical number of projects. Begin with one complete case study and a simple shell around it. Add another project when it proves something meaningfully different.

Choose projects you can talk about honestly

Professional client work is not the only source of evidence. The strongest beginner project is the one that lets you explain the problem, your contribution, your decisions, and what informed them without filling the gaps with invented certainty.

If you have several possible projects, the broader Design Portfolio Guide can help you decide what each project needs to prove.

Write the first case study around decisions

A case study is not a scrapbook of every method you used. It is a guided argument: this was the situation, this is what I contributed, this evidence mattered, and these decisions shaped the result.

1. 1
   Give the project in one screen

   Name the problem or opportunity, audience, your role, project context, current outcome, and one representative visual.
2. 2
   Establish the constraints

   Explain the team, timeline, platform, content, access, production, research, or business conditions that affected the work.
3. 3
   Choose two or three consequential decisions

   Show where the work could have gone another way, what evidence or constraint mattered, and why you chose this direction.
4. 4
   Place evidence beside the claim

   Use research, iteration, interface states, critique, production details, or results where they help the reader understand the decision.
5. 5
   Name the result and its limits

   Separate what shipped, what was measured, what was observed, what was approved, and what is still a hypothesis.
6. 6
   End with a specific reflection

   Say what you would preserve, change, or investigate next—and why.

Use the free Design Case Study Builder to turn project notes into a decision-and-evidence outline before polishing the page. The case study structure guide goes deeper on the finished narrative.

Design the shell around the work

The portfolio shell is the homepage, work selection, navigation, About or resume context, and contact path around your individual case studies. Its job is to help a reader understand you and choose where to go next.

Explore portfolio layout patterns for structure, but keep the choice connected to your work instead of copying the surface of someone else's portfolio.

Use an adaptable eight-week plan

Eight weeks is a planning frame, not a guarantee that everyone becomes job-ready on the same date. Compress it when the material is ready; repeat a week when the evidence needs more work.

1. 1
   Map the role and evidence

   Choose a direction, collect a few relevant job descriptions, and list the proof a strong candidate would need.
2. 2
   Inventory and choose

   Review existing work and select the project with the strongest relevant evidence and clearest personal contribution.
3. 3
   Write the case-study skeleton

   Draft context, role, constraints, key decisions, evidence, outcome, and reflection before styling the page.
4. 4
   Build the evidence layer

   Select, crop, caption, and sequence only the visuals that help explain the project argument.
5. 5
   Build the portfolio shell

   Create the homepage, work selection, About or resume context, navigation, and contact path.
6. 6
   Test with real readers

   Ask three people what role they think you want, what they remember, what feels convincing, and where they become unsure.
7. 7
   Revise the experience

   Fix the largest comprehension problem, then check mobile, keyboard use, contrast, media, performance, and links.
8. 8
   Publish and tailor

   Launch the smallest credible version and make a role-specific pass before sending it with an application or introduction.

Treat accessibility and performance as part of the work

A portfolio is itself a designed experience. It does not need to be technically elaborate, but it should let people reach, understand, and inspect the work across common devices and ways of navigating.

Use AI to clarify, not manufacture experience

AI can help you sort notes, find repeated ideas, shorten a project overview, question a vague claim, or create a list of gaps to check. You still have to decide what is true, relevant, and yours.

Publish before the portfolio feels finished

A portfolio becomes useful when someone else can read it. Publish a credible first version, learn where readers become uncertain, and improve the largest problem before adding more pages.

The portfolio checklist can help with the final pass. Use it as a prompt to inspect the site, not as a substitute for feedback from someone encountering the work for the first time.

Sources and further reading