Wedge
Start with the narrowest measurable department, usually Support, and define the proof gate.
AIducation starts with one measurable wedge, then expands across the workforce using readiness gates, governance controls, manager evidence, integrations, and department-specific academy plans.
The planner turns product architecture into a buyer-facing implementation sequence: who owns each step, what gets proven, and when expansion should happen.
Start with the narrowest measurable department, usually Support, and define the proof gate.
Measure current readiness before practice so the exit evidence means something.
Publish approved tools, policy controls, misuse reporting, and audit expectations.
Use manager evidence to pick the next department instead of expanding on vibes.
Every role gets a launch trigger, cohort recommendation, readiness gates, integration requirements, adoption risks, manager artifacts, and expansion recommendations.
Use Support as the first measurable beachhead for policy-safe AI work.
Launch when sales managers can name the first workflow, risk, and proof artifact.
Launch when marketing managers can name the first workflow, risk, and proof artifact.
Launch when hr managers can name the first workflow, risk, and proof artifact.
Launch when finance managers can name the first workflow, risk, and proof artifact.
Launch when engineering managers can name the first workflow, risk, and proof artifact.
Launch when product managers can name the first workflow, risk, and proof artifact.
Launch when executives managers can name the first workflow, risk, and proof artifact.
Launch when operations managers can name the first workflow, risk, and proof artifact.
Support remains the commercial beachhead, but the rollout plan is explicitly designed to expand into the next departments once the manager evidence clears the gate.
Model rollout ROI