Did you know that coding is now part of the 2026 Ontario Kindergarten Curriculum? It is introduced through unplugged, play-based, and age-appropriate activities rather than computers, screens, or keyboard. This is exciting news for those of us who love STEM education! Students will learn foundational computational thinking and problem-solving through three main specific expectations:
- B11.1 Directional and Positional Language: Using spatial and directional words to create and follow movement instructions (e.g., "Move forward three steps, then turn left and move forward one step" or moving to a specific grid square).
- B11.2 Testing and Refining Instructions: Trial-and-error problem solving. For example, if a student-programmed robot or a peer acting as a "robot" hits a wall or goes the wrong way, the children work together to debug and revise the steps.
- B11.3 Recording and Communicating Sequences: Using symbols, pictures, words, or arrows to map out step-by-step instructions (such as drawing an arrow path on a grid, sequencing picture cards of a daily routine, or detailing steps to build a block structure).
Young children are capable of engaging in rich computational thinking activities in the classroom. In emergent programs, the questions and wonderings children have about the world around them can easily be embedded into unplugged coding activities. Activities that incorporate computational thinking are often misinterpreted as 'more screen time' for young children, when in fact, all of the activities I use in my classroom to encourage computational thinking are screen-free without the need for computers or tablets.
Computational thinking is a foundation of computer science, and intricately related to many of the big math ideas and practices found in early childhood curriculum. It involves many concepts and approaches.
There are many different elements of computational thinking including:
- using logic to predict and analyze when engaging in problem-solving
- making judgments when faced with problems in order to evaluate what is happening and consider how to move forward
- creating and following algorithms (or steps of action) in order to move through the problem solving process
- using patterns in his/her work to find and use similarities efficiently
- deconstructing larger problems or actions into smaller, more manageable parts
- filtering out information that isn't directly related to the problem or an efficient way of solving it
The computational thinker:
- tinkers with loose parts and other open-ended materials
- designs innovative projects and follows through on creating them in some capacity
- debugs by finding errors in his/her work and correcting them in order to move a project forward
- perseveres and continues with projects even when they are challenging
- collaborates with others as part of a team for the betterment of a project
Looking to engage children with computational thinking in your classroom? Here are some ideas to get you started.
2. Provide STEM challenges to children. Ask them to use specific materials to achieve a certain goal, and encourage them to articulate the steps and criteria they used in order to be successful. In this photo a child turns a geoboard into a marble run maze.
3. Introduce the idea of coding using arrow coding cards and positional language. Children can easily explore pathways by creating them using different building materials (e.g., blocks, legos, magnetic tiles) and then exploring direction of movement.
4. Transfer coding into algorithms by helping children create and follow specific sequences of actions. Here children create and follow an 'exercise code' where they must look at each line of code in the script, and follow the movements precisely.
Computational thinking is a versatile, foundational approach to learning that helps engage children in rich mathematical activities that are incredibly fun too!


.jpg)
.png)
.png)




.jpg)

.png)
.png)








.png)



.jpeg)










.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)