originally published mddi september 2001
design & development
product developers who observe end-users' behavior in the actual environment of use generate tangible, workable information about a device—and the requirements of the people who use it.
stephen b. wilcox and william j. reese
|a multitude of devices confront clinicians on a daily basis.|
in new product development, one of the central questions—if not the central question—is how do manufacturers determine what people want and need? without a clear picture of what users need, it is impossible to channel corporate resources to yield results. there is nothing more counterproductive and frustrating than coming up with solutions to the wrong problems—but such scenarios are difficult to avoid without good, solid information about what product users want and need.
how, then, does one go about this? in practice, companies often rely on what people say. verbal behavior is the foundation of the overwhelming bulk of customer research. marketers make much of the difference between qualitative and quantitative research, but these terms describe variations on the same theme: both are based solely on what people say—either in groups or individually, in person or over the phone, on paper or on the internet—rather than what they do and how they do it.
when manufacturers and marketers rely solely on what users say, they fall victim to the fact that people often have difficulty describing what type of product they need or want. end-users typically cannot express their precise problem with a given device only by talking about it. this phenomenon occurs for several reasons.
one problem is that many important user issues are not particularly part of conscious awareness. if a device works correctly, operators don't necessarily notice how they hold the instrument or what exactly takes place when they use it. it is only when something goes wrong that they notice it. indeed, as people become more expert with a task, they are less conscious, not more, of what they do. when learning a new procedure, a surgeon is likely to be highly aware of each hand movement, but after countless procedures, he or she is more likely to carry on a conversation about a recent golf game than to focus on the intricacies of a particular device.
when answering questions about the past, people are subject to various errors. they conflate events that happened at different times; they remember events in such a way that they conform to what they expect; they are highly influenced by the way questions are asked.
another problem is that people have all sorts of agendas that interfere with strict accuracy. they develop opinions about what interviewers want to hear and consciously or unconsciously tailor their statements to fit these opinions. they see themselves as possessing qualities that they do not really possess, so they answer questions for their "ideal" selves rather than their real selves. they are embarrassed to admit that they have problems with products because they fear those problems might reflect poorly on their abilities.
also, to avoid sounding ignorant, people sometimes give answers to questions even when they have no idea what the correct answers actually are. another issue is that people differ enormously in their ability to express themselves. some people can paint an accurate picture with words, but many people cannot.
these commonplace examples of fallibility have been well established by empirical research. for example, several years ago, a. w. wicker reviewed 48 studies that compared actual behavior to peoples' allegedly objective descriptions of that behavior.1 he found a weak correlation between speech and behavior. elizabeth loftus, in her book, eyewitness testimony, showed in study after study that peoples' descriptions of past events are highly fallible.2 new information can be introduced into a person's memory by a later conversation, for example, or parts of an event can be transposed into another event.
if there are inherent dangers in trusting what people say, why do product developers rely so heavily on exactly that? this article explores an another option: ethnographic research.
ethnographic field research
ethnographic research can augment—even supplant entirely—the traditional means of interviewing end-users about a device. as a methodology it stems not from psychology, but from cultural anthropology, and so involves the study of people's behavior in the actual "environments of use" to generate insights about their needs. it means going to wherever people routinely use a given product, from operating theaters and radiology suites to waiting rooms, cafeterias, and even patients' homes.
if the product is not yet available, researchers make every attempt to observe users working with something like it—a prototype, for instance, or a competitor's product.
it is vital to observe behavior in the environments of use because each such environment is unique. differences in use environments make it impossible to know without seeing firsthand what conditions most crucially shape the success or failure of a device.
if surgeons will be using a device in the operating room, researchers need to observe them using the product there, because nobody could reproduce artificially the sounds, distractions, and relationships that characterize that highly specific milieu.
|video ethnographic research in the cardiac catheterization lab.|
the story is the same regardless of the environment. if people will use a device in their homes, then it is vital to learn how patients with the medical condition that the device treats actually behave with the product in their own homes. their usual careful performance with log books, touch screen displays, and hypodermic needles may be compromised when they come home after a long day at work, or when they wake up in the middle of the night.
firsthand knowledge. observing users in their natural habitat helps new-product developers understand the product's strengths and limitations from the user's point of view. but there are many additional benefits. by watching end-users interact with the device, researchers can see behaviors that reveal product performance attributes even when the users don't say a word.
video documentation. one way to make certain that the analysis is detailed and comprehensive is to document everything on videotape. video documentation helps analysts take apart complex events and interactions that happen in rapid succession—such as special hand movements, gestures or facial expressions, offhand verbal statements—and look at each one in turn.
after viewing videotapes of user after user having difficulty aligning two key components of a device (despite their insistence to interviewers that this was not a problem in the procedure), designers might decide not to include those components in the development program. developers could also come away from the discovery process with a more realistic assessment of some common user complaints, and a better understanding of which issues need attention as opposed to those that don't reflect an underlying problem in product quality.
richer information. when compared with focus groups, surveys, and even one-to-one interviews, the discovery process of ethnographic research yields information that is typically more rich, vivid, and concrete. this is because working in a naturalistic context enables researchers to ask people questions while they use the product (or, at the very least, immediately before and after).
why is this important? timing and context have a huge impact on the responses to questions. in the case of design research, there are at least two big advantages to conducting interviews when people are using the product. the first is that they literally remember more. the second is they tend to give more specific and useful answers.
people remember more while they interact with the device because the activity of using the product itself becomes a mnemonic system—it gives users a host of real-world, real-time cues to help them answer questions. through the practice of "ask-and-watch," the interviewee is more likely to recall long-forgotten or disregarded concerns about the product than if he or she were asked about it outside the context of use.
by combining observational research with interviewing, researchers frequently hear comments such as, "oh, i forgot to tell you about this problem," and "i guess i am having a little difficulty here. i never thought about it before—you just become so used to doing things."
the second advantage of on-site interviewing is that the observations people make tend to be more specific and useful than they would be if they had to think of them out of context—on the phone, say, or in a focus-group setting. for example, if researching a new type of self-administered therapy, product developers who visited patients' homes would discover a wealth of information. when asked out of context to discuss the kinds of mistakes they make when using a particular device, patients might volunteer very little information, at first. when they are observed actually using the device, however, the patients tend to become more vocal and list the different errors they often make. patients might point out tasks they were performing out of sequence, buttons they pushed by accident, and tubing connections they failed to secure when they were tired or ill.
questions about the device might get the patient thinking, but actually using the device is what gets them talking.
methodology: understanding the worldview
conducting ethnographic field research is, of course, not quite as simple as just going into the field. if all that product developers needed to do was watch and take notes, everybody would be doing it. according to a study of successful new products over a decade, almost two-thirds of senior executives were disappointed with the results of their firms' new-product programs.3
to be successful, fieldwork depends on adherence to a methodology. the approach under discussion relies upon the framework provided by ethnography. literally meaning "writing about culture," the term and concept of ethnography describes the attempt to understand the beliefs, customs, and rituals of people in different types of societies.
the main principle of successful ethnography is this: understand the subjects' worldview. doing so is not the same thing as merely listening to their opinions. understanding their worldview means discovering their values and norms, identifying their goals and expectations, and determining some of the basic ways they divide space and fill up their days.
casting the net broadly in this way does not provide quick-and-dirty answers. but it can offer a measure of insurance that developers won't miss anything critical that could make or break the new product.
consider the modern pacemaker-defibrillator, a device that neatly straddles the professional worlds of the electrical engineer and the cardiologist, and whose widespread use has helped give rise to the hybrid discipline of electrophysiology. electrical engineers have had a difficult time for years trying to develop a user interface for pacemaker programming that cardiologists will find easy to use. why? because to do it, the device manufacturers essentially need to learn how physicians think. they need to know, for instance, what day-to-day professional language cardiologists and electrophysiologists use, which diagnostic categories are most critical to them, and how they arrive at specific treatment plans.
to develop a user interface that physicians would find intuitive, and which would therefore greatly enhance its value to them, would require understanding their professional worldview in some detail. and yet the world of cardiologists and electrophysiologists is something to which few people, apart from the doctors themselves and others they work with closely, are privy.
rapport. the question then becomes, how does one gain access to such a unique and specialized world? the short answer is: by shadowing the people who live in it, by talking with them and observing them, and then by trying to understand their perceptions of the product.
this objective introduces a slew of new challenges, of course. first and foremost is the simple but often underestimated fact that people cannot be forced to tell researchers what they want to know. short of some pressing utilitarian reason—such as the outright failure of a product—people simply will not share their real feelings, at least not to the level needed to provide a clear understanding of their personal situation, unless they have some authentic, interpersonal basis for interacting with the researcher.
thus, the main ingredient in successful ethnographic work is rapport—developing relationships with people. these needn't be long-term relationships, of course, but short-term relationships characterized by basic expressions of trust and mutual goodwill.
often, it is enough for informants to know and believe that researchers have a genuine interest in their personal situation, and in the difficulties and successes they experience with the product. but it also helps simply to spend time with them.
though it sounds easy enough, many people who conduct traditional market research simply don't follow this principle. a common mistake made while interviewing, for instance, is attempting to extract answers to "bad" questions—questions the data are proving to be on the wrong track. this is often a function of the need to generate statistics. but it makes no sense to amass answers that don't represent the end-users' opinions. when subjects bend their answers to fit bad questions, researchers learn little of value to the product's development.
instead, an ethnographer should take a more flexible view of the interview guide or moderator's protocol, encouraging the subject to talk about the product in his or her own words. rather than doggedly following a predefined route, which can exhaust interviewees or put them on the defensive, the ethnographer should talk around the subject, letting bits and pieces of relevant information gradually fall into place. in this way, the key questions nearly always get answered. in the course of informal give-and-take, some preplanned questions simply become obsolete, while other questions, inevitably, become better and more precise with an ever-improving knowledge of how informants think, speak, and act.
why do so many market research practitioners ignore this natural trajectory? there are many reasons, but all boil down to essentially one theme: the unfair expectation that the interviewee is responsible for answering the researcher's analytical questions.
in fact, informants can answer only questions that are put to them for purposes of gathering data. it is never their responsibility to provide a systematic analysis of their own behavior, nor, of course, to design products for manufacturers. rather, their insights, comments, behaviors, and ideas are useful only as data—to be compared with other data and applied in an analysis based on a far wider sample of behavior and comments, and which is informed by a broader experience of problems associated with the product than individual informants are in a position to command.
time as a magnifying glass
ethnography relies on a combination of smaller sample sizes and longer interaction times with informants than is typical in market research. spending time with informants is important, and it is the key factor that differentiates ethnography from other methodologies, such as surveys.
time is critical as well; understanding what someone needs is a complex and time-consuming process. just think how dimly most people understand their own needs with regard to many of the consumer products they use every day, from cell phones and tape recorders to dishwashers and vacuum cleaners. understanding what others need is considerably more difficult.
so it often takes some time for informants in a research program to really understand what the researchers are after, reflect on their experience, and generate helpful information. the best research takes place over a day, or even over several days—working with a team of nurses, for example, or shadowing a cardiologist during rounds.
on one hand, time helps establish good rapport. people tend to trust researchers more the more time they spend with them. as a result, informants begin to reveal more, both intentionally and inadvertently.
on the other hand, people need time to go beyond ideological responses. strangers who have just met tend to relate to each other in terms of hackneyed stories and canned speeches about themselves, to which they seldom attach much value. they speak less as individuals, and more as types.
a similar phenomenon is evident with professionals in positions of high responsibility, such as physicians, chief nurses, and hospital administrators. in many situations, they tend to speak from their role as the member of a group, and with the group's ideology and interests in mind, rather than from their viewpoint as individuals with their own idiosyncratic opinions and feelings.
this is acceptable when all researchers want is official opinions—the kind of thing one might read in a medical journal or in a hospital newsletter. but it is not acceptable when researchers want practitioners to express their own opinions. their responses do not count as good field data if they don't. and worst of all, if encouraged, group ideology will stifle the flow of authentic information.
for example, if an orthopedic surgeon in a focus group (or even in an anonymous survey) is questioned about the rate of infection at his hospital, he or she will likely provide the same numbers that could be read in a medical journal. but if a researcher asks that surgeon the same question at the end of a long day in which the researcher has participated in rounds, watched several surgeries, and heard the surgeon's explanations of surgical procedures, the odds are much better that the response will become clearer and more helpful—if not more honest.
so a good researcher will spend enough time to be able to recognize the interlocutor's ideology, and help him or her steer clear of it. the researcher will also be open to opportunities available in situations and spaces that offer less formality, such as the car on the way to the hospital, the office after the tape recorder is turned off, or the hallway during the minute or two after the interview. relevant information often emerges from the interstices of a formal discussion, not from its official center.
given time, not only may informants open up more, but they may bring to the surface of their own mind more of what they truly think and feel about a device. everyone has had the feeling of some word or phrase being "just on the tip of the tongue." some time later, the word or phrase surfaces out of nowhere. this is a common example of an important principle: the unconscious mind continues to work on a problem even when the conscious mind has abandoned it. in the same way, the quality of information tends to improve the longer an informant is permitted to ponder the question, meanwhile resuming his or her normal tasks.
what do the users of a product talk about when they are using it? what terms and expressions do they employ? what names for things (and persons) have they invented?
researchers who make the effort to learn about these things are well on their way to forming a map of their subjects' worldviews, and, correspondingly, a knowledge of key mental categories that shape their assessment of the product.
consider the following scenario: in a study of cardiac catheter labs in the united states, a manufacturer was on the verge of producing an innovation that could move in one or more of several directions—improving patient safety, supporting medical record-keeping, or decreasing costs all around. but to choose the optimal direction, the manufacturer needed to understand the dominant values in the cardiac cath lab.
interviews suggested that the dominant concern in clinicians' minds was to improve patient safety. during procedure after procedure, however, researchers found that documentation needs drove much of the activity in the lab—even the performance times of the procedures themselves. after observing numerous procedures, researchers determined that documentation was a much more crucial factor than they had initially believed.
but to make this determination, they first had to understand the culture of the cath lab. that meant developing a knowledge of the division of labor (e.g., nurse as computer "driver"), of the unique pace (how long is too long to complete a given part of a procedure?), and, especially, of the relevant language.
the terms that clinicians used were sometimes medical jargon ("rv/lv pressures"), sometimes slang (such as "pulling settings" from a hemodynamics monitor), and sometimes a combination or contraction of medical and slang terms ("thermals" for thermodilutions).
the researchers observed procedures in a live cath lab to gain a clear understanding of how things worked. in the lab, the technologist, out of the sterile field in a viewing room, preserved the record of each step on her computer, meanwhile keeping an eye on some of the patient's hemodynamic information, such as the heart rate and blood pressure readings.
examples like this drove home the importance of real-time recordkeeping during the cath lab procedures. indeed, full documentation was important enough to force the doctor to actually halt his procedure, momentarily, to allow the technologist time to clear a paper jam and to enter patient data.
the language of the cath lab reflected this social reality: the technician was in a number of important ways the driver of the procedure. chiefly, it was she who controlled the step-by-step documentation of each therapeutic maneuver.
ethnographic research is holistic. it requires researchers to look beyond the immediate answers to their initial questions and see the new product as part of the larger context of personnel, tasks, and incentives that its users confront on a daily basis.
in a study of behavior around office photocopiers, anthropologist j. blomberg discovered that office workers tended to define the term mechanical breakdown simply as any time the machine was unusable, not as when the mechanical components were physically damaged.4 as one might imagine, machines that happened to be in offices with a helper, someone available to clear paper jams and handle other minor problems efficiently, were perceived as more reliable than machines of the same type in offices lacking such an employee.
the example is a good one of how context defines meaning. had researchers been content merely to ask (as in a phone survey) how many times the machines in the office "broke down," they would have received a misleading impression.
from an anthropological perspective, such contextual definitions of device problems are wholly welcome and expected. of course, product users often define error, problem, and difficulty differently than product developers—they live with the device every day.
ethnographic field research is a crucial tool for the development of medical products. it is certainly not the only tool for determining what product users want and need, but it yields a depth and accuracy of results that are not available from any other approach. of course, conducting ethnographic research can be more difficult in various ways than conducting more-conventional research. but the results are worth the trouble.
1. aw wicker, "attitudes versus actions: the relationship of verbal and overt behavioral responses to attitude objects," journal of social issues 25, no. 4 (1969): 41–;78.
2. e loftus and g wells, eyewitness testimony: psychological perspectives (new york: cambridge university press, 1984).
3. rg cooper, new products: the key factors in success (chicago: american marketing association, 1990).
4.j blomberg, "social interaction and office communication: effects on user evaluation of new technologies," in technology and the transformation of white collar work , ed. r kraut (hilldale: lawrence erlbaum associates, 1987) 195–;210.
copyright ©2001 medical device & diagnostic industry