Understanding the app productivity space
Understanding the app productivity space
Understanding the app productivity space
If you were to click through the app or Google Play store, you'd find no shortage of ways to track a goal: apps that encourage daily journaling or meditation, offer boxes to check off so you don't ruin your daily streak, or even tie your progress to the well-being of a fictional habit buddy.
Though these methods help keep users accountable, they're unrealistic for busy users. The emphasis on daily usage makes it difficult to get a quick overview of their goal progress.
If you were to click through the app or Google Play store, you'd find no shortage of ways to track a goal: apps that encourage daily journaling or meditation, offer boxes to check off so you don't ruin your daily streak, or even tie your progress to the well-being of a fictional habit buddy.
Though these methods help keep users accountable, they're unrealistic for busy users. The emphasis on daily usage makes it difficult to get a quick overview of their goal progress.
If you were to click through the app or Google Play store, you'd find no shortage of ways to track a goal: apps that encourage daily journaling or meditation, offer boxes to check off so you don't ruin your daily streak, or even tie your progress to the well-being of a fictional habit buddy.
Though these methods help keep users accountable, they're unrealistic for busy users. The emphasis on daily usage makes it difficult to get a quick overview of their goal progress.
Uncovering key insights
Uncovering key insights
Uncovering key insights
I kicked off the project by talking to people of all ages and occupations, in an attempt to gauge typical goal tracking experiences and pain points. This approach made sense at first, as I wanted to design something for every kind of user, but I very quickly realized that I could be much more effective by focusing on a more specific user base. I then followed up my initial findings with a survey and competitor analysis.
I kicked off the project by talking to people of all ages and occupations, in an attempt to gauge typical goal tracking experiences and pain points. This approach made sense at first, as I wanted to design something for every kind of user, but I very quickly realized that I could be much more effective by focusing on a more specific user base. I then followed up my initial findings with a survey and competitor analysis.
I kicked off the project by talking to people of all ages and occupations, in an attempt to gauge typical goal tracking experiences and pain points. This approach made sense at first, as I wanted to design something for every kind of user, but I very quickly realized that I could be much more effective by focusing on a more specific user base. I then followed up my initial findings with a survey and competitor analysis.
67%
67%
of survey participants said they focus more on the milestones than the goal itself
60
seconds
60
seconds
average time spent by users on goal tracking apps
Be
informational…
Be
informational…
…but to the point. Competitor apps often overwhelmed users.
"I didn't feel very organized when I used [competitor app]."
"I didn't feel very organized when I used [competitor app]."
- Tiffany, goal tracker
Taking shape
Taking shape
Taking shape
(ONBOARDING FLOW)
The next hurdle to tackle was designing how users would get started. I wanted to keep onboarding a bit flexible, allowing users to either jump right in or take their time getting to know the app with a proposed tutorial. I also decided to leave tasks as an optional step, based on my learnings about busy users and app usage habits.
(ONBOARDING FLOW)
The next hurdle to tackle was designing how users would get started. I wanted to keep onboarding a bit flexible, allowing users to either jump right in or take their time getting to know the app with a proposed tutorial. I also decided to leave tasks as an optional step, based on my learnings about busy users and app usage habits.
(ONBOARDING FLOW)
The next hurdle to tackle was designing how users would get started. I wanted to keep onboarding a bit flexible, allowing users to either jump right in or take their time getting to know the app with a proposed tutorial. I also decided to leave tasks as an optional step, based on my learnings about busy users and app usage habits.
(DESIGNING THE MAP UI)
I wanted to associate 'goal mapping' with the idea of a navigational map; an explicit guide to reaching your destination or long-term goal. This would allow interactive abilities and customization, another aspect I learned was important to users.
(DESIGNING THE MAP UI)
I wanted to associate 'goal mapping' with the idea of a navigational map; an explicit guide to reaching your destination or long-term goal. This would allow interactive abilities and customization, another aspect I learned was important to users.
(DESIGNING THE MAP UI)
I wanted to associate 'goal mapping' with the idea of a navigational map; an explicit guide to reaching your destination or long-term goal. This would allow interactive abilities and customization, another aspect I learned was important to users.
(DESIGN VALIDATION)
I ran a usability test to address any information architecture concerns. I specifically looked at the goal maps' ease of use and the navigability of the side bar and bottom nav.
I learned that 80% participants had difficulty understanding where to log progress or add a milestone, which later led me to setting up a mixed card sorting test.
(DESIGN VALIDATION)
I ran a usability test to address any information architecture concerns. I specifically looked at the goal maps' ease of use and the navigability of the side bar and bottom nav.
I learned that 80% participants had difficulty understanding where to log progress or add a milestone, which later led me to setting up a mixed card sorting test.
(DESIGN VALIDATION)
I ran a usability test to address any information architecture concerns. I specifically looked at the goal maps' ease of use and the navigability of the side bar and bottom nav.
I learned that 80% participants had difficulty understanding where to log progress or add a milestone, which later led me to setting up a mixed card sorting test.
A change in the architecture of the map meant a change in the bottom navigation bar as well. The 'Add New' was changed to add a new milestone and moved to the side bar.
A change in the architecture of the map meant a change in the bottom navigation bar as well. The 'Add New' was changed to add a new milestone and moved to the side bar.
A change in the architecture of the map meant a change in the bottom navigation bar as well. The 'Add New' was changed to add a new milestone and moved to the side bar.
Final looks
Final looks
Final looks
