What follows is invented, though you may recognise the scene. A small flying club runs evening ground-school sessions for people learning to fly. The team is tiny: a coordinator, a pair of instructors who teach in their spare hours and a volunteer who keeps the timetable. None of them is paid much, and all of them have other commitments. Over one season they discover that the biggest obstacle to a good evening class is not the syllabus, the room or the projector but the pinging of notifications. What they do about it is a nice illustration of setting quiet hours for notifications, so we will follow them through the season and then pull out the practical lessons.
The setting: a busy club with a noisy group chat
The club’s team keeps in touch through a shared group chat. It started as a convenient way to confirm room bookings. Over time it filled with weather comments, photographs of aircraft, jokes, questions about unrelated matters and urgent-sounding notes that turned out not to be urgent at all. Each member also runs the club’s social media in rotation and receives enquiry messages from prospective students.
During class evenings, the instructors’ phones buzz constantly. The coordinator, sitting at the back to handle late arrivals, answers messages as they come. The volunteer is supposed to be taking attendance but is often replying to someone about next week’s booking. Learners notice. A few of them quietly check their own phones when the instructor glances down at theirs.
The turning point
The turning point comes after a particular evening. The instructor is partway through explaining how a navigation exercise is plotted when their phone buzzes twice. They glance, lose their place, backtrack and run over time. A learner who had been following carefully now looks confused. After class, the coordinator asks the team to stay for ten minutes and suggests an experiment: for the next month, everyone mutes the group chat and social notifications during class, with one exception. If anything involving a learner’s welfare or the building arises, the coordinator’s phone is the only one that rings through, and everyone else can be reached by a call, not a message.
The instructors agree, a little warily. The volunteer, who worries about missing enquiries, asks what will happen to them. The answer is that the volunteer will review all muted messages in a short catch-up straight after class, and answer anything that is waiting.
What the team actually did
- Agreed the windows. The class period itself became a quiet window, plus the planning meeting held beforehand.
- Wrote the exception rule on one line. It was pinned at the top of the group chat so nobody had to remember it.
- Set up the phones together. They sat in the clubhouse and configured the focus settings side by side, helping one another, and tested the exception call.
- Told learners about it. A short note at the start of term explained that phones would be quiet during class and why.
- Booked the catch-up. Ten minutes after each session, one person went through the backlog and reported anything that needed action.
The first weeks
The early sessions felt odd. One instructor admitted to reaching for the phone out of habit several times in the first evening. The volunteer found the silence unnerving. But by the second week, the team noticed a change in the room. Explanations flowed without stumbling. Learners asked more questions, because the instructors were visibly present when they answered. Attendance sheets were completed on time. The coordinator, freed from reflexive replying, spent the quiet stretches greeting latecomers and keeping an eye on the room.
There was one small hiccup. A learner arrived early on a rainy evening and could not find the door, and the message to the coordinator went unseen until the catch-up. Nobody was harmed, but the team talked about it. They decided to add the building entrance line to the exception list, with a note on the door telling arrivals which number to call. That adjustment is typical: the exception path improves with use.
Learning alongside the learners
As the season went on, the team began to think about their own study too. One of the instructors was brushing up on teaching techniques, and another was reading about ways to help students manage the cost of training. The club’s own blog has pieces on cutting the expense of learning to fly and on looking for scholarship support as a flight student, and the team agreed that anyone reading them for the next term’s planning should do so in a protected window, with their own phone quiet.
The coordinator also browsed a few outside learning sites to see how they present their material. One was Wingversity, a site that describes itself as an online learning platform for aviation careers, with areas for courses, learning paths and a blog. The team treated it as an example of layout and navigation only, and made no judgement about its content.
What the learners noticed
The learners were not told to evaluate the experiment, but their comments trickled in anyway. A few said the room felt more settled, and that it was easier to ask a question when the instructor was not half-looking at a screen. One mentioned that they had begun muting their own phone during class too, and that the second hour no longer dragged. Another said they had stopped feeling guilty about not replying to messages during the session, because the instructor was clearly doing the same.
The team took these remarks as encouragement but not as proof. They knew the sample was small, the season was short and enthusiasm for anything new tends to run high in its first weeks. Still, the comments pointed in a consistent direction, and they cost nothing to gather.
An evening in the third month
By the third month, a class evening had a recognisable rhythm. The team arrived a little early, switched on the quiet profile on their phones and glanced once at the pinned exception line. The instructor taught the first block, a practical walk through a chart exercise, and the learners worked through a problem with pencils. The coordinator greeted two latecomers and handed them the handout. The volunteer ticked off attendance, then sat in silence for a few moments, which they later described as an unexpected pleasure.
When the session ended, the phones came back to life. The volunteer ran the catch-up: three enquiry messages, one booking change and a good deal of chat. Two replies were sent, one booking was adjusted and the chat was skimmed and closed. Fifteen minutes later, the room was tidy and everyone went home. It was an ordinary evening, and that was precisely its charm.
What the team concluded at the end of the season
At the closing meeting, the coordinator asked everyone to say one thing that had changed and one thing that had not. The instructors said they felt less rushed in class. The volunteer said that the catch-up turned out to be quicker than expected and that enquiries were answered just as promptly. The coordinator said that the group chat had become calmer, because people had started saving non-urgent chatter for the catch-up. What had not changed was the weather: it still interfered with flying, and no notification setting could alter that.
They agreed to keep the arrangement. They would revisit the exception list every term, and they would keep it short.
Lessons any small team can borrow
- Start with an experiment, not a rule. A month-long trial feels less threatening than a permanent policy.
- Keep the exception route single and simple. One phone, one number, one line of text.
- Do the setup together. It builds goodwill and catches mistakes.
- Tell the people affected. Learners and enquirers are more patient when they know what to expect.
- Review regularly. The list that worked in September may need trimming by December.
The ending, such as it is
There is no dramatic finale. The club did not double in size and no records were broken. Class evenings became steadier, and the people running them felt a little less frayed. That is the realistic scale of benefit for a habit like this. If your own team is wrestling with a busy chat and an evening activity, the story suggests a gentle first step: agree a window, write one exception, test it together and look again in a month.

