The wheels turn. The robot moves. Your child calls you over: “Look what I made!”
Enjoy that moment with them. Then, when they are ready, invite them to tell you a little more. A moving robot opens a conversation about mechanics, programming and the decisions that made it work.
You do not need to know how to code to join in. These three questions give your child a chance to be the person who explains.
Start with the mission. Was the robot meant to follow a route, carry something or stop at a particular point?
A clear goal gives the demonstration meaning. “It moves” becomes “I wanted it to carry this object without dropping it.” You can then ask your child to point out which parts help it do that.
For a younger child, a gesture or a simple sentence may be enough. An older learner could explain how a sensor reading leads to a programmed action. Match your question to the child in front of you, rather than expecting a polished speech.
This invites the story behind the result, including the attempts that went wrong.
Here is an illustrative challenge: a robot needs to carry an object across a bumpy model surface. Perhaps it gets stuck or loses its load. The child could explore wheel choice, grip, balance, speed or how the load is supported.
Ask what they noticed before suggesting a fix. If several things change at once, it can be difficult to tell which change helped. You might ask, “Which part could we change first, while keeping the others the same?”
That is a proposed family conversation, not a report of a particular student’s performance. It helps make room for the observations as well as the finished machine.
A project can work and still leave plenty to explore. Could the robot manage a heavier object? Would it respond consistently on another surface? What evidence would persuade your child that their improvement helped?
Invite one next step. There is no need to turn a happy demonstration into a list of faults. “I would make the base wider because it tipped over” gives you a useful glimpse of how your child connects an observation with a decision.
Explaining a project asks children to organise several things: what they wanted to achieve, what they built and what happened. For parents, it is an opportunity to hear their understanding in their own words.
SUP’s LEGO Elite Team Training brings mechanical understanding and programming together with pitching. Classes end with a short presentation about the build and the student’s thinking.
The programme includes a K3 track using LEGO SPIKE Essential with icon-based programming; Lower Primary uses SPIKE Essential with word blocks and explores mechanisms and robot behaviours; Upper Primary progresses to SPIKE Prime, more advanced coding and sensor-based challenges. Our Education Consultants can discuss the appropriate track for your child.
For ages 4–6, STEAM Junior connects LEGO programming, ScratchJr game design, science and pitching through story-based themes. A young learner might point to a moving part or finish the sentence, “I changed this because…”
The conversation can be short. Listen to the explanation, invite a demonstration, and thank your child for helping you understand. There will be time for another question on another day.
Looking for a course where your child can build, investigate and share their thinking? Explore LEGO Elite Team Training or STEAM Junior, and ask our Education Consultants which starting point suits your child.
