A practical path to team AI adoption
Build your team's AI capability through real work.
A facilitated six-week program that helps employees scope, guide, test, and share a useful AI project—with people accountable for the outcome.
What "AI intern" means here
Think of AI as an intern: it needs a clear assignment, useful context, feedback, and review. Participants learn to manage that work while remaining responsible for its quality and use.
- You define.
- You guide.
- You validate.
- You own it.
Who it fits
- Teams with recurring work that follows a pattern
- A supportive sponsor who can clear time and make decisions
- AI tools the organization has already approved
- Participants with time to take part each week
No developer background is required. Scope depends on your tools, data, participant experience, and the support available.
What's included
- Kickoff session
- A weekly rhythm
- Coaching and office hours
- Participant templates
- Peer demonstrations
- Sponsor touchpoints
- Demo Day
- Reusable assets
Example projects
These are illustrative examples, not a fixed menu. Each project needs a human reviewer and a test of whether it is actually useful.
A recurring report draft
Prepare a first version of a report that someone produces regularly, then review and correct it.
A research summary
Summarize source material against a defined set of questions the team actually needs answered.
A document review
Check documents against an agreed checklist and flag what needs a person's attention.
A structured project update
Turn meeting notes into a consistent update format the team can scan quickly.
The typical proposed structure
Final scope is agreed for your team before the program begins.
Before kickoff
Alignment and setup
Week 1
Define and baseline
Week 2
First version
Week 3
Midpoint demos
Week 4
Reliability
Week 5
Document and measure
Week 6
Demo Day
+30 days
Follow-up
Before kickoff
Alignment and setup
Week 1
Define and baseline
Week 2
First version
Week 3
Midpoint demos
Week 4
Reliability
Week 5
Document and measure
Week 6
Demo Day
+30 days
Follow-up
- Before kickoffSponsor alignment, tool readiness, information boundaries, and project selection.
- Week 1Define the assignment and establish a baseline.
- Week 2Build a first version, plus a prompting clinic.
- Week 3Midpoint demonstrations and testing.
- Week 4Improve reliability.
- Week 5Document, measure, and prepare handoff.
- Week 6Demo Day and next-step decisions.
- Proposed 30-day follow-upReview adoption and what has held up in real use.
After Demo Day
Results are shared, learnings are captured, and projects are assigned a future path.
Graduate
Continue with clear ownership and appropriate controls.
Refine
Make specific improvements before deciding again.
Share
Preserve the reusable methods and lessons.
Archive
Stop the experiment and retain what was learned.
How progress is measured
We agree what to look at before the work starts. We do not promise a particular saving or return.
- Time spent on the task
- Quality of the output
- Rework required
- Repeat use after the program
- Participant confidence, where relevant
Questions
Interested in a program for your team?
Tell us about the team and the kind of work you'd like them to take on, and we'll talk through the right format.