Writing
Other Stuff
That's all for now!
Previews
💸
Refunds
I redesigned the refunds flow to allow Ops to refund trips as Beam credits or to riders' original payment method. While an open field would have been acceptable, I felt that more could be done to make it more efficient, eventually ending up with a design that's optimised for the most common Ops use-cases.
🕵️
User Lookup
As the Ops team often switched between multiple platforms to gather supporting info about a Rider in order to decide if they should be refunded, I redesigned the User Lookup to surface their trip and transaction history from Mixpanel and Redash to reduce the number of platforms Ops had to access for their day-to-day operations.
🛴
Vehicle Management
As we were planning to scale the Operations team and expand the capability of the Ops tool, the information architecture was a key consideration in the redesign. I was able to take on a product role helping to prioritise and scope requirements, future-proof pages and features, and organising Ops requests and feedback.
📍
Map Filters and Markers
I approached the redesign by consolidating the key tasks-to-be-done, resulting in the legend-centric approach as it was the Ops priority to keep inoperable vehicles off the road, and keep the operating vehicles well-distributed. I also wanted to avoid overwhelming Ops with overly granular controls, so I had to pinpoint the filters our ops team were actually using to decide the level of control that was necessary to display as we did not track usage previously.