LinkedIn Thought Leadership Post Writer

Write engaging LinkedIn posts that establish thought leadership, drive meaningful engagement, and build your professional brand with proven content frameworks.

Prompt Template

You are a LinkedIn content strategist who has helped executives and founders build audiences of 50K+ followers. Write a high-engagement LinkedIn post based on the following inputs.

**Topic/insight:** [e.g., why most product roadmaps fail, a lesson from a difficult management decision, the hidden cost of technical debt]
**Author role:** [e.g., VP of Product at a B2B SaaS company, 15 years experience]
**Target audience:** [e.g., product managers, startup founders, engineering leaders]
**Content framework:** [choose one: Contrarian Take, Personal Story + Lesson, Framework/Listicle, Before/After Transformation, Data-Backed Insight]
**Desired CTA:** [e.g., drive comments, promote a newsletter, invite DMs]
**Tone:** [e.g., direct and slightly provocative, warm and reflective, data-driven]

Write the post following these rules:
1. **Hook** — first line must stop the scroll. Max 12 words.
2. **Line breaks** — single-sentence paragraphs for readability
3. **Story/substance** — core insight with specific details (numbers, names, timeframes)
4. **Formatting** — line breaks generously, occasional bold, numbered lists for frameworks
5. **Length** — 150-250 words
6. **CTA** — end with a question that drives comments
7. **No hashtags in body** — add 3-5 as a separate comment
8. **Avoid** — corporate jargon, humble brags, engagement bait

Also provide:
- 2 alternative hooks
- Suggested best posting time
- A follow-up comment to post immediately after publishing

Example Output

LinkedIn Post: Why Roadmaps Fail

I deleted our entire product roadmap last Tuesday.

Our board was not happy.

But here is what 2 years of data showed us:

87% of features we shipped on schedule were used by less than 5% of customers.

The features that actually moved revenue? Almost all came from unplanned discoveries — customer conversations, support tickets, sales call patterns.

We were optimizing for predictability.

We should have been optimizing for learning.

So we replaced the roadmap with 3 things:

1. A top 10 customer problems list (updated weekly)

2. 6-week build cycles with flexible scope

3. A kill metric for every feature (if it doesn't hit X in 30 days, we sunset it)

Result after 6 months:

- Feature adoption up 340%

- Engineering morale at an all-time high

- Revenue growth accelerated from 15% to 28% QoQ

The roadmap was not the strategy.

It was the excuse to avoid hard prioritization calls.

What is the most overrated planning artifact in your org?


Alternative hooks:

1. Our best feature last year was not on any roadmap.

2. Roadmaps are comfort blankets for leadership teams.

**Best posting time:** Tuesday or Wednesday, 7:30-8:30 AM in your audience's primary timezone

**Follow-up comment:** For context — we are a 45-person B2B SaaS company. This approach will not work for everyone. But if you are a startup shipping features nobody uses, it might be worth questioning the system.

Tips for Best Results

  • 💡Your first line is 80% of the battle — spend more time on the hook than the rest of the post
  • 💡Specific numbers and timeframes make posts credible — revenue grew 28% beats revenue grew significantly
  • 💡Post a thoughtful first comment immediately — it boosts algorithmic reach and sets conversation tone
  • 💡The best LinkedIn posts teach one thing clearly, not five things superficially