Ask people to rate ten features on a 1–10 scale and they will call nine of them very important.
Ask them to pick one Best and one Worst from a small set, and they have to trade off.
This tool turns those forced choices into a ranked list of priorities on a 0–100 scale that sums to 100,
flags which rank gaps are statistically real versus ties, and checks whether the average ranking hides opposing customer segments.
👨🏫 Professor Mode: Guided Learning Experience
New to MaxDiff? Enable Professor Mode for step-by-step guidance through reading a best-worst study, telling a real gap from a statistical dead heat, and checking whether the average ranking describes anyone!
OVERVIEW & WHAT THIS TOOL SOLVES
Why forced tradeoffs beat rating scales: On a 1–10 Likert scale (left), respondents rate all six features
8.2–8.9 (“everything matters”). Picking one ✓ Best
and one ✗ Worst per screen (center) forces real tradeoffs and separates
the list into a 0–100 priority budget (right) — revealing clear winners, a statistical tie in the middle,
and a bottom item that looked popular on Likert.
Suppose a product team has budget to build two of six candidate features. If you run a standard 1–10 importance survey, almost every feature comes back between 8.2 and 8.9 because calling everything “very important” costs the respondent nothing. MaxDiff (Best-Worst Scaling) replaces rating scales with a scarce forced choice—“of these four, which is most important and which is least?”—turning those trade-offs into a 0–100 priority budget that sums to 100.
🎯 Questions It Answers
Which claims, messages, or product features sit at the top of customers' true priority list?
Which rank gaps are statistically real winners versus a statistical dead heat?
Does the overall average ranking hide two opposing customer segments with different priorities?
📂 What Data You Need
Long-format Best-Worst choice data: one row per item, per task set, per respondent.
Respondent ID, Task ID, Item label, plus binary Best (0/1) and Worst (0/1) columns.
Optional segment column to compare priority rankings across customer groups.
💡 What You'll Discover
0–100 Priority Shares: Probability-rescaled priority scores summing to 100 against an equal-share benchmark.
Rank-Separation Verdicts: Confidence intervals and pairwise tests flagging real gaps vs. ties.
🔍 Key Nuances & Common Traps to Watch ForClick to expand ▾
Why Best-Worst beats Likert ratings: A 1–10 rating is denominated in a private currency—generous raters live in the 8–10 band while strict raters never pass 6. Best-Worst records only ordinal trade-offs within each set, eliminating scale-use bias.
Relative priority, never absolute demand: Priority scores always sum to 100 across the tested list. If you run MaxDiff on ten features nobody wants, the least-hated item will still win the highest share.
When to use MaxDiff vs. Conjoint: Use MaxDiff to rank a list of standalone items (messages, claims, benefits, features). Use Conjoint when items are combined into multi-attribute product bundles with prices to simulate market share or Willingness-to-Pay.
📐 Under the Hood: Model Equations & Variable DefinitionsClick to expand ▾
1. Linked Best & Worst Multinomial Logit Choice ProbabilitiesBest-Worst Logit
\[ P(\text{best} = b \mid S) = \frac{e^{u_b}}{\sum_{j \in S} e^{u_j}}, \qquad P(\text{worst} = w \mid b, S) = \frac{e^{-u_w}}{\sum_{j \in S \setminus \{b\}} e^{-u_j}} \]
💬 Read it in plain English: Picking the Best item follows a standard multinomial logit over all items in the shown set \(S\), while picking the Worst item is a multinomial logit over the remaining \(a - 1\) items using negated utilities (\(-u_w\)).
Variable & Symbol Directory (Every Term Defined)Hover or focus any role badge for details
b, w
Chosen Best & Worst ItemsYOUR DATA ⓘ
\(b\) is the item picked as Most Important; \(w\) is the item picked as Least Important in task set \(S\).
S
Task Choice SubsetYOUR DATA ⓘ
The set of \(a\) items shown together on a single screen; \(S \setminus \{b\}\) is the set of remaining items after \(b\) is chosen as Best.
uj
Latent Item Utility (Log-Odds Scale)ESTIMATED ⓘ
Estimated priority utility of item \(j\) on a zero-centered log-odds scale (higher \(u_j\) = stronger priority).
\[ \text{Score}_i = \frac{\exp(u_i)}{\exp(u_i) + a - 1} \times \frac{100}{\sum_{j=1}^{K} \frac{\exp(u_j)}{\exp(u_j) + a - 1}} \]
💬 Read it in plain English: Converts zero-centered log-odds utilities \(u_i\) into intuitive 0–100 priority shares that sum to 100 across all \(K\) items, where an average item sits near the equal-share benchmark \(100 / K\).
Variable & Symbol Directory (Every Term Defined)Hover or focus any role badge for details
Scorei
0–100 Priority ShareOUTPUT ⓘ
Item \(i\)'s share of the 100-point priority budget (an item at 20 has twice the modeled relative priority weight of an item at 10).
a, K
Items per Screen & Total ItemsYOUR DATA ⓘ
\(a\) is the number of items displayed per task screen (typically 4 or 5); \(K\) is the total number of items in the study.
STEP 1: LOAD DATA
📚
Use a Case Study
Load a realistic MaxDiff dataset with a written brief.
Select a scenario above to load a preset MaxDiff dataset with context.
📚Use a Case Studyclick to switch
📤
Upload Your Own Data
Long-format best-worst data (CSV or TSV).
Drag & drop your MaxDiff file
Needs respondent, task, item, best and worst columns
No file loaded.
📤Upload Your Own Dataclick to switch
STEP 2: MAP COLUMNS
Tell the tool which column is which. Sensible guesses are pre-selected.
STEP 3: ESTIMATE ITEM SCORES
Advanced settings
Shrinks extreme utilities toward zero. Leave at 0.01 for aggregate estimation. It matters far
more for the per-respondent fit, where an item a person never once picked would otherwise run
off toward minus infinity.
STEP 4: RESULTS
Intervals are approximate and model-based. Adjacent-pair p-values are exploratory and unadjusted for multiple comparisons. Neither establishes population uncertainty under respondent heterogeneity.
Item scores (0–100, sums to 100)
Error bars are approximate 95% model-based confidence intervals, using the full covariance in the score transformation. Resist reading a ranking off
overlapping bars in either direction — overlapping intervals do not mean two items are
tied, because the gap between them has its own, usually much smaller, standard error.
The unadjusted p vs above column in the table below is the test that actually settles it.
Model scores vs. counting analysis
The counting score is simply best-minus-worst over times shown. It needs no model at all. If the
two orderings disagree sharply for an item, that item probably kept appearing alongside unusually
strong or unusually weak company.
Full item table
unadjusted p vs above tests whether each item really outranks the one directly above it.
Rows marked too close to call are pairs the data cannot separate at the 5% level, so the
ranking between those two is not a finding you should defend.
Rank
Item
Score
95% model-based CI
unadjusted p vs above
Utility
Times shown
Best
Worst
B−W
Adjacent-pair tests are exploratory and unadjusted for multiple comparisons. These intervals describe the fitted pooled model; they do not include respondent heterogeneity or design uncertainty.
APA-Style Report
Managerial Interpretation
📥 Export Python Code
Ready for the next step? These scores tell you which items people want most, but not
which set to launch: the top three often appeal to the very same people.
Open in TURF Analysis and upload the respondent
file as-is to find the set that reaches the most people.
STEP 5: FIND SEGMENTS
An aggregate MaxDiff ranking is an average, and an average of two groups who want opposite things
describes nobody. This clusters respondents on their individual item utilities to see whether the
headline ranking is hiding a disagreement.