Guide
Coolest Projects Online
Build it. Show how it works.
Competition Guides
Why Explore is a complete first STEM project rather than a smaller version of Challenge.
FIRST LEGO League Explore Ireland is not Challenge with fewer missions. It is a different learning design for younger students. Teams research an annual real-world theme, develop an idea, build and code a moving LEGO model, create a poster and present the journey at a celebration or showcase event.
The distinction matters. Explore gives children a public reason to finish and explain a project without making the first experience depend on rankings. FLL Ireland describes teams of up to four students with an adult coach, using SPIKE Essential or WeDo 2.0 and an Explore Set. Registration materials include lesson guidance and engineering notebooks, giving adults a structure without requiring them to invent a course.
CompeteMap sees Explore as a good first engineering programme for children who like making things but have not yet learned to document or present a design. The challenge is less about advanced code than about helping every child contribute to one coherent project. Adults should resist repairing every weak mechanism or rewriting the poster. A model that students can explain and improve is more valuable than a flawless display they did not own.
| Field | Details |
|---|---|
| Programme | FIRST LEGO League Explore Ireland |
| Typical students | Ages 7–12, usually 2nd–6th Class |
| Team size | Up to four students with an adult coach |
| Outputs | Research, innovative solution, coded model and poster |
| Event style | Celebration or showcase rather than a robot-game tournament |
| Best for | A first structured STEM project with teamwork and presentation |
For current dates, eligibility and registration details, see the FLL Explore Ireland competition page.
The official materials provide a meeting guide and engineering notebooks. Keep sessions short and purposeful: understand the theme, ask questions, generate ideas, build one function, test it, revise and record what changed.
Give each child a real role, but rotate roles across the season. A child who is hesitant to code may be an excellent interviewer or mechanism tester, then gain confidence to try programming later.
The poster should show a process rather than a collection of decorative facts. Include the problem, the team's idea, how the model works and one change made after testing. Practise a conversation, not a memorised performance. Reviewers want to hear the children's understanding.
Original CompeteMap editorial content. Brief quotations must clearly credit CompeteMap and link to this article. For complete reuse terms, see Copyright & Reuse.
EXPLORE NEXT
Guide
Build it. Show how it works.
Guide
Choose the Task Before the Event
Guide
A local solution. A minute to make it matter.
Loading comments…