First Grade Computer Science Lesson for Teaching Algorithms

Teaching first graders how to think like programmers often feels like teaching them how to organize their own messy thoughts.

When you start a Making a Toy Robot lesson in your first grade computer science block, you are really asking students to move beyond just following instructions. You are asking them to become aware of the structure of instructions themselves. Many teachers find that six and seven year olds do just fine with building things, but they get stuck when asked to define why they did things in a specific order. This is where the lesson shines.

The objective here is simple: a student needs to follow steps to make a toy robot and then be able to tell the steps they used to build it. It is a short fifteen-minute activity that works perfectly when you need a quick way to introduce the logic behind programming without needing a screen.

Understanding the standard behind the robot

The core of this work is governed by CA.CS.K-2.AP.10, which asks students to model daily processes by creating and following algorithms to complete tasks. When we look at this standard, it demands that students stop viewing their actions as random bursts of energy and start viewing them as repeatable, logical sequences. The lesson also incorporates CA.CS.K-2.AP.17, which asks the class to describe the steps taken and choices made during the iterative process of program development. This is the California-adopted standard, and you will see the same framework taught in classrooms across Santa Ana Unified, Garden Grove Unified, Cupertino Union School District, and Temple City Unified. Whether the student is in a small lab or a standard classroom, the goal of CA.CS.K-2.AP.10 is to make the invisible nature of an algorithm visible through physical construction.

Think about the phrase “model daily processes.” In the context of this lesson, a student is not just playing with building blocks or crafts. They are constructing a model of how a machine gets assembled. When they identify that the head of the robot must come after the body, or that the arms should be attached before the head, they are debugging their own construction plan. This is the heart of what this first grade computer science algorithm lesson asks them to demonstrate. It is one thing to follow a teacher’s directions. It is quite another to explain the logic of those directions back to the group after the work is finished.

I have found that the reflective part of this process is often where the most learning happens. A student might try to attach an arm, find it falls off, and then change how they hold the piece. When they describe that shift in approach, they are engaging in the iterative process mentioned in the standard. They are identifying the problem and adjusting their plan, which is exactly what a programmer does when code does not compile or a character in a game moves the wrong way.

How to use this in your classroom

You can fit this lesson into several different parts of your week. It is a solid choice for a whole-class assignment when you are first introducing the concept of sequencing. If you have a student who missed the week during a unit on logical thinking, this is a perfect independent study piece because it is self-contained and easy to follow. It also works for a substitute day if you want the class to do something hands-on that connects to their computer science curriculum without needing access to a device. The materials are simple, which makes it easy to grab and go.

One caveat for those using this with a large group: keep an eye on the students who rush through the building part to get to the talking part. The lesson is meant to be a sequence. If they build the robot without thinking about the steps, they will not have anything meaningful to describe when it is time to reflect. Sometimes, I ask students to write down two of their steps before they even start building. It forces them to look at their materials and map out the process. It transforms the act of building from a play session into a modeling exercise.

The lesson does a good job of keeping the vocabulary accessible. You do not need to overwhelm them with jargon, but introducing the word algorithm as a way to describe their plan is helpful. When they realize that their robot assembly instructions are just a specific type of algorithm, the concept becomes much more concrete. They see that they are capable of writing a program, even if they are doing it with tape and cardboard rather than code blocks or a text editor.

If you see a student struggling to articulate the steps, ask them how they would explain the process to a friend who had no pieces and had to build an identical robot from scratch. This framing usually helps them slow down and realize why the order matters. It forces them to be precise. Precision is exactly what we want from them when we eventually move them toward writing actual lines of code. For now, building a toy robot is enough to build the right mindset for the work ahead.

The process of building and describing is a cycle. By the time they have finished the exercise, they have acted as the creator and the communicator of their own machine. It is a quiet, thoughtful way to spend fifteen minutes, and it leaves them with a much better grasp of why order matters in their computer science work. You can find the instructions for this exercise at the primary link provided to get started right away with your own group of first graders.