How to Run a FIRST LEGO League Team of 8 Kids Without Losing Your Mind

Eight kids. One robot. Two hours. If that math makes you nervous, you're not alone. When we signed up for FIRST LEGO League, I pictured organized meetings where everyone worked on their part and things hummed along like a well-oiled machine. Reality was more like: three kids arguing over a wheel attachment, two staring at the ceiling, one coding in circles, and two others building an unrelated LEGO space station.

I figured out what works the hard way. Here's how to run an FLL team of 8 kids (ages 9–14) so that everyone stays engaged, nobody just watches, and your team actually learns something.

Psst — need a table first? I wrote a whole separate guide on building a portable FLL table that folds up and rolls away: DIY Portable LEGO Robotics Table

The Structure That Actually Works

Here's the biggest mistake I made: letting all 8 kids work on the robot at once. Eight kids around a robot is eight kids jostling for position while two actually do something.

The fix is simple: split the team.

Four Robot Builders, Four Project Researchers — and Rotate

Divide your 8 kids into two groups:

Group A (Robot Squad): 4 kids focused on the robot — building, coding, testing missions Group B (Innovation Squad): 4 kids focused on the Innovation Project — research, solution design, presentation

Every 2–3 sessions, swap. Everyone gets hands-on time with the robot, and everyone contributes to the project. This rotation also means nobody gets burned out on one thing, and your quieter kids often shine in the research role.

Within the Robot Squad: Three Roles

Even with 4 kids, you need defined roles or it's still chaos. Here's what works:

Builder (1–2 kids): In charge of the physical robot — attachments, gearing, structural changes. They implement what the team decides and are the ones with their hands on the LEGO most.
Programmer (1 kid): At the laptop, coding the mission runs. They work closely with the builder to test and iterate. The Spike app's drag-and-drop interface means even kids with zero coding experience can contribute here.
Tester / Documenter (1 kid): Runs the robot on the table, times each mission attempt, notes what went wrong, and keeps the engineering notebook updated. This role sounds boring to kids at first, but once they realize they're the ones analyzing what needs to change, they get into it.

Rotate roles every session. Monday's builder becomes Wednesday's programmer becomes next Monday's tester. This way every kid learns every skill, and nobody gets territorial about "their" robot design.

Within the Innovation Squad: Three Roles

Same concept, different focus:

Researcher (1–2 kids): Digging into the season theme, finding real-world examples, understanding the problem. For the 2025–2026 UNEARTHED season (energy), they might research how their community gets power, interview a local solar installer, or look up energy storage solutions.
Solution Designer (1 kid): Turning research into a concrete idea. What's the team's innovation? How would it work? They sketch, model, prototype. This is often the kid who loves drawing or building in Minecraft — the creative thinker.
Presenter (1 kid): Writing the script, practicing the 5-minute presentation, making sure everyone knows their part. At competition, every team member has to speak during the Innovation Project presentation — not just the designated presenter. This role makes sure that happens smoothly.

How a 90-Minute Session Should Look

Here's an actual practice schedule I landed on after way too many unproductive sessions:

Minutes 0–5: Huddle up. Everyone together. Quick check-in: what's the goal today? One specific thing we're trying to accomplish. Not "work on the robot" — it should be "get the robot to push the energy unit into the green zone consistently." Specific goals keep everyone focused.

Minutes 5–15: Team split + brief. Robot squad goes to the table, Innovation squad goes to their workspace (a different table or corner of the room). Each team lead (rotate this weekly) gives a 2-minute recap of where things stand.

Minutes 15–60: Deep work. This is when things actually happen. Robot squad runs mission attempts, tweaks code, adjusts attachments. Innovation squad researches, builds slides, practices presentation sections. No cross-talk between groups — this is focused time.

Minutes 60–70: Group reconvene. Everyone back together. Robot squad gives a 2-minute demo of what they accomplished today. Innovation squad shares one new finding or slide. This keeps both groups invested in each other's progress and gives kids practice explaining their work — a skill judges will test.

Minutes 70–85: Cross-training. This is the secret ingredient. Mix the groups for one quick exercise:

Have one of the robot programmers teach an Innovation kid how to code a simple move-forward-and-turn sequence
Have one of the researchers explain the season theme to a robot builder who hasn't been in that group yet

This builds depth across the team and prevents the "I only do coding, I don't know anything about the project" problem that shows up at judging.

