feat(linkedin-thought-leadership): v1.0.0 — initial open-source import
Build LinkedIn thought leadership with algorithmic understanding, strategic consistency, and AI-assisted content creation. Updated for the January 2026 360Brew algorithm change. 16 agents, 25 commands, 6 skills, 9 hooks, 24 reference docs. Personal data sanitized: voice samples generalized to template, high-engagement posts cleared, region-specific references replaced with placeholders. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen
parent
7194a37129
commit
39f8b275a6
143 changed files with 32662 additions and 0 deletions
|
|
@ -0,0 +1,364 @@
|
|||
# Engagement Frameworks
|
||||
|
||||
Proven structures for maximizing LinkedIn engagement through hooks, storytelling, and calls-to-action.
|
||||
|
||||
## Hook Frameworks (First 110-140 Characters)
|
||||
|
||||
The hook determines whether people click "see more." It must work standalone on mobile.
|
||||
|
||||
### 10 High-Performing Hook Types
|
||||
|
||||
**1. The Surprising Stat**
|
||||
Pattern: Lead with a number that challenges expectations
|
||||
- "84% of organizations say their data infrastructure can't support AI."
|
||||
- "We spent €2M on infrastructure. It bought us 6 months of delay."
|
||||
- "3 out of 4 AI projects in my organization failed this year."
|
||||
|
||||
**2. The Bold Statement**
|
||||
Pattern: Make a strong, clear claim
|
||||
- "AI readiness is a leadership problem, not a technology problem."
|
||||
- "Your data strategy is probably backwards."
|
||||
- "We need to stop calling them 'AI projects.'"
|
||||
|
||||
**3. The Provocative Question**
|
||||
Pattern: Ask something that makes people stop
|
||||
- "What if the AI revolution requires doing less, not more?"
|
||||
- "Why are we implementing AI before fixing our data?"
|
||||
- "Is your organization brave enough to wait?"
|
||||
|
||||
**4. The Contrarian Opening**
|
||||
Pattern: Challenge what "everyone" believes
|
||||
- "Everyone's rushing to implement AI. That's the mistake."
|
||||
- "Popular opinion: We need more data. Reality: We need better questions."
|
||||
- "The advice you're getting about AI transformation? It's 3 years too late."
|
||||
|
||||
**5. The Personal Confession**
|
||||
Pattern: Admit something unexpected
|
||||
- "I was wrong about AI readiness. Here's what changed my mind:"
|
||||
- "Our €2M AI platform failed. Here's why:"
|
||||
- "I used to think data quality was our problem. I was looking at the wrong problem."
|
||||
|
||||
**6. The Pattern Observation**
|
||||
Pattern: Point out something others might miss
|
||||
- "I've noticed a pattern: Every successful AI project shares this one thing."
|
||||
- "There's a gap between what executives want and what actually works."
|
||||
- "The organizations succeeding with AI aren't the ones you'd expect."
|
||||
|
||||
**7. The Time Frame**
|
||||
Pattern: Create urgency with specific timing
|
||||
- "In 18-36 months, most AI initiatives will fail. Here's why:"
|
||||
- "We have 6 months to fix this. Here's the plan:"
|
||||
- "This week, I learned something that changes everything about AI strategy."
|
||||
|
||||
**8. The Lesson Learned**
|
||||
Pattern: Promise a valuable takeaway
|
||||
- "Three years of AI projects taught me this uncomfortable truth:"
|
||||
- "We failed at AI implementation. The lesson was worth the cost:"
|
||||
- "After 12 failed experiments, we finally figured it out:"
|
||||
|
||||
**9. The Scenario Opening**
|
||||
Pattern: Set a scene that resonates
|
||||
- "You're in a meeting. Everyone's excited about AI. Nobody mentions the data."
|
||||
- "It's 2027. Your AI initiative just failed. Here's what you missed:"
|
||||
- "Picture this: You've spent millions on infrastructure, and nothing works."
|
||||
|
||||
**10. The Direct Address**
|
||||
Pattern: Speak directly to a specific audience
|
||||
- "If you're an AI leader in the public sector, we need to talk."
|
||||
- "To everyone implementing AI right now: Pause and read this."
|
||||
- "Fellow AI advisors: Are we being honest about timelines?"
|
||||
|
||||
### Hook Writing Rules
|
||||
|
||||
1. **Frontload value:** Put the most interesting part first
|
||||
2. **Avoid weak openings:** No "Happy Monday!" or "I hope you're well"
|
||||
3. **Be specific:** "We spent €2M" beats "We spent a lot"
|
||||
4. **Create curiosity:** Make people want to know more
|
||||
5. **Test on mobile:** Does it work in 110 characters?
|
||||
|
||||
### The Hook Psychology Research
|
||||
|
||||
Analysis of 9,000+ viral posts reveals the science behind what works:
|
||||
|
||||
**Pattern Interrupts:**
|
||||
- Viral posts contain **2.7x more pattern interrupts** in first two lines
|
||||
- Pattern interrupts create information gaps that psychologically demand closure
|
||||
- Trigger dopamine release and heightened attention
|
||||
- Brain's prediction error system activates when expectations disrupted
|
||||
|
||||
**Optimal Hook Structure:**
|
||||
- First line: ~49 characters (tested optimal length)
|
||||
- Full opening: Utilize all 140 characters visible on mobile
|
||||
- Keep sentences under 15 words
|
||||
- Use three short lines with spaces between them
|
||||
- Front-load value in first two lines
|
||||
- Skip one line after hook before continuing
|
||||
|
||||
**Justin Welsh's Three-Step Viral Formula:**
|
||||
|
||||
1. **Create scroll-stopper** by attacking relatable enemy
|
||||
Example: "The 9 to 5 is getting pummeled."
|
||||
|
||||
2. **Flip the script** with positive force
|
||||
Example: "The great resignation is growing faster than ever."
|
||||
|
||||
3. **Add gasoline and teaser**
|
||||
Example: "And I love it. Why?"
|
||||
|
||||
This structure creates positive response by opposing forces and compels the "see more" click through strategic curiosity gaps.
|
||||
|
||||
**The Information Gap Technique:**
|
||||
- Create question in reader's mind
|
||||
- Make answer visible only by reading
|
||||
- Hook promises resolution
|
||||
- Satisfaction drives sharing
|
||||
|
||||
**Psychological Mechanisms:**
|
||||
- **Curiosity Gap:** Gap between what they know and want to know
|
||||
- **Cognitive Closure:** Brain demands resolution of incomplete narratives
|
||||
- **Prediction Error:** Unexpected statements force attention
|
||||
- **Emotional Resonance:** Personal relevance creates immediate connection
|
||||
|
||||
**Example Application:**
|
||||
|
||||
❌ Weak: "I learned something about AI this week"
|
||||
- No pattern interrupt
|
||||
- Vague promise
|
||||
- No information gap
|
||||
|
||||
✅ Strong: "84% of organizations can't support AI. Here's the part nobody talks about:"
|
||||
- Surprising statistic (pattern interrupt)
|
||||
- Creates information gap (what's the hidden part?)
|
||||
- Demands cognitive closure
|
||||
- Promises insider knowledge
|
||||
|
||||
## Story Structure Frameworks
|
||||
|
||||
### The Standard Thought Leadership Structure (1,200-1,800 chars)
|
||||
|
||||
**Hook (110-140 chars)**
|
||||
→ Grab attention, create curiosity
|
||||
|
||||
**Context (200-300 chars)**
|
||||
→ Set up the situation/problem/observation
|
||||
→ Why should they care?
|
||||
→ What's at stake?
|
||||
|
||||
**Insight/Argument (400-800 chars)**
|
||||
→ Your main point
|
||||
→ Supporting evidence or logic
|
||||
→ This is the "meat" of the post
|
||||
|
||||
**Implication (200-300 chars)**
|
||||
→ What does this mean?
|
||||
→ Why does it matter?
|
||||
→ Connect to bigger picture
|
||||
|
||||
**Call-to-Action (50-100 chars)**
|
||||
→ What should the reader do/think?
|
||||
→ Engagement prompt
|
||||
|
||||
### The Narrative Arc (For Story-Based Posts)
|
||||
|
||||
**Setup (200 chars)**
|
||||
→ Scene setting
|
||||
→ "Let me tell you about..."
|
||||
|
||||
**Challenge (300 chars)**
|
||||
→ The problem/obstacle
|
||||
→ What went wrong or what was at stake
|
||||
|
||||
**Turning Point (300 chars)**
|
||||
→ The realization/decision/change
|
||||
→ "Then I realized..."
|
||||
|
||||
**Resolution (300 chars)**
|
||||
→ What happened
|
||||
→ The outcome
|
||||
|
||||
**Lesson (200-300 chars)**
|
||||
→ What this teaches us
|
||||
→ The broader application
|
||||
|
||||
**CTA (50-100 chars)**
|
||||
→ Engagement prompt
|
||||
|
||||
### The Data-Driven Post (For Research/Statistics)
|
||||
|
||||
**Stat Hook (100 chars)**
|
||||
→ Lead with the surprising number
|
||||
|
||||
**Context (200 chars)**
|
||||
→ Where this data comes from
|
||||
→ Why it matters
|
||||
|
||||
**Breakdown (500-700 chars)**
|
||||
→ What the data actually means
|
||||
→ Deeper analysis
|
||||
→ Connect to reader's reality
|
||||
|
||||
**Action (200-300 chars)**
|
||||
→ What to do with this information
|
||||
→ Practical takeaways
|
||||
|
||||
**CTA (50-100 chars)**
|
||||
→ Engagement prompt
|
||||
|
||||
### The Contrarian Post (For Challenging Norms)
|
||||
|
||||
**Bold Claim Hook (110 chars)**
|
||||
→ State the contrarian position clearly
|
||||
|
||||
**Common Wisdom (200 chars)**
|
||||
→ Acknowledge what "everyone" thinks
|
||||
→ Show you understand the conventional view
|
||||
|
||||
**The Challenge (400-600 chars)**
|
||||
→ Why the common wisdom fails
|
||||
→ Evidence or logic for your position
|
||||
→ Personal experience or data
|
||||
|
||||
**Alternative View (300-400 chars)**
|
||||
→ What we should do instead
|
||||
→ The better approach
|
||||
|
||||
**CTA (50-100 chars)**
|
||||
→ Invite discussion/disagreement
|
||||
|
||||
## Call-to-Action Frameworks
|
||||
|
||||
CTAs should encourage engagement while feeling natural, not forced.
|
||||
|
||||
### High-Engagement CTAs
|
||||
|
||||
**Genuine Questions:**
|
||||
- "What's your experience with this?"
|
||||
- "Am I missing something here?"
|
||||
- "Is this just my organization, or are others seeing this?"
|
||||
|
||||
**Invitations to Share:**
|
||||
- "Tag someone who needs to see this."
|
||||
- "Share this if you've experienced this."
|
||||
- "Who else is dealing with this challenge?"
|
||||
|
||||
**Specific Asks:**
|
||||
- "What would you add to this list?"
|
||||
- "Which of these resonates most with you?"
|
||||
- "What's worked for you?"
|
||||
|
||||
**Challenge to Status Quo:**
|
||||
- "Change my mind."
|
||||
- "Prove me wrong."
|
||||
- "What am I not considering?"
|
||||
|
||||
**Practical Extension:**
|
||||
- "What questions should I answer in a follow-up?"
|
||||
- "Want me to write more about [specific aspect]?"
|
||||
- "Should I share the framework we use?"
|
||||
|
||||
### CTA Rules
|
||||
|
||||
1. **Make it specific:** "What do you think?" is weak. "Which strategy has worked for your team?" is strong.
|
||||
2. **Keep it genuine:** Don't ask questions you don't care about
|
||||
3. **Create optionality:** Give people multiple ways to engage (comment, share, connect)
|
||||
4. **Match the tone:** Serious post = serious CTA. Personal post = personal CTA.
|
||||
|
||||
## Paragraph Structure Best Practices
|
||||
|
||||
### Visual Readability
|
||||
|
||||
**Use short paragraphs:**
|
||||
- 1-3 sentences per paragraph
|
||||
- Lots of white space
|
||||
- Easy to scan on mobile
|
||||
|
||||
**Strategic formatting:**
|
||||
- Break before key points
|
||||
- Use line breaks for emphasis
|
||||
- Never write walls of text
|
||||
|
||||
**Example of good structure:**
|
||||
```
|
||||
[Hook paragraph - 1 sentence]
|
||||
|
||||
[Context paragraph - 2-3 sentences]
|
||||
|
||||
[Key insight paragraph - 1 sentence]
|
||||
|
||||
[Supporting detail - 2-3 sentences]
|
||||
|
||||
[Implication paragraph - 2 sentences]
|
||||
|
||||
[CTA - 1 sentence]
|
||||
```
|
||||
|
||||
### Sentence Length Variation
|
||||
|
||||
Mix short and long sentences:
|
||||
- Short sentences: impact and emphasis
|
||||
- Medium sentences: explanation and flow
|
||||
- Long sentences: detail and nuance
|
||||
|
||||
**Example:**
|
||||
"We failed. [SHORT - impact]
|
||||
Our €2M data platform took 18 months to build and six months to realize it solved the wrong problem. [LONG - detail]
|
||||
The lesson was expensive but clear. [MEDIUM - transition]"
|
||||
|
||||
## Tone Guidelines
|
||||
|
||||
### What Works on LinkedIn
|
||||
|
||||
**Authoritative but accessible:**
|
||||
- Share expertise without jargon
|
||||
- Explain, don't lecture
|
||||
- Confidence without arrogance
|
||||
|
||||
**Authentic over polished:**
|
||||
- Real stories beat corporate speak
|
||||
- Admit mistakes and uncertainties
|
||||
- Sound human, not like a press release
|
||||
|
||||
**Helpful over promotional:**
|
||||
- Lead with value, not credentials
|
||||
- Make readers smarter
|
||||
- Give away insights freely
|
||||
|
||||
### What Doesn't Work
|
||||
|
||||
- Humble brags disguised as insights
|
||||
- Excessive self-promotion
|
||||
- Corporate jargon without translation
|
||||
- Vague platitudes
|
||||
- Overly formal or academic tone
|
||||
|
||||
## Engagement Timing Best Practices
|
||||
|
||||
### Engagement Quality Hierarchy
|
||||
|
||||
Not all engagement is equal. LinkedIn's algorithm weights different interactions based on their signal value:
|
||||
|
||||
1. **Saves** (Highest signal - indicates content worth returning to)
|
||||
2. **Shares** (High signal - amplification and endorsement)
|
||||
3. **Comments 15+ words** (2.5x more valuable than short comments)
|
||||
4. **Expert comments** (7-9x multiplier - comments from verified experts in your field)
|
||||
5. **Comments <15 words** (Moderate signal)
|
||||
6. **Reactions** (Lowest signal - minimal effort)
|
||||
|
||||
**Key insight:** One save or expert comment is worth significantly more than dozens of reactions. Focus on creating content that people want to save and share, and cultivate engagement from recognized experts in your domain.
|
||||
|
||||
### First Hour Critical
|
||||
- Aim for 15+ engagements in first 60 minutes
|
||||
- Respond quickly to early comments (30-minute response = 64% more follow-up comments)
|
||||
- Seed engagement by notifying key connections
|
||||
|
||||
### Comment Strategy
|
||||
- Reply to every comment in first 2-3 hours
|
||||
- Add value in replies, don't just say "thanks"
|
||||
- Tag relevant people in your responses
|
||||
- Use replies to extend the conversation
|
||||
|
||||
### Post Timing
|
||||
- **Optimal window: 8-9 AM Tuesday-Wednesday** (peak engagement period)
|
||||
- Tuesday-Thursday typically perform best
|
||||
- Early morning (6-8 AM) or lunchtime (12-1 PM) in target timezone
|
||||
- Consistency matters more than "perfect" timing
|
||||
Loading…
Add table
Add a link
Reference in a new issue