After a software rollout, a vendor switch or a website rebuild, every team faces the same quiet decision: how will we keep what we just learned? Three approaches dominate. People rely on memory, they produce a long write-up, or they jot a three-line lesson learned. Each has a place. This comparison sets them against four criteria so the choice is made on purpose and not out of routine.
The three-line format is simple: record the event, state the insight, name the adjustment. The question is whether that brevity helps or hurts compared with the alternatives.
The four criteria
- Effort: minutes needed, and whether the task actually gets done on a busy Friday.
- Fidelity: how closely the record matches what really took place.
- Reuse: how easily someone can find and apply it months later.
- Behaviour change: whether the next attempt is actually different.
Notice that “completeness” is deliberately absent. A record can be complete and still never change anything.
Option one: rely on memory
Memory costs nothing and feels sufficient right up until it fails. Its weakness is not forgetting; it is rewriting. Two weeks after a migration, people recall the vivid incident and lose the quiet sequence that produced it. Fidelity is low and drifts upward in flattering ways.
Reuse is close to nil. A lesson that lives in one head leaves the building with that head. Behaviour change happens only when the individual happens to remember at the right moment, which is unreliable.
Verdict: acceptable for trivial tasks, poor for anything with a cost.
Option two: the long write-up
A formal document captures detail and can satisfy auditors, managers and future newcomers. For a major programme it is often justified. The costs are equally clear. Writing takes hours, so it is postponed; postponed documents are written from memory, which brings back the fidelity problem. Readers rarely finish them, so reuse is poor in practice despite being high in theory.
Behaviour change depends on someone distilling the document into actions, and that distilling is the step most often skipped.
Verdict: valuable for large, one-off, high-stakes work; overkill as the default.
Option three: the three-line lesson
Three lines take two minutes. That alone changes completion rates, because small tasks get done while large ones queue. Fidelity is decent because the note is written while details are fresh, and the format limits embellishment. Reuse is strong when notes live in one searchable place, since a reader can scan fifty of them in the time one report takes to open.
Behaviour change is the standout. The third line forces a concrete commitment: “next time I will confirm the data export format before the cut-over.” That sentence can be pasted straight into a checklist.
The weakness is depth. Three lines cannot carry a full root-cause analysis, and they should not try. They point toward the longer record when one exists.
Verdict: best default for routine work, with an escape hatch to longer documents.
Side by side
- Effort: memory none, write-up high, three lines low.
- Fidelity: memory low, write-up high if written promptly, three lines moderate to high.
- Reuse: memory none, write-up moderate, three lines high when stored together.
- Behaviour change: memory unreliable, write-up indirect, three lines direct.
A worked comparison: a customer-database migration
Picture a small company moving its customer records to a new system. Under the memory approach, the project lead remembers that “the import was messy” and nothing more. Under the long write-up approach, a twelve-page report arrives three weeks later, after the details have blurred, and is filed without being read.
Under the three-line approach, the note written on the afternoon of the import says: duplicate contacts appeared because two spreadsheets used different spellings for the same company; the lesson is that matching rules must be decided before the import, not discovered during it; next time a sample load runs first and someone signs off on the matches. That is a complete, reusable instruction in under fifty words.
Choosing in practice
A workable rule is to scale the record to the cost of repeating the mistake. For small and medium tasks, write three lines. For anything that touched customers, budgets or compliance, write three lines first and then decide whether a longer document is warranted. The short note often reveals that the long one is unnecessary, or shows precisely which section it needs.
Teams planning a technology programme can pair this with upfront thinking. The overview on navigating business technology solutions is a reasonable place to frame the choices, and the article about connecting web solutions, cloud and AI for growth shows how many moving parts a typical project involves, each one a candidate for its own short lesson.
An example from a business trip
The same habit carries over to travel for work. After a client visit abroad, three lines might record that the phone plan was sorted at the airport in a hurry, that a comparison made earlier would have been calmer, and that next time the arrangement gets decided before departure. One resource for that kind of homework is RankeSIM, a website with side-by-side listings of SIM and eSIM plans for local use and for travel, though the point of the exercise is the note, not the tool.
Keeping the format honest
Some guardrails help the three lines keep their value.
- Write them within a day of finishing the task.
- Use specific nouns: name the system, the step, the handover.
- Make the third line an action, not an attitude. “Be more careful” is not an action.
- Store every note in one place with the date and project at the top.
- Review the stack quarterly and promote repeated themes to checklists.
Bottom line
Memory is free but unreliable, long write-ups are thorough but slow, and three-line lessons sit in the useful middle. They are not a replacement for documentation where documentation is required; they are the habit that makes sure something gets recorded at all. If your team captures nothing today, start with three lines per task and revisit the format after a month. The evidence will be sitting in your own notes.

