Design and Govern a People Policy

Flow · 6 controlled steps

1. 01

   Authorize and frame the policy decision

   Confirm why policy is needed and prevent policy from becoming a substitute for another intervention.

   • — State the desired outcome, affected populations, current problem, governing principles, consequence, scope, and decision authority.
   • — Identify current versions, variants, practices, systems, and qualified requirements.
   • — Test policy against alternative interventions.
   • — Define consultation, review, evidence, implementation, and acceptance requirements.

   Responsible

   Policy owner

   Output

   Policy Design Charter

   Decision

   Is a policy or policy change necessary and authorized?

2. 02

   Research requirements, evidence, and operating context

   Base design on qualified obligations, real operating conditions, affected experience, and traceable evidence.

   • — Resolve authoritative legal/specialist requirements through qualified owners.
   • — Discover relevant Lock, Corpus Library, CanonicAI, Book Profile, and Bicycle evidence.
   • — Trace current cases, decisions, exceptions, variants, failure modes, and connected processes.
   • — Consult affected and operating roles proportionately and protect confidentiality.
   • — Record uncertainty and conflicts among requirements or evidence.

   Responsible

   Policy designer

   Output

   Policy Basis and Requirements Record

   Decision

   Is the basis sufficient to draft policy within the authorized boundary?

3. 03

   Design policy and operational architecture

   Create the governing decision framework and the mechanisms required to make it real.

   • — Draft purpose, principles, scope, definitions, rights, responsibilities, requirements, prohibited actions, decision rights, exceptions, escalation, records, review, and version clauses.
   • — Design or identify the processes, practices, roles, systems, data, controls, support, accessibility, communications, and measures required.
   • — Define jurisdictional or workforce variants without hiding inconsistent treatment.
   • — Use plain language and examples without turning the policy into a procedural manual.

   Responsible

   Policy designer

   Output

   Draft Policy · Policy Operating Map

   Decision

   Is the draft clear, proportionate, operable, connected, and consistent with its authorized basis?

4. 04

   Review, test, and approve the policy

   Evaluate meaning and consequence before the policy acquires authority.

   • — Run qualified legal/specialist, owner, process, system, data/privacy, accessibility, communication, equity, and affected-user review as required.
   • — Test representative normal, edge, exception, conflict, and jurisdictional cases.
   • — Assess cost, capacity, unintended effects, enforceability, records, support, and connection impact.
   • — Resolve comments and preserve material decisions and dissent.
   • — Approve, condition, reject, or return with explicit authority.

   Responsible

   Authorized policy approver

   Output

   Policy Approval Record · Approved Policy Version

   Decision

   Should this version become the authorized policy?

5. 05

   Implement and transition the policy

   Make the approved policy usable through aligned operation rather than publication alone.

   • — Configure required processes, practices, roles, systems, records, controls, permissions, support, training, and partner interfaces.
   • — Publish an accessible authoritative version and targeted communications.
   • — Prepare managers and operating roles for decisions, questions, exceptions, and escalation.
   • — Retire or reconcile superseded versions, local artifacts, and conflicting system rules.
   • — Validate readiness and record operational acceptance.

   Responsible

   Policy owner

   Output

   Active Policy Version · Operational Acceptance · Communication and Support Record

   Decision

   Can the policy be operated consistently and safely on the effective date?

6. 06

   Operate, review, and revise the policy

   Use evidence, exceptions, affected experience, and changed requirements to keep policy useful and legitimate.

   • — Operate decisions, support, exceptions, records, controls, and escalations through connected processes.
   • — Monitor outcomes, quality, consistency, cycle time, understanding, use, exceptions, experience, equity, and guardrails.
   • — Review changes in law/specialist requirements, strategy, systems, workforce, and operating context.
   • — Distinguish operating failure from policy-design failure.
   • — Maintain, clarify, improve, redesign, suspend, or retire through authorized version change.

   Responsible

   Policy owner

   Output

   Policy Review Decision · Change Proposal or Retirement Record

   Decision

   What does the combined policy evidence require?

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.

Roles

Systems + Data

Measures

Evidence + judgment

Draft horizontal method. Requires practitioner, policy-operations, accessibility, and qualified legal/specialist review before publication or client use.