Evaluation Method

Observation

Observation is a research method in which researchers watch people, tasks, environments, or interactions to understand what actually happens in context.

Concept facts

Observation is a research method in which researchers watch people, tasks, environments, or interactions to understand what actually happens in context.

Also known as
Field observation, workplace observation, contextual observation, direct observation.
Used in
Field studies, contextual inquiry, usability evaluation, service walkthroughs, workflow analysis, and institutional process review.
Interpret with
Contextual inquiry, ethnography, task analysis, field study, operational workflow, and triangulation.

Plain-language explanation

Observation helps teams see what people do, not only what they say they do. It can reveal interruptions, workarounds, environmental constraints, shared-device use, paper-digital transitions, staff mediation, and informal steps that are missing from process diagrams.

In UX work, observation is valuable when the real service environment is more complex than a screen recording or interview can show.

Why it matters

Many digital systems fail because they are designed around ideal workflows. Real users may face queues, low connectivity, shared computers, noisy offices, supervisory interruptions, missing documents, or conflicting instructions.

Observation helps reveal these real-world conditions before teams overfit the interface to an unrealistic task model.

Use contexts

Observation is used when:

  • workflow behavior differs from official process documentation
  • users perform tasks in constrained or high-pressure environments
  • staff mediate digital services for citizens or customers
  • teams need to understand interruptions, handoffs, and workarounds
  • usability problems may be shaped by physical, social, or institutional context

Application guidance

Observation should have a clear focus. Researchers may observe a task, a service point, a staff role, an environment, or a handoff between actors.

Observation notes should distinguish between what was seen, what was inferred, and what participants later explained. When appropriate, observation should be combined with interviews or contextual inquiry to understand why people act as they do.

Practical example

A local government office introduces a digital dashboard for beneficiary enrollment. Officially, staff are expected to enter applicant information directly into the system.

Observation during peak service hours shows a different process. Staff first sort paper documents, ask applicants to wait while supervisors check eligibility, write temporary notes on paper, and only later enter data into the dashboard when connectivity stabilizes.

The observation reveals that the interface problem is not only form layout. The system also needs draft states, queue handling, offline support, staff role clarity, and better exception handling.

Interpretive boundaries

Observation does not automatically explain motives. Researchers may see what happens but still need interviews or follow-up questions to understand why.

Observed behavior may also change because people know they are being watched. Researchers should document the observation conditions and avoid overgeneralizing from a narrow site or short session.

Applied at Userhub

Userhub uses observation to understand real service environments, staff workflows, user behavior, and task conditions that shape digital interaction.

Observation is especially important when evaluating public-service portals, field data systems, institutional dashboards, and staff-mediated digital journeys.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

Angrosino, M. (2007). Doing Ethnographic and Observational Research. SAGE Publications.

Blomberg, J., Burrell, M., & Guest, G. (2003). An ethnographic approach to design. In J. A. Jacko & A. Sears (Eds.), The Human-Computer Interaction Handbook: Fundamentals, Evolving Technologies and Emerging Applications (pp. 964–986). Lawrence Erlbaum Associates.

Luff, P., Hindmarsh, J., & Heath, C. (Eds.). (2000). Workplace Studies: Recovering Work Practice and Informing System Design. Cambridge University Press. https://doi.org/10.1017/CBO9780511611797

Suchman, L. A. (1987). Plans and Situated Actions: The Problem of Human-Machine Communication. Cambridge University Press.

Cite this entry

APA

Userhub. (2026). Observation. UX Reference. https://userhub.com.bd/reference/observation/