• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Practice : Shadowing & Contextual Inquiry

Purpose and Strategic Importance

Shadowing & Contextual Inquiry immerse teams in the customer’s real environment to see behaviours in context. This provides insights into workflows, constraints, and pain points often invisible through surveys or interviews.

Without contextual inquiry, products risk being designed in isolation from reality, missing friction points or cultural nuances.


Description of the Practice

  • Teams observe customers performing real tasks in natural settings.
  • Clarifying questions are asked to deepen understanding.
  • Observations are synthesised into themes and shared with teams.

How to Practise It (Playbook)

1. Getting Started

  • Select representative customers.
  • Gain consent and explain observation purpose.
  • Observe silently at first, then ask clarifying questions.

2. Scaling and Maturing

  • Use structured templates to capture findings.
  • Incorporate contextual inquiry into research cadences.
  • Combine with analytics for triangulation.

3. Team Behaviours to Encourage

  • Empathy and humility.
  • Curiosity about unexpected behaviours.
  • Respect for privacy and context.

4. Watch Out For…

  • Observer bias distorting interpretation.
  • Customers modifying behaviour when observed.
  • Ethical or privacy violations.

5. Signals of Success

  • Qualitative: Teams demonstrate deeper understanding of customer workflows.
  • Quantitative: Reduction in usability-related defects post-launch.
Associated Standards
  • Customer empathy guides decisions
  • Discovery is embedded in team practice
  • Ethics are embedded in design

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering