tl;dr is an ugly phrase for many. It’s an internet shorthand which stands for “Too long; didn’t read.” Writing it to others immediately gives the impression that you are lazy or ignorant, or at the very least that you are dismissing whatever point they’re making.
But it’s also a great practice to use for yourself. It will force you to think on a macro scale and prepare main talking points for stakeholders.
It forces you to review
One of the habits you might get into is that you might take notes during the meeting, but then only ever reference or review those notes if you need to remember what was that during that time. There’s a great method of doing a 30 second review after every meeting to remember the key points of it, but this takes it a step further.
It forces you to prioritize
One of the arguments against tl;dr is simply “Why not just summarize?” The issue is that sometimes, summaries could be still be 5–10 points or even half a page. The best tl;dr’s are often condensed to 1–2 sentences. This may seem impossible to do, except when considering the next point.
It forces you to think of the user
If your lead developer missed a meeting and asked you to give a tl;dr of it, you wouldn’t talk about the key points for the marketing department. It’s the same thing here. By using tl;dr, you’re forced to think about who the person is, and what points you need to prioritize.
(Bonus) It helps you identify if you’re getting something out of the meeting
If you aren’t able to create a tl;dr for yourself, then there’s two possibilities.
- You’re not paying enough attention/asking the right questions
- Maybe you don’t need to attend that meeting.
I offer no solutions here on how to resolve these things, just something to point out.
tl;dr: Bad to use on others, great exercise for you.