Training & enablement
Role-based enablement paths, a champions network that scales what training can't, and the environment design that makes the safe way the easy way.
'We bought licenses and ran a lunch-and-learn' is the enablement plan of programs that plateau at 15% adoption. Skills are the transmission between your portfolio's engine and the organization's wheels — and they're built with the same portfolio discipline as everything else:
- Enablement is role-based or it's noise. Everyone gets the floor: what the tools are, what's allowed (the one-page policy), how to prompt and verify — a day, not a semester (the shape of our AI Foundations course, and the reason it exists in every track). Beyond the floor, paths diverge by role: analysts learn AI-assisted investigation; ops staff learn workflow-and-gate patterns; the ETA team needs real technical depth; leaders need — well, this course. Map roles to paths once, then route people, don't broadcast content.
- Champions scale what training can't. One volunteer per team, slightly deeper trained, visibly titled, with a monthly hour together: they answer the small questions that never reach a helpdesk ('how do I prompt it for quotes?'), surface the friction that never reaches a survey, and model the verify-everything habit socially. Champions networks are the highest-ROI line in any enablement budget, and they cost almost nothing but recognition.
- Make the safe way the easy way. Enablement is environment design as much as teaching: approved tools one click away with SSO, the good prompt templates preloaded where work happens, the intake form linked in the tool itself, defaults set so the compliant path is the shortest path. Every extra click on the safe path is a user delivered to the shadow path. Your IT lead owns half of enablement and may not know it yet.
Sequencing: train against the portfolio, not the calendar
Generic training decays in two weeks; training that lands the Monday before your workflow changes sticks. Sequence enablement to the rollout plan: the CS team gets their path as triage pilots start, sales-ops as extraction lands, and the floor-level foundations run continuously for everyone else. This is also the budget argument: enablement charged per-initiative (like data readiness) rather than as an amorphous 'training program' survives CFO review, because each tranche has a rollout it de-risks and an adoption metric it moves.
The single most important skill across every path is calibrated trust: use the draft, check the claim, catch the failure, report it without embarrassment. Installed, it makes every deployment safer than its model. Skipped, it produces rubber-stamp review — approval rates near 100%, humans as decoration — which is how organizations discover their 'human in the loop' was a haiku. Your governance gauges (Module 4) and your enablement content teach the same lesson from two sides; make sure both actually say it.