Tag: Branching Logic

Key Takeaways Branching exists to remove questions, not add them. The goal of every branch is a respondent who never sees an irrelevant question — not a more elaborate survey. Design the “no” path as carefully as the “yes” path. Most abandoned branching surveys fail on the answer the designer didn’t plan for, not the one they did. Shallow beats clever. Two or three branch levels cover almost every real use case; anything deeper usually means the survey is trying to do too much. Every path needs to be walked, not just the main one. A branching survey that’s only ever tested top-to-bottom will have broken paths nobody’s found yet. A branching survey shows or hides questions based on how someone answers the ones before it — so a respondent who says “no” to owning a car never sees three follow-up questions about their commute. Done well, it feels like the survey is paying attention. Done poorly, it feels like a maze: dead ends, questions that don’t make sense given what was already answered, or a “back” button that undoes more than intended.