06 — Enablement
Status: Optional · take this after Core Judgment · do not take it first
Purpose
This pack is for people responsible for growing AI capability in others — teams, departments, or the wider organization. It assumes you have completed Core Judgment. You cannot usefully enable judgment in other people if your own filters are still weak. The goal is practical: design learning and support that produces people who can decide better, not people who simply attended more sessions or collected more prompts.
The modules
- What People Actually Need to Be Able to Do — most enablement starts with tools or content; better enablement starts with the decisions people must make
- Design Learning That Produces Evidence — attendance is not competence; completion is not capability
- Transfer, Not Dependence — the point of enablement is that people can operate without you
- Keep the Content Honest as Tools Change — keep the durable core stable; treat product details as thin, dated overlays
- Measure Whether Judgment Actually Improved — satisfaction scores and completion rates are secondary at best
Who this is for
L&D, enablement teams, technical trainers, and the people who answer the same five questions until they build a system to answer them.
What you will be able to decide after this
- What people actually need to learn vs. what they need access, policy, or permission to do.
- How to design learning that produces evidence, not attendance.
- How to build transfer so people operate without ongoing dependence.
- How to keep durable judgment separate from temporary tool details.
- How to measure whether decision quality actually improved — and what to change when it didn't.
Rules of this pack
- Every module produces a usable enablement artifact: a capability statement, a design map, a transfer plan, an overlay schedule, a measurement approach.
- Core Judgment is assumed and referenced — never re-taught.
- 45–90 minutes per module. The point is the transfer, not the theory.
The checkpoint
You are getting value from this pack when you can:
- Define the decisions people must handle and what good judgment looks like
- Design learning that produces observable evidence instead of attendance
- Build transfer so people can operate without ongoing dependence
- Keep durable judgment separate from temporary tool details
- Measure whether decision quality actually improved
If your enablement still centers on tool demos, prompt libraries, or completion metrics, stay here and redesign around judgment and evidence.