27.10.2014 Views

Russel-Research-Method-in-Anthropology

Russel-Research-Method-in-Anthropology

Russel-Research-Method-in-Anthropology

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Structured Interview<strong>in</strong>g I: Questionnaires 287<br />

pretest respondents, no matter whether you’re do<strong>in</strong>g face-to-face <strong>in</strong>terviews,<br />

CAPI, mail surveys, etc. In this method, people th<strong>in</strong>k out loud as they decide<br />

on how to answer each question <strong>in</strong> a survey. There are three alternative outcomes<br />

with the th<strong>in</strong>kaloud technique: (1) People understand the question just<br />

as you <strong>in</strong>tended them to; (2) People understand the question very well, but not<br />

the way you <strong>in</strong>tended them to; and (3) People don’t understand the question<br />

at all. Edwards et al. (2005) used this method to pretest a 28-question survey<br />

on the use of condoms by women sex workers <strong>in</strong> Mombassa, Kenya. The result<br />

was a survey with culturally appropriate vocabulary for various types of sex<br />

clients. (For more on the th<strong>in</strong>kaloud method, see DeMaio and Rothgeb 1996.)<br />

Never use any of the respondents <strong>in</strong> a pretest for the ma<strong>in</strong> survey. If you<br />

are work<strong>in</strong>g <strong>in</strong> a small community, where each respondent is precious (and<br />

you don’t want to use up any of them on a pretest), take the survey <strong>in</strong>strument<br />

to another community and pretest it there. This will also prevent the pretest<br />

respondents <strong>in</strong> a small community from gossip<strong>in</strong>g about the survey before it<br />

actually gets underway. A ‘‘small community,’’ by the way, can be ‘‘the 27<br />

students from Taiwan at your university’’ or all the residents of an Indonesian<br />

rice-farm<strong>in</strong>g village.<br />

If you have a team of face-to-face <strong>in</strong>terviewers, make sure they all take part<br />

<strong>in</strong> the pretest—and be sure to do some of the pretest<strong>in</strong>g yourself. After the<br />

pretests, br<strong>in</strong>g the <strong>in</strong>terviewers together for a discussion on how to improve<br />

the survey <strong>in</strong>strument. Ask them if people found some questions hard to<br />

answer—or even refused to answer. Ask them if they would change the word<strong>in</strong>g<br />

of any of the questions. Check all this yourself by watch<strong>in</strong>g a couple of<br />

<strong>in</strong>terviews done by people on your team and note when <strong>in</strong>formants ask questions<br />

and how the <strong>in</strong>terviewers respond. That way, you can tra<strong>in</strong> <strong>in</strong>terviewers<br />

to respond <strong>in</strong> the same way to questions from <strong>in</strong>formants.<br />

As you conduct the actual survey, ask respondents to tell you what they<br />

th<strong>in</strong>k of the study and of the <strong>in</strong>terview they’ve just been through. At the end<br />

of the study, br<strong>in</strong>g all the <strong>in</strong>terviewers back together for an evaluation of the<br />

project. If it is wise to learn from your mistakes, then the first th<strong>in</strong>g you’ve<br />

got to do is f<strong>in</strong>d out what the mistakes are. If you give them a chance, your<br />

respondents and your <strong>in</strong>terviewers will tell you.<br />

Cross-Sectional and Longitud<strong>in</strong>al Surveys<br />

Most surveys are cross-sectional. The idea is to measure some variables at<br />

a s<strong>in</strong>gle time. Of course, people’s attitudes and reported behaviors change<br />

over time, and you never know if a s<strong>in</strong>gle sample is truly representative of the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!