Playbook: Learning & Capability Development
Core Subprocesses: 1) Critical Capability Mapping · 2) Learning Design & Pathways · 3) Delivery & Enablement · 4) Transfer & Application · 5) Review & Adapt
Subprocess 1 · Critical Capability Mapping
Purpose
Make mission-critical skills visible (today & next 12–24 months), with depth and risk exposure.
- Outputs: capability taxonomy, proficiency map, risk heatmap, role→skill graph.
- Non-goal: exhaustive catalogs ohne Business-Relevanz.
Guardrails
- Business-backlog first (Strategy→Work→Skill).
- Privacy: kein „Hidden Surveillance“ via Lern- oder Tooldaten.
- Bias: Skill-Definitionen & Benchmarks reviewen (Diversity).
Play A Strategy-back Capability Scan (Human-led · Perceptive + Reflective)
When
- Neue Strategie, neue Produkte, M&A.
Flow
- Strategy→Work decomposition (value streams, missions).
- Work→Skill extraction (critical few).
- Proficiency mapping (teams, roles).
- Risk heatmap (single points of failure).
KPIs
- Time-to-map < 6 Wochen
- >80% leadership buy-in
Risks
- Over-engineering → „critical few“ erzwingen.
Play B Augmented Skill Graph Builder (Human-augmented · Perceptive + Generative + Predictive)
Flow
- Pull job/learning data → normalize.
- AI suggests skills, synonyms, relations.
- Human curation; remove noise.
- Predictive: proficiency gaps + risk forecast.
KPIs
- Mapping speed +50%
- Noise < 10%
Governance
- Glossar + Review-Zyklen quartalsweise.
Play C Signal-Driven Refresh (Algorithmic-autonomous · Perceptive + Predictive)
Flow
- Signals: tech releases, market demand, project pipeline.
- Auto-alerts bei Skill-drift >= Schwelle.
- Queue für Human validation.
KPIs
- Drift detection < 2 Wochen
- Validation backlog < 10 Arbeitstage
