Skip to content
Curiotide

Design a Robot Helper on Paper, Then Build the Model

  • Ages 5-7
  • Ages 8-9
  • Ages 10-12
Illustration of a robot drafted on a blueprint sheet, on warm orange waves

Ask a child to design a robot and you get one that does everything. Ask for a robot that does one job properly and you get engineering.

Ages 6 to 12

Time An hour to design, an afternoon to build

You'll need Paper, boxes, tubes, foil, tape, and a chatbot on your account

How it goes

  1. Pick one job. Feeding the cat. Finding the remote. Putting the recycling out. One.
  2. Break the job into steps on paper, in order. Most jobs turn out to have seven steps and your child will be surprised by four of them.
  3. Design a part for each step. A gripper, a way to move, a way to know when it is done. Labelled drawing, no shading.
  4. Let the AI interrogate it: My robot puts the recycling out. Ask me one question at a time about how each part works. Do not design anything for me. “How does it know the bin is full” is the question that changes the design.
  5. Redraw with the fixes.
  6. Build the model from boxes and tubes. It does not have to work; it has to show the parts.

Who does what

AI asks the questions a design review would ask, and names components when your child describes one without knowing the word for it.

Your child chooses the job, breaks it into steps, designs, defends, redraws, and builds.

You save the boxes for a week beforehand.

Make it easier or harder

For a five-year-old: three steps rather than seven, and let the parts be drawn rather than named. A gripper that is just a hand shape labelled “grabber” is a complete design at this age.

For a twelve-year-old: require the robot to detect something and change what it does as a result. A sensor and a decision turn a sequence into a program, and it is the natural bridge into making a custom coding challenge where the same logic gets built for real.

Take it off the screen

Present the model and have your child walk through the seven steps pointing at the parts. That is a design review, and it is worth practising at nine.

Kids who want the robot to actually move can carry the same design into Scratch or MIT App Inventor, where the sequence of steps becomes a program.

When it goes sideways

Most designs stall at “how does it know when it is finished”. If your child cannot answer, that is not a failure of imagination, it is genuinely the hard part of robotics. Offer the standard answers used in real machines: a timer, a switch that gets pressed, or a weight that changes.

If the model floods them with questions, take the three that mention parts they have not drawn and drop the rest. Three good questions produce a better second draft than twelve do.

One thing to watch

Talking to a chatbot about robots invites the question of whether the AI itself is a robot, or alive. It is worth answering plainly rather than deflecting; AI is a tool, not a friend has the language we use.

Related: invent a family gadget is the simpler version, and learning to code with AI covers where this leads. To take it further on a screen, make a custom coding challenge for a beginner.

Keep reading