|
Choosing the Next Paired-Comparison Question
|
|
| · | Concepts should be chosen by a method that gives the author as much control as possible over the interview, in terms of the complexity of the concepts and the number of questions asked.
|
|
|
|
|
| · | The design should be as "balanced" as possible. Observations should be spread as evenly as possible over all attribute levels, and the columns of the design matrix should be as nearly orthogonal as possible.
|
|
|
|
|
| · | We should ask the respondent questions that require careful consideration. There is no point in asking questions for which we already know the answer, such as "High quality at a low price" versus "low quality at a high price." We learn more if we choose concepts nearly equal in attractiveness.
|
| · | Count the number of times each pair of attributes has appeared together in any concept. Pick a set of attributes at random from among those whose members have previously appeared together the fewest times.
|
|
|
|
|
| · | For each of the chosen attributes, repeat similar logic to find levels that have been paired least frequently.
|
|
|
|
|
| · | Examine all possible ways of combining these levels into concepts (with just two attributes there are only two possible ways; with 5 attributes there are 16 ways. Find the pair of concepts most nearly equal in attractiveness, using the current estimates of the respondent's part-worth utilities.
|
|
|
|
|
| · | Randomly determine which concept will appear on each side of the screen.
|
| 1) It gives the respondent the impression that the system is paying attention to his or her answers, and it seems to be asking increasingly insightful questions.
|
| 2) It helps keep the respondent operating within the defined range of a response scale rather than at its ends.
|
| 3) It provides data on "tight" inequalities if estimation is later to be done by nonmetric methods.
|