Founder & Executive LinkedIn Thought Leadership Authority Post
Craft nuanced, high-credibility executive posts on LinkedIn that dismantle industry clichés without sounding arrogant.
Compatibility & Specs
Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedOct 3, 2026
Customizable Variables4 parameters
Main Prompt Template
156 words • 1153 characters
You are a Ghostwriter and Strategic Communications Counsel to Fortune 500 executives and top venture-backed founders. I need a compelling, high-credibility LinkedIn post based on a real operational lesson or counter-narrative.
Author Title & Industry Context:
[author_context]
The Core Contrarian Lesson or Unpopular Truth:
[core_lesson]
The Supporting Incident or Personal Experience:
[supporting_incident]
The Practical Takeaway for the Reader:
[practical_takeaway]
Draft a powerful LinkedIn post with the following craftsmanship:
1. The 2-Line Hook: Write 3 variations of the opening hook that appear before the '...see more' fold, maximizing click-through without clickbait.
2. The Tension Arc (The Story): 3-4 concise, rhythmically varied paragraphs that establish the conventional wisdom, reveal the moment that wisdom failed, and share the real numbers or impact.
3. The Framework / Takeaway: Bullet-pointed actionable principles that the reader can implement in their own company immediately.
4. Thoughtful Engagement Closer: A non-generic closing question that invites high-caliber practitioners to share their experiences in the comments.
Tip:Variables marked in purple brackets can be tailored below.
Customize Prompt
Fill in the variables below. Your customized prompt updates instantly in the browser — no AI API needed.
Parameters (4)* Indicates required field
[author_context]
Your formal background and domain authority
[core_lesson]
The unpopular truth or counter-intuitive insight
[supporting_incident]
The concrete situation that demonstrated this lesson
[practical_takeaway]
What the reader should do differently starting tomorrow
4 parameters active
Live Customized OutputLive Preview
248 wordsYou are a Ghostwriter and Strategic Communications Counsel to Fortune 500 executives and top venture-backed founders. I need a compelling, high-credibility LinkedIn post based on a real operational lesson or counter-narrative.
Author Title & Industry Context:
VP of Engineering at an enterprise infrastructure company who previously scaled engineering teams from 10 to 120 developers.
The Core Contrarian Lesson or Unpopular Truth:
Promoting your best individual coder to Engineering Manager is almost always a mistake that damages both team morale and code velocity.
The Supporting Incident or Personal Experience:
Three years ago, I promoted our 10x Staff Architect to Manager because he 'earned the title.' Within 6 months, he was burned out doing calendar scheduling, our junior devs felt micromanaged, and our core architecture stalled.
The Practical Takeaway for the Reader:
Create a parallel Staff/Principal IC career ladder that matches VP-level compensation and prestige without forcing great builders to become mediocre bureaucrats.
Draft a powerful LinkedIn post with the following craftsmanship:
1. The 2-Line Hook: Write 3 variations of the opening hook that appear before the '...see more' fold, maximizing click-through without clickbait.
2. The Tension Arc (The Story): 3-4 concise, rhythmically varied paragraphs that establish the conventional wisdom, reveal the moment that wisdom failed, and share the real numbers or impact.
3. The Framework / Takeaway: Bullet-pointed actionable principles that the reader can implement in their own company immediately.
4. Thoughtful Engagement Closer: A non-generic closing question that invites high-caliber practitioners to share their experiences in the comments.
How to Use This Prompt
Follow this 3-step workflow to extract high-signal responses from any compatible AI model.
01
1. Tailor the Parameters
Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.
02
2. Send to AI Model
Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.
03
3. Review and Iterate
Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.
Prompt Variables & Parameters
Reference breakdown of every dynamic variable embedded in this prompt template.
| Placeholder | Parameter Name | Type | Status | Description & Guidance |
|---|---|---|---|---|
| [author_context] | Author Title & Industry | text | Required | Your formal background and domain authorityDefault: VP of Engineering at an enterprise infrastructure company who previously scaled engineering teams from 10 to 120 developers. |
| [core_lesson] | The Contrarian Lesson | textarea | Required | The unpopular truth or counter-intuitive insightDefault: Promoting your best individual coder to Engineering Manager is almost always a mistake that damages both team morale and code velocity. |
| [supporting_incident] | Supporting Story / Experience | textarea | Required | The concrete situation that demonstrated this lessonDefault: Three years ago, I promoted our 10x Staff Architect to Manager because he 'earned the title.' Within 6 months, he was burned out doing calendar scheduling, our junior devs felt micromanaged, and our core architecture stalled. |
| [practical_takeaway] | Practical Takeaway | textarea | Required | What the reader should do differently starting tomorrowDefault: Create a parallel Staff/Principal IC career ladder that matches VP-level compensation and prestige without forcing great builders to become mediocre bureaucrats. |
Example Execution & Benchmark Output
Sample input arguments and the verified AI response demonstrating expected quality and formatting.
Sample VariablesInputs
[author_context]
VP of Engineering at an enterprise infrastructure company who previously scaled engineering teams from 10 to 120 developers.
[core_lesson]
Promoting your best individual coder to Engineering Manager is almost always a mistake that damages both team morale and code velocity.
[supporting_incident]
Three years ago, I promoted our 10x Staff Architect to Manager because he 'earned the title.' Within 6 months, he was burned out doing calendar scheduling, our junior devs felt micromanaged, and our core architecture stalled.
[practical_takeaway]
Create a parallel Staff/Principal IC career ladder that matches VP-level compensation and prestige without forcing great builders to become mediocre bureaucrats.
Expected AI ResponseVerified Result
### Hook Variations (Before the '...see more' fold)
- **Option 1 (Direct Contrast):** The fastest way to ruin a brilliant engineering culture is to promote your best coder to Manager.
- **Option 2 (Confessional):** Three years ago, I made the single worst promotion decision of my leadership career.
- **Option 3 (Provocative Question):** Why do we still punish great builders by turning them into mediocre calendar coordinators?
### The Selected Post
Three years ago, I made a promotion decision that nearly broke our core team.
Our Staff Architect was a legend. He could diagnose a distributed deadlock in 10 minutes and architected our payment engine from scratch. When the team grew, I did what conventional wisdom dictated: I made him Engineering Manager.
It was a disaster.
Within six months, he was drowning in 1-on-1s, Jira triage, and HR calibrations. He went from energized problem-solver to exhausted gatekeeper. Worse, our junior engineers felt micromanaged because every PR became a critique of his past work.
We fell into the classic tech trap: treating management as a reward for technical excellence, rather than what it actually is—a complete career change.
If you want to retain top individual contributors, two rules must be sacred:
1. **Build a Twin Ladder:** Your Staff, Principal, and Distinguished Engineers must have equal compensation, equity, and board-level influence as Directors and VPs.
2. **De-couple Status from Direct Reports:** An engineer who solves a $10M scaling bottleneck has just as much organizational leverage as someone managing 15 people.
Management is not a promotion. It is a support role for human systems.
How does your engineering organization handle senior IC growth without forcing people into management?
Best Use Cases
Scenarios and roles where this prompt produces maximum leverage.
Executives and founders building organic credibility and recruiting pipelines on LinkedIn
Practitioners translating hard-earned operational scars into high-engagement articles
Consultants establishing domain authority to attract inbound enterprise advisory clients
Tips for Best Results
Techniques to elevate response fidelity
- •Provide rich background context rather than one-sentence inputs to receive deep, non-generic responses.
- •Engage in multi-turn conversation: use the initial output as a baseline, then ask the AI to sharpen specific sections.
- •Prompt the model to highlight any hidden assumptions or missing trade-offs in its recommendations.
Common Mistakes to Avoid
Frequent failure modes and anti-patterns
- •Giving minimal context and expecting nuanced, expert-level strategic output.
- •Not validating factual references, citations, or statistical claims with verified primary sources.
- •Skipping the customization step and pasting raw bracketed template variables into the AI chat.
Part of Curated Collections
This prompt is sequenced as part of these goal-oriented workflows
Related AI Prompts
Complementary workflows in Social Media
Researchadvanced
Academic Literature Review & Counter-Evidence Auditor
Conduct rigorous research audits, uncover confirmation bias, and find conflicting studies.
claudeperplexitychatgpt
#research#academic#literature-review
Careeradvanced
Executive Promotion Business Case & Brag Sheet Architect
Construct an evidence-backed business case and quantifiable brag sheet to secure your next level promotion.
claudechatgptgemini
#promotion#career-growth#brag-sheet
Content Creationintermediate
30-Day Omnichannel Editorial Content Calendar Planner
Plan a month-long content schedule structured around core narrative pillars, audience personas, and publishing cadences.
claudechatgpt
#content-calendar#editorial-planning#content-strategy