# Design and Validate a Recurring Human Practice

Status: draft · v0.1.0 · Operating System
draft reference — not a fitted standard

Turn an important recurring human interaction into an operable, adaptable, safe, and measurable practice connected to the work it supports.

## Purpose
Design how people prepare, interact, exercise judgment, produce usable outputs, follow through, and improve when a process depends on conversation, coordination, reflection, feedback, learning, or collective decision-making.

## Steps
1. Frame the practice and its operating contribution — Anchor the interaction to work and prevent a ritual, meeting, or template from becoming the objective.
2. Study the participants and operating context — Understand actual use, variation, power, access, and failure conditions before prescribing behavior.
3. Design the practice mechanism — Create a usable interaction that preserves judgment without leaving essential operation implicit.
4. Test with representative scenarios and participants — Find design defects, harmful uses, and transfer failures before broad operation.
5. Authorize, enable, and introduce the practice — Prepare operators and connected systems to use the validated practice responsibly.
6. Operate, review, and improve the practice — Learn from use without allowing undocumented drift or optimizing one signal at participants’ expense.

## Connections
- upstream: Discover and Synthesize Process Evidence (/processes/discover-and-synthesize-process-evidence) — trigger: The practice design requires new or refreshed evidence.
- upstream: Redesign Work and Workflow (/processes/redesign-work-and-workflow) — trigger: An approved or candidate workflow depends materially on a recurring human interaction.
- downstream: Implement a Business System (/processes/implement-business-system) — trigger: The authorized practice requires material system configuration or integration.
- downstream: Operate and Improve a Process (/processes/operate-and-improve-process) — trigger: The practice passes bounded validation and readiness gates.

## Measures
- Supported operating outcome: Context-specific outcome evidence interpreted with the practice contribution and other material influences explicit.
- Usable output quality: Practice outputs accepted by the connected owner without preventable clarification or rework, with qualitative defects retained.
- Follow-through cycle time: Elapsed time from practice close to accepted disposition, reported by commitment or decision type.
- Appropriate practice use: Eligible instances using the authorized practice plus correctly routed non-eligible instances, interpreted with non-use reasons.
- Practice exceptions and adaptations: Exceptions and adaptations by condition, participant context, cause, disposition, recurrence, and materiality.
- Participant and operating guardrails: Triangulated accessibility, workload, privacy, safety, participation, complaint, misuse, and connected-operating signals, with protected reporting boundaries.