Marisol ran operations for a small flight training club with four aircraft and a waiting list of students. Every Monday the same complaint reached her desk: lessons were being cancelled or shuffled, and nobody could say how often. She had a plan to fix it, a new booking tool and a revised briefing routine. Her instructor, Tobias, asked one question before she signed anything: “What does it look like today?” That question is the subject of this account of how one training club learned the value of a baseline.<\/p>\n
Marisol’s proposal was sensible on paper. Replace the shared spreadsheet with a booking application, move pre-flight briefings to a fixed slot, and ask students to confirm lessons the evening before. She expected fewer disruptions within a quarter.<\/p>\n
Tobias did not oppose the changes. He objected to the order. If the club switched everything at once, the first month under the new system would be compared with nothing but impressions. A good month might be luck, a bad one might be blamed on the software, and the committee would be back to arguing from anecdotes. Aviation habits run deep here: before anything on an aircraft is adjusted, its condition is written down, because a reference cannot be rebuilt afterwards.<\/p>\n
They agreed to watch the existing routine for a stretch of ordinary operating days, with no improvements allowed. Three headings went onto a single sheet.<\/p>\n
Marisol admitted afterwards that this felt like delay. She wanted to be fixing things, and the log looked like a pause. Tobias held firm, and the instructors each added one line of their own: what proportion of lessons began on time in their own experience, written as a rough note rather than a precise claim.<\/p>\n
The first surprise was that the biggest delay had nothing to do with the spreadsheet. It sat in the cancellation chain, where a message reached the front desk but waited until the next shift before anyone offered the slot onward. The booking tool Marisol had picked would not have touched that gap at all.<\/p>\n
The second surprise was cost. Staff time spent rearranging lessons turned out to be higher on days of marginal weather, because plans changed late and several people re-did the same adjustments. That finding sent Marisol to a study aid the club already recommended to students, a piece on how trainees can build their weather knowledge<\/a>, and prompted a short briefing for the front desk on how the instructors read the day. Without the numbers, nobody would have connected weather judgment with office workload.<\/p>\n Perhaps most useful of all, the baseline showed how much the club’s own figures moved from week to week without any change at all. That ordinary wobble set a bar. Any improvement smaller than it could not honestly be called an improvement.<\/p>\n Armed with the picture, the committee dropped the idea of a grand switch. They changed the cancellation hand-off first: a single shared message thread monitored by whoever was at the desk, with a standing instruction to offer freed slots immediately. Everything else stayed exactly as before for the following weeks.<\/p>\n When they compared the new figures with the old sheet, the gap between cancellation and re-offer had narrowed clearly, well outside the ordinary wobble. They could point to one change and one result. Only then did they add the booking application, and again they logged the effect separately. The application helped with confirmations but did very little for the cancellation chain, which matched the baseline’s early warning.<\/p>\n The sequencing also settled a budget argument. One committee member wanted to pay for premium software tiers. Because the club had recorded its cost of rearranging bookings before and after each step, the decision became a short conversation about numbers on a page, much like the habit described in the club’s own article on noticing where money quietly drains away<\/a>.<\/p>\nChanging one thing at a time<\/h2>\n
A note on planning resources beyond the airfield<\/h2>\n