C:\ARCHIVE\B_003_BERTH\case_study.txt

B 003Research synthesis · Mobile

Berth

The one answer you need right now: where to stand, and when to wake.

Berth is a companion for long-distance train travellers in India who get on or off at a busy intermediate station, often at night, with luggage, a child or older family.

Berth station screen: platform 3 in signage-size type, changed from 2, with the source and age of the number, and where to stand: 9th coach from the engine.
Role
Solo: study plan, analysis, product design
Methods
Survey · interviews · station observation · diary · stress lines
Platform
Android: app, lock screen, widgets
Timeline
2026

Simulated study data: I framed the problem, planned the study and did the analysis; the responses were simulated with AI from that plan.

01TL;DR

Briefed as an on-board companion. The pain was at both ends of the trip.

The problem

On the platform, travellers don’t know where their coach stops. On the approach to a pre-dawn stop, alarms follow the timetable while the train doesn’t.

What I did

Planned a mixed-methods study: a survey (n = 116), 8 interviews with stress lines, 2 hours of station observation and a 5-person diary. Then coded and analysed every file.

What I designed

One answer in signage-size type, with its source and age, on the lock screen, a widget and a position-based alarm.

Tell me where to stand. Honestly that’s it.
P3, interview

02How I ran it

Five methods, each checking the others.

Method map: 116 survey answers, 8 interviews of 38 to 45 minutes with stress lines, 2 hours at Gwalior Junction and 5 travel diaries feed into a synthesis of 4 insights and 3 principles.
About the data

I framed the problem and wrote the plan: the survey, the interview guide, the stress-line exercise, the station protocol and the diary prompts. The responses were simulated with AI from that plan. I then cleaned, coded and analysed them, and every count on this page traces to that dataset.

03Survey · n = 116

70 of 116 check the train’s status six or more times a trip.

70 of 116 check status 6+ times per trip, across 3.3 sources each.
51 of 116 have missed, or nearly missed, their stop or train.
95 of 116 say battery worry changes how they use their phone.

Most stressful part of the trip. On board, the phase Berth was briefed for, came last.

04Stress lines

None of the 8 stress lines peaks on board.

Eight stress lines over six trip phases with the average: 2.88 before leaving, 3.63 at the station, 3.75 boarding, 2.50 on board, 3.50 approaching, 2.75 arrival. Peaks: before leaving P6; station P2 and P3; boarding P4 and P8; on board none; approaching P1, P5 and P7.

4 of 8 peak at the station or boarding, 3 on the approach, none on board. Both people with a pre-dawn intermediate stop rate the approach a 5. Those whose stop comes in daylight, or is the last one, rate it a 2.

Journey map across six phases with what travellers want, what they do today, average stress and the evidence behind each.
Journey map

05Station observation

The display shows one place. The coach stops at another.

85 people asked someone where a coach stops, in 2 hours.
3 of 4 trains watched closely stopped 1 to 1.5 coaches off their marker.
220 phone uses with the other hand full: a bag, a trolley, a child.
Three coach-position displays: PF 1 working, PF 2 showing another train for about 25 minutes, PF 3 blank until about 15 minutes before arrival.
Three coach displays, one evening PF 1 worked. PF 2 showed another train for about 25 minutes. PF 3 stayed blank until 15 minutes before arrival.

06What turned out wrong

Not missing information. Conflicting, stale information.

Berth was briefed as an offline-first companion for the long on-board stretch. The research says on board is the calmest phase: average stress 2.50, the lowest, and only 11 of 116 chose it.

The pain sits at the two ends: the platform and the approach to the stop. And the data already exists. It just disagrees across board, app and people, and nothing says which one is current.

What changed

From “a trip tracker” to “the one thing you need right now”.

Offline still matters, but at night on the approach, not mid-journey.

07Insights

Four insights, each from two or more sources.