Minutes 85–90: Wrap-up. Quick round of "one thing I learned today" and set the goal for next session. End on time. Kids (and you) need the predictability.

The Rules: What Every Team Needs to Know

Robot Game Rules (The Short Version)

The robot has 2 minutes and 30 seconds to complete as many missions as possible on the field. It runs autonomously — once they press start, no touching. If the robot gets stuck, they can retrieve it to the launch area but lose a precision token (worth points). There are 6 precision tokens total for the match.

Key rules kids need to internalize:

Everything starts in the launch area. The robot and any attachments must fit completely inside the launch/home area at the start of each run
No hand of god. Once the robot leaves the launch area, they can't touch it. It runs on its own until it returns or they interrupt it
Equipment inspection. All attachments and the robot must be made entirely of LEGO elements — no tape, glue, or non-LEGO parts
The ref's call is final. Good sportsmanship is a core value. At tournament, the referee's ruling stands — arguing costs your team grace points

Read the full rulebook together in session 2. Don't wait — kids will build things that aren't legal and have to redo work. I learned this one the expensive way.

Core Values (These Actually Matter for Scoring)

FIRST judges evaluate teams on Core Values just as much as robot performance:

Discovery: We explore new skills and ideas
Innovation: We use creativity and persistence to solve problems
Impact: We apply what we learn to improve our world
Inclusion: We respect each other and embrace our differences
Teamwork: We are stronger when we work together
Fun: We enjoy and celebrate what we do

At judging, teams get asked questions like "Tell us about a time your team disagreed and how you worked through it." The kids need a real answer — not a rehearsed one. Encourage them to actually disagree and resolve it. That's better material than a fake-perfect season.

Competition Day: What Actually Happens

Tournaments run about 6–8 hours. Your team will do:

3 robot game matches — 2.5 minutes each, spread across the day
Robot Design judging — 10 minutes, kids explain their robot and code to judges
Innovation Project judging — 10 minutes, presentation + Q&A
Core Values judging — usually a teamwork activity observed by judges

Between rounds, there's a lot of waiting. Pack snacks. Pack more snacks than you think. And tell the kids to watch other teams' robot matches — they'll learn as much from watching as from competing.

Practical Things Nobody Tells You

You need a second adult. Not optional with 8 kids. You need someone to supervise one group while you run the other. A co-coach, a parent who's willing to be "Innovation Project supervisor," anyone. Rotating parent volunteers works if you give them clear instructions.

Two laptops are better than one. One laptop for coding the robot, one for research and presentation building. The Spike app on the coding laptop, Google Slides on the research laptop. If you only have one, schedule which group gets it during deep work time.

The Spike Prime set has limited pieces. One set is enough for a competition robot but not for eight kids to all build different things. During free-build warmups, they share. During competition build, 4 kids on the robot is the max.

Keep the robot simple. The teams that score highest usually have the simplest, most reliable robots — not the most complicated ones. A robot that does three missions reliably beats one that attempts six and fails five. Drill this into the kids early.

The engineering notebook is mandatory, not optional. Judges look at it. It doesn't need to be beautiful — it needs to show the journey. Scribbled notes, crossed-out ideas, photos of failed prototypes. That's better than a polished document that looks like you wrote it all the night before.

When Things Go Wrong (They Will)

One kid will dominate the robot while others fade. Fix: time-box hands-on turns. The builder gets 15 minutes, then tags in the next person. Use a visible timer.

Two kids will hate each other by session 5. Fix: separate them into different squads for a few weeks. Time apart during practice heals most friction.

The robot will work perfectly at home and fail completely at tournament. Fix: practice on different tables at different times of day. Light conditions, table surface texture, even the angle of the floor — all affect sensor readings. Get at least one practice session on a different table before competition.

Someone's parent will try to take over and build the robot themselves. Fix: have a team agreement signed by parents at the start of the season. "The robot is designed, built, and programmed entirely by the kids." Post it on the wall during practice. It's your shield.

Why It's Worth It

Here's the thing: running an FLL team is work. It's two sessions a week, tournament registration, parent emails, snack logistics. You'll be tired.

But watching a kid who couldn't write a line of code three months ago program a robot that drives itself across a table, picks something up, and sets it in exactly the right spot — that moment is something. Eight kids building, coding, arguing, collaborating, and showing up for each other at a tournament.

That's the stuff that sticks. Way after they forget what year they competed or what the season theme was, they'll remember that they built something together.

Good luck, coach. You've got this. 🤖