Build a 5-step AI adoption playbook for your team

Description

Your exec just declared "AI-first" but the team is stuck on vague mandates, procurement bottlenecks, and no guidance on which workflows to automate first. This five-step playbook — explain the how, track and reward, cut the red tape, turn enthusiasts into teachers, prioritize high-impact tasks — synthesizes the tactics used at Shopify, Ramp, Duolingo, Zapier, Intercom, and Whoop into a sequenced plan you can put in front of leadership this week.

You are a product operator designing an AI adoption playbook for {{team_or_function}} at {{company_stage_and_size}}. Current baseline: {{current_ai_tools_in_use}}. Time horizon: {{rollout_timeframe}}. Success metric leadership cares about: {{target_success_metric}}.

Build a sequenced, 5-step playbook patterned on the tactics used by AI-forward companies such as Shopify, Ramp, Duolingo, Zapier, Intercom, and Whoop. For each step, produce concrete tactics I can implement — not abstract principles.

## Step 1 — Explain the *how*
- Draft the exec memo: what "AI-first" means for daily work at {{team_or_function}}, with 3 specific tactics (not generic "use AI more")
- "Code red" kickoff option: should we call an all-hands moment? If yes, agenda + pre-work
- Define what "embracing AI" means for each sub-role in {{team_or_function}}
- Lead-by-example script: 3 live demos I or a senior leader can run this month

## Step 2 — Track and reward adoption
- Input metrics (who is using AI): list 3 measurable leading indicators
- Output metrics (business value): list 3 lagging indicators tied to {{target_success_metric}}
- Performance review integration: draft the 1-5 scale rubric for "reflexively uses AI tools"
- Transparency play: should we publish team-level AI usage? Pros, cons, suggested cadence.
- 30-day challenge: design it with bite-size 2-minute daily tasks

## Step 3 — Cut the red tape
- AI tool approval process: current state audit template + 3 bottlenecks to pre-empt
- Learning budget: recommended amount per employee and policy for {{company_stage_and_size}}
- Procurement fast-track: who owns it, SLAs, escalation path
- Tool shortlist: Claude, Perplexity, Cursor, Copilot — rationalize for {{team_or_function}}

## Step 4 — Turn enthusiasts into teachers
- Identify power users: query template to find them (Slack activity, tool usage, demo volume)
- Weekly cadence: pick one — AI Fridays (2-hour block), live demos (60+ attendee target), Show & Tell at all-hands
- AI SWAT team charter: mission, staffing, how they pick targets
- Promotion signal: rewrite our promotion rubric to include "uplevels others on AI"

## Step 5 — Prioritize high-impact tasks
- High-volume, repetitive tasks at {{team_or_function}}: rank top 5 by time-saved potential
- Rigorous evaluation framework: for each AI feature we build, answer the 4 questions — (1) what customer problem, (2) is AI better than non-AI, (3) what ground-truth dataset and evals, (4) how we handle model failure
- Distinguish theater from adoption: red flags that signal "flashy demo" not real adoption

## Output
Produce:
1. A one-page playbook summary with the 5 steps and the single most important tactic per step for my context
2. A 90-day rollout timeline with week-by-week owners
3. The 3 biggest risks specific to {{company_stage_and_size}} and how to pre-empt each
4. A draft Slack announcement I can send to the team tomorrow

Keep it opinionated. Pick the tactic most likely to work for {{team_or_function}} instead of listing all options.

Customize This Prompt