Contextual Inquiry & Observation

Watch people complete real work in their own environment and explore the reasons behind each step while the task is still fresh.

Contextual inquiry & observation

Contextual inquiry combines observation of real tasks with conversation that explains why people take the steps they do.

Researchers sit alongside people as they work, noticing tools, interruptions, handovers and workarounds that are hard to recall in a meeting room. Short probes clarify intent without turning the session into a lecture.

UX Pacific ties observation to the decisions your team faces — workflow redesign, system change, training or service improvement — so findings stay actionable rather than merely descriptive.

What this method reveals

  • Actual task sequences versus assumed processes
  • Tools, artefacts and interruptions that shape work
  • Workarounds and informal knowledge sharing
  • Points where systems force extra effort or error

How we run it

  • Sessions scheduled in the participant's normal environment
  • Master–apprentice observation with timely clarifying questions
  • Structured notes on steps, tools, exceptions and handovers
  • Interpretation workshops that connect findings to redesign options

When to research

When observation in context is useful

Use contextual inquiry when you need to understand complex or specialised workflows, diagnose friction in operational systems or design tools that must fit existing practice. It is less suited as a substitute for controlled usability testing of a specific interface when task performance metrics are the priority.

The right participants

People who do the work you need to understand

Participants are people who regularly perform the tasks under study — frontline staff, specialists, customers completing multi-step journeys or partners using shared systems. We plan for role variation and document which parts of the organisation or audience the sessions represent.

Our approach

How we run contextual inquiry research

  1. 01

    Frame the decision

    Agree which workflows matter, what success looks like and which design or operational questions need evidence.

  2. 02

    Secure access

    Arrange site permissions, timing that reflects real workload and consent for observation and note-taking.

  3. 03

    Prepare observation foci

    Define tasks to observe, probing guidelines and how interruptions or sensitive moments will be handled.

  4. 04

    Observe and inquire

    Watch the work unfold, ask clarifying questions at natural pauses and capture steps without taking over the task.

  5. 05

    Model the work

    Map sequences, dependencies, exceptions and the gap between official process and practice.

  6. 06

    Translate findings into action

    Prioritise friction points and opportunities for redesign, tooling or training with supporting evidence.

The conversation

Questions that stay close to the task

Probes focus on what just happened: why a step was taken, what would go wrong if it were skipped and how exceptions are handled. This keeps explanation tied to observed behaviour rather than abstract opinions about the system.

Research in context

Desk, floor, clinic or counter

Sessions take place where the work happens. We plan for noise, shift patterns, shared screens and whether customers or patients will be present, so observation remains ethical and practical.

Research ethics

Respecting work, privacy and bystanders

Participants know what will be observed, how notes or recordings are used and how to pause a session. We avoid capturing unrelated personal data and follow agreed rules when other people enter the scene.

The output

What your team can receive

Outputs may include workflow models, step-level friction inventories, artefact catalogues, opportunity areas and evidence-backed recommendations for process or product change. Readouts show what was observed versus what was assumed.

Clear boundaries

Interpreting observational evidence

Observation shows how selected people work in selected conditions. Presence of a researcher can alter behaviour, and findings may not generalise to every site or role. We distinguish observation from causal proof and recommend complementary methods when you need prevalence, controlled comparison or interface-specific performance metrics.

Let us help shape the next step

Watch the work as it actually happens.
Design for real conditions.

Share the workflow, environment and decisions you need observation to support.