Select a few strong work samples and explain the problem, your contribution, the method and the lessons while respecting privacy and ownership.
A portfolio lets someone inspect the work behind a skills claim. It can be useful beyond design or software: a clear analysis, a research summary or a well-structured project plan may demonstrate professional judgement. The aim is to make a small set of relevant samples understandable to an unfamiliar reader.
Choose for relevance, not volume
Select three or four samples connected to the work you want to do. For each, write a short case note covering the problem, constraints, your role and the final output. Label academic simulations as simulations and distinguish an individual contribution from a team deliverable. Do not imply that a practice brief came from a real client.
Show the reasoning behind the result
Include an early version or a decision note where it adds value. Explain a trade-off, a correction or feedback that changed the work. A polished final document is more convincing when the reader can see how you evaluated alternatives and recognised limitations rather than simply following a template.
Check permission and maintain access
Remove personal data and confidential material, and obtain permission before sharing someone else's work or an employer's documents. Use accessible file formats and test links from outside your own account. Revisit the collection periodically; replace weaker samples and keep descriptions accurate as your experience grows. A concise portfolio is easier to discuss in an interview.
Build one page around a work sample
As an illustrative exercise, choose an options comparison completed during study. Put the comparison question first, show a readable extract from the table and explain why you selected its criteria. State an important limitation, such as hypothetical data or an outcome not tested in practice. Finish with what additional information would change your approach. A new reader should be able to explain both your decision and its limits.
Review the sample from outside your account
A portfolio may look organised to you while its links remain inaccessible or expose more folders than intended. Test permissions without using your own access rights, and inspect attachments, document properties and hidden comments before publication. Do not solve access problems by making the entire working folder public. Create a dedicated display copy, record its review date and identify individual versus team work. Keep useful revisions available to explain how the sample developed.
Further reading
- National Careers Service — How to write a CV
- National Careers Service — Understand and develop your skills
Image: original editorial artwork prepared for the Asas library; it illustrates the topic and does not depict an actual event or student.
