2. DriveDox Problem Statement
In our modern society, the number of tasks people are required
to perform have increased dramatically. As such, people try to
use several methods to remind themselves of “what” to “do”
and “when”.
When it comes to the personal vehicles people use everyday,
there are critical tasks that must be performed in a timely
manner to make sure they have the proper insurance,
registration and maintenance.
If they fail to maintain their vehicle, people can experience
consequences if the form of expensive fines or
unnecessary repairs.
3. DriveDox Solution
In order to avoid these consequences, DriveDox was designed
as a mobile app to assist people in making sure their car is
"legal" and running properly.
In order to be competitive, DriveDox is focusing on the
recording and sending reminders for only three areas (below)
• Insurance
• Registration
• Preventative maintenance
4. Initial Research & Documentation
Given this focus, user research was conducted asking people
how they maintained their vehicles.
It was found that other people maintained the vehicles for
them, or users did it themselves. Both used traditional
reminders such as windshield stickers, postcards or visible
clues from the car itself.
Using this information, a general persona was created along
with their goals and likely tasks they would perform. Based on
this, features were designed that would help them meet these
needs.
5. Prototypes & Testing
Initially, paper prototypes were created incorporating these
features in order to validate user flows and the hypothesis.
Users liked the simplicity of the design and understood the
general idea. Affinity maps were created to prioritize the
features.
Finally, lo-fi wireframes were created and additional tests were
conducted. This exposed some navigation issues and allowed
changes to be made in preparation for a final hi-fi prototype.
Usability tests were then conducted.
6. Final Results
The original assumption of the project was validated, however it
was revealed that users do not take a single path while using
the application.
This could be happening because users tend to use
applications based upon how "comfortable" they are with
similar technology.
For example, while younger users tended to use the defined
path, older users tended to search for shortcuts, or not use the
application feature at all.
However, all users appreciated the simple and uncluttered
"look and feel" as compared to other applications.
8. Initial Research & Documentation - Competitive Analysis
While I realize that there is some stiff competition out there, I noticed something
that I do as a driver. I keep a simple records using small paper notebooks for each
one of my cars. I try to make a note and attach any receipts that I have along with
them in the book.
As such, I would like to design my application using the KISS principle and only
offer the three features I have mentioned above. In addition, I think it would be
great if I could figure out a way to automatically import the car information straight
into the app as well. This way it make is much easier for me to enter information,
without dealing with the extra features I see in these applications.
9. Initial Research & Documentation – Interviewee Profiles
New Driver
• 16-18 years old
• Doesn’t maintain car
• Little experience
• Education Opportunity
• 30-40 years old
• Outsources
Maintenance
• Some experience
• Needs to manage
Older Driver
• 65-75 years old
• DIY maintainer
• Heavy experience
• Mentor?
Co-worker
10. Initial Research & Documentation - Initial Research Questions
• What mode of transportation do you use on a daily basis?
• Who maintains these vehicles?
• What is maintained on the vehicles?
• Do you track the services? Id so, how?
• Where do you have this done?
• Why is it done there?
• Have you ever lost documents (How or why)
• Were there any consequences because of the loss?
• How do you chose your services?
11. Interview
Results
New Driver Co-worker Older Driver
Maintenance
Experience
Minimum Medium High
Needs &
Concerns
Reliable Car.
Maintenance done
by parent
Reliable Car at
lowest cost
Reliable Car with
outsourced
Maintenance
Conclusion
DriveDox could be
used to educate
DriveDox helps
keep costs low
DriveDox helps
document shop
performance
Initial Research & Documentation - Initial Research Questions
12. Name: Bob Johnson
Age: Middle 40s
Job: Project Manager
Location: Denver, CO
Status: Married
Bio: Project Manager in Denver, CO who has been married for over 20 years. He
has two kids, with one who just started driving. He lives close to his older parents
and helps manage their cars as well.
Behaviors & Habits:
Bob maintains his vehicles using the windshield stickers the shop provides, and
post cards from his insurance company and county government. He also checks
on the cars if anyone notices something "wrong" with the cars. He also takes calls
from his parents when they ask how to get anything done for their cars now that
"everything" is on the Internet.
Initial Research & Documentation - Persona
13. Needs & Goals:
• Manage the insurance, registration and maintenance records for his three cars,
plus provide advice to his parents for their two cars.
• Receive reminders as to when insurance, registration and maintenance is due
for all the vehicles he manages, while teaching his daughter what to do as well.
• Keep costs as low as possible, especially since his daughter is heading toward
college
Initial Research & Documentation – Persona (continued)
"With my daughter driving and parents getting older, I need
help making sure her car is running well, and make sure we
are all legal regarding insurance and registration".
15. • Ability to see all services for each vehicle
• Ability to see LAST service for each vehicle
• Ability to see Expiration dates for Insurance and Registration
• Ability to integrate records from original sources automatically
• Ability to manually enter records
• Ability to receive and display diagnostic data provided by the vehicle
• Capability to set reminders for all records sent by push notification, e-mail
or text
• Ability to calculate total repair cost for set period (day, week, month…)
• Capability to make recommendations for next service based on mileage,
time, etc.
• Ability to calculate preventative maintenance vs reactive maintenance.
• Ability to estimate registration fees based on vehicle model, zip code, etc.
• Ability to make insurance recommendations based on vehicle mileage etc.
Prototype & Testing - Features
22. Prototype & Testing – Usability Tests
During the usability test, the Plus Column is what the users did correctly, or liked about the
prototype. There are three users, P1, P2, and P3.
In the Delta Column is what the users didn’t like or where improvements can be made.
23. Prototype & Testing – Usability Tests
Affinity map from the usability test. Here it can be seen that there are at least 4 major themes
that the users commented on, or liked.
a. Reminders
b. Buttons
c. Navigation
d. General Design
