# Contextual Inquiry

> Observing users in their natural environment while they work—reveals context that interviews and surveys never capture.

*Tags: ux, research, mid-level*

---



> [!info] Quick Definition
> Observing users in their natural environment while they work—reveals context that interviews and surveys never capture.


## What is Contextual Inquiry?

Contextual inquiry is a research method where you observe users in their native environment while they perform real tasks. Unlike a lab study where a user sits at a desk, contextual inquiry happens where users actually work. An accountant in their office. A chef in a kitchen. A shopper in a store.

You watch, take notes, and ask questions in the moment. "Why did you click that?" "What are you trying to do?" You're not running a script; you're following the user's work. Context—environment, interruptions, priorities—shapes behavior in ways labs can't replicate.

**One sentence punch:** You learn more watching someone work for 30 minutes than interviewing them for three hours.**

## Why is it important?

- **Captures Unexpected Context:** Labs are controlled. Reality is messy. A cashier might use your POS system while handling a difficult customer, restocking shelves, and managing money simultaneously. That context is invisible in a lab.
- **Reveals Workarounds:** Users develop hacks and workarounds in real environments. They might open a second window to work around your app's limitations. You miss this in a lab. Observing reveals workarounds.
- **Shows Real Priorities:** In a lab, a user says "I want to find products quickly." In a store, they stop and chat with a friend, pick up a magazine, change their mind. Real priorities are different from stated priorities.
- **Improves Design Decisions:** When you see a user struggle, you understand why. You don't hypothesize; you observe. Design recommendations are stronger when based on observed behavior.

## How to Conduct Contextual Inquiry

1. **Recruit users in their environment** — Visit where they work. Ask to observe. You're a fly on the wall, not intrusive.
2. **Brief the user** — "I'm here to understand how you work. Keep doing what you normally do. I'll ask questions as I observe."
3. **Observe without bias** — Don't prompt actions. Let them work naturally. The goal is what they do, not what they think they do.
4. **Ask clarifying questions** — "What are you trying to accomplish?" "Why did you choose that?" Keep questions open-ended.
5. **Take detailed notes** — Capture what you see. User's actions, environment details, interruptions, emotional reactions. Details matter.
6. **Respect their work** — Don't interrupt critical tasks. Be flexible. If they're busy, reschedule. Their work comes before your research.
7. **Record (if permitted)** — Video recordings are gold. They let you revisit behavior and share with teams who can't attend.
8. **Analyze for patterns** — After 4-5 contextual inquiries, patterns emerge. When do users struggle? What's the context of struggle?

## Contextual Inquiry vs Interviews

**Interviews** ask about behavior. "How do you use this app?"

**Contextual inquiry** observes behavior. You watch them use the app.

Interviews are cheaper and faster but less accurate. Contextual inquiry is expensive and time-consuming but reveals truth. Most teams use both: contextual inquiry for depth, interviews for speed.

## Mentor Tips

- **First tip: You need only 4-5 contextual inquiries.** With four observations, patterns emerge. Ten is overkill unless the user population is highly diverse. Quality beats quantity.
- **Find the right environment.** If you're redesigning an accountant's software, observe accountants in their office, not in your office. Environment matters.
- **Go dark on technology.** Don't bring laptops. Don't take photos. Bring a notebook. You're observing, not surveilling.
- **Follow the work, not the person.** Don't watch them all day. Watch them do their job. An accountant's full day isn't relevant; their daily reconciliation process is.

## Resources and Tools

- **Books:** "Contextual Design" by Karen Holtzblatt and Hugh Beyer, "Interviewing Users" by Steve Portigal
- **Tools:** [[Miro]] for synthesis, video recording devices, notebooks for field notes
- **Articles:** Contextual inquiry methods on Nielsen Norman, field research guides on [[UX Collective]]

---

Source: https://www.fernandoux.com/en/wiki/research/contextual-inquiry/