MaxDiff Analysis Without the Math
MaxDiff analysis reveals true priorities by asking people to choose the most and least important items across balanced sets of competing options.

MaxDiff analysis is a choice-based research method for finding relative priorities among many items. Each task shows a small group of options, and the participant marks the most and the least important. After enough rounds, the features, needs, messages or concepts that hold up under trade-offs are the ones that keep winning.
Rate ten features on a scale and plenty of people will tick "important" ten times. That's the weakness of conventional ratings: too many options look equally important, and the team still has nothing to choose with.
Key numbers
Sawtooth's Lighthouse Studio manual generally recommends showing four or five items per task. Its Discover guide recommends three to five for most exercises. These are product-specific design recommendations, not universal requirements. Both sources also caution against putting more than half of the full item list in one task. (Lighthouse Studio; Discover design settings)
Lighthouse suggests at least 3K/k tasks per respondent for its default hierarchical Bayes (HB) estimation, where K is the total number of items and k is the number shown in each task. That is a planning guideline for item appearances under the default model, not a universal sample-size rule. Discover says one or two appearances per item can be sufficient with larger samples when few segment comparisons are needed; more appearances support individual-level precision. (Lighthouse Studio; Discover design settings)
Discover's ordinary rescaled HB scores are positive, ratio-scaled values that sum to 100 across the tested items. Anchored scores use a different reference. These model-based scores are not the same as a simple best-minus-worst count balance. (MaxDiff scores)
When should you use MaxDiff?
Reach for it when your list is long and plain ratings leave everything in a tie. It earns its keep most when the real decision is a trade-off between competing options.
Typical candidates are roadmap features, customer needs or desired outcomes, marketing messages and value propositions, service improvements or experience concepts, and ideas that deserve more testing or investment.
Picture a product team with ten improvements that users would each call valuable on its own. Put them through MaxDiff and you learn which ones still look good once users have to pick.
Our bias: we like the method because it copies how decisions really get made. Budgets, time, attention and product capacity all cap what anyone can have, so a head-to-head comparison says more than asking whether an option sounds important. It's a weaker fit for measuring absolute satisfaction, and it won't tell you why someone prefers something.
What is MaxDiff analysis?
A way of forcing comparison. Nobody judges an item alone; in each task they point at the best and worst of whatever is on screen.
Why not simply ask for ratings? They're poor at showing true priorities. A respondent can call nearly every feature important, because each one sounds useful or because nothing in the task makes them give something up. Scores pile up in one corner and tell you little.
MaxDiff (also written max diff) creates separation by setting options against each other. Across several groups, participants meet different combinations of items, so researchers can watch which choices keep rising and which keep sinking.
The output is relative preference inside the tested set, so read it that way. An item with low preference isn't automatically worthless. It simply loses more often to the other options in this particular study.

How do you design a MaxDiff study?
Most of the work is in the items and the balance. Participants need enough context to choose consistently, and no task should be harder than it has to be.
- Settle the decision context. Does "most" mean most important to adopt, or least useful in one specific situation?
- Build a focused list. Distinct, understandable options at a similar level of detail work best; overlap and vagueness make choices hard to read.
- Create balanced sets. Rotate items through different combinations so the design supports useful comparisons and doesn't keep favoring certain pairings.
- Pilot it, and watch for confusing instructions, items people can't tell apart and fatigue you could have avoided.
The method can't rescue an ambiguous concept, so wording matters. The advice on writing questions that do not bias responses carries over to MaxDiff instructions and item descriptions.
And resist the urge to pour every idea anyone has had into the list. A tight set tied to one defined decision gives clearer priorities than a sprawl of features, outcomes, messages and abstract values.

