Case Study 02 · Research · Product Design · Design Systems
A research-led redesign of a school transport management platform. The insight that unlocked everything: stop designing for the "typical user" and start designing for the feeling that arrives before the app even opens.
-30%
Design Iteration Time
3
User Personas Developed
8
Accessibility Findings
600+
Students Served
The Problem
The GIIS Smart Campus transport app managed school bus logistics for over 600 students. But the experience was built from the inside out — designed for admin efficiency, not for the parent standing at the kitchen counter at 7:45am, watching the minutes tick by, wondering if their child made it onto the bus.
Every notification that didn't arrive, every delay that wasn't communicated, every support pathway that led to a dead end — each one eroded exactly the kind of trust a premium school transport service should be building.
"I just want to stop worrying. Give me proof she's safe and I'll love this service forever."
That's Priya Menon — our primary persona. She wasn't asking for features. She was asking for relief from anxiety. That distinction changed everything about how we designed.
User Research
We started with the User-Centered Design Canvas and field research to build personas that weren't just demographic profiles — they were portraits of emotional reality. What does Priya feel at 7:30am? What does Arjun need to not feel embarrassed in front of his peers? What does Sarah need to do her job without drowning?
Priya Menon
Finance professional · Parent of Grade 5 student
Goals
Fears
A11y Dimension
"I just want to stop worrying. Give me proof she's safe."
Arjun Teo
14 years old · GIIS Secondary 2 student
Goals
Fears
A11y Dimension
"Just let me tap and go. I don't want to think about it."
Sarah Lim
Transport Coordinator · GIIS Admin
Goals
Fears
A11y Dimension
"I need a system that makes me look good — not one that makes every problem my problem."
Design Insights
Requirements documents describe functionality. Research reveals the human truth underneath. These four insights shaped every design decision that followed.
The 2-Minute Trust Window
Any boarding notification delayed more than 2 minutes sent Priya into panic mode. Not frustration — panic. This isn't a performance requirement. It's an emotional design requirement.
Arjun's Peer Visibility Test
If tapping a Smart ID scanner took more than 1 second to confirm, Arjun would assume it was broken — regardless of the actual system state. He'd tap again. And again. Failure had social consequences.
Silence = Failure for Parents
When nothing happened, parents assumed something had gone wrong. The app needed to communicate normalcy — not just exceptions. "All is well" needed to be as deliberate a message as "there's a delay."
Sarah Needs to Look Good
Every complaint that reached Sarah was a failure of the system to communicate earlier. Her real user need wasn't data — it was ammunition. Tools that helped her explain and resolve situations before they escalated.
Experience Mapping
We mapped Priya's daily journey in full — not as a user flow, but as a lived experience. The moments where the design could earn her trust were specific, time-sensitive, and emotionally loaded.
| Stage | Priya's Thought | Emotional State | Design Opportunity |
|---|---|---|---|
Awareness School open day |
"This could stop me worrying every morning. Is it actually good?" | ✦ Hopeful, evaluating | First impression must communicate reliability and calm — not features. |
Onboarding Downloads app, registers Ananya |
"How many steps is this? I don't have time for a tutorial." | ◈ Impatient | Progressive Disclosure Surface only what's needed at each step |
Daily Use 7:30am check |
"Did she board? Why is there nothing? Has the bus left without her?" | ▼ Anxious — Peak | Proactive confirmation before she asks. "Ananya boarded at 7:34am ✓" |
Disruption Bus 20 mins late, no notification |
"No message. I'm calling the school. This is not okay." | ▼▼ Betrayed, trust broken | Critical Proactive delay alerts with ETA. Silence must never be an option. |
Recovery Issue eventually resolved |
"It worked out but I had to chase. I won't recommend this service." | ◈ Relief, but damaged trust | Recovery design: acknowledge, explain, reassure — in that order. |
Accessibility Audit
We audited against WCAG 2.1 AA across all three persona contexts. Sarah's desktop keyboard navigation. Priya's one-handed commute use. Arjun's demand for sub-second response confirmation.
No boarding confirmation notification — silent default
The system recorded boarding but sent no notification unless a delay was detected. For Priya, this meant the absence of a message created the same anxiety as an actual problem. Silence was indistinguishable from failure.
→ Fix: Default-on boarding confirmation push notification within 60 seconds of scan. ARIA live region for in-app view.
Smart ID confirmation latency not communicated
When Arjun tapped his Smart ID, feedback took 1.5-3 seconds. No loading indicator, no interim state. He tapped multiple times, creating duplicate boarding records and confusing the admin dashboard.
→ Fix: Haptic + visual confirmation within 200ms of tap (optimistic UI). Full confirmation within 1 second.
Admin error states say "Something went wrong" — nothing more
When Sarah encountered a system error, the message gave her no information about cause, status, or resolution path. She couldn't explain the situation to parents calling in — which eroded her authority and trust.
→ Fix: Specific error messages with timestamp, affected route/students, and next action. keyboard navigable with focus management.
Live map tracker inaccessible to keyboard-only users
The fleet map used canvas rendering with no accessible text alternative. Sarah — who preferred keyboard navigation on desktop — had no way to get location data without using the mouse.
→ Fix: Accessible text view of all live fleet locations. Keyboard shortcut to switch to text mode.
Delay notifications lack emotional tone
Delay alerts read like system logs: "Route 3B: ETA +18min." For an anxious parent, this text is cold and clinical. It communicates information but not care — and care is part of what a premium service sells.
→ Fix: Rewrite microcopy with empathy. "Ananya's bus is running 18 mins late today — we'll update you as soon as she boards."
My Process
UCDC Analysis + User Research
Ran a full User-Centered Design Canvas analysis. Conducted interviews across parent, student, and admin segments. Identified the emotional truth that would drive all design decisions.
Persona Development (3 Full Personas)
Built Priya, Arjun, and Sarah as complete portraits — including accessibility dimensions, emotional states, and fears. Not demographics. Not user types. Real people with real Tuesday mornings.
Journey Mapping + Emotional Arc Analysis
Mapped Priya's daily journey in full. Identified the exact moments of trust-building and trust-breaking. Used this as the brief for all design decisions.
Accessibility Audit + Prioritised Findings
WCAG 2.1 AA audit across all three contexts. Findings prioritised by human impact — not just technical severity. Safety and trust issues shipped first.
Design System Development
Built a comprehensive design system with components, tokens, and usage guidelines. Consistent across all product features. This is what cut design iteration by 30% — shared language between design and engineering.
Rapid Prototyping + Stakeholder Validation
Iterative wireframes in Figma. Validated against each persona's scenario — not abstract usability. "Would Priya feel calm after seeing this notification?" Not "does this follow the pattern?"
Outcomes
-30%
Faster Design Iteration
The comprehensive design system gave the team a shared language. Decisions that previously required lengthy back-and-forth were resolved by pointing to the system.
8
Accessibility Findings Resolved
All critical and important findings shipped. The notification system was redesigned from the ground up to eliminate the silent default that was breaking Priya's trust every morning.
3
User Groups Now Served
The platform previously optimised for admin efficiency. Post-redesign, it genuinely served Priya's anxiety, Arjun's need for speed, and Sarah's need for control.
600+
Students Protected
Behind every data point is a student whose parent can now trust the system. That's the outcome that matters most.
Reflection
The most important thing I learned on this project was the power of designing for anxiety as a first-class design requirement — not a nice-to-have. When you start with "what does this person feel at 7:30am?" rather than "what features do we need?", you end up with entirely different design decisions.
The notification system wasn't a feature request. It was an emotional design requirement. The design system wasn't a tooling exercise. It was the infrastructure that allowed the team to move fast enough to keep up with the real needs we'd discovered.
If I'd do anything differently: I'd push harder for longitudinal research — specifically around the recovery experience after a disruption. That's where trust is either rebuilt or permanently lost, and we still had more to learn there.