🏫
Obvious University
Website
  • 👋Welcome to Obvious University!
  • Strategy
    • Sprints
      • 1️⃣Map
      • 2️⃣Sketch
      • 3️⃣Decide
      • 4️⃣Prototype
      • 5️⃣Test
    • Benchmarking
    • Research
      • 1️⃣Research guide
      • 2️⃣How to recruit users
      • 3️⃣How to conduct an interview well
      • 4️⃣How to take notes
      • 5️⃣How to prep for remote research
      • 6️⃣How to throw a watch party
      • 7️⃣How to create artefacts
  • Working with Features
    • Building with AI
      • 1️⃣Understand the tech
      • 2️⃣Map your product
      • 3️⃣Build a proof of concept
      • 4️⃣LLM Inputs
      • 5️⃣LLM Responses
    • Building Help and Support
      • 1️⃣How to scope a support experience
      • 2️⃣How to design discovery for support
      • 3️⃣How to design a support centre
      • 4️⃣How to write good support articles
  • Product Design
    • Microcopy
      • 1️⃣How to write well
      • 2️⃣How to write phrases
      • 3️⃣How to write messages
      • 4️⃣How to create a voice
    • Typography
      • 1️⃣How to compose type
      • 2️⃣How to create a type scale
      • 3️⃣How to pick typefaces
      • 4️⃣How to pair typefaces
    • Design System
      • 1️⃣Introduction to design systems
      • 2️⃣How to audit a design system
      • 3️⃣How to run a design system pilot
      • 4️⃣How to set up a design foundation
      • 5️⃣How to build components
      • 6️⃣How to document a design system
      • 7️⃣How to enable adoption and govern a design system
    • Mobile Engineering
      • 1️⃣Trunk based development
      • 2️⃣Agile development terminology
      • 3️⃣Git commit messages
      • 4️⃣Code review and pull requests
      • 5️⃣Readings
  • Delivery
    • Project Management
    • Collaboration
  • Hiring and Growth
    • Growth
      • 1️⃣Design growth framework
      • 2️⃣How to give ongoing feedback
      • 3️⃣How to check-in every quarter
      • 4️⃣How to address underperformance
      • 5️⃣FAQs
    • Hiring and careers
      • 1️⃣The Hiring Process
      • 2️⃣Diverse and Inclusive Hiring
  • PEOPLE EXPERIENCE
    • Benefits and Perks
      • 1️⃣Paid time off
      • 2️⃣Insurance and healthcare
      • 3️⃣Continuing education
      • 4️⃣Speaking at conferences
    • Starting at Obvious
      • 1️⃣Introducing Obvious
      • 2️⃣Set up your workspace
      • 3️⃣Onboarding
      • 4️⃣Finances
      • 5️⃣Code of Conduct
    • Employment policies
      • 1️⃣Equal opportunity employment
      • 2️⃣At-will employment
      • 3️⃣Employee records and privacy
      • 4️⃣Prevention of sexual harassment
      • 5️⃣Drugs and alcohol
      • 6️⃣Fraternisation
      • 7️⃣Non-compete and non-solicitation
      • 8️⃣Non-disclosure
Powered by GitBook
On this page
  • 👋🏼 Introduction
  • 1️⃣ Throw a watch party
  • 2️⃣ Further reading
  1. Strategy
  2. Research

How to throw a watch party

PreviousHow to prep for remote researchNextHow to create artefacts

Last updated 1 year ago

👋🏼 Introduction

Watch Parties are helpful for project kick-offs, new product innovation, and major changes to existing features. They are however a bit of an overkill for quick usability studies.

1️⃣ Throw a watch party

Invite core group to attend as observers

No secondhand research report or highlights video alone can deliver the same jolt of insight and impact as when the core team actively observes a full set of customer interviews.

  • Remind them how it will help the project. Add it to their calendars. Send reminders.

  • Stoke FOMO in stakeholders by sending catchy updates during the interviews!

  • Even create “I’m a customer champion” badges as give-aways.

Set up room with goodies

  • Stickies and pens to take notes on, large TV to watch on.

  • Note taking template on figjam, google sheets, or notion for everyone to anchor to.

  • Snacks and coffee to take care of energy levels through the day.

Record interviews using

This frees up mind space during the call to engage in the conversation and ask insightful questions. Set up your account, create a project and connect to your google account. Meetings will get auto recorded.

  • Add grain to meeting links

  • Record if remote, share screen, open prototype, then give remove access to user

  • If in person, join meeting from test device, share screen, open prototype, then hand device to user. Use computer to record video of user.

Stream to core team

  • If the Participant is joining remotely, and core team is present in person—The note-taker should join from a conference room with mic and camera turned off. Observers can join the conference room in person.

  • If everyone is joining remotely—The note-taker sets up a parallel Observers Meeting. S/he also joins the interview meeting. S/he will then share screen with audio from Interview Meeting on the Observer Meeting.

  • If everyone is joining in person—Assign a note-take/facilitator, who will be with the observing group to help take notes, to call attention to interview techniques, and to do quick debrief after calls. They will also be able to collate questions form the group and share with the interviewer.

2️⃣ Further reading

6️⃣
Grain.com
UX Watch Parties
How to build a simple UX lab anywhere
Grain | Conversation Intelligence and AI Sales Assistant
GoTo Meeting Web Conferencing & Online Meeting Software - GoTo
Google Meet: Livestream a meeting