Skip to content

Normative Assumption Explicitness

Make value judgments and ought-claims explicit before treating them as neutral facts.

The Diagnostic Story

Symptom: A decision is presented as purely technical, evidence-based, or objective, yet stakeholders are surprised by the outcome and cannot locate their disagreement in any of the published inputs. Debate stays in the factual register while the actual conflict is about whose interests count, which risks are acceptable, and which tradeoffs are legitimate — questions that were settled silently inside the model or metric before anyone was asked.

Pivot: Convert implicit value premises into explicit, sourced, contestable, and revisable decision assumptions — separating empirical claims from normative ones, identifying affected parties, surfacing competing credible norms, and recording the accepted rationale alongside the conditions under which it should be reopened.

Resolution: Decision rationale becomes more honest; false neutrality decreases; stakeholder trust and the ability to contest decisions improves; and policies become more durable because the value choices inside them are visible and can be revised when context changes.

Reach for this when you hear…

[algorithmic hiring] “The model doesn't have a gender bias, the data does — and building the model from the data just laundered a value choice through a technical process.”

[public budgeting] “We kept calling it a neutral efficiency cut, but somebody had decided beforehand that parks matter less than road resurfacing — that's not a fact, that's a value.”

[clinical guidelines] “The guideline looks like it's just following the evidence, but the evidence only covers adults over fifty, and applying it to everyone is an unstated choice about who counts.”

Mechanisms / Implementations

  • Value Audit: A value audit reviews a decision surface to find hidden priorities and displaced alternatives.
  • Ethical Impact Assessment: An ethical impact assessment can surface harms, duties, rights, and value conflicts.
  • Metric Value Review: A metric value review asks what a metric rewards, ignores, normalizes, or sacrifices.
  • Policy Rationale Statement: A policy rationale statement records the values and tradeoffs behind a rule.
  • Stakeholder Deliberation: Creates a forum for affected parties and decision makers to compare values.
  • Decision Record: A decision record makes value premises durable.
  • Ethics Checklist: An ethics checklist can prompt useful questions, but it should not be confused with the archetype.
  • Model Card Value Section: A model card value section documents the value assumptions embedded in a technical system.
  • Values Statement: A values statement is an artifact that can support the archetype, but it is not sufficient.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (2)

Also references 8 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Metric Value Review · domain variant · recognized

A metric-focused variant that asks which values are embedded in what is measured, optimized, rewarded, or declared successful.

Policy Rationale Explicitness · governance variant · recognized

A governance-focused variant that requires policies to state the value premises and balancing judgments behind their rules.

Algorithmic Value Assumption Audit · domain variant · recognized

A technical-system variant that surfaces the normative choices embedded in datasets, labels, targets, thresholds, loss functions, deployment constraints, and evaluation priorities.

Objective Weighting Disclosure · governance variant · merge review

A weighting-focused variant that discloses how competing objectives are prioritized when a decision procedure combines them.