Ethnography for Understanding User Needs

Ethnography studies how people behave in real settings, helping teams uncover needs that surveys or hypothetical interviews may miss.

Understanding this reference

Ethnography helps product teams notice workarounds and unspoken constraints that do not appear in a questionnaire. It involves observing activities in their setting and interpreting behaviour cautiously with the people involved. A single unusual observation can generate a useful question, but should not be advertised as a finding about everyone in the population.

How to use the idea in practice

Start with a narrowly framed activity, permission to observe, a consent process, and a plan for protecting personal information. Watch the task from start to finish, noting pauses, interruptions, tools, collaborations, and the physical environment. Separate descriptions from interpretation in field notes. Ask follow-up questions that check whether the observer understood an action correctly.

Applied learning example

Imagine researchers studying how a clinic organizes appointment reminders. Rather than ask only whether staff like the software, researchers might document how paper notes and messages move between desks. They can identify a workaround that reduces missed reminders, prototype a clearer handoff, and test it with staff before proposing broader changes.

Questions to bring to a workshop

• What specific decision or problem gives this method a useful purpose?
• What do we know from direct observation, and what remains an assumption?
• Who experiences the change, including people who might otherwise be left out?
• What is the smallest credible pilot or comparison we could run?
• Which evidence would persuade us to change direction rather than defend the plan?

Evidence, limitations and responsible interpretation

Observation can change behaviour; power differences affect what participants disclose. Do not infer motivations from a gesture without asking. Protect identifiers, avoid recording people unnecessarily, and report uncertainty. Good ethnographic writing makes clear what was actually seen, what was reported by participants, and what remains a plausible interpretation.

The original destination is retained as a historical reference point. The writing above is a contemporary educational explanation; it must not be cited as a recovered source or used to attribute a statement to the former portal. For related research, consult ASQ: Plan–Do–Check–Act and follow its primary references where appropriate.

Documenting a meaningful result

Write a method note that distinguishes a research question, participant or data selection, procedure, observations and interpretation. For Ethnography for Understanding User Needs, describe limitations openly: sample size, missing perspectives, ambiguous measures and the influence of the setting. Keep consent, confidentiality and possible unintended consequences visible rather than treating them as paperwork. If another team cannot tell what was observed and which assumptions remain, the activity is not documented well enough to support a design decision.

Before calling an exercise complete, ask who could challenge the conclusion, which trade-off remains unresolved, and what would count as persuasive counterevidence. Make the reasoning legible to someone who was not in the original meeting. When appropriate, ask users or affected stakeholders to review the interpretation before a proposal becomes policy. Evidence-based work is less about producing perfect certainty than about making choices open to correction.

Continue with the innovation toolkits, or browse the research and case-study collection to compare approaches across settings.