The three core screens. Status by colour, consistently, vermillion for active, amber for delayed, forest for on-schedule. System-written text and human-written text are typographically distinct throughout, so the voice is never ambiguous.
Civic disruption is tolerable. Civic surprise is not.
I noticed something simple, repeatedly: civic work in Bangalore, pipe repairs, road digging, power changes, happens to people, not with them. I couldn't talk to thousands of residents or sit inside city departments, so I used HMHT, my framework for designing when real human access isn't possible, end to end.
Roads close overnight without warning. Pipes get dug up at 7 AM on a workday. A repair that should take three days runs into its third week with no explanation. Residents, including me, find out by encountering the work, not before it.
The information isn't missing, it sits in tender documents, press releases, websites nobody visits. It just doesn't reach the people whose lives it disrupts, in a form they can use, when it would help. That gap is a slow, daily erosion of trust, and it hardens into a working theory: nobody is in charge, or nobody cares.
“Frustrated, then resigned. The frustration is short-lived. The resignation accumulates, until resignation is the default civic emotion.” A composite voice, synthesised from HMHT simulation, not a real quote.
Source: lived experience as a Bangalore resident, informal observation across HSR Layout, Indiranagar, and Jayanagar, and publicly visible civic activity through 2025–2026, cross-checked against TRAI, NPCI, and BBMP/BMRCL public reporting.
HMHT ran in full, five phases, Human Simulation, Behavioural Mapping, Information Architecture, Interaction Direction, and UI Generation, each producing an artifact that fed the next. Phase one alone produced four personas, a commuter, a shopkeeper, a civic-minded resident, and the field officer whose two-tap update has to work in direct sun, each clearly marked HMHT-simulated, not real research.
The three core screens. Status by colour, consistently, vermillion for active, amber for delayed, forest for on-schedule. System-written text and human-written text are typographically distinct throughout, so the voice is never ambiguous.
I thought I was designing a better notification system. Midway through simulating a resident in her late fifties, the simulation surfaced a moment I hadn't anticipated: she missed her granddaughter's school event because an auto-rickshaw couldn't get through, and no one had told her that morning. That's not a problem a notification system solves. It's solved by treating someone's time and dignity as worth the effort of being told.
What's here is the case, end to end. A more detailed walkthrough, personas, journey maps, service blueprint, stakeholder map, is available in conversation.
Request a walkthrough