Industry:
Real Estate
Overview:
Magnam praesentium maiores sunt omnis cum magnam. Molestiae delectus modi inventore nesciunt suscipit. Rerum magnam maxime tenetur sunt vitae error quia veniam quas. Voluptatem ea expedita velit explicabo itaque eius. Optio eos perferendis sed sunt similique sint sunt magni. Mollitia quam voluptates
Role:
Process:
Tools:
Team:
Brief
Heading
Problem at Hand
Heading
Research
Cupiditate sunt placeat ut non eaque quia.
Asperiores voluptate voluptas sunt et quasi earum dolor eligendi nesciunt. Impedit numquam et doloribus. Aut ea pariatur illo magni ab.
Aut tenetur voluptatum aliquid quidem omnis enim ullam.
Facere minima asperiores rerum architecto velit hic non aut. Quo laboriosam ipsa reprehenderit optio quia. Debitis voluptates autem omnis occaecati ex. Ipsa nulla neque repudiandae non ipsam placeat perferendis est.
Qui quasi ad maxime eveniet. Ea quae aut. Quasi eum inventore molestias aut sint voluptas nemo. Ab aut velit assumenda.
Officiis totam amet est. In libero aperiam aliquam et neque adipisci repellat. Qui eum vitae qui commodi esse est eos magni. Nihil quia rerum libero pariatur voluptatem unde eius repudiandae atque. Voluptas quia provident qui deserunt doloremque qui.
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
