The motor is running, but the robot is not doing what its builder intended. It might be slipping, leaning or dropping the object it is meant to carry. Before changing the code, it is worth looking at the physical design.
Robotics brings programming and mechanics into the same conversation. Children can see that an instruction only works as intended when the build can carry it out.
A gear pair can change the relationship between the motor’s rotation and the output movement. Instead of memorising that “bigger is better”, students can observe how a particular arrangement behaves, then compare another arrangement under similar conditions.
A useful question is, “What changed when we changed this part?” The answer should come from the test, not from how impressive the model looks.
A grabber that closes may still fail to hold an object. Students can examine where it touches the object, whether the shape fits and how the object moves as it is lifted. A wheel can also turn without moving a robot effectively if contact with the surface is poor.
These are different problems. Naming what actually happened—slipped, tipped or failed to close—helps the child decide what to investigate next.
A model that stands still successfully may lean when it starts or lifts a load. Encourage children to observe the entire action. Where is the weight? What is supporting it? Which single change could they test first?
For a parent, a simple invitation is, “Show me where it starts going wrong.” It gives the child a concrete place to begin explaining.
SUP’s Lower Primary LEGO track uses SPIKE Essential with word-block programming; Upper Primary uses SPIKE Prime for more advanced work. Mechanical reasoning belongs alongside coding in both stages. When exploring LEGO Elite Team Training, ask about the choices students make and the tests they use—not only the robot they finish.
Explore the programme: LEGO Elite Team Training
