IT teams finish tasks constantly: a change window, a patch cycle, a service handover. Most of them learn something and almost none record it. The three-line lesson learned is a deliberately small answer to that gap. This question-and-answer guide covers what teams ask most when they first adopt it.
What exactly is a three-line lesson learned?
It is a note of three short statements written after a task. The first states the event. The second states the takeaway. The third states the change you will make on the next attempt. The format is fixed so that writing takes minutes and reading takes seconds.
The discipline lies in keeping each line to one sentence. If a line grows, it usually contains two ideas, and the second belongs in a separate note or a longer document.
When should the note be written?
As soon as the task closes, and no later than the same working day. Details decay quickly: the exact error message, the order of the steps, the person you waited on. A note written the next morning is already a reconstruction.
Teams that do this well attach the note to the closing of the task itself, so that “done” includes “lesson written.” It takes no extra meeting.
Who should write it?
The person who did the work. Delegating the note to a manager or a rotating scribe removes the detail that makes it useful. For tasks involving several people, each can add a line of their own, but the format should still stay short.
If a team lead wants to encourage the habit, the most effective move is to write their own notes visibly, in the same place, in the same style.
Where should the notes live?
Somewhere central that everyone on the team can search. A shared document, a wiki page or a folder in your existing tooling will do, so long as it needs no special access and sits within a click or two of daily work. Scattered notes in private files and chat threads defeat the purpose, because the value comes from scanning many notes at once.
Put the date and a short task label on the first line of each entry. That is enough structure for search to do the rest.
How does this differ from an incident review?
An incident review is a structured analysis of something that went badly, often with a timeline and contributing factors. A three-line lesson covers everyday work, including tasks that went fine. The two complement each other: the short note is the routine habit, and the review is the heavier tool you reach for when the stakes justify it.
Resources on improving how teams resolve problems, such as the overview of how AIOps tooling shortens the path to resolving IT problems, assume that teams capture knowledge somewhere. Three-line notes are a low-cost way to supply it.
What makes a good third line?
A good third line is an action you could put on a checklist. “Confirm the rollback path before the window opens” is an action. “Be more careful” is not. A reliable test: could someone else carry it out without asking you what you meant?
When the third line is concrete, the note often graduates into a team checklist after it appears two or three times. Over a quarter, that process produces a living list that reflects your real environment rather than a generic template.
What would a completed note contain?
Take a routine certificate renewal as the example. Happened: the renewal succeeded but a dependent service kept serving the old certificate until it was restarted. Learned: the service caches the certificate in memory, so renewal alone does not finish the job. Next time: add a restart-and-verify step to the renewal runbook entry.
Notice that the note names a system behaviour, not a person’s mistake. That keeps it factual and makes it safe for the whole team to read. It also took well under two minutes, which is the realistic budget for each entry.
How do we get people to keep doing it?
Make it light and visible. Keep the format short, review the notes together briefly at the start of a planning cycle, and promote repeated lessons into practice. People keep a habit when they see it change something. When a note prevents a repeat mistake, mention it. That story does more than any policy.
The roadmap thinking in the guide to building an AIOps implementation roadmap shows how longer programmes depend on feedback loops. A team’s own short lessons are the smallest feedback loop available.
Beyond the data centre
The format is not limited to servers. Staff who travel for support visits or conferences can apply the same format to the trip. For example, someone who forgot to arrange a local data connection on arrival might write that down, and read about options on RankeSIM, which lines up mobile SIM and eSIM options, both local and for visitors before the next journey. Then the note after that trip records how it went.
A quick template
- Date and task label:
- The event (one sentence):
- The takeaway (one sentence):
- The change (one action):
Paste it into your tracker as a task-closure comment, or into a shared page. Within a month you will have enough entries to spot repeating themes, and within a quarter you should have a handful of checklist items that came straight from your own work.
Summary
The three-line lesson is easy to explain and quick to write, and its power comes from being done every time. Write it at closure, keep it specific, store it where the team can search, and let repeated lessons become standard practice. Begin with the next change window and see what the notes tell you by the end of the month.