If you audit the technology provision of a typical school, you usually find something like this: a computer period in the primary years focused on operating software, a coding club that reaches whichever students opt in, a robotics kit purchased three years ago that comes out for the science exhibition, and a senior computer science subject that a small fraction of students take.
Each piece may be perfectly good. Together they are not a programme, because nothing connects them. A student’s experience depends on which teacher they had, whether they joined a club, and whether the kit was working that term.
The cost of discontinuity
Discontinuity is expensive in ways that are easy to miss.
Re-teaching. Every module starts from zero because it cannot assume anything. A meaningful fraction of every year is spent recovering ground.
No compounding. Skills that would compound if sequenced — computational thinking into programming, programming into data, data into machine learning — instead sit as separate experiences that never combine into capability.
Invisible gaps. When there is no map, nobody notices that a cohort reached Grade 9 without ever having debugged anything. The gap only becomes visible when the student hits work that assumes it.
Unfair distribution. Optional provision reaches the students who were already going to be fine. The students who most need a structured route into technology are the least likely to opt in.
What a pathway looks like
A pathway is not a longer syllabus. It is a set of commitments about sequence.
Grades 1–3 — Discover. The objective is confidence and intent. A child who can operate a device deliberately, express an idea digitally and describe a task as a sequence of steps has the foundation. Attempting text-based programming here trades that foundation for a demonstration.
Grades 4–5 — Explore. The shift is from following instructions to designing them. Students begin decomposing problems, planning before building, and producing digital work they chose to make.
Grades 6–8 — Create. The pivotal band. Text-based programming, first interfaces, first hardware, first structured encounter with artificial intelligence as something directable. If a programme is going to fail, it usually fails here, by moving too fast for the foundation underneath.
Grades 9–10 — Build. Projects become systems. Real data, real users, teamwork, security thinking, and the discipline of something that has to keep working after the lesson ends.
Grades 11–12 — Innovate. Students work as junior practitioners: open problems, researched approaches, evaluated trade-offs, work that stands on its own outside school.
The three sequencing decisions that matter most
Where text-based programming enters. Too early and it becomes transcription: students typing symbols they cannot reason about. Too late and there is not enough runway for the senior work. The judgement is about the foundation underneath, not the age on the register.
Where AI enters. Before a student has written rules a machine followed, a model is indistinguishable from magic. After it, a model is a system with properties and failure modes.
Where hardware enters. Physical computing is enormously motivating and it introduces friction that pure software does not — gravity, tolerance, loose wiring. Introduced early enough to build persistence, late enough that the student can already reason about a loop.
Auditing your own provision
Four questions that surface most of the truth quickly:
- If a student joined in Grade 7, what would we assume they already know — and is that assumption written down anywhere?
- What can every Grade 9 student in this school build, without exception?
- Which of our technology experiences are opt-in, and who opts in?
- When a technology teacher leaves, how much of the programme leaves with them?
The last one is the sharpest. A programme that depends on one enthusiastic individual is not a programme; it is a person. It deserves gratitude and it deserves succession planning, and most schools provide only the first.
The argument for continuity
None of this requires an unusual budget or unusual staff. It requires deciding that technology education is a twelve-year pathway with a defined progression, teacher support that does not assume specialists, and evidence of what students can actually do at each stage.
The alternative — a set of well-intentioned modules that never combine — is what most schools already have. It is not a failure of effort. It is a failure of sequence.