Document Management System - B2C

A collection of web screens with the ID veritication designs on them
Company
Microdea
Service
Native app
Industry
Logistics
Role
Lead UI/UX Designer
Team
1 designer, 8 engineers
Duration
3 months
Year
2019

The challenge

Microdea is a document management and back-office automation software company. Drivers should be able to bill their customers fast and simplify the back-office automation process. Drivers should be able to capture all logistic, tax, and custom docs with the mobile app. The users, most of the time, have a poor internet connection and always on move. Other times they have to sign documents that the back-office has sent. Many times the drivers are missing documents and the payment is getting delay. Drivers won’t need to chase down signatures or shuttle paperwork back to the office. And back-office staff won’t need to scan papers or decode sloppy signatures either.

Collection of screens with the final product designed

Data gathering and problem identification

Truck driver personas are fictional, generalized representations of our users and essential in creating. Focusing on the right questions and user's needs is important in creating a user-friendly mobile application. Building meaningful truck driver personas really starts with asking the right questions and then finding the answers to those questions by interviewing many different types of drivers. Documenting truck driver personas allows knowledge sharing to occur across the organization from the product management to the marketing team. The most solid truck driver personas are made from market research as well as knowledge from within the organization. We have interviewed drivers in order to understand their pain-points in document management in general and their frustrations in using the existing mobile application. Understanding human behaviour helps to drive the innovation agenda forward.

A collection of phones with the ID veritication designs on them

My design process

Without caught up in the dogma of the design processes I followed a design sprint with the rest of the product team working together with the development agile scrum methodology. I used mostly the google ventures design sprint methodology always following the business and development needs.

01. Preparing

  • Know the business goals.
  • Identify the specific product problem that needed to be solved.
  • Set expectations. (eg. How will we know if we succeed?)

02. Understanding

  • Agree on the brief and requirements with the stakeholders.
  • Interview users and stakeholders and answer the "5 Whys"
  • User Journey Map focused on the specific goal.

03. Define

  • Define the phases of the User Journey.
  • HMWs on the User Journey (ex. How might we can personalize the user’s experience? , How might we can make the user use the application more often? , How might we can help the user with the onboarding experience? Etc)

04. Diverge

  • White board brainstorm drawing solutioning
  • Lo-fi prototype

05. Decide

  • Presenting the different ideas to the peers and the stakeholders.
  • Make the decision according to the implementation timeline, the technical difficulties, and the most preferable solution.

06. Prototype

  • A prototype focusing on the user interface without integrating the engineering backend.
  • Create a prototype with the happy path to validate the designs

07. Validate

  • Testing the prototype with a small team of participants before delivering to the development team.
  • List out each of the important task or phases of the prototype and the participant to understand which part is working well and which need improvement.
Lpatop screen with a design
Two laptop with the designs of the starting screen
Two laptop with the designs of the starting screen
Two laptop with the designs of the starting screen