MaxDiff vs conjoint: choose priorities or priced configurations
Choose MaxDiff for item priorities or conjoint for complete offers. Work through a meal-planner decision involving features, subscriptions and price.
Use MaxDiff to prioritize comparable items within a list. Use conjoint to estimate tradeoffs among feasible complete offers, including price when price is part of the decision. Priorities can inform the configurations studied next, but they cannot supply a price coefficient. If the uncertainty is whether the function works, observe the task before commissioning either preference design.
Keep the decision in the task
Imagine you are developing a meal planner for households and need either a development priority or a viable paid tier. The illustrative planner has a shopping list, saved weekly plan, preparation-time filters and household sharing. MaxDiff repeats small subsets and asks which benefit is most and least valuable. Conjoint varies complete offers and asks what the buyer would choose.
The buyer makes a different choice
Priority task
From shopping list, weekly plan and time filters, select most and least valuable for dinner planning.
Configuration task
Attribute | Complete offer comparison |
|---|---|
Planning | Offer A: Weekly plan Offer B: Weekly plan Offer C: Weekly plan |
Shopping list | Offer A: Included Offer B: Included Offer C: Not included |
Household sharing | Offer A: Not included Offer B: Included Offer C: Included |
Monthly price | Offer A: $5 Offer B: $9 Offer C: $5 |
Choose a complete plan, or none. Weekly planning is present in every plan.
The two tasks answer different questions. The configuration card compares complete plans; it does not show customer outcomes or a measured price premium.
The illustrated $5/$9 task holds weekly planning constant. It can compare the displayed plans, but cannot estimate the separate contribution of weekly planning. A liked feature is not automatically worth the price of the bundle that contains it. This single illustrative card does not independently identify all feature and price effects; that requires a designed set of varied tasks.
Ask what the result can change
Question | Method comparison |
|---|---|
Which benefits should we investigate? | MaxDiff can contribute: Relative priority of tested items Conjoint can contribute: Tradeoffs within designed offers |
What configuration might appeal? | MaxDiff can contribute: Input to deciding candidate features Conjoint can contribute: Simulated preference for feasible configurations |
How does price affect the offer? | MaxDiff can contribute: Not answered by feature priority alone Conjoint can contribute: Estimated sensitivity within tested price levels |
What will our actual sales be? | MaxDiff can contribute: Not established Conjoint can contribute: Not established by preference shares alone |
A priority result narrows prototype investment. A configuration result helps select a viable tier or product. Both are relative to their supplied alternatives and context. Neither preference output alone forecasts actual sales.
Our worked MaxDiff guide uses example counts, while our bottle simulator uses assumed coefficients. Their scales describe different calculations; do not compare them as customer results.
Choose the next study from the current product stage
Many functions, little development capacity: prioritize a comparable list, then investigate leading functions. A short, clear list may also support ranking; pilot the task before adding repetitions.
Feasible paid tiers, uncertain configuration: study complete offers at the intended prices. Include rejection when realistic and the alternatives buyers actually consider. Keep cost and operations beside modeled preference.
High priority, poor use: observe the grocery-list journey. Missing units or duplicate ingredients cannot be diagnosed by another priority score. Solve delivery of the function before using its appealing description as a launch promise.
Translate a benefit into a deliverable level
Prioritization input | Configuration and evidence |
|---|---|
Shopping-list function is worth investigating | Configuration decision: Included or absent in a realistic plan Evidence still needed: Choices among feasible offers and actual list performance |
Sharing may serve a household subgroup | Configuration decision: Sharing inclusion in a defined tier Evidence still needed: Audience fit and tradeoff with the displayed price |
Saved weekly plan appears useful | Configuration decision: Present across all candidates or varied deliberately Evidence still needed: A study cannot estimate a level held constant in every task |
“Shopping list included” needs a clear mechanism that the team can implement. “Sharing included” needs a defined household/account arrangement. Price needs the same commitment, billing unit and channel across candidates.
Decide whether a function is a shared condition or an attribute to estimate. A level held constant in every task supplies no comparison for its separate effect. That is a design property, rather than a low measured contribution.
Resolve an earlier problem first
Unclear benefit statements need a wording pilot. Infeasible configurations need product and economic work. An actual repeat question needs use or purchase evidence. Neither statistical method repairs those missing inputs.
Write the post-study action in one sentence. “Focus development on two functions” and “take one viable tier into a paid pilot” lead to different instruments. If the action is “fix the abandoned list,” a preference method is premature.
Select one route and keep the handoff visible
For MaxDiff, inspect comparable wording, connected comparisons, actual exposure and score interpretation. For conjoint, inspect levels, restrictions, coding, estimation and held-out prediction. The audience and response source should serve the decision in both.
The practical sequence is priority → product feasibility → priced configurations only when each step adds missing evidence. Stop when the next action is clear. A managed Sapien comparison can investigate modeled priorities or offers; agree the required method and validation in scope.
Further reading
- our MaxDiff tasks and counts guide
- our conjoint cards and simulator
- our ranking versus MaxDiff guide
Bring the decision, audience and evidence needed to a scoped Sapien study discussion.
