The scheduler at a small flying club once told a story over coffee that I have not forgotten. A new term timetable had been printed, pinned to the board and admired. On the first Monday, two instructors turned up to find the same aircraft booked for both of them. Everyone had assumed somebody else had checked how many aircraft were really available. Nobody had written the assumption down, so nobody had been asked. Below is a staged method for an hour-long meeting that drags such beliefs into daylight, the sort of thing a flying organisation could do ahead of a fresh timetable.
Getting ready
Gather a room or a call line, a blank page or shared document, and three to six people who each see the plan from a different side: someone who schedules, someone who flies or instructs, someone who looks after the aircraft or equipment, and someone who deals with students or customers. A kettle helps. You do not need special software or any formal training in a method.
Why one hour is enough
It is tempting to schedule a half-day workshop, but long sessions drift into redesigning the plan rather than listing what it assumes. An hour forces focus. The goal is a first honest page, not a perfect one, and the page will keep growing after the meeting as people remember things on the way home. Many teams find that the lines they add in the following days are the most revealing of all, since they come from reflection rather than from the pressure of the room.
Step 1: State the plan in two sentences
Ask the group to describe what the plan is meant to achieve, in two sentences at most. For the club in the story, it might have been: “Run lessons across the week for all current students, with fixed morning and afternoon blocks. Keep aircraft in use evenly across blocks.” If the group cannot agree on two sentences, you have already found the first useful problem.
Step 2: Give everyone five quiet minutes
Before any discussion, each person writes down every belief they are relying on, finishing the sentence “this will only work if…”. Silence matters, because open discussion tends to anchor everyone on the first idea spoken. Aim for quantity. Ten rough lines from each person is plenty.
Step 3: Collect and merge
Read each person’s lines aloud, one at a time, and write them on the shared page. Merge duplicates but keep distinct wording where it differs slightly, since small differences often reveal that two people hold different beliefs without realising it. In the club’s session, one person wrote “all aircraft available every day” and another wrote “most aircraft available most days”. Seeing both together prompted the first honest conversation about maintenance downtime.
What the lines looked like at the club
A few of the sentences from that first session give a feel for the level of detail that works. “Every instructor can cover any student’s lesson block.” “The weather will allow flying on most mornings in the new term.” “Students will confirm their bookings by the evening before.” “The booking sheet is read by everyone, not just the person who maintains it.” None is dramatic. Several turned out to be wrong in small ways, and each correction saved a muddled morning.
Step 4: Rate confidence together
Go down the list and attach a word to each: solid, likely or guess. Do it quickly, and ask “how do we know?” for anything labelled solid. If the answer is “we have always done it that way”, change the label to likely. This step is where the group learns to separate habit from confirmation.
A note on tone
Keep the mood curious rather than critical. The purpose is not to catch anyone out. A good facilitator thanks people for unpopular lines, because those are often the most valuable ones.
Step 5: Pick the top few to check
You cannot check everything. Ask which unchecked lines would cause the most trouble if wrong, and which can be settled fastest. Choose the three or four that rank highly on either measure. For each chosen line, write the check, the person responsible and the date. Keep the checks small: a phone call, a look at a record, a short conversation with a student.
Step 6: Write the page in its final form
Tidy the list into a single table with five columns: belief, confidence, check, owner and date. Add a sixth column for the result, left empty for now. Send it to everyone in the room before they leave, and keep a copy where the team can find it. A page nobody can locate a month later has little value.
If the group is spread out
A remote session works with a shared document and a timer. Give each person a fixed slot for silent typing, then read the combined list on the call. Use a different colour for each contributor, so that nobody’s lines get lost during merging. The only real change is that the facilitator needs to invite quieter members by name, since silence on a call is easy to mistake for agreement.
Step 7: Close the loop
On the dates set, owners report results at a short stand-up or by message. Mark each line confirmed, corrected or open. When a correction changes the plan, note the change on the page, so the reasoning is preserved. In the club’s case, the check on aircraft availability showed that one machine would be in for scheduled work during a whole week; the timetable was adjusted before anyone reached the airfield.
Step 8: Schedule the next review
Put a date in the calendar, perhaps a few weeks on, for a fifteen-minute look at the list. New beliefs will have accumulated, and some old ones will have aged. Without a review, the page turns into a historical record of a plan that moved on without it.
A short facilitator’s script
If you have never led such a session, these prompts carry most of the load. Open with: “What does this plan need to be true?” During collection, ask: “What are we taking for granted here?” While rating, ask: “How do we know?” At the checking step, ask: “What is the smallest test we could do this week?” And to close: “Who tells us the result, and when?” Five questions, repeated whenever the discussion drifts, keep the hour useful even for a first-time facilitator.
What can go wrong with the session
- One strong voice dominates. Use the silent writing step to prevent this.
- The list becomes a list of complaints. Rephrase each line as a belief the plan depends on.
- Nobody owns the checks. Assign a name before closing the meeting.
- The session overruns. Limit it to an hour and carry unfinished items to the next one.
For software-minded team members
People with a background in IT will recognise the format from design reviews and tickets. If any of them would like to look further into formal study in that field, an Indian training portal whose own description mentions certificate courses, consulting and further services for IT folk is one place to start. It is an aside; the session works without it.
The result
The club ran the exercise before the next term. The first Monday was uneventful, which is the best thing a timetable can be. Nobody remembered that a list had made it so, which is how it should be. Spend one hour on a live plan of your own, and expect to unearth a belief that nobody had ever voiced.
