Consider a small flight school, imagined here for the sake of the lesson, with a handful of instructors, a scheduler, a mechanic on contract and a front desk that doubled as the customer service line. On paper, it was doing well: enrolment was steady and the aircraft were busy. Underneath, a pattern was forming that anyone who has studied how organisations lose their best people would recognise. This case study follows the school across a year, examines what went wrong and measures what changed after it began rotating the hardest jobs among the team. The aim is to show how a modest structural change can protect both learners and staff.
The situation at the start
Three tasks consumed more energy than anything else at the school. The first was early-morning dispatch: confirming aircraft status, checking the weather picture and briefing the first students of the day. The second was handling rebooking after cancellations, a daily source of friction with students who had planned their week around a lesson. The third was the debrief for struggling students, the conversation in which an instructor must say honestly that progress has stalled.
By custom rather than decision, these jobs belonged to two people. Dana, the chief instructor, took every early dispatch because she was the most reliable riser. Luis, the scheduler, took every rebooking call because he was patient and knew the diary best. The hardest debriefs went to whichever instructor had the most experience, which in practice meant Dana again. Neither complained. Both were quietly hitting a wall.
What the signs looked like
Analysing the year in hindsight, several indicators were visible long before the crisis.
- Dana’s lessons began running late because of the morning workload, and students noticed.
- Luis stopped taking leave, since nobody else could manage the diary.
- Newer instructors never developed confidence in difficult debriefs, because they were not asked to hold them.
- Small errors in the records became more frequent, mostly late in the day and mostly from the two overloaded staff.
- Staff meetings shifted in tone from planning to venting.
None of these were dramatic on their own. Together they described an organisation relying on two people’s goodwill, and goodwill is not a resource that can be drawn on indefinitely.
The trigger
The trigger was mundane. Luis fell ill for ten days in the busy season. The diary, which lived largely in his head and in an idiosyncratic spreadsheet, descended into confusion. Students were double-booked, an aircraft was assigned to two lessons and two customers walked out in frustration. The school did not lose its licence or its reputation, but it learned how thin the margin had been.
The intervention
The owner convened a meeting and asked a direct question: which jobs, if they vanished tomorrow, would hurt us most, and who knows how to do them? The honest answers took half an hour and were uncomfortable. The team then agreed a modest set of changes.
- Dispatch rotation. Each instructor took one week in turn of early dispatch, using a one-page checklist that Dana drafted from her own habits.
- Diary sharing. The front desk and two instructors learned the scheduling system. Each took the rebooking desk for a fortnight, with Luis nearby for the first turn.
- Debrief pairing. Difficult debriefs were conducted by a pair, with the newer instructor leading under the eye of the senior one, and the roles swapped on alternating occasions.
- Written handovers. At the end of each turn, the holder wrote a half-page note: what was in flight, what surprised them and what the next person should check first.
- Recovery time. After a particularly heavy turn, the holder was given a lighter schedule for a few days.
The early results
The first cycle was slower, as predicted. Early dispatch took longer when done by an instructor unaccustomed to it, and one rebooking call was handled clumsily. Dana found it hard to resist stepping in. The owner asked her to act as a coach and not a rescuer, and, to her credit, she did.
By the second cycle, the checklist had been improved by three different hands, which made it better than Dana’s original. The rebooking desk had developed a short list of standard replies that students found clearer than the previous improvisation. Newer instructors reported that their first challenging debrief, which they had dreaded, turned out to be survivable and even useful.
What the school learned about itself
Perhaps the most striking lesson was that the knowledge had always been shareable. It had simply never been asked for. Once it was written down and practised, the school’s resilience rose sharply. When another instructor fell ill later in the year, the schedule absorbed it without a ripple, and nobody had to cancel leave.
The financial side was modest but real. Training operations are sensitive to cost, and reductions in confusion, double bookings and customer churn all matter. For readers who want the economics of learning to fly, our pieces on practical routes to spending less on flying lessons and on the connection between a trainer aeroplane and the final bill show how much an orderly operation matters to what students pay.
Reading the numbers without inventing them
A careful reader will ask what the school measured. In truth, it kept no elaborate statistics, and it would be wrong to pretend otherwise. What it did track was simple and observable: how often the diary produced a conflict, how many instructors could run the dispatch checklist unaided, how many people could cover the rebooking desk, and whether staff were taking their leave. Each of those moved in the right direction over the year, and the owner recorded them in a plain notebook at the end of every cycle.
The method matters more than the metrics. By choosing indicators tied directly to the dependencies it wanted to remove, the school avoided the trap of measuring activity instead of resilience. A count of how many people can do a job is a blunt but honest gauge of how fragile the job is.
The wider pattern
The school’s story is not unique to aviation. Organisations that must stay available at awkward hours, such as those running online services, have learned the same lesson and built rotations into their routine. Companies that help teams in that field, among them DevOpsSupport, an India-based consultancy for DevOps and cloud operations, emphasise shared duty and clear handovers as a matter of course. Seen from that angle, the flight school simply rediscovered a principle that other industries had adopted earlier.
Caveats and limits
It would be misleading to present rotation as a cure-all. Some tasks require qualifications that not everyone holds, and in those cases only appropriately authorised people may participate. A very small team may not have enough members to rotate meaningfully, in which case adding capacity must come first. And rotation requires continuing attention: without regular review, charts go stale and old habits return.
There is also a cost in the first months. Some students will meet a less polished briefing, and some staff will feel uncomfortable being seen to learn. Leaders who expect and accept that cost tend to see it fade quickly.
Practical takeaways
- Identify the two or three jobs that drain the most energy and note who currently holds them.
- Write a short checklist for each, drawn from the person who does it best.
- Rotate in turns, with a coach beside the newcomer for the first cycle.
- Require a half-page handover each time.
- Review after a cycle, and adjust the weights and the lengths of turns.
A year after the first meeting, the school had the same aircraft, the same premises and broadly the same students. What it had gained was a team in which several people could do each essential job. The change did not make flying lessons more exciting, but it made them more dependable, which for a flight school is the more valuable quality.
