Last term I watched a colleague prepare for parents' evening with no record of which students were at risk of missing their targets, no list of which pieces of coursework depended on which, and no clear sense of what "finished" looked like for the term. She is a brilliant teacher — warm, sharp, endlessly patient with the students. But she was working enormously hard to compensate for the absence of a system, and I recognised the feeling, because I used to sit on the other side of it.
Before teaching, I was a project manager in London local government. It was not glamorous work, but it drilled into me a set of habits that I picked up through qualifications in PRINCE2 Agile and a postgraduate diploma in leadership and management. When I moved into the classroom, I expected to leave all of that behind. Teaching, after all, is often described as an art: an emotional, deeply human endeavour, supposedly the opposite of the cold and clinical corporate world. Two years in, I think that framing is wrong — or at least incomplete. Teaching is an art, but it is an art practised inside a project. The term has a deadline. The exam has a date. The coursework has dependencies. Pretending otherwise just means managing a project while refusing to use any of the tools built for the job.
The tools that actually transfer
Take risk management first, because it is the least intuitive for teachers and the most useful. In local government, every project opened with a risk register: what could go wrong, how likely is it, how bad would it be, and what will we do about it now rather than later. A teacher's version takes ten minutes at the start of term. Which students are likely to disengage? Which unit is historically taught too quickly? Which assessment falls in the same week as three others? Writing these down does not feel like teaching, but it converts November's crises into September's minor adjustments.
Then there is dependency analysis — the unglamorous business of working out what must happen before what. Students cannot analyse a text they have not finished reading; they cannot revise a skill they have not yet been taught to practise. Mapping these chains backwards from the exam date exposes the hidden critical path of a term, and it tells you which slippages matter and which you can absorb. Most teachers do this intuitively. Writing it down makes it visible to everyone, including your department and, crucially, your students.
The "definition of done" sounds like jargon but solves a real classroom problem. When is a piece of coursework finished? When a student says so? When it has a word count? In project work, done means something agreed in advance and written down. I now agree the definition of done with classes before big assignments: what a complete draft contains, what "revised" means, what standard earns submission. Marking arguments become rarer, because the target was fixed before the work began.
Rhythm and visibility
Sprints and kanban boards transfer surprisingly well. A fortnightly sprint — a short cycle with a small, visible set of tasks — suits revision far better than the vague instruction to "go away and study". A simple kanban (to do, doing, done) on the classroom wall, or a shared spreadsheet, gives a class the same thing it gives a project team: an honest picture of progress that nobody has to chase. Monitoring follows naturally. In local government we tracked a handful of indicators rather than drowning in data; in teaching, a small set of KPIs per class — submission rates, quiz averages, attendance at intervention sessions — tells you early whether your plan is working or merely being followed.
The Gantt chart deserves a special mention for exam preparation. Laying the term out as bars against a calendar, with revision, mock exams and feedback loops visible, turns an anxious abstract countdown into a sequence of concrete steps. Students find it oddly calming. So do teachers.
Teaching the techniques, not just using them
The final point is the one I care about most. These tools should not stay in the staffroom. Group projects are where students first encounter the pathologies of unmanaged work: the free-rider, the duplicated effort, the panicked final night. Giving a class a stripped-down kanban board, asking them to name their dependencies, making them agree a definition of done before they start — this is not bureaucracy imposed on children. It is a genuinely useful life skill, taught through a subject they are already studying. Several of my students now plan their extended essays this way without being asked.
None of this makes teaching clinical. The relationships, the reading of the room, the improvised explanation when a class finally clicks — that remains the art, and no framework will do it for you. But art practised on a shaky scaffold is harder than it needs to be. The corporate world, for all its faults, spent decades learning how to deliver complicated things on deadline with fallible humans. Teachers would be unwise to refuse the inheritance.