Theory
The whole subject, in one story
You have learned the pieces: research, personas, interaction design, visual design, testing, accessibility. A case study is where the pieces become one JOURNEY: a real design problem solved from start to finish.
Let us walk the complete redesign of FestConnect: the very app whose confusing registration opened this subject: applying every unit in order. By the end you will see how the concepts connect into one coherent process, and: just as examinably: how to PRESENT a design case study: problem, process, outcome, with the reasoning that ties them.
Theory
The problem, and the research
Problem: FestConnect worked technically, but few students completed registration. The committee blamed the students; the truth was the DESIGN (Unit 1: UI works, UX fails).
Research (Unit 2): interviews with real first-years, watching them try to register. Findings: they were not tech-confident CS students but nervous newcomers on cheap phones (the say-do gap: everyone SAID it was fine, but half gave up at the date field). This produced 2 personas: Rahul, the anxious first-year who needs simplicity, and Priya, the organiser who needs a powerful overview. The date field and unclear navigation were the top pain points.
Theory
The design and the visuals
Structure (Unit 3): card sorting revealed students expected 'Register' front and centre, not buried under 'Events', so the information architecture was reorganised. The user flow was shortened, the confusing typed date replaced with a simple picker (removing the pain point at its source), clear feedback added after every action, and navigation given always-visible tabs answering where-am-I and how-back. All tested first as cheap grey WIREFRAMES.
Visuals (Unit 4): a warm terracotta-and-cream brand identity that FEELS like a fest; readable typography; visual hierarchy making the Register button the dominant element; consistent components on every screen so students learn the interface once.
Theory
Validation, and the outcome
Validation (Unit 5): usability testing with 5 first-years on the prototype. Four of five now registered smoothly; a new minor label confusion surfaced and was fixed in the next ITERATION (design is a loop, not a line). Then ACCESSIBILITY: contrast raised so low-vision students can read, errors shown with icon-plus-text not colour alone, the form made keyboard-navigable, alt text on images: so EVERYONE can register.
Outcome: FestConnect went from a frustrating form that lost students to a smooth, inclusive product that more students complete: not by adding features, but by understanding users and designing for them. That is the entire subject, proven on one app.
Quiz
In the FestConnect case study, the registration problem was ultimately solved by which approach?
- Adding more colourful decorations to the existing screens
- Understanding real users through research, then redesigning structure, visuals and accessibility, and validating with testing and iteration
- Blaming students for not trying hard enough
- Rewriting the backend code to be faster
- Removing the registration feature entirely
Show the answer
Understanding real users through research, then redesigning structure, visuals and accessibility, and validating with testing and iteration
The fix was the full user-centered design PROCESS: research to understand real users (nervous first-years, the date-field pain), redesign of structure/flow/visuals/accessibility around them, and validation through testing and iteration: exactly the journey the subject teaches. Option A is surface decoration, which never addressed the real (structural and research-based) problems. Option C is the committee's original mistake the case study refutes (blame the design, not the user). Option D targets performance, which was not the issue (it worked technically). Option E abandons the goal. The lesson: real UX improvement comes from understanding and designing for users, validated by evidence, not from cosmetics or blame.
Think first
Present a case study like a designer
An interviewer asks you to 'walk me through a project'. Using FestConnect, what structure should your answer follow, and why does that structure matter? Then tap.
Show the answer
Structure it as Problem → Process → Outcome, with your REASONING at each step. Problem: what was wrong and how you knew (FestConnect lost registrations; research showed the date field and IA were the culprits). Process: what you DID and, crucially, WHY (reorganised IA because card sorting showed users' mental model; added a date picker to remove the pain at its source; tested with 5 users; iterated; made it accessible). Outcome: the result and what you learned (smoother, inclusive registration; more completions). This structure matters because it shows you think like a designer: evidence-driven, user-centered, reflective: not just 'I made it pretty'. The REASONING is what impresses; anyone can list what they did.
Watch out
Case-study slips
Listing actions without reasoning: 'I changed the layout' is weak; say WHY (research showed X), which is what a case study is FOR.
Skipping research/validation: a case study that jumps straight to visuals misses the user-centered core.
Taking credit for luck: attribute improvements to evidence and process, not vibes.
Inventing metrics: in a real portfolio, use honest data; do not fabricate percentages: state outcomes truthfully and directionally.
Theory
Subject complete: you can design for people
From 'UI is not UX' to a fully redesigned, tested, accessible FestConnect, you have run the entire user-centered design process. You can now research users, model them as personas, design structure and visuals with intent, test and iterate on evidence, and include everyone through accessibility. That process: understand people, design for them, validate, repeat: is UX design, and it applies to every product you will ever build, including the very platform you are learning on. Design for the human; the rest follows.
Summary
Key takeaways
- A case study walks a real design problem from start to finish, tying every concept into one journey.
- FestConnect journey: problem (lost registrations) -> research (personas, interviews, the date-field pain).
- Design: reorganised information architecture, shorter flow, date picker, feedback, clear navigation, tested as wireframes.
- Visuals: terracotta-and-cream brand, readable type, visual hierarchy on Register, consistency.
- Validation: usability testing with 5 users, iteration on findings, accessibility (contrast, alt text, keyboard, not colour-only).
- Present a case study as Problem -> Process -> Outcome, with the REASONING behind each decision.
- Memory hook: understand people, design for them, validate, repeat: that is UX.