User research often takes time. How do you make it work in startups?
source link: https://uxdesign.cc/user-research-often-takes-time-how-do-you-make-it-work-in-startups-774904c63ad8
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
User research often takes time. How do you make it work in startups?
Three tips for speeding up user research in small organizations
Photo by Pexels LATAM: https://www.pexels.com/photo/men-running-down-a-countryside-road-in-a-marathon-17979492/
One of the most complex challenges I had when I moved to designing for startups was adapting user research to the fast-paced environment.
User research is often crucial here: when you only have limited resources, you must create products your users want or need.
But getting access to users, not to mention testing and doing analysis can be a big challenge, especially with the amount of time you’re given. It can feel like the team is sprinting down a path as fast as possible, so you don’t get weeks to get user research done; you have days.
So, how can you make user research work in those environments? I figured out three methods to speed up the process through Data-Informed Design.
As it turns out, it often starts with ‘avoiding the spreadsheet.’
Avoid the (text) spreadsheet and focus on the 10,000 ft view
You may have been taught to compile your user testing results into a giant spreadsheet: I know I was.
This massive spreadsheet of data details each user’s response to questions and actions, allowing you to cross-reference user actions and eventually form a report.
The traditional usability testing spreadsheet
The problem is this won’t work for many companies, let alone startups. This is for two reasons: nobody can read the final result, and it takes too long.
Think about it: How long does it take you to dig through a spreadsheet, going back and forth, to compile all that research? It’s often either a ton of late nights and weekends or several weeks.
Moreover, you often do not need that level of detail in many cases. Part of learning about Data-Informed Design was learning how other team members think. In many cases, from C-level executives to Product Managers, your team is looking for the 10,000-foot view.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK