Future-proof your lesson planning
The best way to plan computing lessons that KS3 pupils will find interesting.
If you’ve ever spent your Sunday night planning a “solid” computing lesson only to watch pupils glaze over within a few minutes, you’re not alone.
If you’re the only computing teacher in your school or you are not a subject specialist that feeling hits harder. You’re carrying the subject, the results and the behaviour in one go.
The frustrating bit is this... it’s rarely your teaching.
The problem is the way we’ve been taught to plan lessons.
Why traditional lesson planning keeps letting you down
Traditional lesson planning usually starts with the curriculum statements then turns them into a sequence of lessons.
On paper, it looks efficient but it often creates a unit that feels like a checklist of abstract topics.
This can lead to:
Pupils failing to see the point in what they are learning, so they disengage
Each topic sitting in its own little box so the subject feels fragmented
When the curriculum shifts (and it is shifting with the new computing curriculum) announcement due in spring 2027) you feel like you have to rewrite everything
It also helps explain why computing can earn a reputation for being abstract and harshly graded. Pupils are asked to care about binary, hardware architecture or laws in isolation before they’ve seen how any of it connects to real life.
That is a planning problem and it has nothing to do with how you are teaching the subject.
You could be the best teacher in the world but if your lessons are failing to connect to the pupils then you are never going to be able to get them to love fall in love with computing and they never fully engage with it.
The planning shift that future-proofs your lessons
There’s a different way to plan that makes lessons feel more relevant now and easier to adapt later.
I call it context-first planning.
Instead of starting with the curriculum and trying to make it interesting, you start with something pupils already recognise from the real world then weave the curriculum strands through that context.
It’s a small shift with a big impact.
Because when pupils can see what they’re building or solving, the “why are we learning this?” question disappears.
What context-first planning looks like in practice
Context-first planning is not about gimmicks. It’s about choosing a real system, product or scenario that naturally requires the computing you want to teach.
Think:
recommendation systems
smart devices and the Internet of Things
cryptocurrency and online trust
data visualisation and how graphs can mislead
AI systems and how training data shapes outcomes
These contexts let you teach the same core concepts but in a way that feels cohesive and purposeful.
Traditional vs context-first: Boolean logic example
A traditional sequence might look like:
Logic gates and symbols
Truth tables with 1s and 0s
Drawing circuits then practising longer expressions
A context-first sequence could be:
Recommendation rules: pupils write conditions using AND, OR and NOT to match games to a set of criteria
Design logic circuits: pupils translate requirements into logic, filter a spreadsheet and draw circuits that represent the rules
Build a recommendation system: pupils write IF statements using AND, OR and NOT, use AutoFill and create a working system that flags which games meet the criteria
The same curriculum content is covered “understand simple Boolean logic [for example, AND, OR and NOT] and some of its uses in circuits and programming” but the emphasis in the context-first set of lessons is on recommendation systems and not on the curriculum that needs to be covered.
That leads to a completely different energy in the room. The pupils are learning about recommendation system, which they come across in real life so has a relevance for them, rather than the more abstract concept of logic gates where they don’t necessarily link it to something that affects them.
Why this resonates with pupils (and saves your sanity)
Context-first planning works because it does three things at once.
1. It gives pupils a reason to care
Pupils are far more likely to persist through tricky concepts when they can see the outcome.
They’re not learning Boolean logic “because it’s on the spec”. They’re using it to make a system behave the way they want.
2. It makes computing feel like one subject, not lots of mini subjects
When you plan through a context, strands blend naturally.
Programming, data, networks, safety, ethics and systems all show up because real technology is connected and used across these disparate areas and pupils can see the same tings in lots of different contexts..
That’s exactly where the new computing curriculum is heading too. The direction of travel is towards a more coherent, inclusive and future-facing computing curriculum with stronger emphasis on digital literacy, AI literacy and real-world relevance.
3. It future-proofs your units
If your unit is built around a context, you can swap in or deepen the strands you need as the curriculum changes.
You’re not locked into a rigid checklist.
You’re building a flexible structure that can evolve.
How to plan a context-first unit (without making more work for yourself)
Here’s the simple process I teach.
Step 1: Start with a real-world context
Pick a product, system or scenario pupils recognise and can talk about.
If you’re stuck, start by asking: What tech do they use every day that relies on hidden computing?
Step 2: Define the outcome
Decide what pupils will make, explain or be able to do by the end.
Examples:
build a simple recommendation rule
design a smart device with privacy and security choices
create an infographic from a dataset then justify why it is not misleading
Step 3: Pull out the computing inside it
Now identify the concepts and skills the context relies on then map them to the KS3 curriculum statements.
This when your planning becomes calmer as you are no longer trying to force relevance into a set of abstract concepts but instead the entire unit is based on something that pupils can relate to. You’re just revealing the computing that was already there.
A quick note for the exhausted sole specialist
If you’re thinking, "this sounds brilliant but I don’t have time to redesign everything", I get it.
You don’t need to overhaul your whole curriculum in one go, just start with one unit or even one lesson.
Pick a topic pupils typically find dull and ask, "where does this show up in real technology?"
That one shift can change the vibe of your classroom and it can change how you feel about teaching computing too.
Want the full framework (with examples you can lift and use)?
I’m running a free webinar that walks you through:
why traditional lesson planning switches pupils off
how to structure lessons so they feel connected and purposeful
how to future-proof units so curriculum changes don’t mean starting again
If you want pupils who lean in instead of switch off and you want planning that doesn’t steal your evenings, you’ll love it.
