Welcome to Breaking Big Problems Down! In the last series — Commands: How We Tell Computers What To Do — you learned how to give instructions to computers: A command is a single, specific instruction Every command needs a receiver that is ready and able to understand it Commands must be specific — not vague wishes, but exact instructions Computers do exactly what the command says — nothing more, nothing less Those ideas answered the question: how do we talk to a computer? Now there is a new challenge. What happens when the problem is too big for a single command? You cannot tell a computer: "Build me an app." Or even: "Clean the house." These are not commands — they are goals. A computer cannot act on a goal. It can only act on specific, individual steps. That is the skill this series is about: decomposition — breaking a big problem down into the small steps a computer can actually follow. What You Learned Last Time Idea What It Means ------ -------------- Command A single, specific instruction that tells a computer to do one thing Receiver The thing that hears, understands, and carries out a command Specificity A good command says exactly what to do — not vaguely what result to achieve Computers are literal They do what you say, not what you meant What You Will Learn in This Series Post The Big Idea ------ ------------- What is Decomposition? How breaking a big problem into small pieces makes it solvable Decomposition in Everyday Life Getting ready for school, making food — you already do this without thinking Why Computers Need Small Steps Why computers cannot act on big vague goals, only specific steps Putting It All Together A complete walk-through — big problem, decomposed into exact commands The Problem You Have Already Felt Have you ever been told "go clean your room" and felt overwhelmed? The task feels too big. Where do you even start? But if someone said: 1. Pick up all the clothes from the floor and put them in the laundry basket 2. Make the bed 3. Put your books on the shelf in order 4. Put your toys in the box Suddenly it feels manageable. Each step is clear, specific, and doable. That is decomposition. And it is exactly how programmers think. This is series 3 of 6 in the Kids Programming learning path. New here? Start from the beginning. Questions People Ask What is decomposition in computing, in plain words? It means breaking a big problem into smaller pieces until each piece is simple enough to act on. "Tidy your room" becomes five clear jobs. "Make a cup of tea" becomes thirteen exact steps. It is the first thing a programmer does with any new problem, long before writing code. Does my child need to have read the earlier series first? It helps, but it is not essential. This series builds on Commands, and the first page recaps everything needed in a short table. If your child is new to the path, start at series 1 instead. Is this the same as computational thinking? Decomposition is one of its main parts. The others — precision and spotting patterns — come in series 5 and series 6. Schools often assess decomposition directly, so this series maps neatly onto what is taught in class. How long will this series take? Four posts, each a 5–10 minute read plus an activity of about ten minutes. Most families finish it in an hour, or across two comfortable sittings. Nothing needs to be installed and nothing expires. Will this actually help with schoolwork, or only with coding? Both. The same skill turns a maths word problem, a long essay or a science project into a list of steps you can start. Children who freeze at "where do I even begin" are usually missing decomposition, not effort. A Note for Parents and Teachers This series teaches decomposition — turning a large, vague goal into an ordered list of small, specific steps. It uses nothing but familiar things: a messy bedroom, the school-morning routine, a pot of pasta, an ATM, a cup of tea. There is no code in it at all. The best way to use it at home is out loud, together. Read a post, then do the activity. The one to make time for is The Hidden Tower in Putting It All Together — one player builds something out of blocks behind a screen and writes instructions for the other to copy it. The two towers never match the first time, and the reason why teaches more in five minutes than any explanation can. In a classroom, each post is one lesson: read it, run the activity in pairs, then use the "Check Yourself" questions as the plenary. The Hidden Tower works especially well as a whole-class barrier game, and the sticky-note activity in What is Decomposition? fills a wall nicely as a display. No devices, logins or licences are needed. ✅ Start with the first post: What is Decomposition?