PLAYBOOK
Employee AI enablement playbook
Enablement is not a one-time training; it is a program with stations: preparation before launch, a candid launch, wave-based widening, and register-measured success.
The employee enablement playbook has four stations: preparation (inventory, roles, templates), launch (two departments, candor page), widening (waves built on the two departments' register), and measurement (monthly report reading adoption and adjusting settings). Each station has a named lead and approver.
THE PATH
The four stations
Prepare, launch, widen, measure — and no station opens before the previous closes on register numbers.
WEEKS 1–2
Prepare: inventory, roles, templates
Inventory current usage blamelessly, draw the first role map (three suffice), and prepare templates for the most common cases — before anyone sees a single interface.
WEEKS 3–4
Launch: two departments, declared candor
Open the gate to the two chosen departments — and declare what is recorded and what is never collected before first login. Candor is what pulls people out of the shadow willingly.
WEEKS 5–8
Widen: waves guided by the register
After two weeks of the two-department launch, the register answers: what was used, what was untouched, which use case needs a new template. The next departments benefit from all of it.
MONTH 2 AND BEYOND
Measure: monthly report moves the settings
The register measures: usage growth, decline of external tool requests, and exception cases. The report is read in a monthly meeting and closed with one decision: what changes in settings next month.
Stations and durations are illustrative — the cadence is tuned to your organization's size and technical readiness.
IN DETAIL
Each station detailed
Outputs are clear for every station — program success is measured by the register, not impressions.
WEEKS 1–2
Preparation outputs
Usage map by department, documented role map, three ready templates, two pilot departments chosen, and the launch note drafted.
WEEKS 3–4
Launch outputs
A candor page published, an onboarding session per department, a new-tool request channel announced, and the first register board read.
WEEKS 5–8
Widening outputs
A second wave of departments, templates updated from register usage, and any roles needing review identified.
MONTH 2 AND BEYOND
Measurement outputs
A monthly per-department report, a specific decision on settings changes, and a list of cases needing additional enablement.
ROLES
Roles
Who leads, who approves, who reviews — three questions every successful program answers.
- Who leads: The transformation or HR lead — owns the timeline and follows up on stations.
- Who approves: IT and security leadership — approves settings and sign off on widening.
- Who reviews: Compliance and legal — review the candor page and processing contracts before launch.
CLOSE
Close: enablement doesn't end at launch
Successful programs turn measurement into moving settings — what the register says changes boundaries, roles, and templates every quarter. Enablement that is not measured gradually becomes a rigid structure that no longer reflects actual usage.
IMPLEMENTATION QUESTIONS
Asked in every launch.
Do we need to complete every station before moving to the next?
The core outputs of each station, yes — but partial overlap between preparation and launch is practical in large organizations.
How long does the full playbook take?
The illustrative frame is eight weeks for the first three stations, with the fourth ongoing — the actual cadence is tuned to your size and technical readiness.
What do we do if a department declines to participate in the launch?
Refusal is valuable data — ask what prevents them. If the gate is harder than their current alternative, that is a solvable technical issue. If data concerns, the security conversation comes first.
The first station starts with a session.
Print the playbook and pencil in the roles — then come with the hard questions: what prevents your first station this week?