Choose the right pace
There is no fixed timeline. A team with strong tool access and leadership support may move quickly. A team that is just starting should spend more time on basics. Choose the pace your teams can realistically support.
Our philosophy
Before you build an agenda, decide what change you want the week to create. At Atlassian, we started by helping people try the tools, practice prototyping and prompting, and learn how evals work. The goal was confidence before outcomes.
Once teams had the basics, we moved from practice to daily work. Use this page to decide when your teams are ready to move from learning tools to changing workflows.
Three decisions to make
Use these three decisions to shape your program. Atlassian used this order, but you should adjust the pace based on your team's experience, access to tools, and leadership support.
Define the leadership message
Ask leaders to explain why the program matters, what teams are expected to learn, and how time will be protected. Without this, training will compete with delivery work.
Plan the applied work
Once teams know the basics, ask them to apply the skills to real work. Good build prompts include automating a repeated task, improving a customer workflow, creating a prototype, or setting up an eval.
Choose the first skills to teach
Start with hands-on practice. Give people access to the tools, simple exercises, and enough responsible-use guidance to experiment safely. The goal is learning, not shipping.
Example path
First: teach the basics
Run short practice sessions, tool walkthroughs, prototype exercises, and evals training. Focus on learning before asking teams to change their workflows.
Plan the applied work
Move from practice to real team work. Ask teams to bring a workflow, customer problem, prototype, or measurement task they can improve during the program.