Industry:
Ride Share
Overview:
Dollaride is a ride share company that focuses on Transits deserts and the Dollar Vans that serve those areas. Dollar vans traditionally run on word of mouth route to find passengers who need to be taken to public transit hubs. Dollaride's mission is to evolve this community focused commuting system to a more reliable and structured form of transportation that allows driver to run specific routes where passengers will be waiting.
Role:
User Interviews
Competitor/Comparator Persona Development
Journey Mapping
DesignStudio
Interface design
Wireframes
Testing
Technical Blue Print
Rapid Prototyping
Usability Testing
Process:
Tools:
Sketch
Invision
Adobe CS
Keynote
Zeplin
Team:
UX Lead
UX Research Assist
UI Designer
Scrum Master
Robert - Ux Researcher
Larry - Product Manager
Nicolas -Developer
Chris- Developer
Brief
Heading
Dollaride's visions relied greatly on a efficient way of creating and entering effective routes however there is currently no streamlined route-entry process, so it takes a very long time, is complex and technical. The goal is to create a tool that be used by any Dollaride employee regardless of technical knowledge for efficient and effective route entry
Problem at Hand
Heading
It was believe the above all else the time for route entry was the biggest problem at hand. And the clients number one concern was to drastically reduce the user complexity to allow for the tasks to be completed in a shorter length or time than current process.
Research
My team and I wanted to find all of the hardships in Dollaride's current process for route entry so we would find the underlining issues and solve for them. To do so we conducted interviews with all Dollaride employees.
Our findings were able to confirm the route entry process was long and complicated however also highlighted a underlying concern that was crucial to this tools success
Validation: Every user mentioned the importance of a more efficient way to validate the route is possible and accurate.
Problem Statement
Dollaride has identified several new routes that they wish to digitize into their existing website, but the process is time consuming and requires back and forth input with the developer team.
Jon cares about the project and wants to get drivers onto beneficial routes, making them available to the riders as soon as the research is complete.
How might we assist Jon with streamlining the data entry process, and ensure ongoing confidence in the routes created?
What Jon's Journey Would Be Today?
My team and I were wanted to better understand the current process for route entry and it's pain points. The way we went about exploring this issue was to map out what Jon would need to go through for the start to finish using the original process.'
Notable Pain Points
We calculated at least 10 handoffs for the route from start to finish.
Some handoffs were to developers in Nigeria which came with a time difference and a delay for respond
The current entry was a manual input that could only be done by the developers.
The entry had no visual interface so it would need to be returned to Jon to verify on the live app.
Numerous revisions between Jon and developers often took weeks.
Low-Fidelity Sketch
Mid-Fi Wireframes: Route Entry
User Testing:Route Entry
Mid-Fi Wire Frames: Validation
User Testing : Validation
Blue Printing Possibilities
To ensure execution and that the tool was truly possible Ux and the Dev team teamed up to ensure we had a full understanding of how the tool would not only work but fit within constraints and was a solid MVP that is scalable for the future we envisioned for the product. To assist us with this feat we worked on creating a blueprint.
High- Fi Mockups
After testing mid fidelity wireframes and securing a full understanding of frontend and backend limitations my team and I wanted to make the flow easier to understand and we accomplished this by simplifying the language used in CTA as well as adding simple direction for each task tool.
HiFi Validation Flow
The Validation flow proved to be hard to understand after mid fidelity testing so the mockups show simplification that we accomplished by removing the map and only showing errors one at a time. CTA were made larger and the format was kept as uncluttered as possible.
Next Steps
Further testing with the full Dollaride staff base prior to development (Phase 2)
Provide training so the full process from creation to live testing can be completed by one person
Merge the validation engine into the route drawing tool for seamless live correction and confirmation at
the same time (Phase 3)
Adding data-aggregation features to aid in preferred route creation (Phase 4)
Persona
%20(2).png)
Problem Statement
Dollaride has identified several new routes that they wish to digitise into their existing website, but the process is time consuming and requires back and forth input with the developer team.
Jon cares about the project and wants to get drivers onto beneficial routes, making them available to the riders as soon as the research is complete.
How might we assist Jon with streamlining the data entry process, and ensure ongoing confidence in the routes created?
What Jon's Journey Would Be Today?
My team and I were wanted to better understand the current process for route entry and it's pain points. The way we went about exploring this issue was to map out what Jon would need to go through for the start to finish using the original process.'
Notable Pain Points
Some handoffs were to developers in Nigeria which came with a time difference and a delay for responds.
The current entry was a manual input that could only be done by the developers.
The entry had no visual interface so it would need to be returned to Jon to verify on the live app.
Numerous revisions between Jon and developers often took weeks.
Feature Prioritization
Each feature that the team decided to implement for the MVP route entry tool was directly due to data from users.
Low-Fidelity Sketch
Mid-Fi Wireframes: Route Entry
User Testing:
Route Entry
Mid-Fi Wire Frames: Validation
User Testing:
Validation Flow
Blue Printing Possibilities
To ensure execution and that the tool was truly possible Ux and the Dev team teamed up to ensure we had a full understanding of how the tool would not only work but fit within constraints and was a solid MVP that is scalable for the future we envisioned for the product. To assist us with this feat we worked on creating a blueprint.
High- Fi Mockups
After testing mid fidelity wireframes and securing a full understanding of frontend and backend limitations my team and I wanted to make the flow easier to understand and we accomplished this by simplifying the language used in CTA as well as adding simple direction for each task tool.
HiFi Validation Flow
The Validation flow proved to be hard to understand after mid fidelity testing so the mockups show simplification that we accomplished by removing the map and only showing errors one at a time. CTA were made larger and the format was kept as uncluttered as possible.
Next Steps
Further testing with the full Dollaride staff base prior to development (Phase 2)
Provide training so the full process from creation to live testing can be completed by one person
Merge the validation engine into the route drawing tool for seamless live correction and confirmation at
the same time (Phase 3)
Adding data-aggregation features to aid in preferred route creation (Phase 4)
.png)
.png)
Follow
