- Reading time: 3 minutes
- Price: Free download
- Published: 16th September 2026
- Word count: 618 words
- File format: Text
Personal statement example
My final-year undergraduate project began with a fairly mundane observation from a summer job packing orders in a warehouse: almost everyone made the same mistake, reaching for the wrong shelf when two product codes differed by a single digit. I designed a computer-based picking task in which participants retrieved items from a grid of on-screen bins, comparing plain numeric labels with labels that added a redundant colour band. Colour-coding reduced errors modestly, but what interested my supervisor and me more was the pattern of the errors that remained: they clustered when participants were working quickly and when two similar codes sat adjacent. Writing that up taught me to be careful about what a small study can support. My sample was fifty-two undergraduates, my task was much simpler than a real warehouse, and my conclusion was properly limited to suggesting which design features deserved a better-controlled test. I would like to spend a master's learning to do that kind of work more rigorously.
My degree gave me the foundations I keep returning to: attention and working memory, signal detection theory, and research methods, including the mixed-design analysis I used in my project. Reading around the subject has shaped how I think about error. Reason's distinction between active failures and latent conditions, and his work on the different mechanisms behind slips and mistakes, changed how I interpreted my own results. Norman's The Design of Everyday Things gave me a vocabulary for affordances and mappings that I found myself using constantly once I started looking at everyday equipment. I am now more interested in the measurement side: how workload is actually assessed in the field, and how far self-report instruments can be trusted alongside performance data.
My job in a university library has been an unexpectedly good source of examples. I look after the self-service borrowing machines and the room booking system, which means I see the same confusions repeatedly. Users routinely tap the screen before placing the book on the pad, because the visible prompt appears before the sensor is ready. I logged the problems staff were reporting for a month, grouped them, and suggested to my supervisor that the prompt wording and its timing were the likeliest culprits rather than user inattention. We changed the on-screen text and added a printed card; queries at the desk dropped noticeably, though I did not collect the kind of data that would let me claim a measured effect. It was a small, useful change, and a reminder that most human factors work is incremental.
I also collaborated on a group project in my second year evaluating the usability of a local council's recycling information pages. My part was writing and piloting the task scenarios and keeping the notes consistent across the four of us, which mattered more than I expected when we came to pool our observations. Outside work I restore second-hand bicycles and pass them on cheaply to students. Setting up brake levers for people with different hand sizes has made anthropometry feel less abstract than it did in lectures.
A taught master's suits me because I want structured grounding in areas my degree only touched: task analysis, human reliability, and the standards used in safety-critical industries. I am particularly keen to learn cognitive task analysis properly, since my instinct at the moment is to jump to redesign before I have understood how the work is currently done. Afterwards I hope to work as a human factors practitioner, most likely in transport or healthcare, where the questions are concrete and the consequences of poor design are clear. I would rather spend my career making ordinary systems less error-prone than looking for something more dramatic.
Why this example works — strengths and ways to improve
This is a strong, coherent taught master's statement built from ordinary evidence: a warehouse job, a library role and a modest undergraduate study. Its main virtue is calibrated reflection, especially your honesty about what your data can and cannot support. The remaining gaps are mostly about depth. Your measurement interest, methods detail and future direction could each be developed a little further.
Subject motivation
almost everyone made the same mistake, reaching for the wrong shelf
Your motivation grows from a concrete, repeated observation rather than a declared passion, which makes it believable. You then show that curiosity developing into a research question about error patterns. The closing preference for 'ordinary systems' is consistent with this opening and feels earned rather than tacked on.
Academic preparation
Reason's distinction between active failures and latent conditions
You cite specific theory and explain how it changed your interpretation of your results, which is better than listing reading. You also name signal detection theory and the mixed-design analysis. Briefly explaining how that analysis handled your speed and adjacency factors would show methodological readiness more directly.
Evidence and reflection
my conclusion was properly limited to suggesting which design features deserved a better-controlled test
This is genuine reflection. You identify concrete limitations, including the sample, the task simplicity and the generalisability, and draw an appropriate conclusion from them. Noticing that the residual errors clustered by speed and adjacency shows analytical interest beyond the headline result. Admitting your tendency to jump to redesign is similarly self-aware.
Relevant experience
I logged the problems staff were reporting for a month, grouped them
The library example works because it shows a method: collect reports, categorise them, form a hypothesis about timing and wording, then intervene. The group project adds pilot-testing and coordination. The bicycle anthropometry link is plausible but thin. One sentence on what you actually adjusted, or what you learned from doing it, would strengthen it.
Credibility and voice
though I did not collect the kind of data that would let me claim a measured effect
Your refusal to overclaim strengthens trust throughout. Your roles are stage-appropriate, and you credit your supervisor rather than inflating your authority. The voice is plain, precise and personal, with no ornate phrasing or generic skill claims weakening it.
Structure and format
A taught master's suits me because I want structured grounding
The structure flows well: project, theory, workplace, other experience, then aims. You correctly frame this as taught study rather than doctoral research. The final paragraph's career aim of 'transport or healthcare' is reasonable but brief compared with the earlier detail. The rest of the statement is economical.
What you’ve done well
- Calibrated discussion of your project's limitations shows readiness for rigorous postgraduate methods.
- Ordinary jobs are used as evidence of systematic observation and intervention, not as decoration.
- Your reading is connected explicitly to how you reinterpreted your own data.
How this draft could improve
- Develop your stated interest in workload measurement and self-report reliability by linking it to a specific question raised by your project or your library work.
- Add a sentence on what the bicycle setups or the group project's pooled observations taught you methodologically, so these examples carry reflection rather than just mention.
- For a real application, tailor the final paragraph to the actual programme and say briefly why transport or healthcare interests you specifically.