Be careful when using “negative” logic conditions
Think twice, especially when using “negative” logic conditions such as “is not”, “does not contain”, or “is not equal to”. They’re pretty tricky and can cause problems. Negative logic conditions such as “is not”,
“does not contain”, or “is not equal to” can save you time, because usually they can accomplish
the same result as positive conditions, but with fewer clicks and less complicated flows. However,
it is important that you remember, the negative logic conditions get triggered, only if the
question is actually answered by the participant. If the question is skipped, our system does not
care about the negative conditions. To make this easier to understand, let’s look at this NPS example:
How likely are you to recommend our company to a friend?
- 0
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
Not at all likely
Extremely likely
The example above shows a Net Promoter Score® (NPS) question.
Some respondents are hopefully “promoters” (those who choose 9 or 10) and some are “detractors” (those
who choose 0 to 6). But you specifically want to ask the “passive” group (those who choose 7 or 8),
this a series of follow-up questions and evaluate what could become better in your company, for them
to choose 9 or 10? So you include those questions which are directed to the passive group, in page 2
of your survey, and then formulate the following logic flow:
Logic Flow #1
IF
How likely are you to recommend our company to a friend?
- 0
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
Not at all likely
Extremely likely
THEN
end of logic flow
Note:
Please note that this types of problems are NOT always limited to negative logic conditions.
They may also happen, even if you set up the logic flow, using positive logic conditions. For
example, you would face the same issue even if you made your logic flow like this: if answer
to this NPS question is 0 or 1 or 2 or 3 or 4 or 5 or 6 or 9 or 10, then skip to page 3.