Tools of Observation — When You Don't Know What Users Are Doing
Introducing eleven observation tools to reach for when you can't tell what users are doing or why. From Shadowing to ZMET, we look at each tool's use and its limits.
These are the tools you reach for when you don’t know what users are doing.
We’ve talked about the iceberg of cognition, and about the vortex of behavior. Consciousness, the part that surfaces, is only a fraction of the whole, and the real substance of what a user actually experiences is buried in unconscious behavior — that was the claim. So how do you capture that behavior? Every tool introduced here starts from the same question: “What is the user doing right now, and why are they doing it?”
None of these tools belong to a single project phase. You can use them early on to discover problems, bring them back mid-design to test hypotheses, or deploy them after launch to trace unexpected usage patterns. The moment a question comes to mind is the moment to use one of these tools.
Shadowing
“In what actual order, and in what context, does this user act?”
A method where you select a specific user and follow their every move as they perform a target task. The observer becomes the user’s shadow, recording the flow of behavior as it unfolds in their environment, unaltered.
The key, as the name implies, is to become a shadow. The observer’s greatest enemy is the Observer Effect — the fact that the act of observation itself influences the user being observed. The moment a user becomes aware of the observer, their behavior loses its naturalness and turns into “behavior performed for an audience.” The skill lies in erasing your own presence. It’s not about making the observer comfortable for the user — the observer must become part of the environment itself.
Shadowing is the most direct tool for capturing a user’s unconscious behavior — not Activity, as discussed in the earlier post on behavior, but Behavior itself. However, since it can only follow one user deeply at a time, it suits gaining depth in an individual experience more than surveying patterns across a wide population.
Town Watching
“What patterns do people show overall in this place?”
A method where you post up in a specific location and observe an unspecified number of users. If Shadowing is a tool for following one user deeply, Town Watching is a tool for broadly collecting behavioral patterns from many people in one place.
You take a position in the target environment — a café, a store, a hospital waiting room, a subway station — and observe the flow of people. It’s hard to understand any individual user’s context deeply this way, but the method excels at surfacing recurring behavioral patterns: hesitation at a particular spot, movement that diverges from expectation, unconscious avoidance behavior.
One thing to watch for is the observer’s own bias. It’s easy for the eye to be drawn only to “interesting” behavior, when it’s often the unremarkable, repetitive behavior that reveals a user’s unconscious cognition.
Behavioral Mapping
“What patterns emerge when you overlay users’ behavior onto a space?”
A method of visualizing users’ movement or behavior on a two-dimensional plane for analysis. By recording the results of direct observation spatially, you can uncover patterned regularities that aren’t visible in any single instance of behavior.
Overlay the paths of multiple users onto one map, and stalling, detours, and backtracking at specific points become visually apparent. The earlier post on behavior covered the case of a shopping mall’s elevator — Behavioral Mapping is useful for uncovering exactly that kind of problem. You can’t directly ask a user what they were thinking, but you can infer it from the pattern that many overlapping paths create.
This tool is rarely used on its own; it’s more often used as a follow-up to organize and interpret data gathered through Shadowing or Town Watching.
Eye Tracking
“Where is the user’s gaze actually landing?”
A method that tracks a user’s eye movements to record exactly where they’re looking on a screen or in a space. A user saying “I saw this button” and their gaze actually having landed on that button are two different things. Eye Tracking turns this gap into data.
It’s one of the most direct tools for measuring unconscious cognition, but it comes with high equipment costs and constraints on the experimental environment. It also tells you “where” someone looked, but not “why.” Gaze data isn’t an answer in itself — it’s a clue that only gains meaning when interpreted alongside other observation tools.
Diary Study
“How does a user’s experience change over time?”
A method that asks users to record their own experience over a set period. It’s useful for capturing situations an observer can’t always be present for — everyday context, long-term usage patterns, emotional shifts over time.
This is the archetypal indirect-observation tool. Its strength is gathering experience from a user’s natural environment without an observer needing to see it firsthand. But keep in mind that the act of recording can itself distort the experience, and results can be skewed by the recorder’s own subjectivity. Since users only record what they’re consciously aware of, unconscious behavior remains this tool’s blind spot.
Interview
“How does the user themselves perceive their own experience?”
A method of meeting a user face to face and asking directly about their experience. It’s the most familiar and accessible tool — and also the one that demands the most caution.
Problems a user is consciously aware of — “this button is too small,” “loading is slow” — are relatively easy to surface through interviews. But as the earlier post on cognition showed, most cognition sits below the threshold of awareness, so users themselves often can’t accurately explain the substance of their own experience. When an answer comes back as “I don’t know why, but something about it feels off,” that’s not a limitation of the interview — it’s a feature of how cognition is structured. Answers can also be easily skewed by how the interviewer leads the questioning.
Interviews are effective for confirming a user’s conscious awareness, but identifying the cause of unconscious behavior requires pairing them with other observation tools.
Survey
“What experience do users commonly, consciously recognize?”
A method of collecting quantitative data from a large number of users through structured questions. If interviews are a tool for depth, surveys are a tool for breadth.
Surveys are clearly cost-effective and can gather data at scale, but they inherit all the limitations of interviews and add a new one on top: bias in question design. The order of questions, the structure of the answer choices, the choice of wording — all of it can distort responses. What a survey can capture is limited to the range of experience a user can consciously recognize and put into words; the unconscious behavior beyond that range is out of reach.
FGI (Focus Group Interview)
“Does the conversation within a group surface experiences an individual wouldn’t consciously recognize alone?”
A method where you recruit a representative group of target users to have a free-flowing conversation about their experience, guided by a moderator. It’s widely used in practice, and also one of the most rarely used correctly.
The essence of an FGI is not “group interview” but “group conversation.” It’s often run as little more than a one-to-many interview with several people at once — that’s the wrong way to do it. The core of an FGI is that free conversation among participants stimulates each other’s memories and experiences, letting unconscious experiences that a person sitting alone would struggle to recall surface naturally within the flow of the conversation. The moderator’s job is to design and sustain that flow — and, just as importantly, to observe and collect participants’ unconscious reactions and behavior from a third-party vantage point: facial expressions, gestures, shifts in speech pace, avoidance of certain topics.
A relaxed atmosphere is a precondition. The goal is to draw out stories buried in the unconscious by chatting casually with an experienced group about their experience — not to collect answers to a fixed set of questions.
Contextual Inquiry
“Can you trace the reasons behind a behavior together, in the very context where the user actually does their work?”
A method of observing a user while simultaneously asking questions, in their actual working environment, while they carry out a task. It can be thought of as combining the on-the-ground quality of Shadowing with the explanatory power of an interview.
The observer takes the posture of an “apprentice.” The user is the “master,” and the observer acts like someone there to learn the craft, naturally asking “why did you just do that?” This captures behavior while also confirming, on the spot, the context and reasoning behind it.
Two things to watch for. First, questions must not interrupt the observation. If questions come frequently enough to break the flow of the work, the naturalness of the observation suffers. Second, you have to distinguish between a user’s real reason and post-hoc rationalization when they explain their own behavior. Users often answer “why?” not with the actual reason but with a plausible-sounding one they construct on the spot. This, too, is a feature of cognition covered in the earlier post on the subject.
Personal Inventories
“What do the objects a user carries reveal about their mental model?”
A method of examining the personal items a group of users habitually carries in order to infer the mental model they’ve formed about a subject.
Experience is an abstract image, and that abstractness is sometimes revealed more clearly through objects than through language. What items a user carries, and how they organize and use them, indirectly shows that user’s values, priorities, and way of perceiving the world. Because this tool doesn’t rely on a user’s verbal self-report, it can compensate for the blind spots of interviews and surveys.
Cultural Probes
“What cognitive clues are embedded in the everyday things users make?”
A method of giving users tools — a camera, a diary, a map, postcards — and asking them to freely document their experience and environment over a set period. It resembles a Diary Study, but differs in that the medium of recording isn’t limited to language and extends into images and objects.
The premise of this tool is that experience isn’t captured by language alone. The photos users take, the drawings they make, the objects they collect all become clues that reveal the user’s cognitive world in their own right. That said, these clues require interpretation, and the quality of the result depends heavily on the interpreter’s skill.
ZMET (Zaltman Metaphor Elicitation Technique)
“When a user’s experience is expressed through images and metaphor, does it reveal cognition that language can’t reach?”
A method where you have users collect images (photos, pictures) related to an experience and talk through their own interpretation of those images, in order to extract the abstract cognitive structure underlying that experience.
The core insight behind this approach is that experience is, by nature, an abstract image — and so the clues for inferring it can be gathered more richly through images and metaphor than through verbal statements. Ask a user “please describe your experience,” and you only pull up what’s floating on the surface of consciousness. Ask them “please choose an image that represents your experience,” and you open the possibility of drawing up the sensory, emotional dimensions that lie beneath the surface.
That said, this is among the most abstract of the observation tools, and the process of interpreting the collected metaphors inevitably involves a heavy dose of the analyst’s own subjectivity. It’s better suited to gaining qualitative insight into a user’s cognitive world than to producing rigorous quantitative results.
Each of these tools has its own strengths and blind spots, and in real projects they’re rarely used alone — they’re more often woven together. You visualize a behavioral pattern found through Shadowing with Behavioral Mapping; you confirm, on the ground with Contextual Inquiry, a clue to experience that surfaced in an FGI; you explore, in an interview, an image obtained through ZMET, in greater depth.
But whichever tool you use, and however skillfully you use it, one principle doesn’t change. The goal of these tools is to empathize with the cognition underlying a user’s surface behavior and representations. Fail to empathize — fail to synchronize with the user — and countless observations amount to nothing but the superficial. That costs a great deal and can end up accomplishing less than simply sitting and meditating on the user.
No tool means anything if it fails to synchronize with the user.
Having looked at the tools of observation, the next post turns to the tools of analysis — the tools for reading structure and meaning out of the data that observation accumulates.