A UX portfolio should help a reviewer understand how you approached a problem and what evidence informed the design. Attractive screens can support the story, but they do not establish that a need was understood or a result was tested.
Use your own or authorised work. Label self-directed projects, synthetic examples and your part in a team clearly.
1. A specific problem
Explain the user, situation and question. Avoid inventing a business problem after designing a screen simply to make the case study look complete.
2. Your actual responsibility
State which research, design or coordination work you performed. Give appropriate credit to teammates and do not claim an entire project as an individual delivery.
3. Research context and limits
Describe what information you gathered and what it can support. A few informal conversations should not be presented as proof about every user.
4. Alternatives considered
Show a small number of meaningful options and the reasoning behind the choice. A sequence of polished versions does not explain the trade-off on its own.
5. A usable design explanation
Connect the layout or flow to the problem. Explain labels, errors and important interactions rather than assuming the reader understands a static image.
6. Evaluation evidence
State what you checked, with whom and what changed. Avoid fabricated conversion improvements or claims of universal accessibility from limited testing.
7. Reflection and next questions
Identify what remains uncertain and what you would investigate next. A thoughtful limitation is more credible than an invented perfect outcome.
Choose the next practical step
Choose a few relevant case studies and make them easy to follow. Protect participant and employer information, and check permissions before sharing material. The work-portfolio guide provides a broader evidence structure. A reviewer should be able to distinguish the work you did from the story you wish the project had demonstrated.
