Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

8 tips to build a quicker, easier research practice

211 views

Published on

Aurelius and User Interviews teamed up to bring you this free webinar to share tips and practices to speed up your user research efforts.

https://blog.aureliuslab.com/quick-easy-user-research

Published in: Technology
  • Be the first to comment

  • Be the first to like this

8 tips to build a quicker, easier research practice

  1. 1. 8 Tips to Build a Quicker, Easier Research Practice
  2. 2. Hi 👋 I’m Zack Co-founder and CEO at Aurelius zack@aureliuslab.com www.aureliuslab.com
  3. 3. Hi 👋 I’m Carrie Content Creator at User Interviews carrie@userinterviews.com www.userinterviews.com
  4. 4. What we’re doing today… 1. 8 tips to build a user research practice a. no need to take notes, we’ll send you the slides afterwards! 2. Q & A 3. Stay after for a live demo of UI + Aurelius, and learn how you can use our tools to make research even easier
  5. 5. First things first— It’s never going to be totally easy. Unfortunately, we can’t magically make your research work perfectly every time. But we can help you learn how to make it easier, quicker, and try to take some of the pain out of research.
  6. 6. 1. Make Research Habitual ● First, decide on a cadence that works for you and your team ○ Once a week, with focus on frequency over # of sessions ● Be realistic about your time and resources. ○ $$ for software, participant incentives ○ You and your team’s time, including preparation, actual research sessions, and analysis ● Stick to it! ○ Create recurring calendar events, so it’s baked into your week like anything else.
  7. 7. 2. Organize your research projects consistently ● Projects by research effort or product ○ Consistent structure for organizing projects allows you find information from past studies faster and easier after the research is done ● Organizing notes and observations ○ Avoid the “wall of text” for notes on a project ○ Organize notes by “source” or participant to track findings and patterns in analysis ○ Group notes based on the organization scheme you choose for your project
  8. 8. 3. Assemble a panel of participants ● Build a good list of participants you can use for research, so you don’t have to spend time recruiting every time. ● A panel allows you to keep track of... ○ the last time they participated ○ gather details about them as they participate
  9. 9. 3. Assemble a panel of participants ● How do I build a panel? Chat Intercepts In-App Intercepts Existing Customer Lists Feedback opt-in In-context links Social media P.S. You can manage your panel through User Interviews
  10. 10. 4. Tag and organize notes as you go ● Speeds up analysis time later and allows you to “dig deeper” ○ Sometimes referred to as “data coding” ○ Create themes as you go ● Keep detailed participation notes ○ Keep track of the last time they participated, any new information you learn about them in the session, etc. ○ Use tags to describe your notes and observations in ways you’ll want to group, analyze and search later
  11. 11. 4. Tag and organize notes as you go
  12. 12. 5. Involve the whole team ● Research is really important, and it’s a great opportunity for teams of all kinds to hear from customers firsthand ● Your team can help… ○ Set learning goals that have more impact ○ Take notes ○ Synthesize data ● To keep things organized, create shareable templates
  13. 13. 6. Document everything you can ● You never know when certain observations may be useful today or tomorrow, so take diligent notes about everything ● Tag/code those notes for context and detail ● Include any additional artifacts like pictures, audio, video, etc. ● Put everything in one central location ○ This should all be organized by the project/product just like we talked about earlier
  14. 14. 7. Create key insights for sharing nuggets or findings ● Don’t share raw data or single observations ● Create Key Insights (aka “findings” or “nuggets”) to build a reusable library of user research knowledge ● 4 parts to a Key Insight ○ Title: Statement of what you learned ○ Description: Details about that statement and why it’s important ○ Supporting Data: Notes, observations and artifacts that support the key insight and provide more context ○ Tags: Labels that describe the key insight to easily organize, find and reuse the insight by pattern or theme
  15. 15. 7. Create key insights for sharing nuggets or findings
  16. 16. 8. Group relevant key insights across projects and get them shared! ● Group your Key Insights from all user research ○ By topic or theme ○ By product ○ By feature ○ By department or team ○ By persona or customer segment ● Share those groups with relevant team members!
  17. 17. Questions? Answers!
  18. 18. UI Walkthrough Launch your first project with 3 free participants. Schedule a demo with our research consultants to learn how UI can work for your team.
  19. 19. Aurelius Walkthrough

×