# Build and Operate a Development Plan

Status: draft · v0.1.0 · Performance and Development System
draft reference — not a fitted standard

Build capability through relevant work, deliberate practice, feedback, support, and evidence—not a catalog of courses.

## Purpose
Connect an important capability need or aspiration to an operating outcome and run a supported learning cycle until evidence justifies adaptation, transfer, continuation, or closure.

## Steps
1. Frame the capability need — Define why development matters before selecting an activity.
2. Define capability and transfer evidence — Specify what useful learning would look like in relevant work.
3. Design the development path — Combine the smallest useful set of learning methods around actual capability-building.
4. Secure opportunity and support — Make the organization’s development commitments operational.
5. Approve and acknowledge the plan — Create one realistic, controlled development agreement.
6. Practice, apply, and receive feedback — Build capability through cycles of action, evidence, reflection, and adjustment.
7. Evaluate transfer and decide the next state — Close or continue the plan through evidence rather than elapsed time or activity completion.

## Connections
- upstream: Review Performance and Contribution (/processes/review-performance-and-contribution) — trigger: Development is an accepted forward implication.
- upstream: Approve Workforce Need and Headcount (/processes/approve-workforce-need) — trigger: Development is selected as a workforce response.
- downstream: Align Role Outcomes and Expectations (/processes/align-role-outcomes) — trigger: Capability evidence changes appropriate work or expectations.
- downstream: Make a Progression or Talent Decision (/processes/make-progression-or-talent-decision) — trigger: A separate talent decision is authorized.

## Measures
- Capability transfer to work: Context-specific assessment of approved capability evidence and work application; not course completion or causal attribution alone.
- Development evidence completeness: Required disposition evidence fields complete or explicitly waived divided by all required fields.
- Time to meaningful practice: Elapsed time from approval to verified meaningful practice, with delay cause and owner.
- Development-plan operation: Completed material plan events divided by due material events, interpreted for relevance rather than compliance alone.
- Development barrier pattern: Barriers by type, capability, owner, severity, age, cause, and disposition.
- Access, burden, safety, dignity, and promise guardrail: Qualified review of access, assignments, workload, support, outcomes, participant feedback, and downstream use; not a causal or legal conclusion.