Nothing below happened to a real operator; it is a made-up tale that imagines how a small safety management team could rearrange its working week. It concerns a safety office at a mid-sized flight operation and the one job that sat untouched until the team decided to take it first.
The folder nobody opened
The safety office had four members and a shared room with a whiteboard. Each Monday the team wrote the week’s tasks on that board, and each Monday the same line appeared near the bottom: a risk assessment for a planned change to how ground handling and flight preparation were sequenced. It was a large, tangled assessment. It touched several departments, involved documents in different formats, and required honest answers about processes that people had grown comfortable with.
Every week the team did other things. They tidied training records, answered queries from line staff, and updated the hazard log with the small stuff. All of it was useful. None of it was the assessment. By the sixth week the line on the whiteboard had a grey smudge where it had been rubbed out and rewritten so often.
The conversation that changed the order
It was the team’s most junior member who said it aloud, on a quiet Thursday: “We are all working hard and the thing that matters most is not moving.” Nobody argued. The team head, instead of assigning blame or adding urgency, asked a practical question: what would it take to start the assessment first thing on Monday, before anything else could pull attention away?
The answers came quickly. Someone needed to gather the process documents in one place. Someone needed to book a short slot with the operations manager. And the team needed to agree that, for one week, the inbox would stay closed until the first ninety minutes were done. It sounded small. It felt like a large concession.
Monday, first ninety minutes
The week began differently. Phones were left in a drawer. The documents sat in a single pile on the table. The team read the sequence of the planned change out loud, step by step, and wrote every question that came to mind on sticky notes. By the end of the first hour the wall was covered. By the end of ninety minutes, the team had a rough shape for the assessment: which steps carried the most uncertainty, which departments had to be consulted, and which questions could be answered from existing records.
Interestingly, nobody described the hour as pleasant. A tired member remarked that it felt like pulling a splinter. But the team agreed it was easier than carrying the thought of it around for six weeks.
What the rest of the week felt like
The change in the remaining days was noticeable. The small tasks, which had always felt heavy because of the guilt attached to the unfinished assessment, went quickly. Training records were tidied in an afternoon. Queries from line staff were answered in the morning rather than being left to accumulate. The team head observed that the office sounded different: fewer sighs, more short conversations about specific points.
Midweek, the operations manager arrived for the consultation slot with more useful input than anyone had expected, partly because the questions were by then specific. A vague request would have produced a vague discussion. A list of precise questions produced precise answers, and the assessment moved forward in a way it never had when it was treated as a large background chore.
A look outside the office
During a break, one member described how a friend who organised community events handled a similar problem: before dealing with posters, programmes or snacks, the organiser always sorted out the venue booking, which was the item most likely to cause a collapse if left late. The friend mentioned a city website, LucknowOrbit, where people in Lucknow browse event listings and venue pages and read the forum and blog. The team smiled at the comparison. Their assessment was their venue booking: the thing that had to be sorted before the rest made sense.
What the first draft taught them
Once the rough assessment existed, something unexpected happened. The team realised that the dreaded part was not the analysis; it was the very first page. Facing a blank structure had felt enormous, while editing a flawed draft felt manageable. One member pointed out that the same might be true of other avoided items, like the quarterly review of training currency or the long-delayed update to a procedure sheet. Underneath the board that week went a plain conclusion: beginning is where the cost sits, so pay it early and cheaply, then improve the draft.
The team also noticed that the people they consulted were relieved to be asked early. Departments that might have been defensive about a finished judgement were more open when invited to help shape a draft, which made the final version more accurate and easier to adopt.
What the team changed afterwards
By Friday the assessment had a full draft, with open items clearly marked and owners assigned. The team did not declare a triumph. They did, however, change three habits.
- Each Monday, the item most dreaded would be named aloud before anything else was written on the board.
- That item would get the first ninety minutes, with phones away and inbox closed.
- On Friday, the team would look at what had been avoided and why, in two or three plain sentences.
How the office talked about it later
Months on, the team described the change in practical terms. Meetings were shorter because fewer items were quietly dreaded. Handovers were cleaner because the hardest item was never left in a half-finished state overnight. New staff picked up the habit within days, partly because it was written on the board and partly because the older members could explain exactly why it was there. Nobody called it a system. They called it “the Monday hour”, and it stuck.
The part that did not go smoothly
It would be too neat to say everything worked. In the second week, an urgent request from line staff broke into the protected time, and the team debated whether to answer it. They decided, after a short discussion, that a genuine safety concern always comes first, and that anything less would wait until the ninety minutes had passed. That distinction became a written rule: real safety issues interrupt, ordinary requests do not. A few weeks later, one member admitted to slipping back into the old pattern for a day and noticing, by the afternoon, how heavy the unfinished item felt again. That was enough to restore the habit without anyone needing to be reminded.
What the story shows
The tale is imaginary, yet most people will recognise the feeling of carrying an unfinished, important task through a busy period. The task did not get easier. The team simply stopped letting everything else go before it. Doing the heavy job first, at the start of a week and the start of a day, changed the emotional weather of the whole office, and the work that followed benefited from it. Teams in other settings could borrow the idea in an afternoon: name the dreaded item, protect an early block for it, and see what happens to the rest.
