Atlassian

    Facilitator notes

    Use the build portion to move from training to practice. Decide how much time you can protect, who will mentor teams, and what types of work participants should bring.

    1. Define categories for builds

    Give participants a short list of build categories. This helps them choose a useful problem and avoids unfocused experiments.

    2. Provide support

    Assign mentors to each build category. If the session is virtual, create support rooms. If it is in person, make it clear where teams can ask for help.

    3. Encourage sharing

    Create one place where participants can ask questions, share links, and post what they learned.

    The build portion of your training

    In Atlassian's AI Builders Weeks, we dedicate a full day called Build Day for teams to practice the skills they've learned prior. At the end of each build day, teams or individuals should leave with a concrete artifact, such as a prototype, process change, template, demo, or workflow. This should be something they can share with others and ideally showcase in the final demo to show what they learned and how they are applying it within their local environment. We recommend having people work in pairs or small teams so they can learn from and support each other. This works especially well in a remote-first environment, where it can be easy to feel discouraged when you hit a wall without a teammate nearby. There are many ways to organize build groups. We have found a couple of options that work well for us.

    Format: Live or virtual breakouts by build group, with mentors and technical support circulating.

    Option 1: Build groups organized by type of build — prototyping, evals, automations

    Use this option when you want people to practice a specific skill. Group participants by build type so mentors can give focused support. Ask mentors to explain the options in advance so participants can choose the right group. The cards below are Atlassian examples.

    Group #1: Prototyping → Production

    • Sample live support block
    • Repeat for major regions as needed
    • Async support option

    Bring an engineering partner to pair on a feature together, with design technologists and platform engineers available for live support throughout your build.

    Target audience: Product managers, designers, and engineering partners

    Group #3: Build your own agentic end-to-end automation

    • Sample live support block
    • Repeat for major regions as needed
    • Async support option

    Use this group for participants who want to automate a real workflow. Provide help with connecting tools, APIs, and knowledge sources, and include time to test whether the automation works.

    Target audience: everyone

    Option 2: Build groups by business area

    Use this option when teams share goals, codebases, customers, or operating constraints. Bring those teams together so they can solve related problems and reuse what others learn. If possible, ask leaders or senior craft experts to coach teams during the session.