What this subject family covers
Courses in this area deal with how people use, understand and move through designed things: screens, devices, information, systems and services. Unlike graphic design, the main question is not how something looks. It is what happens when someone tries to use it. Unlike product design, the thing being designed is often a behaviour, a sequence or a system rather than a physical object. A personal statement for this area works best when it shows you notice how people act, how designs can fail them, and how you would find out why.
Course titles here vary, and the emphasis differs between them:
- Interaction design looks at the moment-to-moment exchange between a person and a system: inputs, feedback, timing, gesture, sound, and physical or digital interfaces. Prototyping and making often matter a great deal, sometimes including electronics or code.
- User experience (UX) design is usually centred on digital products. It covers research with users, information architecture, task flows, usability testing and iterating on interfaces.
- Service design deals with services delivered across many touchpoints and people, such as a GP appointment system, a library, a council process or a delivery service. It involves staff as well as customers, back-stage processes, policy and organisational constraints.
- Information design concerns making complex information understandable: forms, wayfinding, timetables, data visualisation, instructions and public information. It overlaps with graphic design but is judged by comprehension rather than expression.
- Experience design is often broader and more speculative. It can include events, exhibitions, immersive or narrative experiences and emerging technology, and sometimes critical or future-facing work.
Read the course descriptions closely. One programme may expect coding and physical computing. Another may lean towards social research and public-sector services. You do not need evidence for every branch. Pick the emphasis of the course you are applying for and choose evidence that fits it.
Interests that carry weight
A general enthusiasm for technology or apps says very little. Specific interests are stronger, especially ones that show you have looked at a design problem from the user’s side. Some directions that work well:
- Failure and friction. A self-checkout that confuses older shoppers, a train ticket machine, a benefits form, a hospital’s signage. Explaining why it fails is useful: unclear feedback, wrong mental model, too many decisions, language barriers, or an assumption that everyone owns a smartphone.
- Accessibility and inclusion. How screen readers handle a website, how captions or colour contrast change who can use something, how design affects people with cognitive or motor impairments. This is strongest when it comes from observation or testing rather than a slogan.
- Systems behind the surface. For service design in particular, noticing that a bad experience is caused by a handover between departments, a staffing rule or a data system, and not by a badly drawn screen.
- Making information clear. Redesigning a confusing timetable, comparing how two news outlets visualise the same data, or seeing how a misleading chart changes what readers believe.
- Ethics of persuasion. Dark patterns, attention-driven feeds, consent screens, and the tension between business goals and user interests. Show a view you have reasoned through, not just a complaint.
- New interaction forms. Voice interfaces, wearables, games, sensors, or interactive installations, approached through what they make easier or harder for people.
When you write about reading or designers you admire, connect them to something you did or noticed. Saying a book changed how you looked at door handles only matters if you then describe what you looked at differently.
Evidence that shows how you design
Admissions readers for these courses usually want to understand your process, not just finished outputs. The most useful evidence shows a cycle: observing or asking people, identifying a problem, trying a solution, testing it and changing it. Small projects described honestly can do this better than polished screens.
Self-directed projects
- Redesign of something real. Choose an everyday thing you can watch people use: a school’s online homework portal, a club’s sign-up process, a café’s ordering system. Watch or interview a few users, sketch alternatives, test a paper prototype, and note what changed. The point is the reasoning, not the polish.
- Usability testing on a small scale. Asking five friends or relatives to complete a task on a website while thinking aloud teaches a lot. Report what surprised you. Do not present a handful of tests as rigorous research.
- Service mapping. Map a service you have experienced, such as registering at a doctor’s, moving house or returning an online order, step by step. Include what staff and systems do out of view. Identify where it breaks down and suggest a change, noting the constraints a real organisation would face.
- Information redesign. Take a bus timetable, a medicine leaflet or a set of instructions and redesign it, then check whether someone else can actually use your version faster or with fewer errors.
- Prototyping with code or electronics. For interaction design courses, a simple Arduino project, a small web prototype or an interactive Scratch or Processing sketch shows you can build to test ideas. What you learned from it not working first time is often the most useful thing to write about.
School and college subjects
- Design and technology / product design: user research, iteration and testing carry over well. Emphasise the parts about users, not just materials and manufacture.
- Art and graphics: visual skills are useful, but link them to communication and clarity. A strong poster is less relevant than evidence that you tested whether people understood it.
- Computing: useful for interaction and UX, especially if you built interfaces or thought about users. Programming alone does not show design thinking.
- Psychology: attention, memory, perception and research methods connect directly to how people use interfaces. Show the link with a specific example.
- Sociology, geography, business or politics: relevant to service design, where systems, institutions, inequality and policy shape experiences.
- English or media: useful for writing for interfaces, narrative experiences and audience awareness.
- Maths and statistics: relevant to data visualisation and to interpreting test results carefully.
Using experience that is not design work
Many applicants have no design placement. Ordinary experience can be strong evidence if you treat it as observation of how people and systems behave. Be precise about what it shows and avoid claiming it was design work.
- Retail or hospitality jobs. You see customers struggle with menus, tills, queueing and returns, and you see the staff side of a service. This connects directly to service design. It shows observation of a real service and its constraints. It does not show you can design one unless you describe something you noticed, proposed or changed, and why.
- Call centre, reception or customer support. You hear repeated questions that point to unclear information or poor processes. Useful for service and information design. Describe a pattern you spotted and what might cause it.
- Caring for a relative. Helping someone use health services, online banking or medication can show how design fails people with less confidence, limited sight or memory difficulties. This is valuable insight into inclusion. Write about it respectfully and keep the focus on what you observed in the systems, not personal medical details.
- Volunteering. A food bank, charity shop or youth club often runs on improvised systems. If you reorganised a rota, a sign-up sheet or a donation process, explain the problem, what you tried and whether it worked. If you only took part, say what you noticed rather than overstating your role.
- Tutoring or helping others with technology. Teaching a grandparent to video call shows how people build mental models of interfaces. It is real evidence of empathy and explanation, though not of research method.
- Gaming and modding. Thinking about onboarding, difficulty curves, control mapping or accessibility settings is relevant to interaction design. Simply playing a lot of games is not.
- Running a club, social media page or small event. If you designed how people found information or signed up, and adjusted it when it confused people, that is relevant. Follower numbers are not.
In each case the useful part is a specific moment: what someone did, why you think it happened, and what a better design might do. One detailed example is worth more than a list of jobs.
Reflection that works for this subject
Good reflection here usually shows a shift from your own assumptions to what users actually did. Points worth including:
- Where you were wrong. A prototype you thought was obvious that testers could not use is a strong example, provided you explain what you changed.
- Trade-offs. Simplicity against flexibility, speed against accuracy, business needs against user needs, accessibility against a particular visual style. Showing you weighed these is more convincing than claiming a perfect solution.
- Who was missing. If you only tested with friends your own age, say so, and say how that might have affected the result. This shows research awareness.
- Scale and context. Recognising that a fix for one café may not work for a national service, or that a change needs staff training and not just a new screen.
Avoid reflection that only states feelings or that you “learned the importance of the user”. Describe the actual change in how you worked.
Postgraduate applications
Many courses in this area, such as experience design, service design and design informatics, are postgraduate and admit people from varied backgrounds. If you are coming from another discipline, explain what it gives you: research methods from social sciences, systems thinking from engineering, writing from humanities, or care-sector knowledge from work. Then be honest about what you need the course to teach you. If you already work in a related role, distinguish the projects you led from those you contributed to, and say what limits of your current practice made you want further study. A focused area of interest, such as public services, healthcare, data or emerging technology, helps, as long as it is grounded in experience rather than fashion.
Pitfalls specific to this subject
- Equating UX with making screens look nice. Visual polish without evidence of research or testing suggests a graphic design interest instead.
- Buzzword process. Listing “empathise, define, ideate, prototype, test” without showing you did any of it reads as copied. Describe what you actually did.
- Overclaiming research. Five informal interviews are useful but not a study. Say what they were.
- Tool lists. Naming Figma or other software says little. What you used it to find out matters more.
- App ideas without users. Describing an app you would like to build, with no sign of who needs it or how you checked, is weak evidence.
- Treating the course as job training. Interest in becoming a UX designer is fine, but courses also cover research, theory, critique and ethics. Show interest in the questions, not only the career.
- Ignoring the course’s emphasis. A statement full of interface work sent to a service design course focused on public systems, or the reverse, will seem poorly matched.
For general advice on planning, structure and editing, read our personal statement writing guide.
Interaction, user experience and service design personal statement examples