Visiting your customers at their place of work ó sometimes called ethnography, shadowing, contextual inquiry or simply a site visit ó is the best way to understand the way people do their job. This understanding is central to doing great design as it helps you really understand the needs, motivations and goals of your users.
But if youíre not careful, itís easy to waste the opportunity and end up overwhelmed by what youíve observed.
Iíve been fortunate to work with a number of user experience researchers, and Iíve noticed they all tend to be detail-oriented, highly motivated and conscientious. But when I think specifically about the field researchers Iíve worked with who have stood out from the crowd, there are a handful of particular behaviours I see in each of them:
- They create a focus question.
- They audio record the sessions.
- They take photographs of the environment.
- They take great notes.
- They write up a short summary of their observation immediately.
Create a focus question
When you make a field visit to a customer, thereís so much to observe that itís been likened to drinking from a fire hose. So before carrying out the visit, highly effective field researchers create a focus question to zero in on the aims of the project. A focus question ó sometimes called a hunt statement ó is usually expressed in this form: ďI am going to research [activity] so that I can [design a system].Ē An example of a focus question might be, ďI am going to research how our customers use our support materials so that I can design an online troubleshooting tool.Ē The focus question helps you concentrate on the observations that matter and prevent you from treating every observation as equal in value.
Practical tip: Iíve noticed that highly effective field researchers donít create the focus question in isolation but develop it by working with the project team. A simple and quick technique (first described by Teresa Brazen as a way of engaging school children in user research) is to use a sticky note activity, where you give the project team 5 minutes to brainstorm all of the questions they would like to ask their users. Tell them to write each question on a sticky note, one question per sticky note. After 5 minutes, all the sticky notes are placed on the wall and the team first arrange the questions into groups and then vote for the most important group. That group of questions then becomes the articulation of the focus question.
Record the session
You need to record the session because the participant's verbal protocol is central to your later analysis. Unless youíre an expert at shorthand, youíll miss comments, phrases and some of the technical language that the participants use. Even if youíre great at shorthand, youíll still miss intonation. Recordings are so important for a proper, in-depth analysis that highly effective field researchers get the sessions transcribed. Typically this costs around £1 per minute of audio, so if you run 15, 1hr sessions it will cost you £900 (about $1400). This isnít cheap, but you need to balance the price against the time youíve spent setting up the field visit, travelling to the location and collecting the data. Reviewing the transcript in depth is the most important analysis step youíll make.
Our friends at Adaptive Path like to video record their ethnographic observations. I've found that this is feasible in large, relatively anonymous spaces such as manufacturing plants and production lines, where you are able to set up a camera and film a large area in long shot (very much like the view of a ceiling-mounted surveillance camera). But in an office space — even a large office space such as a call centre — video recording participants is risky, for three reasons:
- To video record on business premises you need to ask for permission from a very senior person in the organisation ó and this is often all it takes to have the whole visit cancelled. (ďWhy are they doing this anyway?Ē)
- Video recording draws attention to the observation and changes the behaviour in the workplace, with employees understandably anxious that management might use the videos to rate their performance.
- Commercial confidentiality and data protection issues mean that it just isnít feasible in many situations (for example, when a customerís personal data appears on the participantís computer screen).
Audio recording on the other hand is usually possible in most environments. Because it's more discreet, you donít need to ask permission before your visit: you can wait until you start the observation. I ask permission by trying not to make too a big deal of it: ďIíll be taking notes during our interview, but if itís OK with you Iíd also like to record the session as I canít take notes quickly enough.Ē I also make it clear how the recordings will be used: ďThe recording is just for my purposes and anything you tell me will be kept confidentialĒ. Itís also easy to pause the recording if sensitive data gets discussed, like when a customerís credit card details are read over the phone. When I get the transcriptions, I change the participantís name along with any other information in the transcript that could identify the participant.
Practical tip: You can keep transcription costs low by supplying the transcriber with high quality audio recordings. We like the Olympus LS-11 PCM because the audio quality is outstanding — it's like listening to a DAB radio broadcast.
When you enter a new environment, thereís often so much going on, youíre not sure what to record. The risk is that youíll review your notes and transcripts later, only to realise that you canít recall a key element of the environment. Highly effective field researchers tend to take three kinds of photograph:
- Pictures that show the overall context, such as photographs of the exterior of the building and pictures of the entire office.
- Pictures that show the participant alongside other people and objects in the environment.
- Close-up photographs of the participant interacting with specific objects in his or her environment.
Once again, you need to ask permission but in my experience people are quite happy for you to take photographs so long as they know how they will be used. Itís even easier to ask if you wait until the end of the session and give the participant a gift before asking (such as some chocolates).
Practical tip: If you really, really canít take photographs, you can always make a sketch. These donít need to be works of art, but useful prompts to remind you about the relations between people and things in the environment.
Take great notes
Although youíll be audio recording the session, donít use this as an excuse not to take notes. The audio recording saves you from having to write extensive verbatim quotations, but it wonít tell you about the participantís behaviour and environment.
The challenge when youíre taking notes is to make sure that your note taking doesn't disrupt your relationship with the participant. You need to choreograph your note taking so that it is balanced with appropriate eye contact, other signs that youíre attending (ďuh-huhĒ) and behavioural observations. Despite these constraints, Iíve noticed that highly effective field researchers somehow manage to take around 4 pages of A5 notes (steno-pad pages in the US) for each 30-minute observation. They also reserve the first page of their notes for any abbreviations and jargon that they hear: this quickly builds into a useful glossary.
My experience working alongside less experienced researchers is that they try to write down everything people say — even when they have an audio-recorder running. The moment the respondent's mouth opens you can hear them scribbling. Hiding behind a notebook is a sure way to miss observations and is very distracting for the participant. So knowing what to write in your notes is important. In addition to a few quotes (the ones that really strike you) you should jot down ideas, key themes as they start to form, and also questions that you want to ask later in the discussion.
Practical tip: If you find that your mind goes blank and youíre not sure what to write down, try the ĎAEIOUí method. This acronym stands for Activities, Environments, Interactions, Objects and Users:
- Activities are goal directed sets of actions ó things that people want to accomplish. What primary activities do users need to perform to meet their goals? What do users mention first? Which action words (verbs) do they use?
- Environments include the entire arena where activities take place. Take photographs or make a sketch of the environment where the action happens.
- Interactions are the exchanges between a person and someone or something else. What are the intermediate steps or tasks in the process? What steps does the user enjoy most? What are the userís pet peeves? Who reviews or authorises the work?
- Objects are the artifacts that people interact with. What physical items does the participant interact with? What software does the participant use?
- Users are the people providing the behaviours, preferences and needs. What are the participantís goals, attitudes and motivations? What are the participantís capabilities with the product domain and with technology? What education and training do participants have?
AEIOU is just one of several frameworks for making ethnographic notes, but itís the one I find most useful for user experience observations.
Summarise observations immediately
How often have you turned to your notes a week after taking them, only to realise that you canít remember what on earth you were thinking?
This experience is even worse if youíve observed 4-6 people in a single day, as they all begin to blend into one another. Because of this, highly effective field researchers always schedule around 15 minutes after each participant to summarise what they have learnt.
Practical tip: To make sure you create an accurate summary, try using a standardised form. You will customise this for each project, but in general it will include some demographic information (like gender and age), a description of the context, any stand-out observations or user stories and a description of similarities or differences with other observations that youíve made (this last information is useful if you want to create personas as it helps you group participants). The image below shows an example of a form I use.
Figure 1: Use this form to summarise your observations like a pro
Try it yourself
Although a site visit may take just a few days, if you do it right youíll find yourself returning to your recordings, photographs, notes, and summaries for months afterwards. Itís an activity that just keeps on giving. This is because it provides the key data that you need to generate red routes, build personas, create mental models, craft user stories and understand the context of use.
Next time you get the opportunity to visit a customer, behave like a highly effective field researcher and you'll discover how much easier this makes your life as a designer.
About the author
Dr. David Travis (@userfocus on Twitter) is a User Experience Strategist. He has worked in the fields of human factors, usability and user experience since 1989 and has published two books on usability. David helps both large firms and start ups connect with their customers and bring business ideas to market. If you like his articles, why not join the thousands of other people taking his free online user experience course?
Foundation Certificate in UX
Gain hands-on practice in all the key areas of UX while you prepare for the BCS Foundation Certificate in User Experience. More details
Every month, we share an in-depth article on user experience with over 10,000 newsletter readers. Want in? Sign up now and download a free guide to usability test moderation.
User Experience Articles
Our most recent articles
Our most commented articles
Search for articles by keyword
- 7 articles tagged accessibility
- 4 articles tagged axure
- 5 articles tagged benefits
- 16 articles tagged careers
- 8 articles tagged case study
- 1 article tagged css
- 8 articles tagged discount usability
- 2 articles tagged ecommerce
- 17 articles tagged ethnography
- 14 articles tagged expert review
- 2 articles tagged fitts law
- 4 articles tagged focus groups
- 1 article tagged forms
- 6 articles tagged guidelines
- 11 articles tagged heuristic evaluation
- 7 articles tagged ia
- 14 articles tagged iso 9241
- 11 articles tagged iterative design
- 2 articles tagged legal
- 11 articles tagged metrics
- 3 articles tagged mobile
- 8 articles tagged moderating
- 3 articles tagged morae
- 2 articles tagged navigation
- 9 articles tagged personas
- 15 articles tagged prototyping
- 7 articles tagged questionnaires
- 1 article tagged quotations
- 4 articles tagged roi
- 17 articles tagged selling usability
- 12 articles tagged standards
- 47 articles tagged strategy
- 2 articles tagged style guide
- 4 articles tagged survey design
- 5 articles tagged task scenarios
- 2 articles tagged templates
- 21 articles tagged tools
- 57 articles tagged usability testing
- 3 articles tagged user manual