RESEARCH REPORT User Experience Design - Project 1 Spring 2017 Nan Zhao nanzhao@nyu.edu
Table of Content
● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
Project Goal Initial Assumptions Areas of Focus Approach Brain Bump Competitive Analysis Comparative Analysis User Interview Survey and Data Analysis Persona User Flow Task Analysis Design Recommendations & Application Feature Requirements Next Steps Pecha Kucha Style Presentation
PROJECT GOAL To give design recommendations and feature requirements based on research to help the client to create a mobile application to help users keep track of their design documentation throughout the course of a project.
INITIAL ASSUMPTIONS
Who is our users? Examples: People who have a goal or task or project to accomplish which needs earlier plan, ideation, preparation, and execution.
●
● ●
● ● ●
Designers( product designer, user experience designer, maker, prototyper, etc) Programmers Visual Designers (graphic designer, video producer, animator, photographer, etc.) Fine Artists (sculptor, painter, etc) Social Media activist (Instagrammer, Lofter) Students who are currently pursuing the above fields.
Why do the target user do documentations? ●
To track the progress of a project
●
Show people he/she is doing a project (social media)
●
Show people how to get the product done step by step (product designer, maker, artist)
●
For preparing the portfolio so as to get potential career opportunities
●
Required by professors/employers
●
Teamwork: Accessibility to the team members
What is the definition of “documentation” to the target user? ●
Take photos, videos of a prototype, brain bumps, sticker maps, sketches, etc to document the process of making a product/accomplishing a project.
●
Screenshots of pictures or references found online, visual effect tried, etc.
●
Thoughts on what he/she learned throughout the design process of a project, what problem met and how he/she solved that problem.
●
Save the codes, etc.
Where are the target user accessing from?
The target user will use our mobile app to constantly update their process of doing a project
When // Where // What // How
in the place they are doing the project(where) anytime there is progress or things valuable to record(when). Mainly by taking photos, shooting videos with date and comments/thoughts/insights(how and what).
The target user will also use their leisure time(when) on bus, train, metro, car(situation, where) to write down thoughts or brainstorming on the mobile app or update their photos, videos, comments uploaded before. (what)
The Competitors
Wordpress
Google Drive
Github
Trello
Evernote
1. 2.
3.
Areas of Focus
4.
5.
6.
Identify who is the primary user How to integrate the app into the process of documenting during the design process of a project How to avoid competition with the existing competitors How to add additional dimension to distinguish the app from other services Find what the app can help on documentation and at the same time match the target user’ current habits. Use user interviews and surveys to validate and testify assumptions formed by each other.
APPROACH / PROCESS
APPROACH / PROCESS Contextual Inquiry
Brain Dump / Concept Map
Interview
Persona Survey
Scenario User Story
Generate features Feature Priority
Competitive Analysis Comparative Analysis
User Flow Task Analysis
BRAIN DUMP / CONCEPT MAP
● ● ● ●
Analyze the project Generate assumptions Plan Get mind organized
Brain Dump / Concept map
Version 1 Version 2
Some of My Sketches about the Idea Generation
Link to the competitive analysis
Competitive Analysis Wordpress // Google Drive // Github // Trello // Evernote
Notes: Every app/platform/service the target users are using during their documentation can be our potential competitors. Identifying competitors and trying not to compete directly with them but rather cooperate with them is important. Based on the findings of interviews and survey results, Trello and Evernote are rarely used or considered as a tool for documentation by the target group. But they do have essential features helping people tracking progress of doing projects.
COMPARATIVE ANALYSIS MyfitnessPal // Instagram // Xiumi
USER INTERVIEW
Goals of the interviews:
USER INTERVIEW User Interview Insights
●
Verify assumpted target users, primary/secondary/special user groups
●
Understand the reasons of their documentations
●
Understand the process/behaviors of documentations, the user flow
●
Their attitudes on documentations
●
Find opportunities of their pain points during the task journey throughout their user flow
●
Testify and identify competitors, competitive advantages, and comparative advantages
Participants
USER INTERVIEW User Interview Insights
●
Students majoring in Interactive Media Arts (Prudence, Wendy, Arial)
●
Student majoring in Computer Science and Interactive Media Arts (Ada Zhao, Cindy Hu)
●
Students majoring in Computer Science (Bin Ni)
●
Professor in sculpture in Gallatin Individualized study (Harry Kleeman)
●
Art student in Gallatin Individualized study (study video art production)
●
Graduate students in Interactive Telecommunications Program, Tisch. (Background covering engineering, programming, generative art, video art and physical computing, tangible interaction, etc.)
●
Business student in Stern Business school
Target User
USER INTERVIEW Findings
●
People doing physical design or having interaction with the real world (talking to people, researching, etc), such as product designer, maker, UX designer, tend to do a lot of documentations to record the design process. They are the primary users.
●
People doing more on business teamwork will do documentations solely for teamwork convenience and efficiency. They mainly use laptop/computer to document the process of completing a project. They are secondary users. (Or future users we can extend.)
●
People having picture based or image based projects on social media. Although they need planning and executing, they don’t do a lot of documentations.
●
People doing digital production like video art, or generative art don’t have a habit to do documentation to record the design process. So they are not our target user.
Platforms/Tools they are using for documentation
USER INTERVIEW Findings
●
Wordpress
●
Google Drive
●
iPhone notes
●
iPhone camera
●
Notebook
●
Github
What they document ●
Photos
USER INTERVIEW
●
Videos
●
Sketches and notes
●
Codes
Findings
●
Components and materials used
●
References or inspirations they found (links, photos, videos)
Behaviors / Habits ●
USER INTERVIEW Findings
They use different kinds of platforms/services at the same time to complete the full documentation ○
Use notebook to draw sketches and write notes and thoughts
○
Use iPhone camera to take photos and videos
○
Use iPhone notes to write notes
○
Use Github to save changes of codes
○
Use Google Drive to store files
○
Use Wordpress to write the final documentation post and publish it
○
Sometimes forget to document
Attitudes
USER INTERVIEW Findings
●
They like uploading the media files and drafting the final documentation post in the end of the final product or project.
●
For sketches, they prefer drawing on paper instead of typing on phones and computers, because it gives them more free space to write what they are thinking in any format.
●
Documentation is to let people understand the theory or design process behind a product, so documentation posts should be public to let more people to see and read.
Reasons for documenting the design process
USER INTERVIEW Findings
●
To prepare for the portfolio
●
To show the design process as part of their qualifications for future career opportunities
●
To teach people how they complete a product step by step
●
Make it accessible for them to go back and check the process
●
Efficiency and convenience for teamworking
●
Course requirement
“A
lot of unpredictable things would happen when
doing a project. You will never know what would happen in the next step.
“Doing
a project or designing a product is a
journey of exploration.
USER INTERVIEW User Interview Quotes
“Doing
”
”
documentations is related to the sharing
and learning experience in the field of technology. If you don’t document, people would not understand it.
“I
”
like deadlines. To check lists gives me a
sense of accomplishment. Documentation is more about teamwork to me.
“Putting
”
thoughts and ideas on it besides the
final work shows more about my process of ideation and lets people understand me better.
”
What kind of projects do you do? How you define “documentation”? Do you do documentation? Why? Why you think documentation is important to you and your project? ● Can you describe the whole process of your documentation, depending on your own experience? ● What do you document? Why? ● What platforms/services are you using? For what purpose? Why? ● Do you use the mobile versions of these services? Why? ● Do you make your documentation public? Why or why not? ● Is there anything during a documentation that makes you feel annoyed or inconvenient? ● Have any problem happened before when you do a documentation? ● Did you try to solve it? How? If not, why failed to solve it? ● Do you have anything else would like to share? * Additional follow-up questions varies on different interviewees. ● ● ● ●
USER INTERVIEW User Interview Questions
User Interview Documentations of the interviews
SURVEY
SURVEY Goal
●
Get quantitative data about target users’ documenting behaviors
●
Evaluate and testify the assumptions and insights from the interviews
●
Identify target users
●
Analyze the competitive advantage of Airbnb’s competitors
SURVEY
●
NYU network
●
Facebook network
Distribution
●
WeChat network
SURVEY - LINKS Draft’s Link
Survey’s Link
Responses’ Link
Survey Report
SURVEY - RESULTS & ANALYSIS Get 44 effective survey feedbacks ●
●
●
Not many people say they are doing it for teamwork 8/44 ○ People documenting for team work are not the primary users Majority of the participants use wordpress 60% ○ Wordpress is the biggest competitor, the app should avoid the direct competition with wordpress. ○ But the app can have multiple ways to match users’ needs when using Wordpress. Integrating itself into the user’s journey of designing and documenting. 67% set categories, 49% set tags ○ Features helping organize and identification are essential.
● ●
●
● ●
Re-editability ranks 8.41 out of 10 when people judging a documentation. 91% of participants publish their documentation of the design process. ○ According to the interviews, making the documentation public means sharing, education, and showing qualifications for career opportunities. ○ The app should make the documentation public or help users to publish documentations. Photo, videos, sketches, notes, and codes are the top five things the participants would document and have in their final documentation posts. Only 16% of the participants don’t use mobile phone to document. 88% of the participants use mobile phone to take photos for documentation; 63% shoot videos. ○ Photos and videos are essential to a documentation.
PERSONA
USER FLOW
TASK ANALYSIS Assign a new category for an existing photo piece in a document.
Ideation/Research
User Story Iteration
The process of doing a project
Making Doing Prototyping
Progress Problem Unexpected Things Solving
Testing Final Deliverables Organize + Plus writing and thoughts + Publish
Ideation/Research
User Story Iteration
The steps that need documentation.
Making Doing Prototyping
Progress Problem Unexpected Things Solving
Testing Final Deliverables Organize + Plus writing and thoughts + Publish
Ideation/Research
User Story Iteration
The step that creates a pain point to the user.
Making Doing Prototyping
Progress Problem Unexpected Things Solving
Testing Final Deliverables Organize + Plus writing and thoughts + Publish
Must Have ● ●
FEATURE RECOMMENDATIONS
●
The MOSCOW Method ● ● ●
Account system Create different projects and ability to manage them(name, delete, create) For photo and videos ○ Access to the album on mobile phones ○ Access to the camera for taking photos/videos ○ Write comments/descriptions to the files ○ Set tags/categories/labels ○ Set name ○ Set date Ability to be viewed online or on computers / exported Re-editable Ability to save
FEATURE RECOMMENDATIONS The MOSCOW Method
Should Have ●
●
For sketches and notes ○ Sketch board for sketching and typing ○ Set tags/categories/labels ○ Set name ○ Set date Module system to drag documents and different categories cards.
Could Have
FEATURE RECOMMENDATIONS The MOSCOW Method
● ● ● ● ●
● ●
●
sharable for teamworking Checklist Set timelines Send reminders according to the timeline A database to insert information of the used materials (product name, link, purchase platform, price) Ability to create your own product information Connect with mobile apps of wordpress, github, and other competitors’ platforms Customize the appearance like theme, color, background
FEATURE RECOMMENDATIONS The MOSCOW Method
Won’t Have ●
Public function
●
Codes editing and uploading
●
Social media features (subscription, followers, etc)
NEXT STEP
NEXT STEPS Research ● ● ● ● ● ●
Interviews Focus Group Survey Data Analysis A/B Testing ...
Branding ● ● ● ●
Name Logo Visual Identity ...
Prototyping ● ● ● ● ● ●
Sketch Sitemap Wireframe Prototype User testing ...
LINK TO THE
FINAL PRESENTATION