Missile: Process Page
Role
Tools
Deliverables
Duration
UX Researcher
Prototyper
FigJam
Figma
Research
Interviews
Wireframes
Prototype
5 Months
Overview
Missile is an app that helps users stay on track with their goals/tasks; whether they're work, personal, or fitness goals. My team and I took the time to gather research, by creating personas (fictional characters that represent the target user for an app/website), creating affinity maps, conducting interviews, designing wireframes, etc. Therefore, we were able to design an app that satisfied our users' needs.
Our Goal
When designing Missile, our main goal was to create simple features that allowed users to easily navigate and utilize the app to their specific needs.
Simple
Easy to navigate
Usable
UX Research
Research Phase
Modeling Phase
To start the research phase, we began with the kickoff meeting. During the kickoff meeting, we came up with the problem statement (the problem the company is facing) and assumption statements (discussed among our teammates; each came up with assumptions about our user and product). The problem statement we came up with was, "The current state of productivity tools has focused primarily on organization. What existing products/services fail to address is simplicity. Our product/service will address this gap by creating simple features that allow users to easily navigate and utilize the app to their specific needs."
After, we then came up with the persona hypothesis. This helped us assume the ideal interviewee we wanted. Provided below, are images of our problem statement, assumption statement, and persona hypothesis
The modeling phase included:
Grouping our interview subjects by role,
Identifying behavioral variables
Mapping interview subjects to behavior variables
Identifying significant behavior variables
Synthesize characteristics & define goals
Designate Persona Type
Expand on attributes/behaviors and complete persona
After grouping our interview subjects by role, we concluded that we would have one user type; a goal setter. We then took the research gathered from the interviews and identified their behavior variables. My team and I came up with 15 variables for our user role. A few of them being:
Experience with organizational tools
Motivation for organization
Professional v Personal goals
Current level of organization
Aggressiveness of reminders
Amount of tools/methods used
Ability to manage periods of stress
Positive v Negative feelings towards current tools.
Difficulty staying organized
Number of methods used for professional goals
After completing this part of the research phase, we moved on to conducting interviews. We had a set of 8 questions for 5 interviewees. Two of our interviewees are university students, and three of them are professionals. This gave us insight from both the student's perspective and the professional perspective. We met with each interviewee via Microsoft Teams. Provided below are images of our interview questions and affinity maps along with screenshots of each interview:
Interview Questions
Interviews
Interviewee: Jason
Interviewee: Kim
Interviewee: Rosaly
Interviewees: Necole & Miranda
Affinity Maps
Kim
Jason
Rosaly
Necole
Miranda
Once we were done with identifying behavior variables, we mapped our interviewees to the behavior variables. We started by creating continuums that express the behavior variables (from low to high), then created sticky notes with our interviewee's names on them. After, we placed each of their names on each continuum, and rated their relative accuracy. Once we laid it out, we identified significant behavior patterns and clustered them together.
Mapping Behavior Variables
Identified Significant Behavior Patterns
The 5th and 6th step of the modeling phase was to synthesize characteristics and define goals. Which is where we typed out bullet points describing characteristics of the behavior we identified in the continuum. These characteristics can include feelings, skills, aspirations, capabilities, frustration, etc. After, we then created goals (end, life, or and/or experience goals)
Towards the end of the modeling phase, we created our primary persona; David Johnson (DJ). We decided that he would be a 23 year old, who is a recent grad and works in Atlanta, Georgia as a Tech Salesman. David is also a fitness enthusiast. His end goals are to be able to keep track of his work and team tasks, to keep track of his gym/fitness goals, and to create healthy habits. His life goal is to be organized. His experience goal is to feel stress-free and not overwhelmed. We created a narrative to describe how our user/persona would use Missile in his day-to-day life. This helps us see how our product would be utilized, and if it solves our users problems.
Requirements Phase
The requirements phase was started by typing out our problem and vision statement. However, since we already had a problem statement, we didn't change anything. A vision statement focuses on user first, whereas the problem statement focuses on business first.
Brainstorm
After, we began brainstorming what we thought our product would look like. We created sections for each feature we wanted in our product; to-do list, calendar, collaborative tools, pages, scheduling, messages, etc. On each sticky note, we typed out what we wanted to include in our features.
Frameworks Phase
The frameworks phase is where we started our wireframing process. We each split up the features and worked on the screens individually. However, we had meetings and would ask for everyone's opinions. In our wireframe, we came up with 15 screens; onboarding(features), log-in/sign up, create account, tailor page, settings, notifications, home screen, work folder, fitness folder, notes, calendar, create a folder, messaging, to-do list, and events. All of this can change during the prototype process, but the wireframe helps us get an idea of how our product would look like.
