"Clean your room" can feel impossible to a child. "Put the books on the shelf" does not. Same job, but the second version is small enough to start. That shift, from one giant task to many tiny ones, is called decomposition, and it is the first of the four pillars described in computational thinking for kids.
Why it matters for coding
No programmer writes a whole game in one go. They split it up: draw the player, make the player move, add enemies, count the score. Each piece is small enough to build, test and fix by itself. A child who learns to do this will find big projects far less overwhelming.
It is also a life skill. Homework, science fair projects and even birthday parties get easier when you can break them down.
Everyday practice
You can practise decomposition without any screen at all.
Make a sandwich. Ask: what are all the smaller jobs? Get the bread, get the filling, spread, assemble, cut. Then go smaller: getting the bread means open the cupboard, take out the bag, open it, take two slices. For more on this one, see teach algorithms with sandwiches.
Plan a pretend trip. Where are we going? How will we get there? What do we pack? Who do we tell? Each answer splits again into smaller ones.
Tidy a messy drawer. Sort by type first. Then sort each pile. Then put each pile away.
A simple method to teach
Give your child a tree-shaped way of thinking:
- Write the big goal at the top of a page.
- Ask "what are the main parts?" and write them underneath.
- Pick one part and ask again: "What small steps does this need?"
- Stop when each step is something you could do right now without further thinking.
A paper drawing with boxes and lines works beautifully, and kids enjoy making it look like a family tree.
Decomposition in a real project
Take a simple catch-the-fruit game in Scratch:
- Make the basket (draw it, put it at the bottom).
- Move the basket (left and right keys).
- Make a fruit (draw it, make it fall).
- Catch the fruit (touching the basket).
- Keep score (a variable that goes up).
Five small jobs instead of one huge one. If the fruit does not fall properly, your child knows exactly which piece to fix, which makes debugging far less frightening.
What parents can say
- "What is the very first small step?"
- "Can you split that into two smaller jobs?"
- "Which part do you already know how to do?"
That last question is gold. It reminds a child that they are never starting from zero. When they get stuck, going back to decomposing is nearly always the answer. The Thinking course practises exactly this skill through short, playful challenges.