Skip to content

Values Statement

Artifact — instantiates Normative Assumption Explicitness

Names organizational or project values that can anchor later rationale. It is only a mechanism; the archetype requires linking those values to actual decision assumptions and tradeoffs.

A Values Statement is a published artifact that names, in the abstract, the values an organization or project claims to hold and grounds them in a source — a mission, a heritage, a mandate. Its defining trait is that it is decontextualized: it declares "we value X" without attaching X to any particular decision, tradeoff, or affected party. That is at once its use and its ceiling. As an anchor it is genuinely useful — it gives later rationale a citable vocabulary and a shared reference point — but on its own it governs nothing, because a value with no decision attached cannot be weighed, contested, or improved. This mechanism is included precisely to mark that boundary: it implements the naming end of the archetype and none of the governing end, and honesty about that gap is the whole point of the entry.

Example

A mid-size logistics company publishes an "Our Values" statement on its intranet and in onboarding: Safety first. Respect for our drivers. Relentless efficiency. Each value is named and grounded — the statement traces them to the founder's story of a near-miss on the road decades earlier, which gives them a source and some authority. As an anchor this does real work: a new dispatcher learns the vocabulary, and future memos can cite "safety first" as shared ground.

But when a routing algorithm is later tuned to shave delivery times in a way that quietly compresses driver rest breaks, the statement cannot adjudicate. "Safety first" and "relentless efficiency" both sit on the wall with no stated priority between them, no map of who is affected, no rationale for the trade being made. The artifact named the values; it never linked them to the decision, so at the moment it was needed it had nothing to say. That gap — between the values on the poster and the values enacted in the routing code — is exactly what the rest of the archetype exists to close.

How it works

  • Name the values. State the handful of standards the organization claims to hold, as explicit claims about what ought to matter.
  • Ground them in a source. Trace each to a mission, heritage, or mandate so the claim has authority rather than floating free.
  • Publish for reference. Place the artifact where it can be cited by later decisions — and stop there, deliberately, since linking to decisions is other mechanisms' work.

Tuning parameters

  • Number of values — how many are named. Fewer are memorable and force priority; more are comprehensive but dilute.
  • Priority ordering — whether any ranking among the values is stated. Stating priority makes the statement more useful in conflict but far more contentious to agree.
  • Specificity — how concretely each value is defined. More specificity narrows the say-do gap but reduces the artifact's rallying breadth.
  • Prominence — how visibly it is published, which sets how often later rationale actually cites it.

When it helps, and when it misleads

Its strength is providing shared vocabulary and a citable anchor — a common reference that decision records and policy rationales can point back to, so value talk across an organization uses the same words.

Its failure mode is the say-do gap: espoused values that no actual decision honors, the classic divergence between an organization's stated theory and its theory-in-use.[n1] The classic misuse is publishing the statement as the ethics work — values-washing, where the poster substitutes for governing the decisions the values were supposed to shape. The guarding discipline is to treat the statement strictly as an input, never a deliverable: require every named value to be cited by at least one real decision rationale, or the artifact remains decoration.

How it implements the components

  • normative_claim — names, in the abstract, the standards the organization claims ought to matter.
  • value_source — grounds those values in a mission, heritage, or mandate, giving the claim inspectable authority.

It names values but links them to no decision: it does not map who they affect (affected_party_map) or compare what they displace (competing_norm), which is Value Audit's work; it records no reasoned choice (decision_rationale, assumption_record), which belongs to Policy Rationale Statement and Decision Record; and it opens nothing to live challenge (contestation_channel, Stakeholder Deliberation). Until its values are tied to actual assumptions and tradeoffs, it is an artifact, not yet the archetype.

Editorial Notes

Form Classification

Form family: Representation, Specification & Plan

Rationale: Values Statement operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it names organizational or project values that can anchor later rationale. It is only a mechanism; the archetype requires linking those values to actual decision assumptions and tradeoffs.

Independent corroboration: The frozen evidence defines Values Statement as 'Names organizational or project values that can anchor later rationale; It is only a mechanism; the archetype requires linking those values to actual decision assumptions and tradeoffs', so its operative form is Representation, Specification & Plan.

Review outcome: Independent reviewer agreement; high confidence.

Origin Attribution

Primary origin: Organizational & Management Science

Origin pattern: Single lineage

Present-day reach: Universal

Rationale: Both independent reviews identify organizational management as the historical home of the operation—Names organizational or project values that can anchor later rationale. It is only a mechanism; the archetype requires linking those values to actual decision assumptions and tradeoffs.. The retained alternates document formative adjacent traditions; the reach field, not the origin field, carries later applicability.

Related originating lineages:

  • Communication & Media Studies — Communication and media research supplies a parallel or contributing lineage for the mechanism's defining operation: names organizational or project values that can anchor later rationale. It is only a mechanism; the archetype requires linking those values to actual decision assumptions and tradeoffs.
  • Philosophy — Philosophical logic, epistemology, and normative reasoning supplies a parallel or contributing lineage for the mechanism's defining operation: names organizational or project values that can anchor later rationale. It is only a mechanism; the archetype requires linking those values to actual decision assumptions and tradeoffs.
  • Systems Thinking & Cybernetics — Systems science's feedback, boundaries, control, and regulation tradition contributes a separate formative lineage to the mechanism's values statement logic.

Review resolution: Both blind reviewers independently place the defining operation—Names organizational or project values that can anchor later rationale. It is only a mechanism; the archetype requires linking those values to actual decision assumptions and tradeoffs.—in organizational management. Their queued differences are secondary: alternate_origin_disagreement, origin_mode_disagreement, encyclopedia_synthesis_disagreement. Reviewer A uniquely contributes no additional alternate; reviewer B uniquely contributes ['communication_media_studies', 'philosophy']. I preserve the full evidence-supported union of 3 alternate domain(s), without a numeric cap. origin_mode=single_lineage reflects the more specific lineage judgment in reviewer B's evidence, while domain_reach=universal separately records present-day portability. The affirmative encyclopedia-synthesis finding is preserved, and confidence=high uses the more conservative reviewer level.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Reconciled after independent review; high confidence.

Notes

[n1] Espoused theory vs. theory-in-use — Chris Argyris and Donald Schön's distinction between the values people say they hold and the values their actual behavior reveals. A Values Statement records only the espoused side; the archetype's other mechanisms are what force the two to meet.