Flight rulesHow I decide

How I decide

Seven calls, each with the fact it came from. What I did when the answer was not in the spec.

  1. Rule 01MapMyIndia · fleet & telematics platforms

    Define the states before the screens.

    A vehicle is moving, stopped, idle, delayed or offline. Until those five words meant one thing each, no dashboard could be right.

    Evidence Defined vehicle status logic (moving / stopped / idle / delayed / offline); alarm, geofence and ticketing workflows.

  2. Rule 02MapMyIndia · every active mission

    Write it down early enough to be wrong cheaply.

    The PRD is the argument. Problem statement, user stories, acceptance criteria, edge cases, all before a screen exists.

    Evidence Authored full PRDs: problem statements, user stories, acceptance criteria, edge cases.

  3. Rule 03MapMyIndia · Mappls Shop Admin

    Replace the manual process; don't decorate it.

    Billing was done by hand. The work was not the arithmetic. It was finding every place a person was quietly deciding.

    Evidence Mappls Shop Admin + automatic billing replaced a fully manual billing process. Owns UI/UX, the PRD, cross-functional delivery. Live, earning, and the billing and accounts teams are 80% more productive.

  4. Rule 04MapMyIndia · Technician App

    Three jobs are not one screen.

    Installation, replacement and rectification wear the same uniform and are different work. The app is built around the job, not the technician.

    Evidence Technician App: end-to-end tracking of technicians and field operations: installation, replacement, and rectification jobs.

  5. Rule 05MapMyIndia · operational & analytics dashboards~40% measured

    Speed is a product decision.

    A data-heavy dashboard that takes too long is a dashboard nobody trusts. Caching, RxJS state and API shape were product work.

    Evidence ~40% performance improvement on data-heavy dashboards via caching, RxJS state management, API optimisation.

  6. Rule 06MapMyIndia · Vahan Shakti, 200,000+ users200,000+ measured

    A map is behaviour, not a layer.

    Rotation, fit-to-route and playback are what make a map answer a question. Markers alone are a picture.

    Evidence Map UX: rotation, fit-to-route, route playback. React map components for live location, custom markers, route plotting, clustering, heatmaps.

  7. Rule 07This siteverifiable in the source

    No number without a source.

    The case studies once carried survey percentages nobody could trace. They were cut. Each note now ends with what would be measured instead.

    Evidence Every result on this site is transcribed from a verified record; active missions read “Not yet measured” until they are.

Next · MissionsWhere the rules were appliedThe missions, with what was decided, built and carried with the team on each.