How do you run a team AI reset day?
Summary: Tools update constantly, and teams drift without a shared space to learn from each other. Last week, our central team ran a full AI reset day to close that gap. Spark’s Operations Director, Chris Caira, outlines the day’s six-step structure to help you run your own.
Date: 29.07.26
Author: Chris Caira
Read time: 4 min read
Spark AI is the AI performance partner that builds organisation-wide AI capability for creative agencies and brand teams. We take ambitious teams from fragmented experimentation to AI embedded across your people, processes and systems – so it delivers real commercial impact.
Why should you have a team AI day?
Tools update constantly, and with everyone's heads-down on their own projects, it's easy for a team to grow without a shared space to learn from each other. Left unchecked, that turns into everyone running their own private version of AI, with separate prompts and habits nobody else can see. Last week, our central team stepped out of the business for a day to fix that. A reset as a team rather than as individuals.
Why start with deliberately mixed pairs?
A full day, everyone, no exceptions – not a lunch-and-learn squeezed around delivery. And the pairs matter: mix backgrounds, perspectives and skills. Put the operations brain next to the creative one, the longest-serving next to the newest joiner. Two people with different instincts looking at the same problem build better things than two who think alike – and the knowledge spreads in both directions.
Why lead with quick wins everyone takes home?
First hour, get the quick wins out there: things that pay for themselves the same week. A morning brief that runs on a schedule before you're at your desk. Personal instructions so the AI stops flattering you and starts challenging you. Dictation, because you'll give ten times more context speaking than typing. Setting up an AI Chief of Staff to brief you on the day and kick off tasks. These fundamentals are always where the room switches on, and even once you have them set up they need continuous revisiting and refreshing.
One of our team members had been out of office for two days. Her first morning brief came back with what she'd have spent half the morning piecing together from her inbox, including a client negotiation a colleague had covered on her behalf. "That would have saved me half an hour," she said, looking slightly annoyed she hadn't been running it all along.
Why reinforce the rule before the tools?
Active minds, not autopilot. Form your own view first. Brief the AI well. Then interrogate what comes back. If you don't know what's in the output, you've outsourced too much of your own thinking. AI can generate a 10-page document for something that only needs one. It can write it quickly, but nobody can read it quickly. If you skip the "is this good?" step, the time you've saved has just been lost by whoever has to wade through the output. AI is the middle step, never the last one. Every exercise for the rest of the day ran through that filter.
Why audit your shared foundations first?
One source of truth for company context – services, pricing, who your clients are, how you sound – with a named owner and a review rhythm. This is the first thing to sprawl as a team grows, so we went looking for it. Sure enough, we found three slightly different versions of the same context in three places, exactly the drift we warn clients about. Caught, and cut back to one, with a new owner appointed. Unglamorous, and probably the highest-value fix of the day.
Why explore before you build?
There's a library of pre-built skills sitting in these tools that most teams never open. And they are excellent. So before anyone built anything, everyone picked one and tested it on real work. Then, and only then, build your own – and the trick is to do the task once, conversationally, until the output is right, then save the whole process as a reusable skill.
Why leave with names against things?
This is the step most teams skip, and it's the one that decides whether the day was a reset or a jolly. We left with a shared backlog of what we're building next, a name against each item, a single owner for the skills library and its version control, and the next quarter's cadence back in everyone's diaries.
Frequently asked questions
Does this only work for teams that are already confident with AI?
No. The structure is built to raise the floor, not just reward the people already ahead. Mixed pairing does the work here – pairing your most fluent people with your newest joiners closes the gap faster than training either group alone.
How long should a session like this take?
We ran ours for a full day. If a full day isn't realistic yet, protect at least a half-day with no client work scheduled either side of it.
How often should you run a team AI day?
We run ours every quarter. That's frequent enough that there's usually been a real update worth bringing everyone up to speed on, but spaced out enough to actually get on with the work in between.
Spark AI – AI training, consultancy and agent building for agencies and brands. Your AI performance partner
