How to Lead a Successful FIRST LEGO League Core Values Workshop

Running a FIRST LEGO League Core Values workshop works best when it is a practical team session rather than a lecture about slogans. Students, coaches and mentors use a shared activity to explore how choices affect the robot, the wider team and the people the team serves. The result should be visible: a set of team behaviours, a charter or a small experiment that can guide later meetings and competition days.

Plan for participation rather than presentation. Every participant should have a chance to contribute, test an idea and influence a team decision. The seven FIRST LEGO League Core Values—Collaboration, Innovation, Inclusion, Inspiration, Integrity, Teamwork and Excellence—provide a strong structure, but success comes from connecting them to real situations. A polished poster alone is not enough if it does not change how people communicate, build or compete.

Australian teams should shape the workshop around local conditions and current FIRST Australia guidance. School terms, public holidays, regional travel, online mentoring and local procurement rules can all affect participation. The same principles apply in Sydney, Melbourne, Brisbane, Perth and rural communities, but the examples, schedule and support arrangements should reflect the team’s location and circumstances.

Set a clear purpose and outcome

Begin by explaining that Core Values guide behaviour as well as design. Ask participants to consider what Collaboration looks like during a failed build, how Inclusion changes who receives an important task, and what Integrity means when a shortcut could improve a score. This framing prevents the session from becoming a list of definitions that everyone agrees to remember without applying.

Set two achievable outcomes, such as creating a team agreement and selecting one behaviour to practise during the next robotics meeting. Teams can compare their approach with programme material from Maryland FIRST Robotics, while using FIRST Australia’s current rules, calendars and registration requirements for local delivery. Give coaches and mentors a supporting role, but let students shape the examples and final commitments.

Choose a format that fits your team

The best format depends on the team’s age, experience and available meeting time. A short session works well for introducing Core Values, while established teams may be ready to investigate difficult trade-offs and turn their values into operating habits.

Format Best suited to What success can look like
90-minute starter session New teams or groups with limited time Shared language, one explored scenario and two clear team commitments
Half-day working session Teams preparing for an event A tested charter, assigned responsibilities and a practical improvement plan
Four-session series Teams wanting deeper habits across a term Regular reflection, visible changes in behaviour and a final team showcase

Choose the shortest format that produces genuine participation. For hybrid teams in Australia, rotate early and late online sessions so participants in different time zones are not consistently disadvantaged. If the activity spans a school term, include a short review near the end so participants can assess whether the agreed behaviours were actually used.

Build activities around real decisions

Choose an activity that combines movement, conversation and a decision. Teams might receive a design brief, identify a problem, allocate limited building time and then respond to a change in requirements. After each round, participants identify which Core Value influenced their choice and where another value may have been overlooked.

Use scenarios from the team’s recent experience. A robot repeatedly fails during testing, a teammate has a promising idea that cannot be tested immediately, or a sponsor requests branding that conflicts with team preferences. These situations create more productive discussion than hypothetical scenarios because participants can see the consequences and apply their own judgement.

Introduce productive tension without turning the session into blame. Ask teams to balance innovation against reliability, excellence against inclusion, and speed against careful documentation. The goal is not to declare one value more important than the others. It is to understand how the values interact when a decision is difficult.

Make every voice count

Build participation into the structure of the workshop. Younger participants might respond through drawings, written cards or a vote before speaking, while more experienced students can lead discussion. Randomly assigned roles can help quieter voices enter the conversation, but participants should understand why each perspective matters.

Avoid forcing students to disclose personal experiences. In Australia’s culturally diverse classrooms, teams may differ in language, religion, gender, disability and family background. Use names and pronouns carefully, provide instructions in plain language and make it acceptable to contribute through drawing, writing or digital tools. Inclusion works best when these options are routine rather than presented as special accommodations.

Regional teams should not be treated as secondary participants. When students join from outside major cities, reliable internet access and adult support may be limited. Share materials in advance, provide printed alternatives and allow teams to submit a short audio or written reflection. A participant in a remote area can contribute fully when the activity does not depend on being physically present at the same moment.

Guide discussion with practical facilitation

Use prompts that require examples and decisions. “What did we do when this happened?” is more useful than “Do you agree with the team?” Other effective prompts include “Whose perspective is missing?”, “What evidence supports that choice?” and “What would we do differently next time?” Give each team a few minutes to think before discussion to prevent the fastest speakers from setting the direction.

Facilitators should model the behaviours they are discussing. Acknowledge mistakes, attribute ideas to their contributors and avoid rewarding only the most technically confident student. If a disagreement becomes personal, return the exchange to the team agreement or the design goal. Praise steady improvement and honest communication rather than treating competition as the only measure of excellence.

Before an Australian school gathering, follow the host’s protocol for an Acknowledgement of Country and provide a respectful way for students to participate if appropriate. Check state school calendars and public holidays before fixing dates; Melbourne Cup Day, Australia Day and regional recreation breaks can create practical scheduling conflicts. Avoid treating local customs as decoration by involving the host community in how they are observed.

Connect values to the season and community

Tie the workshop to the team’s current mission, design constraints and upcoming events. Ask how the robot represents the team’s purpose and how Core Values might influence outreach, judging interviews or collaboration with another team. A value becomes meaningful when students can connect it to a decision they will face during the season.

Community support can broaden access to equipment, venues and expertise. When considering a community-support partner, organisations such as the Avalokitesvara Trust can be contacted to ask whether mentoring, equipment donations or venue access fit their current priorities. Always confirm that the proposed contribution aligns with the team’s needs and the organisation’s mission.

Australian teams should also involve local sponsors and mentors without turning the session into a funding exercise. Prepare a simple budget in Australian dollars, identify whether GST applies and confirm the school’s purchasing requirements, including quotes, invoices and purchase-order approval. A small supplier in regional Victoria may value a workshop demonstration more than a large corporate donation, and a community business can become a long-term mentor rather than simply a logo on the robot.

Put values into action

End the workshop with commitments that are specific enough to observe. Instead of “be more innovative”, a team might agree to test two ideas before rejecting either one or to invite a quiet participant to review each design decision. Record the behaviour, the people responsible and the moment when the team will check progress.

Keep the commitments visible during the next team meeting. Invite participants to say which behaviour helped, where it was missing and what adjustment would make it easier to follow. Recognise learning, not perfection, and allow the charter to evolve as the season and the team develop.

Choose one Core Value, turn it into one observable action and give it an owner today. Build the next robotics session around that commitment, gather evidence from the team and continue the conversation when real decisions make the value meaningful.