Indifference Map¶
Analytical artifact — instantiates Acceptable Substitution Mapping
Draws the contours of bundles a specific decision-maker treats as equally good, mapping the subjective equivalence region under current, explicitly provisional assumptions.
An Indifference Map is a set of contours, each connecting the bundles that one decision-maker regards as equally acceptable — the person would as soon have any point on a given curve as any other. Its defining move is that the equivalence it draws is subjective and owner-specific: the map records what a stakeholder feels is equally good, not what is physically achievable or officially certified. Two attributes span the plane, each curve is a band of "equally fine" trades, and curves further out are simply preferred to curves nearer in. The map is drawn explicitly under current assumptions and carries a visible uncertainty margin, because preferences drift, are imperfectly known, and differ from one stakeholder to the next — so an indifference map is always somebody's map, provisionally, rather than a settled fact about the world.
Example¶
A product manager is planning a release and keeps trading two things against each other: how complete the feature set is and how soon it ships. She builds an indifference map. The horizontal axis is feature completeness (from a thin MVP to the full vision); the vertical is ship date (from next month to next quarter). She marks bundles she'd feel equally good about: thin feature set shipped next month sits on the same contour as a richer feature set shipped six weeks later — to her, right now, those are equally acceptable outcomes. A fuller, faster bundle would sit on a more-preferred contour; a thinner, slower one on a worse one. Two things make the map honest rather than a doodle. First, it is hers — the engineering lead's map, drawn on the same axes, bows the other way, because he weights completeness far above speed, and the divergence is the point of contention the team must actually resolve. Second, every curve is tagged "as of this quarter's priorities," with a shaded band of doubt, because she knows a competitor's move could redraw the whole thing next month.
How it works¶
What makes this the mechanism, rather than a chart of options, is that it captures felt equivalence and wears its provisionality on its sleeve:
- Contours are equally-preferred, not equally-capable. Each curve links bundles the owner would trade freely among; the map says nothing about whether those bundles are feasible or certified, only about how they feel.
- The map belongs to a stakeholder. It is drawn for a named decision-maker or segment, and different owners get different maps — surfacing whose acceptability a proposed swap actually satisfies.
- Assumptions are on the page. The map is stamped with the conditions it holds under, so a reader knows it is a snapshot of current preference, not a durable rule.
- Uncertainty is shown, not hidden. Contours carry a band of doubt where preference is soft or unelicited, so the map invites revisiting rather than false confidence.
Tuning parameters¶
- Quantitative vs. qualitative contours — whether curves are numerically estimated or sketched from judgment. Quantitative maps support sharper comparison but demand data the softer values may not have; qualitative maps are honest about fuzziness but easy to over-read.
- Granularity — a few broad acceptability zones or many fine contours. Fine contours express nuance but imply a precision the underlying preference rarely warrants.
- Whose map — a single owner, a segment, or an attempted aggregate. Per-stakeholder maps expose disagreement (its most valuable output); an aggregate can paper over the very conflict the team needs to see.
- Uncertainty-band width — how much doubt the contours carry. Wide bands keep the map appropriately tentative but blur decisions; narrow bands look decisive but can overstate what is known.
- Refresh cadence — how often the map is redrawn as priorities shift. Frequent refresh tracks changing preference at a cost; stale maps quietly harden yesterday's mood into today's rule.
When it helps, and when it misleads¶
Its strength is making "equally good" explicit and comparable across people: laying two stakeholders' maps side by side turns a vague disagreement into a visible geometry, and reveals which trades are genuinely contested versus merely assumed — the graphical logic of the economist's indifference curve[1] put to work on a live decision.
Its failure modes all come from forgetting the map is subjective and provisional. Drawn from an analyst's guess rather than the owner's elicited preference, it becomes an armchair map that confidently misstates what people actually value. Treating one powerful stakeholder's map as everyone's is preference capture in visual form. And the smooth contours lend false precision to soft values like dignity or trust that resist being plotted at all. The classic misuse is hardening a provisional map into a fixed rule and acting on it after the assumptions behind it have expired. The discipline is to keep the assumptions and the uncertainty band on the page, draw separate maps where stakeholders diverge, and treat the map as an input to revisit rather than a verdict to freeze.
How it implements the components¶
The map realizes the subjective-equivalence slice of the archetype — it renders felt acceptability, provisionally and per-owner, and nothing about physical feasibility:
preference_surface_or_equivalence_region— the contours are the equivalence region: the bundles a stakeholder treats as equally acceptable, drawn as a surface.stakeholder_preference_source— every map is owned by a named decision-maker or segment, tying the equivalence to whose values it reflects.uncertainty_margin— the "under current assumptions" stamp and the band of doubt keep the map honest about how soft and provisional the preferences are.
It does not encode the objective outcome_requirement that a design must physically preserve; that is the Design Tradeoff Curve, its nearest twin. This map's contours trace what a stakeholder subjectively prefers; the design curve's contour traces what is physically achievable while a function is held intact.
Related¶
- Instantiates: Acceptable Substitution Mapping — it visualizes the subjective equivalence region that tells a map which swaps a stakeholder will accept.
- Consumes: Preference Elicitation Workshop and Conjoint or Tradeoff Survey — the elicited or estimated preferences those mechanisms produce are what this map renders.
- Sibling mechanisms: Design Tradeoff Curve · Equivalency Table · Service Tier Mapping · Conjoint or Tradeoff Survey · Preference Elicitation Workshop · Approved Alternative Catalog · Procurement Equivalence Review · Substitution Matrix · Exception Review Workflow
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: The mechanism models a decision-maker's provisional preferences and derives contours of bundles treated as equally good.
Nearest alternative: Representation, Specification & Plan — A map displays the contours, but the operative contribution is the preference-model inference that constructs them.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Economics & Finance
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Mapping equally valued bundles is directly descended from indifference-curve analysis in microeconomics.
Review outcome: Independent reviewer agreement; high confidence.
References¶
[1] Keeney, R. L., and H. Raiffa. Decisions with Multiple Objectives: Preferences and Value Trade-Offs. Cambridge University Press (1993). Uses indifference judgments and curves to make equal-value tradeoffs explicit in multi-objective decisions. registry ↩