Marcus Bell·
A 10-post LinkedIn thought-leadership series with hooks and engagement questions, scheduled out
Create a 10-post LinkedIn thought leadership series that builds authority, sparks debate, and drives engagement.
LinkedIn Thought Leadership Post Series
You are a LinkedIn ghostwriter for C-suite executives and industry leaders. Create a 10-post thought leadership series for {{author_name}}, a {{job_title}} at {{company_name}} in the {{industry}} industry. The series should establish authority on the topic of {{topic}}. For EACH post: (1) Write a compelling hook (first line), (2) Write the full post body (150-300 words) using storytelling, frameworks, or contrarian takes, (3) Include a pattern interrupt or insight that sparks comments, (4) End with an engagement-driving question or CTA, (5) Suggest a visual/chart/image to accompany the post, (6) Recommend 3 hashtags. The writing voice should be {{voice_style}} (e.g., authoritative yet approachable, bold and provocative, wise and mentoring). Space the posts across a 3-week publishing schedule. Include a mix of: personal stories, industry predictions, contrarian opinions, lessons learned, frameworks, and calls for community input.
Ergebnisse
# 10-Post LinkedIn Series: David Okafor, VP Engineering at Cloudwall, on engineering culture
**Voice:** authoritative yet approachable. **Schedule:** Mon/Wed/Fri across 3 weeks.
## Week 1
**Post 1 (Mon) — Personal story.** *Hook:* "I shipped a feature that took down production for 40 minutes. My CTO's response taught me everything about engineering culture." Body: the blameless-postmortem moment that reframed failure. *Pattern interrupt:* the CTO thanked him. *CTA:* "What's a mistake that made you better?" *Visual:* a redacted postmortem doc. *#engineeringleadership #devculture #blameless*
**Post 2 (Wed) — Contrarian.** *Hook:* "Stop measuring developers by lines of code or velocity." Argues for outcome metrics; ends with "What's the worst metric you've been measured on?"
**Post 3 (Fri) — Framework.** *Hook:* "The 3-question test before any architecture decision." Reversible? Blast radius? Who maintains it? Carousel-ready.
## Week 2
**Post 4 (Mon) — Lesson learned.** *Hook:* "We hired 12 engineers in 6 months. 4 quit. Here's what we got wrong." Onboarding and expectations honesty.
**Post 5 (Wed) — Industry prediction.** *Hook:* "By 2028, the 'full-stack engineer' title will mean something completely different." AI-assisted dev shift; chart suggested.
**Post 6 (Fri) — Community input.** *Hook:* "I'm rewriting our on-call policy. What actually made on-call humane on your team?" Genuine ask.
## Week 3
**Post 7 (Mon) — Personal story.** *Hook:* "The best engineer I ever hired bombed the coding interview." Rethinking hiring signals.
**Post 8 (Wed) — Contrarian.** *Hook:* "Your 'rockstar' engineer might be your biggest liability." Bus-factor + knowledge hoarding.
**Post 9 (Fri) — Framework.** *Hook:* "How we cut meetings 40% without losing alignment." The async-first playbook.
**Post 10 (Mon) — Lessons + vision.** *Hook:* "5 things I wish I'd known before becoming a VP of Engineering." Wrap-up, forward-looking, strong "follow for more."
*Each post: 150–300 words, one quotable line, an engagement question, suggested visual, 3 hashtags.*
Modell: Claude Sonnet 4
14 Likes3 SavesScore: 6
1 Kommentar
Hannah Meier·
That's a clean PAS framework. Sending to my whole team.