Conjoint vs. asking what people want

Analyst primer

Below we compare instruments with examples from beverage, snacks, and wellness studies — including where we still start with qual even when the board asks for ‘a conjoint immediately’.

Why stated importance fails

Asking respondents to rate feature importance produces socially desirable, undifferentiated scores. Everything is "important." The method measures salience, not preference.

Product teams that rely on stated importance alone often over-invest in table-stakes features and under-invest in differentiators that actually drive choice.

Stated importance in isolation flatters concepts with good copy. Indian shoppers are polite in rooms and ruthless in conjoint tasks when rupee totals appear — especially for multi-SKU categories with ₹5 and ₹10 anchors.

Use stated tools to kill bad language early, not to rank launch SKUs. The moment the decision is ‘which pack on shelf’, move to trade-offs.

A practical rule: if the concept board uses words shoppers never used in calls — ‘premiumisation’, ‘occasion elevation’ — stated work is not finished. Member-checked verbatims should precede any quant ranking.

Trade-off design fundamentals

Conjoint and discrete choice methods force trade-offs: bundles of attributes at realistic price points, with experimental design that separates main effects.

Instrument quality depends on attribute selection, level realism, and sample definition. A conjoint on the wrong sample or with fantasy bundles produces precise nonsense.

Good conjoint design hurts: it forces sacrifices the brand team did not list in the workshop. Holdouts and realistic bundles beat feature lists because kirana shoppers buy bundles, not attributes.

We routinely include options the client cannot manufacture yet to test occasion demand before capex — uncomfortable, but cheaper than tooling a SKU nobody repeats.

When to use each method

Use Van Westendorp and Gabor-Granger when the decision is primarily price-led. Use choice-based conjoint when feature bundles and willingness-to-pay for combinations matter.

Use adaptive interviewing when you need the "why" behind the trade-off — conjoint tells you what they choose; qual tells you what the choice means.

If leadership asks for conjoint on day one, ask what decision breaks if price is wrong by ₹5. If nothing breaks, you are not ready for conjoint — you are ready for qual framing.

Hybrid designs are normal: qual defines occasions and language, conjoint quantifies architecture, shop-alongs validate findability. Skipping a leg is how teams launch winners that cannot be found.

Integrating quant and qual

Our strongest pricing engagements triangulate: conjoint for structure, adaptive interviews for narrative, and behavioral data where available for validation.

“A simulator without limits is a liability. A recommendation with limits is an asset.”

The deliverable is not a simulator alone — it is a recommendation with explicit limits, confidence grades, and the segments where the model holds versus breaks.

Integration means one evidence table: claim → instrument → confidence. Conjoint coefficients sit next to member-checked verbatims, not in a separate appendix finance never opens.

For your next pricing or pack decision, map which claims require trade-off proof versus narrative proof — then sequence field accordingly instead of running omnibus habit.

When a conjoint main effect contradicts qual, we do not average them — we design a targeted follow-up wave to explain the gap. That follow-up is often where the real decision insight lives.