Skip to content
Operating System
Lock reference · Draft
v0.1.0

Design and Validate a Recurring Human Practice

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

Adopt · export.mdAdopt · export.jsonDraft reference — not a fitted standard

Profile

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.

Intended outcome

A versioned practice specification and operator guide that representative participants can use, adapt within stated boundaries, and connect to an accountable process outcome.

Accountable
Practice owner
Operator
Practice designer
Use when
  • — A process step depends materially on a meeting, conversation, review, exercise, feedback exchange, or decision forum.
  • — A recurring people practice exists mainly as custom, a script, a form, or a calendar event.
  • — Participation is inconsistent, burdensome, inaccessible, unsafe, or disconnected from follow-through.
  • — Training has been proposed for a problem that may instead require better practice, authority, workflow, or conditions.

Entry gate

  • The supported process, operating condition, intended outcome, accountable owner, and practice boundary are explicit.
  • Representative participants and relevant power, access, privacy, safety, and qualification conditions are identifiable.
  • The design need is not being used to avoid a process, authority, capacity, conduct, or system problem.

Exit gate

  • Purpose, trigger, participants, preparation, interaction moves, judgment boundaries, outputs, follow-through, enablement, safeguards, and measures are controlled.
  • Representative normal, edge, failure, recovery, accessibility, and misuse scenarios have been tested.
  • The receiving process accepts the output contract and material risks have qualified dispositions.
  • An authorized version, operator support, review cadence, and improvement route exist.

Flow · 6 controlled steps

  1. 01

    Frame the practice and its operating contribution

    Anchor the interaction to work and prevent a ritual, meeting, or template from becoming the objective.

    • — Name the supported process step, customer, outcome, and failure being addressed.
    • — State what the practice may decide, recommend, record, or never do.
    • — Describe participants, context, frequency or trigger, current variation, effort, and constraints.
    • — Test whether the cause instead belongs to workflow, authority, capacity, policy, system, conduct, or qualified support.
    Responsible
    Practice owner
    Output
    Practice Design Brief
    Decision
    Is a recurring human practice an appropriate mechanism for the stated need?
  2. 02

    Study the participants and operating context

    Understand actual use, variation, power, access, and failure conditions before prescribing behavior.

    • — Observe or reconstruct representative current interactions and follow-through.
    • — Identify participant goals, preparation, language, access needs, power relationships, workload, trust, incentives, and constraints.
    • — Map connected inputs, outputs, decisions, records, systems, exceptions, escalation, and qualified-support boundaries.
    • — Seek missing and dissenting perspectives without requiring unsafe disclosure.
    Responsible
    Practice designer
    Output
    Practice Context Model · Risk and Access Conditions
    Decision
    Is the context evidence sufficient and responsibly obtained?
  3. 03

    Design the practice mechanism

    Create a usable interaction that preserves judgment without leaving essential operation implicit.

    • — Specify trigger, cadence, participants, authority, preparation, setting, and alternatives.
    • — Design a sequence of prompts, observations, sense-making, decisions, commitments, checks, and closure.
    • — Define required consistency, permitted adaptation, stop conditions, escalation, confidentiality limits, and qualified-help triggers.
    • — Define the minimum output, destination, owner, due point, acknowledgement, and record boundary.
    • — Create examples, aids, accessibility paths, and facilitation guidance proportionate to the practice.
    Responsible
    Practice designer
    Output
    Draft Practice Specification · Draft Operator Guide
    Decision
    Does the design support the outcome while remaining usable, adaptable, and controlled?
  4. 04

    Test with representative scenarios and participants

    Find design defects, harmful uses, and transfer failures before broad operation.

    • — Walk or simulate normal, edge, failure, recovery, accessibility, remote, time-constrained, and misuse scenarios.
    • — Invite representative participants to use and adapt the practice with realistic inputs.
    • — Observe comprehension, judgment, participation, burden, output quality, follow-through, and unintended consequences.
    • — Record defects and disagreement; do not convert comfort, satisfaction, or compliance into outcome evidence.
    Responsible
    Practice designer
    Output
    Practice Validation Record · Revised Practice Specification
    Decision
    Is the practice sufficiently usable, safe, and connected for a bounded pilot?
  5. 05

    Authorize, enable, and introduce the practice

    Prepare operators and connected systems to use the validated practice responsibly.

    • — Obtain process-owner, output-owner, and qualified approvals required by context.
    • — Version the specification, guide, aids, records, measures, conditions, and effective scope.
    • — Build explanation, demonstration, rehearsal, feedback, coaching, and support around actual use.
    • — Confirm systems, scheduling, access, privacy, escalation, and receiving-process readiness.
    • — Introduce through a bounded pilot with support and rollback conditions.
    Responsible
    Practice owner
    Output
    Authorized Practice Version · Enablement and Pilot Plan
    Decision
    Are people and connected mechanisms ready to operate the practice within its boundary?
  6. 06

    Operate, review, and improve the practice

    Learn from use without allowing undocumented drift or optimizing one signal at participants’ expense.

    • — Review the supported outcome, output quality, adoption, effort, exceptions, follow-through, experience, and guardrails together.
    • — Distinguish practice design, operator skill, surrounding process, authority, capacity, system, and contextual causes.
    • — Coach within the approved design and route material changes through impact review and versioning.
    • — Retire the practice when it adds ritual or burden without sufficient operating value.
    Responsible
    Practice owner
    Output
    Practice Health Review · Improvement Proposal or Retirement Decision
    Decision
    What does operating evidence justify?

