Information systems personal statement example

Why do you want to study this course or subject?

I became interested in information systems because of a queue. At the supermarket where I work on Saturdays, the self-service area has six tills, a card-only lane and one member of staff overseeing all of it. On paper the system should be fast, but the delays almost never come from the machines: they come from age-restricted items, weighing errors, and customers who cannot tell which lane accepts cash. Watching that, I started to see technology as only one part of a much larger arrangement of people, rules and habits. The interesting questions were not about the hardware at all. Why were the instructions on the screen written in that order? Who decided that a single assistant could supervise seven points of failure? What information did the shift manager actually see at the end of the day, and what did they never see?

That way of thinking is what draws me to information systems rather than to pure computer science. I enjoy programming and want to get much better at it, but I am more curious about how organisations decide what to record, who is allowed to see it, and what happens when the official process and the real process drift apart. My Business A-level has given me some vocabulary for this, particularly around stock control and management information, while Computer Science has shown me how databases and networks work underneath. What I do not yet have is any rigorous method for analysing a whole organisation, modelling its processes, or judging whether a proposed system will actually be used by the people it is meant to help. I want a degree that treats requirements, data quality, security and human behaviour as serious technical problems, and that expects me to justify design decisions to non-specialists as well as to programmers. Working in teams on real client briefs appeals to me strongly, because I already know from small projects that the hardest part is usually agreeing what the problem is.

How have your qualifications and studies helped you to prepare?

My A-levels in Business, Mathematics and Computer Science fit together more closely than I expected. In Business I studied operations management and found that the topics I returned to were about information: how a firm knows its stock levels, how forecasting errors travel through a supply chain, and why managers sometimes make worse decisions when given more data. In Mathematics, the statistics content has been the most useful for this. Learning to think about sampling, variation and correlation has made me cautious about dashboards that present a single number as the truth, and my work on probability has helped me understand why systems need to be designed around uncertainty rather than pretending it away.

Computer Science has provided the technical foundation. I have worked in Python, written SQL queries against small relational databases, and learned to normalise tables properly after producing a first attempt full of repeated data. My non-exam assessment is a booking and attendance tracker for a sixth form study room, which forced me to think about edge cases I had not considered, such as what happens when two students book overlapping slots or when someone books and never arrives. Documenting my test plan taught me that writing down expected behaviour in advance is harder, and more valuable, than writing the code.

Outside the syllabus I have read Robert Lucky's ideas on communication and information second-hand and found more use in shorter material: free introductory guides to entity relationship modelling, and articles on data protection principles, which made me rethink how long the food pantry log should keep names. I also follow reports of public sector IT projects going wrong, and it is striking how often the failure is described as technical when the accounts suggest unclear requirements and users who were never consulted.

What else have you done to prepare outside of education, and why are these experiences useful?

The project I have learned most from is small. The community centre near me runs a food pantry, and records of donations and collections were kept on loose paper sheets that volunteers filled in differently each week. I offered to help and spent three sessions simply watching and asking questions before touching a computer, because I wanted to know how volunteers actually worked rather than how I imagined they did. I then built a spreadsheet with structured data entry, drop-down lists for item categories, and a summary sheet showing weekly totals and low-stock items. Almost everything I changed after the first version came from feedback: the volunteers needed larger text, fewer columns visible at once, and a printable sheet for days when the laptop was in use elsewhere. I wrote a one-page guide and trained two other volunteers so the system did not depend on me. It is not sophisticated software, but it taught me about requirements gathering, usability and the value of a system someone can still run when the designer is absent.

My supermarket job has been an education in process. I have covered checkouts, self-service and stock replenishment, and I have seen how staff invent workarounds when the official procedure is slow, and how those workarounds then make the recorded data less accurate. Dealing with frustrated customers has improved my patience and my ability to explain something clearly under pressure.

I am also fixtures secretary for my sister's under-13s football team, which means keeping track of availability, pitch bookings and cancellations for around eighteen families. I moved the arrangements from a chaotic group chat to a shared calendar and a simple availability form, and reducing the number of weekly messages was surprisingly satisfying. Alongside this I help at home with my younger brothers' routines, so I have had to become organised about my own study time. Together these commitments have given me the habits I think a demanding degree will need: planning ahead, asking questions before assuming, and finishing what I start.

This example has 5,882 characters across the three answers. Use it for ideas and structure. Your own UCAS answers must fit within 4,000 characters in total, including spaces.