Why a Sprint Format Works for AI Adoption
Most AI adoption programmes fail for one of two reasons: they try to change everything at once (overwhelming), or they offer optional training that nobody attends (ineffective). The AI Adoption Sprint solves both problems.
A sprint is time-boxed, focused, and produces a concrete output. It creates the social pressure of a shared deadline and the psychological safety of an explicit experiment window — "we are trying this for two weeks, not committing to it forever." This framing dramatically increases participation and honest feedback.
The structure below is the one we use with McKenna clients across Agile, OKR, and AI transformation engagements. It works for teams of 5 to 50.
Before the Sprint: Prerequisites
The sprint works best when three things are in place before Day 1:
- A sponsor with authority — Someone with the power to say "this team will spend time on the sprint" and mean it. Without this, the sprint competes with business-as-usual and loses.
- AI tool access — All participants need access to at least one AI tool before the sprint starts. Ideally this is a tool already licensed by the organisation (Microsoft Copilot, ChatGPT Enterprise, GitHub Copilot, etc.). Sort access issues out before Day 1 — do not let licensing delays derail the first week.
- A sprint challenge — A real work problem the team will try to solve using AI tools during the sprint. Generic exercises produce generic learning. A real challenge (rewrite our monthly reporting pack, generate our Q2 OKR first draft, automate our sprint summary) produces learning that sticks.
Week 1: Exploration
Day 1: Kickoff and Tool Walk-Through (2 hours)
Start with a 30-minute session on the sprint challenge and why AI might help. Then spend 90 minutes on hands-on exploration of the primary AI tool. Give everyone the same three prompts to run: one from their actual work, one deliberately bad prompt to observe failure modes, one that stretches the tool's capabilities. Share and discuss results as a group.
The goal of Day 1 is to get past the "I don't know how to start" barrier and to surface early surprises — both positive and negative.
Days 2–4: Daily Experimentation
Each team member sets a personal AI experiment each day: one task they will try to do faster or better using an AI tool. This should be a real task from their current workload, not a simulation. At the end of each day, they record: what they tried, how long it took with AI vs. their estimate without AI, and one observation about the experience.
This daily habit builds the experimentation muscle that is the foundation of AI literacy. It also generates honest, specific data about where AI adds value and where it does not — which is more useful than any vendor demonstration.
Day 5: Week 1 Retrospective (45 minutes)
Gather the team's experiment logs and run a structured retrospective: what worked, what did not, what surprised you, what do you want to try in Week 2. An AI tool should be used to synthesise the retrospective data — this is itself an example of AI in practice and models the behaviour you are trying to embed.
Week 2: Integration
Days 6–9: Sprint Challenge Work
Week 2 pivots from individual exploration to collective challenge. The team works on the sprint challenge defined in the prerequisites — using AI tools as part of their standard workflow rather than as a separate experiment. The facilitator should be available to help with prompting strategies and to observe where friction occurs.
The goal is to get one complete end-to-end example of the sprint challenge being done with AI assistance. This becomes the demonstration artefact for the sprint close.
Day 10: Sprint Close and Playbook
The final day has two outputs:
- Sprint close presentation (30 minutes): The team demos what they built with AI assistance and compares it to the old way. Be honest about where AI helped and where it did not. Leaders often underestimate how important it is to hear the nuanced view — not just the wins.
- Team AI Playbook (60 minutes): A one-page document capturing the specific prompts, tools, and workflows that produced the best results. This is the institutional knowledge the sprint creates — without it, the learning exists only in individuals' heads and will fade within weeks.
Common Mistakes to Avoid
Using the Sprint as a Sales Demo
If leadership uses the sprint close as an opportunity to showcase AI adoption to stakeholders rather than to generate honest learning, teams will learn to curate their experience rather than report it accurately. This undermines the learning value of every future sprint.
Not Protecting Sprint Time
The single biggest predictor of sprint success is whether participants actually have time to do the experiments. If the sprint competes with sprint ceremonies, client calls, and normal BAU demands, it will lose. The sponsor must protect time explicitly.
Moving Too Fast to Scale
The AI Adoption Sprint is a learning mechanism, not a rollout mechanism. The output — the playbook and the evidence base — should inform a larger rollout plan. But rolling out before the sprint has generated honest data about what works in this organisation's specific context is a common and costly mistake.
What Comes After the Sprint
A two-week sprint builds the foundation for adoption. It does not complete it. After the sprint, the organisation needs:
- A rollout plan based on sprint learnings, not based on vendor promises
- An AI champion in each team (see our AI Champion Model article)
- A quarterly AI capability review to track whether adoption is deepening or plateauing
- Updated team ways of working that embed the AI habits developed in the sprint into standard practice
The sprint is where you learn what AI can do for your organisation. What happens in the three months after the sprint determines whether that learning compounds or fades.
