CareCar Web App
Design a Ride Share Agent portal for transport of medical patients
CareCar As a benefit of insurance, CareCar is a growing market network platform and ancillary health services company, working primarily in non-emergency medical transportation. Founded in September 2017, the company operates in of California and North Carolina. When I was brought on, the platform was designed by engineers. The agents had numerous browsers open (Uber, Lyft, CareCar, Patient info/Driver info) and the goal was to aggregate all the browsers into one platform where all of the above was available on one dashboard.
DELIVERABLES: Product Design, Marketing Website: Audit, UX Strategy, Visual Design, UX Flows, Sitemaps, User Flows, Annotated Wireframes, Wireframe to Product, Responsive, Hi Fidelity Prototyping, B2C Marketing, eCommerce, Social Media Final Visual Comps.
AUDIT: These are the screens that the agents were using. There were 5 screens they had to manage all at once. It was too much to manage as all of them were live feeds. I proposed we aggregate them into one screen with the most pressing encounters (rides) on top. The stakeholders (CEO/PM, Dev team) and I brainstormed on the top use cases to prioritize what was the most prominent on the page.
SITEMAP: The most pressing use case was for the agent / dispatch as they organized the rides, dealt with no shows, cancelled trips, etc. With the PM, we mapped out all the paths and use cases
WIREFRAMES: Placed all the features from the sitemap into one screen. The main idea was that the users would never have to leave this screen. If any tasked needed to be done, ie new encounter called in or the agent needed information on where a car was or needed more details on a member or trip, a “detail panel” would slide in and depending on the nav, would should them the info or provide input screens.
UI/VISUAL DESIGN-TABLE: This is how all the members would be displayed on one of two views: This view is on hover. Status was the only color coded element so the agent could recognize it quickly vs read it.
UI/VISUAL DESIGN-TABLE: View is “On click” of the member and then their info in a synopsis would appear, along with a map if their ride is in progress.
UI/VISUAL DESIGN-CARDS: If space isn’t as important and the agent wants to see details of the trip with more visual cues, they would switch to a card/gallery view
UI/VISUAL DESIGN-CARDS: If a new encounter call comes while the agent is managing the trips, this is their view. Its a step by step prompt. Here they just inputed the destination details.
MEMBER VIEW MOBILE APP / USER FLOW: The average age of the member is a senior and they are using Android. This was apart of the investor presentation and wasn’t meant for future builds.
DESIGN SYSTEM COMPONENT LIBRARY: I built and maintained this modular and scalable library.
FEATURES: Features called out for training screen for the agents.
PROVIDER MOBILE APP / SITE MAP: Providers are drivers. For an investors meeting, I designed the driver flow and user flow. What that might look like for a future build.