25 thread templates
Every example is written for this page with made up details. None is a real person's thread.
Share what a stretch of work taught you, one lesson per post.
Outline1/7 [Number] lessons from [time or project]. The last one changed how I [do the work].
2/7 Lesson 1: [lesson]. [One line of what happened].
3/7 Lesson 2: [lesson]. [One line of what happened].
4/7 Lesson 3: [lesson]. [One line of what happened].
5/7 Lesson 4: [lesson]. [One line of what happened].
6/7 Lesson 5: [the lesson that changed your approach]. [What you do now].
7/7 If you are [in the same spot], start with lesson [number]. Follow for more on [topic].
Why it works. Each post stands alone, so readers can skim and still get value. Teasing the last lesson in the hook gives people a reason to keep going.
Break down a page, email or product and show what works and what does not.
Outline1/7 I took apart [thing] to see why it [works or fails]. Here is what I found.
2/7 First, the [part 1]. [What it does well or badly].
3/7 Then the [part 2]. [What it does well or badly].
4/7 The [part 3] is where it [wins or loses]. [Why].
5/7 One small detail most people miss: [detail].
6/7 What I would change: [fix].
7/7 The takeaway for your own [thing]: [lesson].
Why it works. Teardowns teach through a real example, which is easier to follow than theory. Readers also get a checklist they can run on their own work.
Walk people through how you reached a specific result, step by step.
Outline1/7 How I [got result] in [time frame], without [common thing people assume you need].
2/7 Where I started: [starting point].
3/7 Step 1: [what you did first and why].
4/7 Step 2: [what you did next].
5/7 Step 3: [the step that made the biggest difference].
6/7 What did not work: [thing you tried and dropped].
7/7 The result: [outcome]. If I did it again, I would [change].
Why it works. A clear result in the hook earns attention, and the step by step format makes it easy to copy. Sharing what failed makes the whole thread more believable.
04The mistakes thread
7 postsShare mistakes you made so others can skip them.
Outline1/7 I made [number] mistakes [doing thing] that cost me [time or money]. Here they are so you do not have to.
2/7 Mistake 1: [mistake]. What it cost: [cost].
3/7 Mistake 2: [mistake]. What it cost: [cost].
4/7 Mistake 3: [mistake]. What it cost: [cost].
5/7 Mistake 4: [mistake]. What it cost: [cost].
6/7 The pattern behind all of them: [root cause].
7/7 What I do now instead: [new habit]. Which one have you made?
Why it works. Mistakes feel honest and useful at the same time. Putting the cost next to each one shows the stakes without any hype.
Correct common beliefs in your field with what you have seen.
Outline1/7 [Number] things people believe about [topic] that do not match what I see. Myth vs fact:
2/7 Myth: [belief]. Fact: [what you have seen].
3/7 Myth: [belief]. Fact: [what you have seen].
4/7 Myth: [belief]. Fact: [what you have seen].
5/7 Myth: [belief]. Fact: [what you have seen].
6/7 Why these myths stick around: [reason].
7/7 The one fact I would tattoo on every [role]: [fact].
Why it works. The myth vs fact pattern creates small moments of surprise in every post. It also positions you as someone with real reps in the field.
06The step by step guide
8 postsTeach a process from start to finish in numbered steps.
Outline1/8 How to [do task] in [number] steps, even if [common worry].
2/8 Step 1: [step]. [Short tip].
3/8 Step 2: [step]. [Short tip].
4/8 Step 3: [step]. [Short tip].
5/8 Step 4: [step]. [Short tip].
6/8 Step 5: [step]. [Short tip].
7/8 Common mistake to avoid: [mistake].
8/8 Save this for the next time you [do task].
Why it works. Numbered steps are easy to follow and easy to save. A clear promise in the hook tells people exactly what they will get.
Show your working setup and why each piece earns its place.
Outline1/7 The [number] tools I use to [do job] as a [role]. None of them are fancy.
2/7 For [task 1]: [type of tool]. Why: [reason].
3/7 For [task 2]: [type of tool]. Why: [reason].
4/7 For [task 3]: [type of tool]. Why: [reason].
5/7 For [task 4]: [type of tool]. Why: [reason].
6/7 What I stopped using: [tool type] because [reason].
7/7 The rule I follow: [rule for picking tools].
Why it works. People love seeing how others work, and a lean setup feels doable. The rule at the end gives readers something to take away even if they use different tools.
Tell the story of one client or project from problem to result.
Outline1/7 [Client type] came to me with [problem]. [Time] later, [result]. Here is what we did.
2/7 The situation: [context and stakes].
3/7 What they had tried: [past attempts].
4/7 What we found: [real cause].
5/7 What we changed: [the fix].
6/7 What happened: [result with details].
7/7 What you can take from this: [lesson]. [Soft call to action].
Why it works. A before and after story with a clear cause is the most convincing thing an expert can post. It shows your thinking, not just your claim.
09The build in public update
7 postsShare an honest progress update on something you are building.
Outline1/7 [Product] update, [time period]. [One honest headline about how it went].
2/7 What shipped: [features or changes].
3/7 The numbers: [simple fictional metrics].
4/7 What went well: [win].
5/7 What went badly: [problem].
6/7 What I am changing: [plan].
7/7 Next [period] goal: [goal]. I will report back.
Why it works. Honest updates build trust over time because readers see the bad months too. A clear goal at the end brings people back for the next one.
10The contrarian take
7 postsArgue against popular advice in your field, with reasons.
Outline1/7 Unpopular opinion: [common advice] is [wrong or overrated] for [who].
2/7 The usual advice: [advice as people say it].
3/7 Why it sounds right: [fair point].
4/7 Where it breaks: [problem].
5/7 What I have seen instead: [your experience].
6/7 What I do: [your approach].
7/7 When the usual advice does fit: [exception]. Where do you land?
Why it works. A clear stance gets people to stop and think. Being fair to the other side keeps it from feeling like a hot take for its own sake.
11The before and after
7 postsShow a clear change and what caused it.
Outline1/7 [Time] ago I [before state]. Now I [after state]. The change came from [number] things.
2/7 Before: [picture of the old way].
3/7 The moment I knew it had to change: [trigger].
4/7 Change 1: [change].
5/7 Change 2: [change].
6/7 Change 3: [change].
7/7 After: [picture of the new way]. [What you would tell your old self].
Why it works. Readers can picture both states, so the change feels real. Breaking it into small changes makes it feel possible for them too.
12The timeline story
7 postsTell how something unfolded over time, one milestone per post.
Outline1/7 The full story of [thing], from [start] to [now].
2/7 [Date 1]: [what happened].
3/7 [Date 2]: [what happened].
4/7 [Date 3]: [the low point].
5/7 [Date 4]: [the turn].
6/7 [Date 5]: [where things are now].
7/7 What I would tell anyone at [early stage]: [lesson].
Why it works. Stories with dates feel concrete and are easy to follow. A clear low point gives the thread tension and keeps people reading.
Give readers a list they can run before a common task.
Outline1/7 My [number] point checklist before I [task]. I run it every time.
2/7 1. [Check]. [Why].
3/7 2. [Check]. [Why].
4/7 3. [Check]. [Why].
5/7 4. [Check]. [Why].
6/7 5. [Check]. [Why].
7/7 Bookmark this for your next [task].
Why it works. Checklists are practical and get saved a lot. The small story in the hook explains why the list exists.
Answer the questions people ask you most, in one place.
Outline1/7 The [number] questions I get most about [topic], answered.
2/7 Q: [question]? A: [answer].
3/7 Q: [question]? A: [answer].
4/7 Q: [question]? A: [answer].
5/7 Q: [question]? A: [answer].
6/7 Q: [question]? A: [answer].
7/7 Got a question I missed? Ask below and I will answer it.
Why it works. An FAQ thread answers what people already want to know, so it earns replies. It also saves you time the next time someone asks.
Explain the key terms in your field in plain words.
Outline1/7 [Number] [topic] terms explained in plain English. No jargon.
2/7 [Term]: [plain meaning]. [Simple example].
3/7 [Term]: [plain meaning]. [Simple example].
4/7 [Term]: [plain meaning]. [Simple example].
5/7 [Term]: [plain meaning]. [Simple example].
6/7 [Term]: [plain meaning]. [Simple example].
7/7 Which term confused you the longest?
Why it works. Plain definitions help beginners and signal that you know the field well. Each post is a small, useful bite people can save.
16What I would do if I started over
7 postsShare the plan you would follow if you had to start from zero today.
Outline1/7 If I had to start my [business or career] from zero today, here is exactly what I would do.
2/7 Week 1: [first move].
3/7 Month 1: [next move].
4/7 What I would skip: [thing you did that was a waste].
5/7 What I would do much earlier: [thing you did late].
6/7 The one habit I would start on day one: [habit].
7/7 It would not be fast. But it would be [benefit].
Why it works. This format packs years of lessons into a clear plan. Readers who are just starting can follow it almost word for word.
17The resource roundup
7 postsShare the kinds of resources that helped you most, and why.
Outline1/7 The [number] things that taught me the most about [topic]. None of them cost much.
2/7 1. [Resource type]: [what you learned].
3/7 2. [Resource type]: [what you learned].
4/7 3. [Resource type]: [what you learned].
5/7 4. [Resource type]: [what you learned].
6/7 5. [Resource type]: [what you learned].
7/7 The best one was free: [which and why].
Why it works. Readers want shortcuts, and a curated list gives them one. Explaining what each resource taught you makes the list useful even without names.
18The framework explainer
7 postsTeach a simple model you use to make decisions.
Outline1/7 I use a simple [number] part framework to decide [decision]. Here is how it works.
2/7 Part 1: [name]. [What it means].
3/7 Part 2: [name]. [What it means].
4/7 Part 3: [name]. [What it means].
5/7 How I use it: [example].
6/7 Where it fails: [limit].
7/7 Try it on your next [decision]. Follow for more on [topic].
Why it works. A named framework is easy to remember and share. Showing where it fails makes it more trustworthy.
19The numbers recap
7 postsShare the real numbers behind a project, with what they mean.
Outline1/7 [Project] by the numbers after [time]. The most useful number is not the biggest one.
2/7 [Number]: [what it counts]. [What it means].
3/7 [Number]: [what it counts]. [What it means].
4/7 [Number]: [what it counts]. [What it means].
5/7 [Number]: [what it counts]. [What it means].
6/7 The number that matters most: [number and why].
7/7 What I am tracking next: [metric].
Why it works. Specific numbers inside a real story feel honest. Pointing to the one number that matters teaches readers what to watch.
Share what you learned from hiring, good and bad.
Outline1/7 I have hired [number] people. Here is what I wish I knew before the first one.
2/7 Lesson 1: [lesson]. [Story].
3/7 Lesson 2: [lesson]. [Story].
4/7 Lesson 3: [lesson]. [Story].
5/7 Lesson 4: [lesson]. [Story].
6/7 The question I now ask every candidate: [question].
7/7 Hiring is [short summary]. What is your best hiring lesson?
Why it works. Hiring stories are relatable for any founder or manager. Specific questions and tests give readers something to use this week.
Share what changing your prices taught you.
Outline1/7 I changed my prices [number] times in [time]. Here is what each change taught me.
2/7 Change 1: [from and to]. What happened: [result].
3/7 Change 2: [from and to]. What happened: [result].
4/7 Change 3: [from and to]. What happened: [result].
5/7 What surprised me: [surprise].
6/7 How I set prices now: [method].
7/7 If you are nervous about raising your price: [advice].
Why it works. Pricing is a topic most experts are nervous about, so real stories get attention. Clear before and after numbers make the lessons stick.
22Customer interview notes
7 postsShare patterns from talking to customers.
Outline1/7 I talked to [number] [customer type] this month. Here is what they told me.
2/7 Pattern 1: [what many said].
3/7 Pattern 2: [what many said].
4/7 Pattern 3: [what many said].
5/7 The quote I cannot stop thinking about: [quote].
6/7 What surprised me: [surprise].
7/7 What I am changing because of it: [change].
Why it works. Real customer patterns are rare and useful to anyone in the same market. A strong quote gives the thread a memorable center.
23The launch recap
8 postsShare how a launch went, what worked and what did not.
Outline1/8 I launched [product] [time] ago. Here is the honest recap.
2/8 The plan: [what you planned].
3/8 Launch day: [what happened].
4/8 What worked: [channel or tactic].
5/8 What flopped: [channel or tactic].
6/8 The numbers: [simple fictional numbers].
7/8 What I would do differently: [change].
8/8 What is next: [plan].
Why it works. Honest launch recaps are useful to anyone planning one. Including the flops shows you are sharing to teach, not to brag.
24Notes on an idea
7 postsShare notes on one idea or a book you read, and how you applied it.
Outline1/7 One idea from [a book I read or a talk I heard] changed how I [do something]. My notes:
2/7 The idea in one line: [idea].
3/7 Why it clicked for me: [context].
4/7 Note 1: [point].
5/7 Note 2: [point].
6/7 How I applied it: [example].
7/7 The result so far: [result]. Worth trying if you [situation].
Why it works. One idea explained well beats a long summary. Showing how you applied it turns reading notes into proof.
25The weekly notes
7 postsShare a short set of notes from your week of work.
Outline1/7 Notes from this week of [work]. [Number] things worth sharing.
2/7 1. [Observation].
3/7 2. [Observation].
4/7 3. [Observation].
5/7 4. [Observation].
6/7 One thing I got wrong: [mistake].
7/7 Next week I am [plan]. What was your week like?
Why it works. Weekly notes are easy to write and build a habit of posting. Small true details make readers feel like they are in the room.