There is a version of school technology education that assumes a specialist teacher: a computer science graduate, comfortable with code, able to debug a student’s project in real time. That teacher exists. There are nowhere near enough of them, in any country, and there will not be within the working life of any curriculum being designed now.
So the useful question is not how to recruit specialists. It is what a programme owes to a capable teacher who did not train for this.
What a non-specialist teacher is actually good at
It is worth being clear that this is not a deficit conversation. An experienced teacher who is new to technology brings things a technically fluent novice teacher does not: classroom management under pressure, the ability to read a room, knowledge of individual students across years, judgement about when a struggling student needs help and when they need to be left alone, and a well-calibrated sense of what is age-appropriate.
Those are the hard-to-acquire skills. Technical content is comparatively easy to supply. Programmes fail when they invert this — supplying enthusiasm and hardware while assuming the pedagogy will look after itself.
What the programme owes the teacher
A worked solution for every project. Not an answer key — a complete reference build, with the reasoning. A teacher who has seen the finished thing can supervise a class building it. A teacher who has not is improvising in front of thirty students.
Anticipated failure modes, in the lesson notes. Not “students may find loops difficult”, but “students will typically write this off-by-one error; here is what it looks like and here is the question to ask them”. This is the single highest-value item in any teacher material and the most frequently missing.
A stated fallback. The hardware will fail, the network will be down, the licence will not activate. Every session should carry an explicit alternative that still teaches the concept. Without one, the session becomes a lost period and the programme loses a little credibility each time.
A definition of good enough. Non-specialist teachers frequently over-help, because they cannot tell whether a student is productively stuck or actually lost. A stated standard for the grade — this is what an acceptable Grade 6 solution looks like, this is what an excellent one looks like — resolves that faster than any amount of encouragement.
Permission not to know. The most useful sentence a teacher can say in a technology classroom is “I don’t know — how would we find out?”. Programmes should say so explicitly in their training, because teachers who believe they must be the authority will avoid the open-ended work where the learning is.
What training should actually contain
Most technology teacher training is a product demonstration. The teacher watches the platform being used and leaves with an account.
The training that changes classroom outcomes has a different shape. Teachers build the projects themselves, at the level their students will — including hitting the errors. They practise the specific moves: how to run a debugging conversation without taking the keyboard, how to structure group work when there are four devices and thirty students, how to assess a project that does not fully work. And they leave with a concrete plan for the first three weeks, not a general capability.
Continuity is a design problem
The most common failure is not initial training. It is the second year.
The trained teacher moves schools. The champion takes on a different responsibility. A new teacher arrives to a programme with an account and no context.
Programmes that survive this build for it deliberately: material that stands alone without the person who was trained on it, onboarding available on demand rather than only at annual sessions, more than one trained teacher per school as a deployment requirement rather than an aspiration, and a school-level record of what has been delivered so a successor inherits a position rather than a mystery.
The measure
A technology programme’s teacher support can be evaluated with a single test: hand a session’s material to a competent teacher who has never seen the programme, and see whether they can run it tomorrow.
If they can, the programme will scale. If they cannot, it will work wherever there happens to be an enthusiast — and only there, and only while they stay.