Contextual Inquiry Template for User Research

Interviews rely on memory. Contextual inquiry relies on observation. In an interview, a support agent might say "I check the customer's account status." In a contextual inquiry, you watch them open three browser tabs, cross-reference data in a spreadsheet, and consult a colleague before making a decision. The details that interviews miss are exactly the details that reveal product opportunities. For more on the interview approach, see the [User Interview Script Template](/templates/user-interview-script-template).

Yes, with trade-offs. Remote contextual inquiry works via screen-share with a camera showing the participant's environment. You lose the ability to see physical artifacts, overhear conversations, and observe the full workspace. But for software-centric workflows, remote observation captures most of the value. Ask participants to share their full screen (not just one window) so you can see tool-switching behavior.

Four to six sessions is standard. After 4 sessions you typically see strong patterns. Sessions 5-6 confirm the patterns and surface edge cases. If you see entirely new behaviors in session 6, add 2 more sessions. For complex workflows involving multiple roles, you may need 8-10 sessions to cover all the actors in the process.

This is the observer effect, and it is unavoidable. Three tactics minimize it. First, schedule the session during real work, not a demo. Second, stay quiet during the observation phase. The more you talk, the more the participant performs for you. Third, schedule a longer session (90 minutes). Participants almost always revert to natural behavior after 15-20 minutes because the cognitive load of "performing" while doing real work is too high.

Build work models (flow, sequence, artifact) from your observations, then identify breakdowns. Each breakdown is a potential product opportunity. Use the [RICE Calculator](/tools/rice-calculator) to score opportunities by reach, impact, confidence, and effort. Breakdowns observed across multiple participants with high impact become your highest-priority features. Document the findings in your [PRD](/templates/prd-template) with references to the specific observations that support each requirement. ---