Minimum HCD operating agreement

Purpose

When to use this agreement

Use it when creating an HCD capability, beginning work with a new portfolio or program, aligning several delivery teams, or correcting inconsistent demand, evidence, accessibility, and decision practices.

Keep the initial agreement short enough to review and use. Link to policies, role definitions, standards, procedures, and detailed playbooks rather than copying them into a document that becomes difficult to maintain.

Preparation

Build it with the people who must act on it

1. Identify the accountable leader and the decisions the agreement must govern.
2. Bring together HCD, product, delivery, accessibility, operations, policy, privacy, security, and other relevant authority.
3. Use current demand, delays, findings, exceptions, incidents, and outcome evidence to expose operating gaps.
4. Agree on the minimum viable controls before documenting an ideal future organization.
5. Test the draft against one real request and one consequential delivery decision.
6. Approve, publish, communicate, and assign the first review date and evidence owner.

Structure

Connect seven operating sections

Reusable artifact

Copy the Markdown agreement

Adapt this structure in a governed knowledge or documentation environment. Preserve ownership, version, effective date, review date, and change history wherever it is maintained.

# Minimum HCD operating agreement

## Agreement control
- Scope:
- Accountable owner:
- Approving authority:
- Contributors and reviewers:
- Status and version:
- Effective date:
- Next review:
- Related records:
- Change history:

## Mandate and outcomes
- Purpose of the HCD capability:
- People, services, and organizational areas supported:
- User and experience outcomes:
- Mission and service outcomes:
- Accessibility and inclusion outcomes:
- Delivery and organizational-capability outcomes:
- Boundaries, obligations, constraints, and assumptions:
- Work outside the mandate:

## Demand and capacity
- How requests enter:
- Minimum intake information:
- Priority dimensions:
- Routing outcomes and authority:
- Capacity assumptions and service expectations:
- How deferred, declined, and unmet demand remains visible:
- Urgent risk and escalation path:

## Evidence and knowledge
- Permitted evidence sources and research safeguards:
- Traceability and confidence expectations:
- Required records and stable identifiers:
- Storage, access, retention, and publication rules:
- How findings become requirements and decisions:
- How reusable knowledge is reviewed, connected, and maintained:

## Decision and delivery integration
- Recommendation, review, decision, and risk-acceptance roles:
- Disagreement and escalation path:
- Required delivery checkpoints:
- Minimum evidence at consequential decisions:
- Acceptance and release conditions:
- Exception approval and remediation controls:
- Post-release learning and follow-through:

## Accessibility and responsible practice
- Applicable commitments, standards, policies, and environments:
- Accessibility ownership and specialist participation:
- Privacy, consent, ethics, inclusion, safety, security, and human-review controls:
- Required evaluation methods and evidence:
- Accessible feedback and support path:
- Barrier remediation and exception governance:

## Measures and model review
For each material measure, record its definition, source, owner, cadence,
threshold, limitations, decision, and resulting action.

- Experience and user outcomes:
- Accessibility and unequal effects:
- Delivery and operational outcomes:
- Risk and remediation:
- Demand, capacity, and unmet need:
- Organizational capability and learning:
- Conditions that trigger operating-model review:
- Evidence and authority required to revise this agreement:

Governance

Approve an operating system, not aspirations

• Can a person outside HCD understand when and how to engage?
• Are priority, capacity, and unmet demand visible?
• Can evidence be traced through requirements and decisions?
• Are authority, disagreement, escalation, and risk acceptance explicit?
• Does accessibility affect procurement, requirements, acceptance, and release?
• Do records support continuity without exposing sensitive information?
• Do measures lead to decisions rather than reporting activity alone?
• Is there an owner, date, evidence set, and authority for the next review?