TRUST / OPERATING PRINCIPLES

Trust is part of the record.

Consequential decisions are sensitive by nature. The system around them should make authority, access, and change visible before anyone needs to ask.

Ask a trust question Read the principles

RECORD BOUNDARYPRIVATE / DP-042

DECISION CONTEXTMarket entry / DACHOne record. Named authority.

OWNERCommercial strategy

REVIEWERSFinance · Operations

APPROVALPending challenge

HISTORY4 changes recorded

THE RULE

Nothing important should be invisible to the person accountable for the decision.

THE TRUST QUESTION

Transparency without control is just exposure.

A trustworthy decision record does not ask teams to reveal more. It gives them control over what becomes visible, to whom, and when.

THE PRINCIPLES

Designed for sensitive decisions, not performative transparency.

These are the product decisions that shape how a record should behave around consequential work.

PRIVATE BY DEFAULT

Access follows the decision, not the org chart.

A consequential record starts with the smallest relevant group. Participation should be intentional, visible, and easy to review.

HUMAN AUTHORITY

The accountable person never disappears behind the system.

Owners, reviewers, dissenters, and approvers are named in the record. The product structures judgment; it does not impersonate it.

CHANGE HAS A SHAPE

A changed fact should be visible, not quietly overwritten.

When an assumption, source, or outcome changes, the record should make the change legible and show which commitments it touches.

DECISION RIGHTS

Review is different from approval.

A useful record separates the person who supplied evidence, the person who challenged it, and the person who can commit the organization.

THE OPERATING MODEL

Trust is built across the life of a decision.

01BEFORE THE FIRST UPLOAD

Set the boundary

Define the decision, its owner, the relevant participants, and what should remain outside the record.

02WHILE THE DECISION IS LIVE

Make the reasoning inspectable

Keep evidence, assumptions, dissent, and approval states attached to the decision they affect.

03AFTER THE OUTCOME ARRIVES

Let the record learn

Capture what changed, what held, and which future decisions should inherit the lesson.

BEFORE A PILOT

The right trust questions are specific.

Who can see this decision record?

Which changes should create a visible history?

Who can challenge, review, and approve?

What should never leave the agreed boundary?

START WITH A CONVERSATION

Bring your hardest trust question with the decision.

Request a private audit