Connections

Seams · 11 hops within 2 steps

Upstream and downstream neighbourhood over public reference processes only. Each hop shows the trigger, carried objects, and what the receiving process loses if the producing step is skipped.

downstream · hop 1

Open process

Implement a Business System

Trigger · The authorized practice requires material system configuration or integration.

Carries · Authorized Practice Version · Practice System Requirements

If Authorize, enable, and introduce the practice is skipped, Implement a Business System loses Authorized Practice Version · Practice System Requirements.

downstream · hop 1

Open process

Operate and Improve a Process

Trigger · The practice passes bounded validation and readiness gates.

Carries · Authorized Practice Version · Practice Health Plan

If Authorize, enable, and introduce the practice is skipped, Operate and Improve a Process loses Authorized Practice Version · Practice Health Plan.

upstream · hop 1

Open process

Discover and Synthesize Process Evidence

Trigger · The practice design requires new or refreshed evidence.

Carries · Process Evidence Packet

If the handoff from Discover and Synthesize Process Evidence is skipped, Design and Validate a Recurring Human Practice loses Process Evidence Packet.

upstream · hop 1

Open process

Redesign Work and Workflow

Trigger · An approved or candidate workflow depends materially on a recurring human interaction.

Carries · Workflow Specification · Practice Design Need

If the handoff from Redesign Work and Workflow is skipped, Design and Validate a Recurring Human Practice loses Workflow Specification · Practice Design Need.

downstream · hop 2

Open process

Design and Govern a People Policy

Trigger · Policy and operating mechanisms receive operational acceptance.

Carries · Active Policy Version · Operational Acceptance

If Implement and transition the policy is skipped, Operate and Improve a Process loses Active Policy Version · Operational Acceptance.

downstream · hop 2

Open process

Onboard the New Hire

Trigger · The manager accepts transition to normal operation.

Carries · Onboarding Transition Record · Improvement Inputs

If Transition to normal operation and improve is skipped, Operate and Improve a Process loses Onboarding Transition Record · Improvement Inputs.

downstream · hop 2

Open process

Select a Business System

Trigger · A system and implementation path are approved.

Carries · System Decision · Commercial and Risk Record

If the handoff from Select a Business System is skipped, Implement a Business System loses System Decision · Commercial and Risk Record.

upstream · hop 2

Open process

Approve Workforce Need and Headcount

Trigger · The approved response includes redesigning, reallocating, stopping, or automating work.

Carries · Workforce Decision · Capacity and Capability Assessment

If Assess capacity and capability is skipped, Redesign Work and Workflow loses Workforce Decision · Capacity and Capability Assessment.

upstream · hop 2

Open process

Architect a People Management System

Trigger · The roadmap authorizes workflow or operating-process design.

Carries · Design Charter · Target System Architecture

If Architect components and interfaces is skipped, Redesign Work and Workflow loses Design Charter · Target System Architecture.

upstream · hop 2

Open process

Manage Team Capacity and Priorities

Trigger · Capacity review identifies work or process design as a material cause.

Carries · Capacity and Priority Review · Improvement Handoff

If Review outcomes and improve capacity design is skipped, Redesign Work and Workflow loses Capacity and Priority Review · Improvement Handoff.

upstream · hop 2

Open process

Review Manager-System Health

