Design Informatics MSc postgraduate personal statement example

Personal statement example

Most mornings at the public library where I work, someone hands me a self-checkout receipt and asks what it means. The machine prints the titles borrowed, the due dates and a line reading "Items not processed: 1", with no indication of which item failed or why. I have learned to spot the book with a damaged tag, but every time I explain it I wonder who decided the receipt should look this way, and whether they ever stood beside the kiosk watching people read it. That question, about how data reaches the people it describes, is why I am applying for postgraduate study in Design Informatics.

My degree was in Sociology with a minor in digital media. The sociology gave me methods: interviewing, coding qualitative data and an awareness that technologies carry assumptions about their users. The digital media modules gave me basic HTML, CSS and some Python, which I used mostly to clean survey spreadsheets. For my dissertation I ran a three-week diary study with eleven library users over sixty-five, looking at how they booked public computer sessions. Participants recorded each attempt, what went wrong and who, if anyone, helped them. The most consistent finding was not that the online system was hard to use, but that people did not trust it to hold a booking, so many came in early anyway. I presented this to the branch manager, and staff now print a small confirmation slip for anyone who books by phone. It was a modest change, but it showed me that understanding behaviour and designing an artefact around it belong together.

The project also showed me the limits of my skills. I could describe the problem well, but I could not prototype an alternative booking flow, nor analyse the booking logs that the council holds. Since graduating I have worked through an introductory online course in data visualisation and read Don Norman's The Design of Everyday Things, whose distinction between the gulf of execution and the gulf of evaluation describes my receipt problem neatly: the machine has acted, but the person cannot tell what happened. I have also started building small interactive charts with a JavaScript library, beginning with a chart of how our branch's opening hours have changed over ten years, using figures from old leaflets. It is rough, but it taught me how many design decisions sit inside a single axis.

Away from screens, I volunteer one Saturday a month at a repair café, mostly helping with sewing machines and clothing. I sew most of my own clothes, and drafting a pattern has more in common with interface work than I expected: it is a set of instructions that only succeeds if someone else can follow it. At the repair café I log every item brought in on a shared spreadsheet, and I have suggested adding a field for the cause of failure so the group can see which faults recur. Volunteers now fill it in, though inconsistently, which is its own lesson in designing for data collection.

I am drawn to a programme that treats design and data as one discipline rather than two. I want to develop stronger skills in prototyping, data analysis and physical computing, and to learn how to make data-driven systems legible to people who did not ask to be measured by them. I would like to work on public services, libraries, councils and transport, where users rarely choose the system and cannot easily opt out.

I bring careful qualitative research experience, patience with people who are confused or frustrated, and enough technical grounding to learn quickly. Two years at a front desk have taught me to notice small failures that designers often never see, and I want to learn to fix them properly.