Musa Drivers

SUMMARY

From route tool to Driver OS. We rebuilt Musa’s driver app around a new My Account that turns operational data into actionable insight drivers actually use off-route: earnings they can plan with, a transparent reliability score they can improve, and ownership essentials (docs, support, micro-learning) that cut surprises. In a transparency-first business, off-route engagement is the lever that stabilizes supply and cleans the data you bill on.

Musa exists to collect, track, and turn waste into raw material, a business built on operational transparency. The driver app did that job during routes, so the moment engines stopped, engagement flatlined. Autonomous drivers treated it like a turn-by-turn tool, not a place to manage their work. That off-route silence was the risk: lower stickiness, fragile supply predictability, and zero surface area to return value to the people doing the heavy lifting.

 

I reframed the brief with our PM and ops leads: if we want drivers back outside the route, the app must stop behaving like a checklist and start acting like a Driver OS, a home for their own data, progress, and opportunity.

Listening before designing

Instead of “make logging easier,” the bet became “make insight obvious.” I helped to set a North Star that would force us to prove continuous value, off-route sessions per driver/week, and designed a new My Account as the anchor. Not a profile page: a living summary of Earnings, Performance, and Ownership with Data Insights the driver actually uses to plan, improve, and feel in control.

 

To ground decisions, I co-ran field shadowing in São Paulo, mapped the information architecture of My Account, and the PM defined the first set of insights and the telemetry behind them (what we show, how we calculate, and what action we recommend next).

What We Built

We started by turning “data exhaust” into signals the driver actually cares about. Field-level completeness became a plain-English Data Quality Score that highlights the two fields hurting accuracy that week and offers a single tap to fix the workflow that caused them.

Efficiency moved from folklore to fact with stops per hour and batching detection that expose where minutes leak by day and time, plus an offline-first path to log on the spot without breaking pace. Materials stopped being an afterthought: mix and impact reveal composition by area and convert it into tons diverted from landfill, with a one-tap monthly PDF drivers and co-ops can share. Connectivity, often blamed but rarely measured, turned into sync health, showing offline windows and time-to-server, and offering route packs for weak-signal zones.

Across the experience, microcopy follows a strict rhythm, cause, effect, next step, and the UI stays time-respectful: snapshots, small multiples, sparklines; the answer in three seconds or less.

Results (Test group vs. control over 30 days)

  • +18% avg. session time (3m20s → 3m55s)
  • 26% support tickets on routes and collections
  • +14% drivers active 5+ days/week
  • 7 organic positive mentions in WhatsApp groups

Business Impact

The redesign improved data accuracy, reduced support dependency, and increased driver connection to the platform — making it easier to scale with independent drivers while protecting the subscription revenue model.