Diagram: the display says stand here, but B2 stopped 1 to 1.5 coaches further along. Seen on 3 of 4 trains watched closely.
1 · The display says one place; the coach stops at another People fall back on vendors and coolies.
Three phones after a platform change showing PF 2, PF 3 and PF dash, each with no source and no time.
2 · Three sources, no single truth People trust a number only when two sources agree, and nothing shows how old it is.
P1’s last trip home: alarms at 2:55, 4:35 and 4:50 set by the timetable, awake and checking every 15 to 20 minutes, and the train arrived at 6:05.
3 · Alarms follow the timetable; trains don’t Intermediate-stop travellers stay awake instead.
What the app said through P5’s night: 30 minutes late, then 1 hour, then 2 hours, and it reached 4 hours late.
4 · An honest early estimate beats a precise late one Because someone else acts on it.

08Design principles

Three rules, then one answer per moment.

Insight 2

Every number shows its source and its age.

“PF 3 · board and NTES agree · 2 min ago”

Insights 3 and 4

Run on the train’s real position, and say it early.

Alarms, ETAs and lead times follow where the train is, shown as an honest range.

Observation

Readable at arm’s length, with one hand, in plain words.

Signage-size numbers, no codes without meaning, Hindi station names.

Grey wireframe of a dashboard with tiles for platform, coach, delay, arrival, PNR and a map.
A · Dashboard Everything at once. Rejected: nothing reads at arm’s length.
Grey wireframe with one answer: a huge platform number and a coach-position strip.
B · One answer (chosen) One number per moment, big enough to read on a crowded platform.

09Final design

The same answer on every surface you can reach with one hand.

Add a journey screen with a PNR field, the journey Gwalior to Prayagraj, coach B2 seat 33 lower, and a Set alarm button.
Add a journey Paste a PNR or a ticket SMS; saved for offline.
Station screen: platform 3, changed from 2, announcement and NTES agree, and where to stand: 9th coach from the engine.
At the station The platform, its source and age, and where to stand.
On-board screen, offline and showing an estimate: you reach Prayagraj between 5:55 and 6:15, about 55 minutes late, last live update 12 minutes ago, with the train’s position between stations and Wake-up on.
On board, offline An honest range, not a fake-precise time, with how old the last update is.
Wake-up alarm: wake me 40 minutes before Prayagraj Jn. Rings by where the train is, not by the timetable. Fallbacks for no GPS, phone on silent and battery below 15%. Set alarm, rings around 5:25.
Wake-up by position Rings by where the train is, not the timetable, with fallbacks if things go wrong.
Wake-up alarm ringing: Prayagraj in 40 minutes, slide to stop.
Ringing Slide to dismiss; the stop and time left in huge type.
Low-power mode at 8% battery on black: next stop Fatehpur in about 50 minutes, your stop Prayagraj around 6:05, about 55 minutes late, coach B2 21 lower, alarm still on 40 minutes before.
Low battery At 8%, it keeps only the next stop, your stop, your coach and the alarm.
Lock screen with a live update: platform 3, changed from 2, B2 is the 9th coach from the engine, arrives 20:45, 25 minutes late.
Lock screen No unlocking with one hand full.
Home-screen widgets showing platform 3 with the coach, and 40 minutes to Prayagraj.
Widgets The answer sits on the home screen.
Flow from adding a journey to the Now view, which feeds the lock-screen live update, home-screen widget, wake-up alarm and low-power mode.
One flow, four surfaces
Before: the first version of the station screen. After: the research-driven version with four numbered changes: a change is a state, every number names its source and age, lead time not just lateness, and where to stand with an honest warning.
Before and after the research

10What I learned

Map stress first. Design for trust. Know where simulation stops.

01

Map stress before features.

The brief pointed at the calmest part of the trip. Stress lines and the phase question moved the whole product to the two ends.

02

Design for trust, not just data.

The information existed. What was missing was a reason to believe one number over another: its source and its age.

03

Simulation has a ceiling.

Simulated responses let me practise the whole pipeline, from plan to coding to design. They can’t surprise me the way real travellers would.

Next folder / T 004

ThriftUp →

Making second-hand fashion feel first-rate, with a buy-back program called ModaCash.