AIPOM Learning System Designer
What Is It
Design an operating system that moves role capability from instruction into applied work, feedback, coaching, peer learning, assessed progression, manager reinforcement, reusable practices, and measurable outcomes.
Why Use It
Courses and tool demos decay when people lack practice, feedback, permission, useful workflows, and support. A learning system connects competence to the real decisions and operating conditions people must improve.
When to Use It
Use after role competencies and priority workflows are clear. Start with a bounded role and practice where capability can be observed; do not launch an enterprise curriculum before identifying the work it must change.
What It Produces
- Target roles, decisions, competencies, and progression
- Instruction, deliberate practice, real-work application, coaching, peer feedback, and assessment
- Manager, community, resource, and workflow reinforcement
- Accessibility, support, stewardship, evidence, and improvement cadence
Who Should Participate
Include practitioners, role leaders, Product Operations, learning and development, managers, coaches, workflow owners, governance partners, and people affected by assessment or progression decisions.
Evidence to Bring
Bring competency maps, work artifacts, workflow evidence, decisions, failure examples, capability assessments, support requests, manager routines, reuse evidence, barriers, and outcome baselines.
How to Do It
- Define the role, decisions, workflow outcomes, and capability gap.
- Load supplied evidence and separate individual learning needs from system barriers.
- Select a small set of observable competencies and progression evidence.
- Design instruction only for knowledge needed before practice.
- Create representative practice with feedback, reflection, and safe failure.
- Integrate application into real work with coaching and peer review.
- Define manager reinforcement, communities, office hours, examples, and reusable skills.
- Establish accessible assessment and progression without turning the system into credential theater.
- Measure changed behavior, decision quality, workflow outcomes, reuse, and unintended burden.
- Assign stewardship, review cadence, and revise or retire rules.
Facilitation Protocol
Support guided, context-dump, and best-guess modes during design. Begin with the work outcome, not course topics. Ask only questions that change the learning architecture. In best-guess mode propose a small pilot and label organizational commitments and learner needs as assumptions.
Decision Logic
- Teach: a knowledge gap blocks safe practice.
- Practice: people know concepts but cannot perform representative work.
- Coach: judgment varies and feedback is the missing mechanism.
- Reinforce: capability exists but managers, incentives, access, or workflows suppress use.
- Reuse: effective local practice should become governed and discoverable.
- Redesign the system: repeated learner failure reflects authority, tool, policy, capacity, or workflow barriers.
Do not prescribe more training when evidence points to a non-learning constraint.
Completion Criteria
Finish with role and workflow scope, competency targets, applied pathway, practice and coaching, assessment evidence, system supports, accessibility and fairness safeguards, measures, owners, pilot decision, and improvement cadence.
Key Concepts
- Capability is demonstrated in work.
- Feedback and reflection convert activity into learning.
- Managers and workflows shape transfer more than course completion.
- Progression should increase responsible ownership, not status alone.
Organizational Applications
Use for Product Managers, leaders, designers, engineers, data specialists, governance partners, operations, facilitators, and cross-functional product teams.
Common Pitfalls
- Starting with a course catalog
- Giving every role identical training
- Measuring attendance and confidence only
- Assessing knowledge without applied judgment
- Blaming learners for system barriers
- Running a cohort with no ongoing owner
Combine With
Use aipom-adoption-impact-scorecard for outcome evidence, workflow-to-skill-converter to preserve effective practice, and aipom-operating-model-retrospective to address structural barriers.
Assets and Templates
- Learning system template
- Synthetic worked example
- Weak example
Sources
This workflow is an original AIPOM synthesis of competency-based development, deliberate practice, workplace learning, coaching, transfer, and continuous improvement.
1---2name: aipom-learning-system-designer3description: Design a role-based applied learning system with real work, practice, coaching, peer feedback, progression, reinforcement, stewardship, and outcome evidence.4---56# AIPOM Learning System Designer78## What Is It910Design an operating system that moves role capability from instruction into applied work, feedback, coaching, peer learning, assessed progression, manager reinforcement, reusable practices, and measurable outcomes.1112## Why Use It1314Courses and tool demos decay when people lack practice, feedback, permission, useful workflows, and support. A learning system connects competence to the real decisions and operating conditions people must improve.1516## When to Use It1718Use after role competencies and priority workflows are clear. Start with a bounded role and practice where capability can be observed; do not launch an enterprise curriculum before identifying the work it must change.1920## What It Produces2122- Target roles, decisions, competencies, and progression23- Instruction, deliberate practice, real-work application, coaching, peer feedback, and assessment24- Manager, community, resource, and workflow reinforcement25- Accessibility, support, stewardship, evidence, and improvement cadence2627## Who Should Participate2829Include practitioners, role leaders, Product Operations, learning and development, managers, coaches, workflow owners, governance partners, and people affected by assessment or progression decisions.3031## Evidence to Bring3233Bring competency maps, work artifacts, workflow evidence, decisions, failure examples, capability assessments, support requests, manager routines, reuse evidence, barriers, and outcome baselines.3435## How to Do It36371. Define the role, decisions, workflow outcomes, and capability gap.382. Load supplied evidence and separate individual learning needs from system barriers.393. Select a small set of observable competencies and progression evidence.404. Design instruction only for knowledge needed before practice.415. Create representative practice with feedback, reflection, and safe failure.426. Integrate application into real work with coaching and peer review.437. Define manager reinforcement, communities, office hours, examples, and reusable skills.448. Establish accessible assessment and progression without turning the system into credential theater.459. Measure changed behavior, decision quality, workflow outcomes, reuse, and unintended burden.4610. Assign stewardship, review cadence, and revise or retire rules.4748## Facilitation Protocol4950Support guided, context-dump, and best-guess modes during design. Begin with the work outcome, not course topics. Ask only questions that change the learning architecture. In best-guess mode propose a small pilot and label organizational commitments and learner needs as assumptions.5152## Decision Logic53541. **Teach:** a knowledge gap blocks safe practice.552. **Practice:** people know concepts but cannot perform representative work.563. **Coach:** judgment varies and feedback is the missing mechanism.574. **Reinforce:** capability exists but managers, incentives, access, or workflows suppress use.585. **Reuse:** effective local practice should become governed and discoverable.596. **Redesign the system:** repeated learner failure reflects authority, tool, policy, capacity, or workflow barriers.6061Do not prescribe more training when evidence points to a non-learning constraint.6263## Completion Criteria6465Finish with role and workflow scope, competency targets, applied pathway, practice and coaching, assessment evidence, system supports, accessibility and fairness safeguards, measures, owners, pilot decision, and improvement cadence.6667## Key Concepts6869- Capability is demonstrated in work.70- Feedback and reflection convert activity into learning.71- Managers and workflows shape transfer more than course completion.72- Progression should increase responsible ownership, not status alone.7374## Organizational Applications7576Use for Product Managers, leaders, designers, engineers, data specialists, governance partners, operations, facilitators, and cross-functional product teams.7778## Common Pitfalls7980- Starting with a course catalog81- Giving every role identical training82- Measuring attendance and confidence only83- Assessing knowledge without applied judgment84- Blaming learners for system barriers85- Running a cohort with no ongoing owner8687## Combine With8889Use `aipom-adoption-impact-scorecard` for outcome evidence, `workflow-to-skill-converter` to preserve effective practice, and `aipom-operating-model-retrospective` to address structural barriers.9091## Assets and Templates9293- [Learning system template](template.md)94- [Synthetic worked example](examples/worked-example.md)95- [Weak example](examples/weak-example.md)9697## Sources9899This workflow is an original AIPOM synthesis of competency-based development, deliberate practice, workplace learning, coaching, transfer, and continuous improvement.
Dean Peters