Trigger · The diagnosis identifies work or process design as a material cause.

Carries · Improvement Handoff

If the handoff from Review Manager-System Health is skipped, Redesign Work and Workflow loses Improvement Handoff.

Roles

Practice owner

Owns purpose, boundary, risk, authorization, sustained value, and retirement.

Practice designer

Studies context and designs, tests, documents, and improves the mechanism.

Representative participant

Tests usability, access, adaptation, output, burden, and unintended effects.

Process owner

Owns the supported workflow and accepts the practice input or output contract.

Qualified reviewer

Reviews accessibility, privacy, employment, safety, clinical, legal, labor, or regulated boundaries when triggered.

Systems + Data

Data object

Practice Design Brief

Anchors the practice to an operating need and defines its boundary.

System of record · Process and practice repository

Data object

Practice Specification

Defines the repeatable human mechanism and controlled variation.

System of record · Process and practice repository

Data object

Practice Validation Record

Preserves scenarios, participant evidence, defects, decisions, and conditions.

System of record · Practice validation repository

Data object

Practice Health Review

Connects operating evidence to support, redesign, continuation, or retirement.

System of record · Measurement and improvement system

Versioned process and practice repository

Required

Stores the authoritative specification, guide, connections, conditions, and history.

Accessible communication and collaboration

Required

Supports the synchronous, asynchronous, assistive, language, and scheduling paths the practice requires.

Controlled action and decision record

Required

Routes minimum necessary outputs and follow-through without creating shadow sensitive notes.

Learning and support channel

Required

Provides examples, rehearsal, feedback, coaching, help, and issue escalation.

Measures

outcome

Supported operating outcome

Does the practice contribute to the process outcome it was designed to support?

Context-specific outcome evidence interpreted with the practice contribution and other material influences explicit.

At agreed outcome-review points

quality

Usable output quality

Does the practice produce complete, relevant, and accepted outputs?

Practice outputs accepted by the connected owner without preventable clarification or rework, with qualitative defects retained.

Monthly or at the natural cycle

cycle-time

Follow-through cycle time

How long do commitments or decisions take to reach their defined closure?

Elapsed time from practice close to accepted disposition, reported by commitment or decision type.

Monthly

adoption

Appropriate practice use

Is the practice used when applicable and avoided when its conditions do not fit?

Eligible instances using the authorized practice plus correctly routed non-eligible instances, interpreted with non-use reasons.

During pilot; then quarterly

exceptions

Practice exceptions and adaptations

Where does use require adaptation, escalation, recovery, or abandonment?

Exceptions and adaptations by condition, participant context, cause, disposition, recurrence, and materiality.

During pilot; then quarterly

guardrail

Participant and operating guardrails

Does the practice create burden, exclusion, coercion, privacy loss, retaliation risk, unsafe action, or displaced work?

Triangulated accessibility, workload, privacy, safety, participation, complaint, misuse, and connected-operating signals, with protected reporting boundaries.

During pilot and at each formal review

Evidence + judgment

Lock process and practice design contract

lock-judgment

Lock judgment distinguishing a connected process from the recurring human interaction that makes a process step operable.

lock · process-and-practice-design · docs/PROCESS-AND-PRACTICE-DESIGN.md

Human-centered design and representative-use testing

cross-source-synthesis

Supports diagnosis, stakeholder participation, iterative design, testing, and evaluation in the context of use.

bicycle-guide · organization-development · hr-practice-and-talent.artifact.json

Deliberate practice, feedback, and transfer into work

cross-source-synthesis

Supports explanation, demonstration, realistic practice, feedback, support, and evidence of transfer rather than content exposure alone.

bicycle-guide · learning-and-development · hr-practice-and-talent.artifact.json

Lock accessible and inclusive practice boundary

lock-judgment

Lock judgment: practice design must include accessible routes and inspect how context and power affect participation.

lock · people-management-system-map · docs/PEOPLE-MANAGEMENT-SYSTEM-MAP.md

Lock ethical participation and minimum-record principle

lock-judgment

Lock judgment: do not require unsafe disclosure or create unnecessary sensitive records; provide alternate and qualified routes.

lock · process-and-practice-design · docs/PROCESS-AND-PRACTICE-DESIGN.md

Draft reference standard. Requires practitioner, accessibility, privacy, employment, labor, safety, clinical, regulated-work, and representative-participant review appropriate to each use before client deployment.