Worked example: prioritizing a support experience
This is a hypothetical design, not a PulseLake study or a claim about expected precision. A support team has twelve possible improvements and wants an initial relative-priority list. For this example, applying Lighthouse's default-HB planning guideline with four items shown in each task gives 3 × 12 ÷ 4 = nine tasks per respondent. Nine tasks with four slots each create 36 item appearances, or three appearances per item if the design is balanced. This arithmetic describes exposure; it does not establish a sufficient respondent sample or guarantee precision.
Imagine the aggregate counts for three improvements are as follows. The counts are invented solely to show the calculation, and each item appeared 300 times:
| Improvement | Appearances | Best | Worst | (Best − worst) ÷ appearances |
|---|---|---|---|---|
| Clear case ownership | 300 | 150 | 30 | 0.40 |
| Proactive progress updates | 300 | 120 | 45 | 0.25 |
| More visual customization | 300 | 30 | 135 | −0.35 |
For clear case ownership, the descriptive count balance is (150 − 30) ÷ 300 = 0.40. It is also the best count proportion (150 ÷ 300 = 0.50) minus the worst count proportion (30 ÷ 300 = 0.10). A count balance can range from −1 to +1. It is not an HB utility estimate or Discover's rescaled ratio score, which is a separate model output. The table demonstrates arithmetic on invented counts; it does not claim to reproduce a vendor's model.
In this example, ownership was chosen best more often than worst when it appeared. It does not mean 40% of customers will renew, that the improvement is worth a particular price, or that all respondents agree. The team should check segment patterns and follow-up comments: new customers might value knowing who owns a case, while established customers may care more about progress updates.
How should you interpret MaxDiff analysis results?
Look for relative preference patterns: who wins consistently, who carries less weight, and where priorities differ between participant groups. Stay inside the tested context. These numbers aren't a universal measure of importance.
Under the hood, the analysis pools choices across tasks and participants to estimate where each item sits. You'll want the overall order, how sharply options separate and what the audiences you care about are doing. One segment may put different needs first even when the overall result points to a single leader.
Keep the decision the study was built for in view. A preferred message won't automatically change behavior, and a low-ranked feature isn't worthless everywhere. MaxDiff tells you what wins in comparison. It can't establish causation, and it can't expose every reason behind a choice.
This is where a qualitative follow-up pays off. Interviews or open-ended questions can explain why certain items matter, what participants took each option to mean and what would shift their priorities. Pairing the two is one practical form of mixed methods research.
Choose the analysis before fieldwork
Decide whether the study needs an overall ordering, comparisons between defined segments or individual-level scores. Plan the number of item appearances for that output before recruiting. A sparse design may support a population-level analysis in some settings, but it should not be presented as if it were designed for precise individual estimates.
Keep a record of the estimation method, exclusions and any score transformations. A rescaled score is relative to the items in that exercise; adding or removing options changes the comparison context. Report uncertainty and treat near-ties as near-ties. A team can combine similar priorities with feasibility, cost or strategic fit when choosing what to do next, rather than presenting small numerical differences as decisive.
Limits and when another method fits
MaxDiff estimates relative preferences within a defined list and criterion. It does not establish that the leading choice is good enough in absolute terms, predict purchasing by itself, or remove recruitment and sampling bias. The current MaxDiff result should be interpreted as evidence about the people and options studied.
When the decision is about realistic bundles made from several varying attributes, conjoint analysis for product decisions may fit the question better. Use interviews or other exploratory work when the team does not yet know which needs belong in the list; use behavioral evidence when the decision depends on actual adoption.
Generated or synthetic choices are simulated signals, not observed survey respondents. Increasing the number of generated choices does not make them representative of a population. They can help rehearse an instrument or explore hypotheses, but findings that require human evidence should be checked with people from the intended audience.
How PulseLake helps
PulseLake can keep MaxDiff objectives, methodology, evidence, analysis and decisions together in one persistent study context. You can run the choice exercise through traditional research workflows and connect it with AI-led interviews or qualitative analysis agents, with judgment and approvals staying with researchers throughout. Research intelligence also supports cross-study search and evidence provenance when you want to connect priorities with earlier findings. To talk through the workflow, talk to our team.
Frequently asked questions
Can MaxDiff explain why participants prefer one item over another?
Only in part. It shows relative preference; the reasoning behind each pick mostly stays hidden. To learn what people understood, which experiences shaped their choices and why a given feature, need, message or concept stood out, add open-ended follow-ups, interviews or other qualitative methods.
Is MaxDiff the same as asking participants to rank every option?
No. Full ranking means putting the whole list in order, which gets painful as the list grows. MaxDiff shows small groups and asks for just the most and least preferred option in each. The analysis then pools those repeated choices into estimated priorities for the complete item set.
Can MaxDiff results be compared across audience segments?
Yes, provided the study design and sample can support it. A segment view might reveal that an option with middling overall preference matters enormously to one audience. Read any such difference against the tested item set and the decision context.
How many tasks should each person answer?
There is no single task count for every study. Lighthouse suggests at least 3K/k tasks per respondent for its default HB estimation, where K is the total number of items and k is the number shown in each task. Discover allows fewer appearances in some larger-sample studies with limited segment comparisons. Choose the design for the intended analysis and audience, then pilot it.
Does the highest MaxDiff score predict purchase?
No. MaxDiff estimates relative preference within the tested list and criterion. Purchase also depends on price, availability, alternatives and circumstances.
Can synthetic respondents replace a human MaxDiff study?
No. Their choices are simulated, not observed population preferences. They can support exploration or instrument rehearsal, but more synthetic choices do not establish representativeness.



