Say it like this
- TL;DR: we're moving the release to Thursday.
- TL;DR at the bottom if you're short on time.
- Can you add a TL;DR to the top of the doc?
Use it at work
Summarising your update
- TL;DR: we're on track for Friday.
- TL;DR at the bottom.
Asking for a summary politely
- Could you add a TL;DR for people who missed the meeting?
- What's the short version?
In a document
- TL;DR: we recommend option A.
- Summary: option A is cheaper and faster.
Don't say this
Replying "TL;DR" to someone else means "I didn't read it". It sounds rude at work.
Don't mix it up
| Term | What it is | Who writes or uses it | When |
|---|---|---|---|
| TL;DR | a one-line summary of a long text | tech teams, chat, docs | long messages and docs |
| exec summary | a short formal summary for leaders | managers, executives | reports and proposals |
| FYI | information with no action needed | everyone | sharing something useful |
Practice
Try it
4 quick exercises
1. You wrote a long email about a migration. Which line works best at the top?
2. _______: we need one more week to finish testing.
3. Which use of TL;DR is natural at work?
4. Write a one-line TL;DR for this: 'After testing three options for two weeks, the team found that option B is the fastest and cheapest, so we will use it.'
Say it out loud
Phrase 1 of 3
"TL;DR: we're moving the release to Thursday."
We don't save your recording. The word check uses your browser's speech recognition.
More about TL;DR
Real examples(3)
- in Slack
"TL;DR: the bug is fixed in staging, and we ship to production tomorrow morning."
- in a design doc
"TL;DR: we recommend Postgres over DynamoDB because our queries are relational."
- in a code review
"Long comment below, but TL;DR: let's move this logic into the service layer."
More mistakes(2)
Handle with care. Use TL;DR to summarise your own writing. As a reply to a colleague it sounds like "I could not be bothered to read this".
- ✕TL;DR: In this message I will explain the background of the project and then...✓TL;DR: the project is two weeks late because the vendor API changed.
A TL;DR is the conclusion, not an introduction. Put the result or decision in it.
- ✕TLDR the meeting notes please.✓Can you give me the TL;DR of the meeting notes?
TL;DR is a noun or a label, not a verb.
Other forms(3)
- too long; didn't read full form
"TL;DR means too long; didn't read."
- the TL;DR noun
"What's the TL;DR of the incident report?"
- TLDR / tl;dr spelling
"All three spellings are common in chat."
Often used with(3)
- add a TL;DR · write a short summary at the top
- the TL;DR is · giving the main point
- TL;DR at the bottom · summary placed at the end
Similar words(3)
- in short · neutral, good for email
- summary · formal docs
- bottom line · business email, slightly direct
Opposites(2)
- deep dive
- full write-up
Questions(4)
- What is the full form of TL;DR?
- TL;DR stands for "too long; didn't read".
- Is it rude to write TL;DR at work?
- Not when you write it yourself to summarise your own message. It is rude only as a reply that means you did not read someone else's message.
- Where do I put a TL;DR?
- At the top of a long message works best, so readers see the main point first. Some people put it at the bottom.
- How do you pronounce TL;DR?
- Most people say the letters: "tee-el-dee-ar". Some say "too long, didn't read".
