Templates · Thread
Lessons learned thread template
Turn experience into a thread people save. One lesson per tweet, each one backed by something that actually happened to you.
The template
- 1
[Time period] of [doing the thing]. [Honest one-line result]. [Number] lessons I wish I'd known on day one:
- 2
1. [Lesson as a short rule]. [The moment you learned it, in one or two sentences.]
- 3
2. [Lesson as a short rule]. [The moment you learned it.]
- 4
3. [Lesson as a short rule]. [The moment you learned it.]
- 5
4. [Lesson as a short rule]. [The moment you learned it.]
- 6
5. [Lesson as a short rule]. [The moment you learned it.]
- 7
If I had to keep one: [the lesson that matters most, restated]. What would you add?
When to use it
- You've hit a milestone (a year in business, a project shipped, a role left) and have something to reflect on.
- You made a mistake others in your field are likely to make too.
- You want a post that builds credibility without selling anything.
Why it works
The credibility line
The time period and an honest result tell the reader why your lessons are worth reading. Honest beats impressive: a failure earns as much trust as a win.
Rule, then story
Each tweet opens with the lesson as a short rule people can quote, followed by the specific moment you learned it. The story is what makes it believable.
Numbered tweets
Numbers set expectations and let readers jump around. They also make replies easy: "number 3 is so true".
The one to keep
Ending with the single most important lesson gives readers a takeaway, and the question invites replies from people with their own lessons.
Examples
- Y
Your name@you1/7
3 years running a design studio. Grew to 6 people, then back down to 3 by choice. 5 lessons I wish I'd known on day one:
- Y
Your name@you2/7
1. Price the project, not the hours. Our best year was the year we stopped sending timesheets. Clients cared about the launch date, not how long the logo took.
- Y
Your name@you3/7
2. Your first hire should free up your weakest hour, not your strongest. I hired a designer when I needed someone to handle invoices and scheduling. I was still drowning.
- Y
Your name@you4/7
3. A small client can cost more than a big one. Our most demanding client paid us $4k total and took more meetings than a $60k retainer.
- Y
Your name@you5/7
4. Say the uncomfortable thing in the first call. Every project that went wrong had a red flag I noticed and didn't mention.
- Y
Your name@you6/7
5. Growth isn't the only direction. Shrinking back to 3 people doubled my margin and gave me my evenings back.
- Y
Your name@you7/7
If I had to keep one: say the uncomfortable thing early. It's cheaper every time. What would you add?
- Y
Your name@you1/7
10 years writing software, the last 4 as a tech lead. 5 lessons I wish I'd known as a junior:
- Y
Your name@you2/7
1. Read the error message. All of it. I once lost a full day to a bug the stack trace described in plain English on line two.
- Y
Your name@you3/7
2. Boring code is a feature. The clever abstraction I was proudest of was the first thing the next team rewrote.
- Y
Your name@you4/7
3. Write the doc before the code. Half my bad designs fell apart when I tried to explain them in a paragraph. Better to find out in a doc than in review.
- Y
Your name@you5/7
4. Ask the question in public. Every time I asked in a team channel instead of a DM, someone else had the same question.
- Y
Your name@you6/7
5. Ship small. My worst release was 4,000 lines in one PR. My calmest year was the year nothing went out larger than 300.
- Y
Your name@you7/7
If I had to keep one: boring code is a feature. Future you is the main reader. What would you add?
Tips
- Five lessons is plenty. Three great ones beat ten generic ones.
- Cut any lesson you can't tie to a specific moment. "Consistency matters" with no story reads like a poster.
- Keep the rule line under ten words so it's easy to quote.
- Draft the stories as a rough list first, then turn them into a thread with the thread maker.
Go deeper: How to write a thread on X that people read to the end · How to write hooks that make people read the next line
Your next week of posts,
done this afternoon.
Sign up with your email, set your brand, and start writing. Upgrade when you want AI and auto-posting.