Industry:
Fitness
Overview:
My Team and I were challenged to find an area for opportunity and work on a solution. After some market analysis we decided to focus on fitness and primarly how it caters to those who are less motivated to participate in traditional fitness.
Role:
Competitive matrix
User Interviews
Competitor Analysis
Persona Development
Journey Mapping
DesignStudio
Sketching
Wireframes
Iterative
Testing
Rapid Prototyping
Usability Testing
Full Spec Doc
Process:
Tools:
Sketch
Invision
Adobe CS
Keynote
Zeplin
Team:
UX Designer
UI Designer
Handoff Lead
Adam El-Kahtib
Eric Goldberg
Brief
Heading
Platform
Mobile Application
Reasoning:We will need access to the accelerometer in the phone which simply does not exist on a desktop platform, the ability to potential add accessories like a fitness tracker can be essential. Furthermore, Access to the camera may also be necessary.
Problem at Hand
Heading
Opportunity Statement
We will improve the experience of Being Active for Inconsistently Active Individuals.
The user struggles today because of a lack of Adequate Incentive, Accountability and Fun.
Research
Research Key Insights
After completing the user interviews, we gathered the data together and created an affinity map. Using the affinity map, we uncovered the major pain points of the user. We uncovered that the major pain points were that users were confused with how to complete certain tasks due to unclear navigation, they were unsure about direction, due to SwearBy lacking an effective on boarding process, and a lack of credentials and customization for product sharing. After the research was synthesized, personas were created in order to humanize the data.
.png)
.png)
Problem Statement
How might we help Steve maintain the motivation and interest to accomplish his activity goals while continuing to be able to navigate his busy work and social life?
.png)
Low Fidelity
My Team and I wanted to ensure that the app was simple engaging and motivating we drew up a few sketches of what the product could potentially look like and worked on testing and iterating on these concepts.
High- Fi Mockups
.png)
User Testing Iconography
While everyone tested was able to complete the tasks asked of them, there was some confusion about the placement of “daily” quests and “current” quests on the profile screen leading to a bit of searching to see how added a quest affected the “profile” screen.
Users cited having a “Add Quest” button directly was mildly confusing as they would need the information given by clicking the splash art to see the details of the quest.
Recommendation:
Switch the positions of “current” quests and “daily quests”
Remove “Add Quest” button from “Quest log” screen.
Next Steps
Randomly generated quests
Geo location controlled
More stories and quest lines
Different overlays and skins
Bag/Item system
Customizable avatars
Battle arena to compete with friends
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
