Outcome Mapping
Outcome mapping is the process of defining rules that connect a respondent's quiz answers or score to a specific result, offer, or next action.
Key takeaways
- Each row pairs a condition over the answers with a concrete consequence.
- Rules evaluate in order, so a broad row can make later rows unreachable.
- Coverage means every reachable answer combination matches at least one row.
- Overrides that ignore the score make maps powerful and harder to predict.
- Adding a question changes the maximum score and can shift every band.
In depth
An outcome map is a table of conditions and consequences. Each row states a condition over the collected answers, whether a score range, a specific answer, or a combination of several, and names what should happen: which result the respondent sees, which tag is written, which owner is assigned. The engine evaluates the rows in a defined order and applies the first match, which makes order part of the logic. A row placed above another can leave the one below unreachable.
Two properties decide whether a map holds together: coverage and precedence. Coverage means every reachable answer combination matches at least one row. Precedence means overlapping rows resolve predictably. Adding override rules, such as sending any regulated industry to the top outcome regardless of score, is what makes maps genuinely useful and also what makes them fragile, because each override cuts across the score logic. The more overrides you add, the harder any given path's destination becomes to predict.
Teams usually keep the map somewhere they can read as a whole rather than only inside the funnel builder, because reviewing rules one screen at a time hides conflicts. In a scorecard funnel the map drives more than the page: it decides which result sections render, which lead-capture fields appear, and which segment value reaches the CRM. Reviewing it belongs to the work of adding a question, since a new question changes the maximum score and can shift every band.
A map only routes what it can see. Anything the quiz did not ask about, and anything a respondent misreported, is invisible to it, so an outcome can be confidently wrong. Maps also age badly: rules written for an old offer keep firing long after the offer is retired, and nobody notices because the funnel still appears to work. Set a review point, and treat an outcome nobody has received in months as a rule to delete rather than a rare edge case.
Example in practice
How to measure it
The first check is the share of completions that land on the default or fallback outcome. That number should be near zero, and anything above a few percent means the map has gaps rather than that your respondents are unusual. Break the fallback cases down by the answers that produced them, because the pattern usually points at one question added after the map was last reviewed.
Then look at how completions distribute across outcomes and compare that with what you intended. An outcome that has never fired is either an unreachable rule or a condition nobody meets, and both are worth removing. Track the distribution after each rule change so a shift can be attributed to the edit rather than to traffic, and keep a dated note of what you changed.
Common mistakes
The first failure is building the map only inside the editor, one rule screen at a time. Conflicts and gaps stay invisible that way, because you never see two rules side by side. Keep the whole map in one readable table listing every condition and its destination, and walk a few deliberately awkward answer paths through it by hand before launch, including the all-lowest and all-highest cases nobody thinks to test.
The second is adding an override rule without deciding where it sits in the order. An override for regulated industries placed below a score rule never fires at all, while one placed at the very top silently catches cases you never intended to divert. Write the precedence down explicitly, and after each new rule re-test one path that should still reach every existing outcome, so nothing quietly becomes unreachable.
Frequently asked questions
How is outcome mapping different from a result archetype?
An archetype is the named result a person receives, while outcome mapping is the rule set that decides which archetype and action each answer path triggers. Mapping is the logic; the archetype is the destination.
What happens if my outcome map has gaps?
Respondents whose answers fall outside your rules either hit a generic default or, in poorly built funnels, no result at all. A complete map covers every score range and answer combination so no respondent slips through.
Can a single answer override the score in mapping?
Yes. Many funnels use override rules where a specific answer, such as company size or industry, forces an outcome regardless of total score. This handles qualification signals that scoring alone would miss.
How do I make sure my outcome map has no gaps?
Work from the answer side rather than the rule side. List the possible values of every question that appears in a condition, then confirm each combination reaches a row. For score-based rules, check that the bands are contiguous and cover the full range your weights can produce, including the theoretical minimum and maximum totals nobody expects to see.
What order should the rules be evaluated in?
Put the most specific conditions first and the broadest last, so a narrow override is reached before a general score band catches it. Document that order somewhere outside the tool. Whenever you add a rule, decide its position deliberately rather than appending it, because appended rules often sit below something that already matches the same cases.
Should one answer be able to override the score?
Yes, when a single fact genuinely settles the outcome, such as a disqualifying industry or a stated timeline. Overrides encode judgement the score cannot express. Keep them few and write them down, because each one breaks the assumption that a higher total always means a better outcome, and that assumption is what everyone else on the team relies on.
How is outcome mapping different from skip logic?
Skip logic changes which questions a respondent sees during the quiz, while outcome mapping decides what happens once they finish. The two interact, though: if skip logic removed a question your map depends on, the rule may never match anything. Check both together whenever you change either one, and test a path where the skip actually fires.
Where should the outcome map live?
In one place you can read end to end, whichever tool that turns out to be. The rules also live inside the funnel, but a separate readable copy is what lets you spot conflicts, review coverage, and hand the logic to someone else. Keep it dated, because knowing when a rule was written explains a great deal when results look wrong.
How often should an outcome map be reviewed?
At minimum whenever you add or remove a question, change weights, or retire an offer that a rule points at. A calendar review each quarter catches the rest, particularly rules that still fire but send people to something that no longer exists. Deleting rules that no longer apply is usually most of the work.