Ask people in aviation operations whether they write down what they learn after a task and you will usually get a polite yes, followed by a pause. Most do some version of it, but it is often scattered, informal or reserved for big events. The idea of a three-line lesson learned, a short note after any piece of work, tends to meet a handful of stock objections. Some are fair concerns; others are myths that stop good teams from trying a very small habit. Here are six, with the plain truth behind each.
Myth 1: “Three lines is too simple to be useful”
It sounds plausible that a serious field needs serious documentation. But simple and useful are not opposites. The three lines are a prompt, not a substitute for proper records. Their value lies in the thinking they force: stating a fact, finding a cause and deciding on one change. Plenty of valuable improvements in operations are small and specific, such as moving a check earlier in a routine or adding a line to a handover. A three-line note is exactly the right size for those.
The reality: short notes are useful precisely because they are short enough to be written every time and read every time.
Myth 2: “We already have a formal process, so we do not need this”
Formal processes matter, and nothing here replaces them. But formal records are written for formal purposes, and they are rarely the thing a technician or student opens before starting tomorrow’s task. A personal three-line note serves a different audience: you. It records the practical insight, in your own wording, that might never make it into a formal report because it feels too minor.
The reality: the note sits beside the official process, not in place of it. It fills the gap between “something happened” and “something was formally recorded”.
Myth 3: “It will turn into blame”
This is the most understandable worry. If lessons are written down, will they be read as accusations? The structure of the note is your protection. Line one states an event, line two states a cause about the process or the situation, and line three states a change. Nothing in the format asks who was at fault, and if a draft drifts into naming or judging, the fix is simply to rewrite line two as a cause. Written well, the notes talk about work rather than people.
The reality: the format steers toward causes and actions, and away from verdicts.
Myth 4: “Nobody has the time”
The honest way to test this one is to time it. Most people can write three short lines in around two minutes. Compare that to the time spent re-solving a problem that was solved last month, or searching a chat history for what was decided. The time is not saved on the day you write the note; it is saved later, when the lesson stops you from repeating a slip.
The reality: the habit costs minutes and returns them, with interest, the next time a similar task arrives.
Myth 5: “You only need one after something goes wrong”
It is natural to associate lessons with mishaps, but that wastes half the learning. When a task goes smoothly, there is usually a reason: a good preparation step, a clear briefing, a sensible buffer. If nobody writes it down, the reason is forgotten and the next person improvises again. A brief note such as “the handover went smoothly because the checklist was printed ahead; keep printing it” preserves success as deliberately as you would preserve a fix.
The reality: some of the best lessons come from days when everything worked.
Myth 6: “It is just another form to fill in”
Forms ask you to describe your work for someone else. The three-line lesson does the opposite. It asks you to describe your work for yourself, with no template to satisfy and no one to approve it. There is no required field, no category, no deadline imposed by anyone else. If it ever starts to feel like a form, it has drifted, and the cure is to shrink it back to three plain sentences.
The reality: it is a personal study aid, and its power depends on staying informal.
The shared assumption behind them all
Each of these objections leans on one belief, namely that a note must be big to be worth writing. Big notes are indeed costly, slow to produce and easy to skip. But the whole point of the three-line version is that it removes size from the equation. When a note costs almost nothing, the question changes from “is this worth documenting?” to “what did I learn today?”, and that is a much healthier question for any operation to ask of itself. Teams that adopt the short format often report that the conversation shifts too, from remembering what happened to deciding what to try.
A short worked example
To see how little it takes, imagine a technician finishing a routine task and writing: “The tool I needed was in a different cabinet from where I expected. I had assumed the layout was unchanged since the last time. Next time I check the layout at the start of the shift.” That is it. The note takes a couple of minutes and prevents a small, repeated delay.
A practical side note
People who travel for training sometimes mention that they also want a clear view of phone arrangements before leaving, and a site like RankeSIM, which presents local SIM and travel eSIM mobile plans for comparison, is one they browse. Whatever route you take, note how it went.
Getting started without ceremony
Beginning takes no permission slip and no special software. Choose a notes file, write the date and three lines after your next task, and read them before the following one. After two or three weeks, look for repeated themes. If the habit is helping, keep going; if it is not, adjust the wording of the prompts rather than abandoning the idea. The practice is meant to be light and flexible.
- Keep the notes in one place that you actually open.
- Write them the same day, while the details are fresh.
- Make the third line a step you could do within a week.
- Keep the tone neutral and focused on the work.
The bottom line
Put the six side by side and the habit holds up against each one. It is short, so it gets done. It is personal, so it does not compete with formal processes. It is built around causes and changes, so it does not become blame. Try it for a fortnight on one routine task and judge it by what you notice, not by what you assumed beforehand.
