Divami design assignment · Problem statement 1 · Workflow 1

Forty bikes go dark.
Jacob doesn't have to watch.

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.

Run the storm The rule Jacob should never have to watch a screen to know something needs his attention. 🔊 Turn your sound on. The prototype rings, buzzes and speaks.

A narrated walkthrough, about 3 minutes · turn your sound on · ← → to skip scenes

What makes this hard

The problem isn't too many bikes going dark.
It's that silence looks the same every time.

3,000

alerts a day in Hyderabad. Fewer than 1 in 10 needs a human. GPS jumps under flyovers look exactly like a real problem.

40

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.

3 vans

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

An attention ladder.

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.

1

Silent

Handled by the system. Bikes that reconnect safely close themselves. A Live Activity counter shows progress without a sound.

2

Digest

Good to know. A gentle tap and an end-of-incident summary.

3

Wrist tap and push

A decision is needed soon. The watch taps, and the push has its answer buttons built in. If nobody answers, a safe default happens.

4

Ring and voice

Act now. The phone rings and a voice explains. Jacob approves by saying "approve". Goes to the backup person after 3 minutes.

Key decisions

What I chose, and what I said no to.

01

One incident, not forty alerts

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.

02

Tell Jacob through ears and wrist, not eyes

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.

03

The system plans, Jacob approves, crews execute

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.

04

Every question has a safe default

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.

05

Say "I'm not sure" out loud

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

How this answers each thing you're judging.

Critical thinking and problem-solving

The hard part is that silence is ambiguous.

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

Design thinking and innovation

Jacob decides. He never monitors.

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

Assignment quality

Start to end, and it adds up.

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

Communication and experience

Every scene explains its own decision.

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

The whole workflow on one page

From 40 silent bikes to 40 accounted for.

1

Detect

40 bikes go silent in one rain cell. The system opens one incident, not 40 alerts.

2

Sort

Last readings sort bikes into at risk, not sure and probably fine.

If a rider is still riding: warn them and guide them to a safe spot.
3

Tell Jacob

Watch tap, phone call, spoken plan. He says approve or change.

If no answer in 10 min: the safe plan starts by itself. He can still change or stop it.
4

Dispatch

Jobs go to Van A and Van B with safe routes. Van C stays free.

If a phone is missed for 2 min: the van alerts with light and voice. Still nothing: the job moves to Van C.
5

Recover

One tap per bike, works offline. Bikes that reconnect safely close themselves.

If water is too deep: skip and re-queue.
If the bike is not there: widen the search.
6

Handle surprises

The system acts where it is safe and asks Jacob only for judgement.

If it isn't sure: one question with odds, safe default after 2 min.
If a bike moves with no ride: cut the motor, critical alert, send Van C.
7

Tell riders

Riders of flooded bikes are told they won't be fined. Riders nearby are told bikes are paused.

Zones are Workflow 2 and fine disputes are Workflow 3. Not designed here.
8

Close

All 40 recovered or confirmed safe. Repairs go to the 6 am shift.

Confirmed safe: online, locked and still for 10 min, or seen by a crew.
If a bike is never found: the incident stays open and Jacob decides.

Built as a web prototype: MapLibre and OpenStreetMap for the map, OSRM for real road routes, browser audio and speech for sound and voice, hosted on Cloudflare Pages. Bike positions, names and odds are illustrative. Flood, traffic and the in-van alert unit are assumptions. Out of scope and only labelled: dashboards, navigation, settings, onboarding, the other two workflows, sign-up, booking, payments, pricing, bike hardware, police reporting and repairs.