{"slug":"design-and-govern-people-policy","name":"Design and Govern a People Policy","family":"Lock Method","version":"0.1.0","status":"draft","note":"draft reference — not a fitted standard","summary":"Create a policy that expresses authorized principles, requirements, rights, boundaries, decisions, and exceptions—and connect it to the processes and practices that make it operable.","purpose":"Turn an approved policy need into a clear, proportionate, reviewable policy with qualified input, operational mechanisms, communication, ownership, measurement, and controlled revision.","steps":[{"sequence":1,"name":"Authorize and frame the policy decision","purpose":"Confirm why policy is needed and prevent policy from becoming a substitute for another intervention."},{"sequence":2,"name":"Research requirements, evidence, and operating context","purpose":"Base design on qualified obligations, real operating conditions, affected experience, and traceable evidence."},{"sequence":3,"name":"Design policy and operational architecture","purpose":"Create the governing decision framework and the mechanisms required to make it real."},{"sequence":4,"name":"Review, test, and approve the policy","purpose":"Evaluate meaning and consequence before the policy acquires authority."},{"sequence":5,"name":"Implement and transition the policy","purpose":"Make the approved policy usable through aligned operation rather than publication alone."},{"sequence":6,"name":"Operate, review, and revise the policy","purpose":"Use evidence, exceptions, affected experience, and changed requirements to keep policy useful and legitimate."}],"connections":[{"direction":"upstream","processName":"Architect a People Management System","processSlug":"architect-people-management-system","trigger":"The system roadmap authorizes policy design or revision."},{"direction":"upstream","processName":"Discover and Synthesize Process Evidence","processSlug":"discover-and-synthesize-process-evidence","trigger":"Policy design or review requires evidence beyond authoritative requirements and current operating records."},{"direction":"downstream","processName":"Redesign Work and Workflow","processSlug":"redesign-work-and-workflow","trigger":"Policy implementation requires a new or revised operating process."},{"direction":"downstream","processName":"Operate and Improve a Process","processSlug":"operate-and-improve-process","trigger":"Policy and operating mechanisms receive operational acceptance."}],"plannedConnections":[],"measures":[{"name":"Policy outcome evidence","definition":"The policy-specific outcome set interpreted with context, connected-process evidence, and other material influences.","cadence":"At scheduled policy review"},{"name":"Decision quality and consistency","definition":"Reviewed decisions meeting policy criteria, authority, rationale, record, and exception requirements, with legitimate variation separated.","cadence":"Quarterly or risk-based"},{"name":"Policy decision cycle time","definition":"Elapsed time by decision/exception type, consequence, population, and disposition.","cadence":"Monthly or quarterly"},{"name":"Policy understanding and controlled use","definition":"Evidence of authoritative-version use, comprehension, support demand, and correct routing for eligible decisions.","cadence":"After launch and quarterly"},{"name":"Policy exception pattern","definition":"Exceptions by reason, policy clause, process, population, severity, owner, age, and disposition.","cadence":"Monthly or quarterly"},{"name":"Policy guardrails","definition":"Context-specific guardrail evidence reviewed with outcomes, exceptions, experience, and qualified-owner input.","cadence":"At every material review"}]}