Everyday Computational Thinking

Module 3 · Section 4 of 6

Everyday Computational Thinking

You’re standing in your kitchen, staring at a recipe for chocolate chip cookies, and suddenly you realise you’re already thinking like a computer scientist. You’ve broken the recipe into steps, identified patterns in the baking process, and started troubleshooting when you discovered you’re out of brown sugar. Welcome to computational thinking — the mental toolkit that’s been hiding in plain sight throughout your daily life.

Computational thinking isn’t just about computers or coding. It’s a way of approaching problems that makes even the most complex challenges manageable. Think of it as your brain’s operating system for solving puzzles, whether you’re planning a trip, organising your schedule, or figuring out why your wifi keeps cutting out.

The Four Superpowers

Every computational thinker has four trusty tools, and you’ve probably been using them without realising it.

Decomposition is breaking big, scary problems into smaller, manageable chunks. When you’re planning to clean your entire house, you don’t tackle everything at once — you might start with one room, then focus on specific tasks like making beds or washing dishes.

Pattern recognition involves spotting similarities and trends. You’ve mastered this when you notice that traffic is always worse on rainy Monday mornings, or when you realise a particular colleague always pushes back on estimates when they haven’t been involved in scoping.

Abstraction means focusing on the important details while ignoring the irrelevant ones. When you give someone directions to your house, you don’t mention every single tree they’ll pass — you highlight the key landmarks and turns that actually matter.

Algorithm design is creating step-by-step instructions to solve problems. Every time you teach someone to make your favourite dish or explain how to handle a specific type of customer complaint, you’re designing an algorithm.

Route Planning: Your Daily Navigation Algorithm

Getting from Point A to Point B involves all four superpowers working together. First comes decomposition: you break your journey into stages — leave office, navigate to main road, get through town centre, arrive at destination. Then pattern recognition kicks in — you remember that the high street gets congested during lunch hours.

Abstraction helps you focus on what matters. You don’t plan your route around every building number, but you do note important landmarks. Finally, your algorithm emerges: “Walk to the corner, turn right at the post office, continue straight until you see the park, then turn left.”

The brilliant thing is, once you’ve created this mental algorithm, you can modify it based on new information. Construction blocking your usual path? Your algorithm adapts. Running late? It optimises for speed.

Cooking as Code

Every recipe is essentially a program, and every cook is a programmer who isn’t afraid to debug on the fly. Making a simple sandwich involves decomposing the task (gather ingredients, prepare bread, assemble, serve), recognising patterns (condiments go on both sides for even coverage), abstracting away unnecessary details (the exact brand of cheese doesn’t matter), and following an algorithm (bread first, then lettuce, then tomato, then cheese).

Cooking also teaches you about conditional statements and problem-solving. “If the bread is stale, toast it first.” “If there’s no mayonnaise, try mustard instead.” When you’re preparing a full meal, you’re managing parallel processing — the potatoes need an hour, the vegetables need thirty minutes, and the gravy can be prepared while everything else is finishing. You’re optimising timing to ensure everything comes together perfectly.

Time Management: The Ultimate Scheduling Algorithm

Managing your time is perhaps the most sophisticated computational thinking challenge you face daily. Consider planning a busy day: you need to finish a report, have two meetings, review a colleague’s work, and respond to a backlog of messages.

Decomposition breaks your day into discrete tasks and estimates how long each will take. Pattern recognition helps you remember that the report always takes longer than you expect, and that email responses expand to fill whatever time you give them. Abstraction focuses on dependencies — you can’t send the report until the review is complete.

Your scheduling algorithm considers constraints (meeting times, deadlines) and optimises for the right output. Maybe you tackle the report first thing when your focus is sharpest, batch the email replies into a single afternoon block, and build a buffer before the final meeting.

The Problem-Solving Mindset

What makes computational thinking truly powerful isn’t just the ability to break things down — it’s the mindset shift towards seeing problems as puzzles to be solved rather than obstacles to endure. When something breaks or goes wrong, computational thinking transforms frustration into curiosity. You decompose the problem, recognise patterns from past experience, abstract the core issue, and design a fix.

This approach works for messy, human-scale problems too. Planning a team event becomes a project management exercise with dependent tasks and resource allocation. Resolving a disagreement involves decomposing the conflict, recognising underlying patterns in communication, abstracting the core concerns, and designing a step-by-step path to resolution.

The remarkable thing about computational thinking is that you’re already doing it — you just might not have recognised it yet. Every time you troubleshoot why something isn’t working, organise a project with multiple moving parts, or figure out how to sequence a week’s worth of tasks, you’re flexing these muscles. The more you recognise and intentionally use computational thinking, the stronger your ability becomes — not just with AI, but in every aspect of your work.

---

Bridge to AI

These four superpowers give you the vocabulary for decomposing any AI task — and each one maps directly to something you need to do before you start typing.

Decomposition is the primary skill: what are the distinct parts of this task? A strategy document isn’t one thing. It has a situation analysis, a set of options, a recommendation, and a rationale. Those are four different cognitive tasks, and handing all of them to an AI at once — without separating them — produces output that’s soft on all four.

Pattern recognition tells you which parts are routine (and therefore safe to delegate wholesale) versus which parts require your judgment (and therefore need your input before the AI can contribute). Writing a status update is mostly pattern — the AI can handle the structure. Deciding which risks to surface is not a pattern — that requires your knowledge of the room.

Abstraction tells you what context the AI actually needs versus what would be noise. Every piece of background you include is a token spent. Include what changes the output; leave out what doesn’t. The AI doesn’t need the full history of the project; it needs the three facts that are relevant to today’s decision.

Algorithm design is the sequence you run the task in. Some AI tasks have a natural order — context before recommendations, problem definition before solution options, outline before prose. When you design the sequence deliberately instead of firing one big prompt, you get checkpoints where you can course-correct before it’s too late to matter.

Four computational thinking superpowers give you the vocabulary for decomposing any AI task. Use them before you open the chat window, and the conversation becomes an execution problem rather than a guessing game.