Our general user population consists of English speaking, smartphone owners looking to make a new habit or break an old one. By interviewing a variety of members within this population and asking them to describe a time in which they were unsuccessful in making or breaking a habit, we have identified three user classes--users whose goal falls low on their priorities and need reminders to stay on track, users who struggle with keeping or breaking habits and need consistent positive reinforcement, and users who are easily discouraged by a setback and need constant encouragement to avoid giving up.
|
|
|
|
| Name | New Year Nadia | Bad Habit Harrison | Mid-Life Crisis Mark |
| Age | 19 | 26 | 42 |
| Education | Some college | High School Degree | Bachelor's Degree |
| Motivation & Attitude | The New Year has just begun and Nadia is looking to change a few things in her life. After setting her new year's goals, she turns to our app to help her keep on track. She's excited about making a change, but as the thrill of the new year wears off and school starts again, her resolutions become less of a priority. | Throughout his life, Harrison has picked up some nasty habits. Now, for the first time, he has fallen in love and wants to reform himself for the boy of his dreams. He turns to our app in hopes of kicking habits of smoking and nail-biting that he's had for years. | In the midst of a mid-life crisis and freshly divorced, Mark acknowledges that his life needs some serious TLC. He turns to our app in the hopes of making himself a better man in order to pull himself out of his current funk. Feeling rejected and worthless, Mark is easily discouraged and needs consistent reassurance that he is making progress. |
| Domain Experience | Familiar with smartphone applications but has no experience specifically with habit making or breaking apps | Familiar with similar habit making and breaking apps but hasn't had any luck due to the lack of positive reinforcement, falls back into old patterns easily | Familiar with similiar habit making and breaking applications but has been discouraged by their "streak" centered model where a single setback restarts all progress |
| User Needs | Reminders | Reinforcement | Encouragement |
Plan 0: Do 1 and 2. 2 can be done up to 3 times, for maximum of 3 goals. Do 3 up to 3 times a day, as each task is completed, or once a day for all tasks. Do 4 as often as desired, when motivation or feedback is needed. 5 and 6 are optional, and can be done at any point after 1 and 2
Plan 1: This needs to be done only once per user. At least one of 1.1, 1.2 and (1.3, 1.4) is required to being using the app, and the other two can be done at a later point as well. 1.5 is optional but recommended to get used to the application.
This step would most likely be performed at home, or in any situation where the user would be idle enough to download the app and set it up. The margin of error is slim, and users will have the option to edit any incorrect information.
Plan 2: This tasks only needs to be completed once, but can be completed up to three times to create three different goals (or more times if a goal is deleted and a new one is added). Do 2.1-2.3 in order. 2.4 and 2.5 are optional. Any of the steps could be edited at a later point as well. If the user chooses to do 2.4, 2.4.1 and 2.4.2 can be done in either order, but are both required.
This step is also likely to be performed in a more idle environment, when the user has time to do set up. Here, the users can make some small, accidental errors. For example, they can make a typo in naming the habit they want to make/break and their time period, or they can choose a color they don’t actually like. All of these are easily fixable at a later point.
Plan 3: This task can be completed either once or several times a day. 3.1 and 3.2 should be done in order, and 3.3 is optional. Users can choose to do this as tasks are completed throughout the day, or once for all tasks at the end of a day. Users have the option to retrospectively edit days as well.
If the user has not complied with their goal behavior, they should not perform this task; this is where the most major user error can occur, but we have no means of enforcing honesty. The user might accidentally tap the checkmark, marking a success when there was none or before they had completed the day/the behavior. This task can be completed anywhere at anytime, and will most likely depend on what the user’s goal is. For example, if the user’s goal is to sleep more, they might complete this task in bed every morning, or if their goal is to exercise everyday, they might complete this task right after their workout at the gym.
Plan 4: This task can be done anywhere, at any time, any number of times. 4.1 and 4.2 should be done in that order, and 4.3 is optional. It would be most productive and encouraging to the user to complete this task at least once a week. There is no room for error in completing this task.
Plan 5: This task is optional, and its completion will vary depending on the user and their goal. Tasks 5.1-5.4 should be completed in that order, although 5.4 is optional should the user decide not to save the note.
An extremely motivated and organized user whose goal is to work out everyday would complete this task daily, making note of what kind of workout it was, how long the workout lasted, how they felt, etc. A similar habit may appear with someone who is trying to keep track of the food that they are eating, how many calories or carbs they are intaking, etc. On the other hand, someone who wants to stop biting their nails may not find it necessary to use the notes feature at all. Users who want to complete this task just for the sake of doing so may write a note of encouragement when they are doing particularly well or when they feel that they need some motivation to get back on track. There can be an error in the user mistyping or accidentally writing a note for the wrong date.
Plan 6: This task is optional and can be performed at any time. 6.1 is required to perform the task. 6.2 (and its subtasks), as well as 6.3 and 6.4 are optional. 6.5 is not required, but necessary if the user wishes to save the changes. 6.4 can only be done once for each goal and is irreversible; all data associated with the task will be lost.
Users are likely to do this task in a calmer environment, when they have time to sit down and change their goals. The task could also be done on-the-go, should a user notice an accidental error. The most dangerous error would be accidentally deleting a goal, but there will be a confirmation dialogue before the action is complete. Any other subtask is easily reversible.
