Divami design assignment · Problem statement 1 · Workflow 1
A live prototype of a mass incident in a Hyderabad rainstorm. The system watches, sorts and plans. Jacob is told through his wrist, his ringtone and a voice, and he decides with one word. His field crews get the job on their phones.
What makes this hard
alerts a day in Hyderabad. Fewer than 1 in 10 needs a human. GPS jumps under flyovers look exactly like a real problem.
bikes go silent in 10 minutes. Some are fine, some are underwater, and one might be getting stolen. Silence alone can't tell you which.
and 5 people on the evening shift. Sending everyone everywhere isn't a plan. The scarce resource is Jacob's attention, not information.
The one idea
Every event gets a level. The louder the channel, the rarer it is. Jacob is only reached when a decision is truly his, through his wrist, his ringtone or a voice, never a screen he has to keep checking.
Handled by the system. Bikes that reconnect safely close themselves. A Live Activity counter shows progress without a sound.
Good to know. A gentle tap and an end-of-incident summary.
A decision is needed soon. The watch taps, and the push has its answer buttons built in. If nobody answers, a safe default happens.
Act now. The phone rings and a voice explains. Jacob approves by saying "approve". Goes to the backup person after 3 minutes.
Key decisions
Bikes that go silent together, in the same rain cell, become one incident with one owner.
Rejected: a smarter alert list with filters. It still makes Jacob read 40 rows.
Watch haptics, ringtones, and a spoken summary he can approve by voice. Each level of urgency has its own sound, so he knows how urgent it is before he looks.
Rejected: a better dashboard or map view. That's still watching a screen.
Jacob's approval becomes a job on each crew's phone with the route already drawn. Nobody drags vans around a map.
Rejected: Jacob phoning each crew to coordinate. It's slow and error-prone in the rain.
If Jacob doesn't answer, the system takes the cautious choice and tells him afterwards. Silence never blocks the work.
Rejected: waiting for confirmation. A blocked plan at 7 pm in a flood is worse than an imperfect one.
Uncertain bikes show the likely causes with honest odds, instead of a confident guess that could be wrong.
Rejected: hiding uncertainty behind one status. False confidence is how 46 bikes sat for 48 hours.
Against the brief
A bike that stops reporting could be fine, flooded or stolen. The workflow is built around telling those apart using only facts from the brief: GPS, lock status, battery, speed, ride status every 10 seconds, remote lock and speed limits, in-ride notifications, and 3 vans with 5 people on the evening shift.
See it in: Storm → Alert → Not sure
There's no dashboard to read better. Alerts become incidents. Incidents reach Jacob through wrist, ring and voice with a plan attached. His yes becomes the crews' jobs. The system acts on its own where it's safe.
See it in: Alert, Dispatch, Theft
It starts when 40 bikes go silent near Hussain Sagar within 10 minutes. It ends when all 40 are recovered or confirmed safe. Every number is consistent: 17 + 14 + 9 = 40, and 19 + 4 + 16 + 1 = 40. It includes an uncertain state (bike 1187) and a failure state (bike 0932).
See it in: All clear, plus every chapter
The caption under the map says what's happening and why it was designed that way. The decisions above list what I rejected. Anyone can replay any chapter without me in the room.
See it in: the caption strip, Key decisions
How it's built
Three live WebGL maps: the operations view, Jacob's in-phone map and the crew's 3D turn-by-turn view. Every bike, van and route is a live GeoJSON layer.
Real vector tiles of Hyderabad, no API key. Hussain Sagar, Necklace Road and Tank Bund are the actual streets.
Van routes are fetched live from the OSRM engine on real road geometry. If it's unreachable, the prototype falls back to direct paths.
Every sound is synthesised in the browser: the ringtone, the critical siren, chimes and wrist-tap buzzes. Each level of the attention ladder sounds different.
The incident call is spoken by the best voice the device has, with live captions, so Jacob can understand it without looking.
Static files on Cloudflare's edge network. No servers and no build step: the whole prototype loads from a single deploy.
Bike positions, IDs, crew names and odds are illustrative and consistent with the brief: 2,000 bikes in Hyderabad, 3 vans, 10 field staff across two shifts, 6 am to 11 pm. Out of scope and only labelled: dashboards, navigation, settings, onboarding, the other two workflows, police reporting and repairs.