Ask ten people how they handle the aftermath of a tech task and you will hear roughly three approaches. Some keep everything in their heads, some write long reports that nobody reads, and a few write a short, fixed-format note. This comparison looks at those options and explains why, for a busy person in Chennai or anywhere else, the three-line lesson learned usually comes out ahead.
Meet the contenders
Option one is memory. It costs nothing and requires no discipline, but it is unreliable, and it fades fast once the next task arrives. Option two is the long write-up: a page or more describing what happened, why and what to do. It is thorough on paper and rarely finished in practice. Option three is the three-line lesson learned, which pairs an event with a takeaway and a planned change in one sentence apiece.
All three have their uses; the real question is which one gives you the most useful result for the least effort on ordinary tasks, such as setting up a new device, migrating files or fixing a recurring app problem.
Comparing them on effort
Memory takes no time, but it also has no output, so it deserves no credit for effort. A long write-up can take thirty minutes or more, which is why people postpone it, and postponed notes lose detail. A three-line note takes two minutes. If you have to choose between a perfect habit you drop in a fortnight and a modest one you keep for years, the modest one wins on effort alone.
Comparing them on reuse
Here the gap widens. Memory cannot be shared, and it shifts each time you recall it. Long write-ups can be shared, but readers skim them and miss the one actionable sentence buried in the middle. A three-line note puts the action line where everyone can see it. When you scan a page of dated notes, you can pull out repeated lessons in minutes.
For a team, the difference is more pronounced still. A new colleague can read a month of short notes over a cup of tea, whereas the same month of long reports would be a week of reading.
Comparing them on honesty
People are more candid in short notes than in formal reports. A long report invites polish and defensiveness, while a three-line format leaves little room for either. Memory is the least honest of all, because it rewrites events to flatter you. The short note forces you to commit to a specific thing that happened before the story changes.
Where the long write-up still wins
It would be unfair to dismiss detailed reports. For a serious outage, a legal matter or an expensive project, a full account is appropriate. The sensible approach is to use both: write the three-line note straight after the task, and expand into a longer document only when the stakes justify it. The three lines can then serve as the summary at the top.
A side-by-side example
Suppose you lost an afternoon because a shared drive’s permissions were set wrongly after a move. With memory, you will recall “that was annoying” and nothing more. With a long report, you spend an evening documenting it and still forget to mention the one setting that mattered. With three lines, you write:
- Happened: files were unreachable for the team after the folder move.
- Learned: the permissions did not carry over with the folder.
- Change: check sharing settings straight after any move, before telling anyone it is done.
That is the one thing you needed to remember, delivered in under a minute.
Keeping the habit while you travel or explore
The comparison also holds for life around the work. If you are curious about the city beyond the office, a read such as a roundup of memorable Chennai outings pairs nicely with a note habit: after an outing, jot three lines on what worked about how you got there and what you would plan differently. For those thinking of wider trips, a piece on Kerala’s events, places and local experiences offers more places to try the idea.
One errand, three approaches
Take a familiar chore: getting a phone ready for a work trip abroad. By memory, you repeat last year’s scramble. With a long report, you never bother. With three lines, you read what you wrote after the previous trip, start earlier, look at RankeSIM, a site comparing SIM and eSIM options for locals and travellers, and add a fresh note when you get back.
Scorecard
- Effort: memory lowest, three lines low, long report high.
- Reuse: three lines highest, long report medium, memory lowest.
- Honesty: three lines highest, memory lowest.
- Depth: long report highest, three lines moderate, memory shallow.
- Likelihood of being done: three lines highest, long report lowest.
Verdict
For everyday technology tasks, the three-line lesson learned is the practical winner. It is cheap enough to do every time, structured enough to reuse and plain enough to be honest. Keep long reports for the rare, high-stakes cases and keep memory for what it does well, such as recalling the feel of a task, not its details.
Which option suits which person
If you work alone and rarely repeat tasks, memory may be enough for the odd one-off job. If you repeat tasks weekly, such as updates, backups or onboarding a new device, the three-line note quickly pays for itself. If you lead others or answer to a client, keep the short note for yourself and write the long version only when someone outside your team needs a full account.
How to switch in one sitting
Create a document titled “Lessons” with three headings: Happened, Learned, Change. Write a note about your most recent task now, while you still remember it. Add a weekly calendar alert at the close of each working week to add anything you missed and to read the pile.
After a month, review the notes together and pick the one that repeated most. Turn it into a checklist step. That single step will likely save you more time than any app you could install this week.