WiredIn
A productivity app
Overview
Project Type: Solo Capstone Project
Timeline: 12 weeks
Role: UX/UI Design, User Research, Prototyping
Tools: Figma, InVision, Zoom
Platform: Mobile
WiredIn is a digital solution made for people having trouble with multitasking and task switching. By reducing digital distractions, WiredIn boosts work productivity for its users
The Dark Side of Multitasking
Switching tasks takes a toll on productivity of young professionals. For example, a person is working on a report, then all of a sudden, checks phone notifications or goes online shopping. These interruptions can cost someone’s productive time and negatively impact work.
Design Challenge
Determine the most common task interruptions and the impact of multitasking in a work environment in order to develop a mobile application that would assist young professionals in reducing and preventing ineffective interruptions while working to boost output.
Approaching the problem
I wanted to approach this project with the assurance that my designs and values were in line with resolving issues for actual people. I organised this research using the design thinking methodology to keep the focus on creating a human-centered solution that is not just technically and economically feasible but also ultimately desirable in addressing the demands of my users.
EMPATHIZE
What’s out there
23
Research showed that about 82 percent of all interrupted work is resumed on the same day but it takes an average of 23 minutes and 15 seconds to get back to the task
Multitasking may seem efficient on the surface but may actually take more time in the end and involve more error. Brief mental blocks created by shifting between tasks can cost as much as 40% of someone's productive time
40
Willpower is limited, just like other resources. We are quickly out of what little we have. While we make an effort to block out distractions, the digital age is specifically made to achieve the opposite.
User Research
To gather proper information and deep insights needed, I used 1-on-1 interviews as my main method of user research. The participants were young professionals who work at home or in an office who have access to multiple devices (computers, phones, tablets). Below are some the questions I asked them
How do you determine your priorities at work?
Can you please name 3 distractions or interruptions you normally experience while working
Do you check you notifications regularly? If yes, how often?
Can you please share an experience when you had to multitask while working? How did it affect your work flow?
What I’ve heard . . .
“Honestly it’s bad because I end up spending time checking out stuff outside of work during work hours”
“It would be awesome if there’s a way I could stop that habit”
“I’m pretty active in social media so I do check them often”
“Twitter is life!”
Key Insights and Themes
After the interviews, I’ve mapped out my user research findings and grouped them into pain points, motivation, goals, and behaviour. From there, I was able to synthesize my findings into 3 distinct themes. For this project, I’ve decided to focus on the theme of ‘Distractions’.
(click images to enlarge)
Notifications - participants were mostly disrupted by phone notifications while working
Time Management - participants wanted better ways to manage time at work to be efficient
Distractions - most participants had a lot of digital distractions and for others, started to become a habit
How Might We
With the help of my research findings and having the focus on the theme of ‘Distractions’, I’ve formulated my “How might we” question
How might we help young professionals limit or prevent interruptions in order to focus more and increase productivity at work?
DEFINE
User Persona
To dive deeper, I’ve created a user persona - Ron. He is a representation of the target users of WiredIn.
Using the persona, I developed an experience map to show the end-to-end experience that a user goes through when dealing with multitasking at work
IDEATE
User Stories
From the opportunities in the experience map , I made user stories in order to show product functionality in the perspective of a user. I’ve grouped them into functionally-related epics and focused on one to base my task flow on.
As it directly connects to the objectives of the project goals and HMW question, I have chosen to use this epic because it will have a significant impact on user productivity. This will be the first step in creating a solution that meets their needs.
Task Flow
With the focus on chosen epic, I have created a task flow to show the process that the user would go through when using the product
PROTOTYPE
Sketches and Wireframes
Based on the task flow, I started with paper sketches then proceeded to creating low fidelity wireframes.
Prototyping
I made my initial prototype, mostly concentrating on functionality and generating concepts for potential interactions. At this stage, I also considered how my product's tone and aesthetic might be used to brand future content.
V1 - before user testing
TEST
User Testing
2 rounds of 1-on-1 user tests were done through Zoom with 5 participants in each round. Design iterations were made based on test results
V2 - after 1st round of user test
Moved the buttons to switch from the “Apps” tab to the “Websites“ tab out of the frame because users said they were hard to notice
Added “Add new“ button on the Apps tab, Websites tab, and Notifications tab
Resized “Begin Session“ button as most users find it too large
V3 - after 2nd round of user test
Created a carousel to put Apps tab, Websites tab, and Notifications tab under the Blocklist button reducing the number of buttons in the nav bar
Redesigned the indicator for the nav bar
Reduced confirmation screens (modals)
Final Screens
Interactive Prototype
Reflections
What’s next?
I would like to add an incentive system to the app. That way, users would would be more encouraged to use the app. Lastly, I want to make this app in multiple platforms including desktop and smart watch.
What did I learn?
I learned that research is a HUGE factor when defining where to focus on the problem. I also learned the value of feedbacks and how it affects design iterations. Another lesson learned for me is that it’s important to prioritize features that have the highest impact in order to create a minimal yet viable product.