W2D1: Mini Contextual Inquiry

In this exercise, we’ll get a taste for what a contextual inquiry is like.

Background

• Goal of contextual inquiry: understand user needs in the context of their work by collecting data from users doing real tasks at the site of real work
• Master/Apprentice model
  • Master: does the work “in context” and talks aloud.
  • Apprentice: makes observations & interrupts with questions
• Four principles
  • Context: avoid summary / abstraction
  • Partnership: collaboratively unfold, alternate between watch & probe
  • Interpretation: Fact -> Hypothesis -> Implication -> Design idea
  • Focus: bring your own purpose & beliefs
• Concrete vs essential tasks
  • Concrete tasks: “save a file”
  • Essential tasks: “make sure I can come back to my work later”
  • focus on the essential tasks

For more background, see our Needfinding reading.

Instructions

1. Pair up with a partner. Choose who starts as the Apprentice.
2. Apprentice: Interview your partner to find out how they manage their schedule. (3 mins)
   • Have them actually do a task (e.g., add an event to their calendar)
3. Write down:
   • The key essential tasks they perform in order to manage their schedule.
   • Any breakdowns (problems) you observe.
   • Submit your observations at this form
4. Switch roles and repat steps 2 & 3.