AI Play/Pause Days
Use AI as much as possible for one workday, then work without it for another. Compare the experience as a team and agree on the AI habits, workflows, and practices worth carrying forward.
PREP TIME
20m
Run TIME
2 days
Persons
3-15
5-second summary
- Run one AI Play Day and one AI Pause Day, then compare what felt easier, harder, better, or worse.
- Use end-of-day reflections to capture observations before they fade.
- Turn individual experiences into 1–3 shared practices your team can keep or scale.
WHAT YOU WILL NEED
- Shared document, like a Confluence page or whiteboard
- AI tool, such as Atlassian’s Rovo or your preferred AI tool
- Meeting space or video conferencing
PLAY resources
How to run AI Play and Pause Days
Work one day with AI and one day without it to sharpen your team’s judgment about when and how to use AI.
What are AI Play/Pause Days?
AI Play/Pause is a two-day team experiment designed to answer a few seemingly simple questions: Where does AI actually help your team? Where does it get in the way? And where would human thinking be better?
Here's how the Play works:
Your team picks two back-to-back workdays. On AI Play Day, everyone uses AI for as much of their work as they can: drafting, summarizing, meeting prep, brainstorming, you name it. On AI Pause Day, they do similar work without any AI tools.
Then the team comes together to compare notes. What worked better and felt better with and without AI? Where had AI become the default choice, but human judgment would be better?
The magic is in the contrast. Experiencing both extremes back-to-back – and then talking about it as a team – is what creates real, shared insight into how AI fits (and doesn't fit) into your team's work.
Why run this Play?
Because most teams don't realize how automatic their AI use has become or whether it's actually paying off.
When Atlassian's Teamwork Lab ran this experiment, over 80% of participants felt the urge to "just ask AI" on Pause Day, and nearly 1 in 4 reached for it without even thinking.
At the same time, AI Play Day wasn't all upside. Nearly half of reflections flagged how much effort it took to check and correct AI output. AI often shifts the work rather than eliminating it.
The biggest impact came from talking about it as a team. After comparing notes, 89% of participants said their team had a clearer, shared understanding of when to use AI.
When should you run AI Play/Pause Days?
The best times to run this Play are:
- When your team has adopted AI tools but hasn't really talked about them. People might be using AI every day without any shared sense of what works, what doesn't, or what the team's norms should be. This Play starts that conversation.
- When you suspect over-reliance or under-use. Maybe some folks on your team are all-in on AI, and others haven't touched it. Or perhaps everyone's using it, but nobody's sure if it's actually saving time. The two-day contrast surfaces these patterns fast.
- When you're onboarding to new AI tools. Instead of guessing where a new tool will help, let your team try it under real conditions and see what sticks.
- When you want to build shared norms, not just individual habits. Atlassian’s internal experiment showed that individual AI gains don't automatically become team gains. Structured reflection is what bridges the gap.
- After a major rollout or change. If your org just launched a new AI tool or updated its AI policies, this is an easy way to ground adoption in actual experience rather than assumptions.
Top benefits of AI Play/ Pause Days
When Atlassian's Teamwork Lab ran this experiment with about 120 people, they found AI Play/Pause Days:
- Reveal hidden habits. Over 80% of participants felt the urge to "just ask AI" on Pause Day, and nearly 1 in 4 reached for it without even thinking. Most people don't realize how automatic their AI use has become until they try to stop. The experiment makes those invisible defaults visible.
- Build real discernment. After experiencing both extremes, 92% of participants felt more confident about when not to use AI. That's the real outcome here: not more AI use, but better judgment about when it helps and when it doesn't.
- Help create shared team norms. Here's a surprising finding: Dialing AI up or down didn't change how much teammates collaborated. Collaboration looked exactly the same on both days. What did produce a team-level shift was the structured reflection afterward. In fact, 89% of participants reported a clearer shared understanding of when to use AI. Individual experience created individual insight, and the deliberate conversation turned it into shared judgment.
- Surface the “verification tax.” AI often makes work feel faster, but nearly half of Play Day reflections flagged the cost of reviewing, correcting, or rewriting AI output. That trade-off isn't always obvious in day-to-day work. The experiment brings it into focus so your team can decide where the trade pays off and where it doesn't.
- Make work feel genuinely better. This isn't just about efficiency. On AI Play Day, people described their work as engaging (64%), satisfying (51%), and purposeful (47%). Priority work felt significantly easier, and stress was notably lower. When AI is applied with intention – to the right tasks, in the right ways – it doesn't just save time. It makes the work itself feel better.
1. Set up the experiment
Est. time: 20 MIN
- Choose a facilitator — you or a nominated team member — and pick two back-to-back workdays. Designate one as AI Play Day and the other as AI Pause Day. The Teamwork Lab experiment ran Play Day first, but you can choose the order that works for your team.
- Confirm the AI tools your team can use and review your organization’s AI, data-handling, privacy, and security policies.
- Create a shared document, like a Confluence whiteboard or page, to make notes as the team reflects about Play Day, Pause Day, patterns, and practices they want to carry forward. See the steps below for guidance on how to set up the document.
- Reserve 15–30 minutes in an existing team meeting for group discussion after both days.
- Ask people to keep their usual responsibilities and meetings as intact as possible. The exercise works best under real conditions.
Crear normas de equipo
tip: Frame the exercise around learning
The team should know this experiment is about learning, not about testing their AI skills.
2. Run AI Play Day
Est. time: 1 workday
Have the team do their normal work while leaning into AI wherever it is appropriate and approved.
- Try familiar tasks, such as drafting, meeting preparation, summarizing, finding information, and capturing action items.
- Push beyond your defaults. Use AI as a thought partner, turn rough thinking into structured content, build repeatable prompts or skills, prototype a workflow, write or review code, or try a new approved model or tool.
- Notice where AI helps, where output needs heavy checking or rewriting, what feels easier or less stressful, and which decisions still need human judgment.
Throughout the day or the end of the day, capture notes in the shared document or whiteboard. You can write a few stickies or record a brief Loom video and use it to create or inform your notes.
Crear normas de equipo
tip: Guardrails still apply
Follow your organization’s policies and data-handling standards. Human team members remain accountable for final decisions, communications, and quality.
3. Run AI Pause Day
Est. time: 1 workday
Work as you would have before AI tools became part of the workflow.
- Whenever possible, don’t use AI assistants and chat tools, AI writing and summarization features, AI-generated search or recommendations, or AI-supported workflow helpers.
- Standard non-AI automations and tools or features that can’t or are not practical to disable are still acceptable. Use essential exceptions if avoiding AI would block necessary work.
- Try your best rather than aiming for perfect compliance. Slips, frustration, and workarounds are useful information. Notice and capture them.
At the end of the day, add a second reflection to the shared space. You can make notes on the whiteboard or page, or record a Loom and share the takeaways that are most appropriate for your team.
Crear normas de equipo
tip: Notice what feels hard
If it feels awkward or difficult to avoid using AI, that's the point. Observe whether AI usually saves time, gives confidence, or helps with tasks that feel tedious without it.
4. Reflect as a team
Est. time: 15 min
This is where you turn individual observations into shared team judgment. During an existing team meeting, save the last 15 minutes for reflection about Play and Pause Days.
Before the meeting, ask everyone to review both day’s reflections in the shared document and add anything they missed. As facilitator, scan for themes.
Spend the first ten minutes discussing a few reflection questions, such as:
- Which workflows or use cases felt meaningfully better with AI, and which were only faster but not better?
- Where did AI Pause Day feel hardest, and what did that reveal about habits, over-reliance, or skill atrophy?
- Were there any tasks that felt better without AI, or moments when someone tried something that surprised them?
- What AI-supported workflows should the team keep doing, scale, or make part of normal practice?
- What norms, support, or examples would help the team use AI more intentionally going forward?
Sort observations into "AI clearly helps" / "Still a toss-up" / "Better without AI." Then, spend the last five minutes agreeing on 1–3 practices to keep, scale, or make permanent, plus one thing each person will do differently.
Capture the team’s norms somewhere visible and accessible, like in your shared Confluence space or Slack channel.
tip: Make sorting and voting easy
If you’re not sure if you’ve provided enough information or the right details, just ask! AI will tell you what other context would help it provide a better answer.
Crear normas de equipo
Follow-up
AI Working Agreements
Treat your AI interaction as a conversation, and provide more details or instructions to refine the output. For example, if you asked for help creating a project plan but the timeline it provided was too aggressive, give that feedback and tell the tool to extend the project plan over a longer period of time.
AI Use Case Demos
Treat your AI interaction as a conversation, and provide more details or instructions to refine the output. For example, if you asked for help creating a project plan but the timeline it provided was too aggressive, give that feedback and tell the tool to extend the project plan over a longer period of time.
AI Innovation Day
Build your team’s confidence with the AI Innovation Day Play, a focused day of learning and doing with AI.
Variantes
Acuerdos de trabajo
Cada persona tiene su propio estilo de trabajo, pero para alcanzar tus metas, hay que trabajar juntos. Describe las formas de trabajo compartidas de tu equipo para que puedas establecer expectativas mutuas, ahorrar tiempo y colaborar de forma eficaz.
Async version
Replace the live reflection with an async brainstorm on your shared page or whiteboard. Have the facilitator synthesize themes and invite the team to comment.
Repeat cadence
Run the exercise monthly or quarterly, focusing each round on a different workflow or team norm.
¿Aún tienes preguntas?
Conversa con otros usuarios del Manual de estrategias para equipos de Atlassian, obtén asistencia o envía tus comentarios.
Otras estrategias que puede que te gusten
Optimiza con la IA
Día de la innovación en IA
Saca el máximo provecho a la IA generativa con un día centrado en aprender y crear.
Optimiza con la IA
Compañero de equipo de IA
Crea tu primer agente de IA
Innova con la IA
Taller de capacitación sobre IA
Organiza un taller para ayudar a cualquiera a aprender los conceptos básicos del uso de la IA en el trabajo.
Innova con la IA
Definir el rol de la IA en el proyecto
Identifica oportunidades para usar la IA con el fin de contribuir al éxito de tu próximo proyecto.
Mantente al día
Descubre las últimas estrategias y consejos sobre la vida laboral al inscribirte a nuestro boletín.