Record value conflicts instead of avoiding them
Aliases: value tension · trade-off documentation · documented trade-offs
What it is
A value conflict (or value tension) is a situation where one design move enhances one value while damaging another: safety versus autonomy (parental monitoring protects a child and strips their privacy), personalization versus privacy (recommendation quality depends on data concentration), growth versus wellbeing (screen-time reminders cut engagement). "Record rather than avoid" means that once identified, a conflict becomes a first-class document — the two values in tension, the options considered, the rationale for the trade-off, and the conditions under which it should be revisited — not an argument deferred while everyone builds along the default path.
Why it happens
Unrecorded conflicts do not disappear; they get settled silently by defaults and metrics. Whoever owns the current default configuration, and whoever's metric is on the dashboard, wins automatically. Avoidance has a second cost: the same conflict is re-argued from zero in every new project, because the organization never accumulates a memory of "why we traded it this way last time," and conclusions drift with the seniority of whoever is in the room. A written record turns an implicit resolution into an explicit decision: it gives the conflict a citable handle, so later reviews can append evidence and trigger re-examination instead of pretending no disagreement exists. Recording also improves the argument itself — being forced to write down what was given up is far harder, and more honest, than writing down why the choice is good.
Where it stops holding
Recording does not resolve a conflict; it makes it visible and reviewable. Treating "documented" as "handled" is avoidance in a new costume. Some conflicts genuinely cannot be adjudicated pre-launch; the record should then contain assumptions and the conditions that would falsify them, not conclusions. Conflict documents also have maintenance costs: records no one revisits rot into ritual — milestone reviews must include real re-examination points, or the record itself becomes compliance theater.
Applying it
- Add a "conflict" field to the decision-record template: which value this decision damages, how much, and who bears it; blank answers send the decision back.
- Fix four items per conflict record: the two sides, the alternatives considered, the rationale for the choice, and the re-evaluation triggers (user-mix change, regulatory change, harm incident).
- At milestone reviews, walk the conflict list rather than the feature list, checking whether any recorded trigger has already fired.
- Verify: sample a one-year-old conflict record and ask whether a new team member can reconstruct the original trade-off logic from the document alone; if not, fix the template.