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,283 @@
|
|||
# Carousel Templates
|
||||
|
||||
Slide-by-slide blueprints for LinkedIn carousels (PDF document posts). Carousels have the highest engagement rate of all LinkedIn formats (6.6%) because they maximize dwell time and encourage swipe completion.
|
||||
|
||||
## Universal Design Specs
|
||||
|
||||
- **Slide dimensions:** 1080 x 1350 px (4:5 portrait, recommended)
|
||||
- **Font:** Sans-serif, minimum 24pt body, 36pt+ headlines
|
||||
- **Colors:** Max 3 per carousel (background, text, accent)
|
||||
- **Text per slide:** 5-7 lines maximum
|
||||
- **Optimal length:** 8-10 slides (including cover and CTA)
|
||||
- **Export format:** PDF
|
||||
- **Caption length:** 300-500 characters with hook and context
|
||||
|
||||
---
|
||||
|
||||
## Template 1: How-To Guide
|
||||
|
||||
**Best for:** Teaching a process, explaining a method, step-by-step instructions
|
||||
**Structure:** 8-10 slides
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | Bold question or promise: "How to [achieve X] in [timeframe]" |
|
||||
| 2 | Problem | "Most people [common mistake]. Here's what actually works." |
|
||||
| 3 | Step 1 | **Step name** + 2-3 lines of explanation |
|
||||
| 4 | Step 2 | **Step name** + 2-3 lines of explanation |
|
||||
| 5 | Step 3 | **Step name** + 2-3 lines of explanation |
|
||||
| 6 | Step 4 | **Step name** + 2-3 lines of explanation |
|
||||
| 7 | Step 5 | **Step name** + 2-3 lines of explanation |
|
||||
| 8 | Common mistakes | "3 mistakes to avoid: [quick list]" |
|
||||
| 9 | Summary | Recap all steps in a numbered list |
|
||||
| 10 | CTA | "Save this for later. Follow for more [topic]." |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
How to [specific outcome]
|
||||
(without [common pain point])
|
||||
|
||||
[Your name] | [Your title]
|
||||
```
|
||||
|
||||
**Step slide formula:**
|
||||
```
|
||||
Step [N]: [Action verb] + [Object]
|
||||
|
||||
[2-3 sentences explaining the step]
|
||||
|
||||
Pro tip: [One practical detail]
|
||||
```
|
||||
|
||||
**Caption template:**
|
||||
```
|
||||
Most [audience] struggle with [problem].
|
||||
|
||||
I've been doing [process] for [timeframe], and here's the method that consistently works.
|
||||
|
||||
Swipe through for the full breakdown.
|
||||
|
||||
Save this if you want to come back to it later.
|
||||
|
||||
#[topic] #[niche] #[format]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 2: Listicle / Top N
|
||||
|
||||
**Best for:** Curated lists, tool recommendations, lessons learned, tips
|
||||
**Structure:** 8-12 slides (1 item per slide)
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | "[N] [things] every [audience] should know about [topic]" |
|
||||
| 2 | Item 1 | **Name/Title** + Why it matters (2-3 lines) |
|
||||
| 3 | Item 2 | **Name/Title** + Why it matters |
|
||||
| 4 | Item 3 | **Name/Title** + Why it matters |
|
||||
| 5 | Item 4 | **Name/Title** + Why it matters |
|
||||
| 6 | Item 5 | **Name/Title** + Why it matters |
|
||||
| 7 | Item 6 | **Name/Title** + Why it matters |
|
||||
| 8 | Item 7 | **Name/Title** + Why it matters |
|
||||
| 9 | Bonus | "One more that most people miss: [unexpected item]" |
|
||||
| 10 | CTA | "Which one was new to you? Tell me in the comments." |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
[N] [things] that changed how I
|
||||
[outcome]
|
||||
|
||||
(#[N] surprised me the most)
|
||||
```
|
||||
|
||||
**Item slide formula:**
|
||||
```
|
||||
#[N]: [Item name]
|
||||
|
||||
[Why it matters in 2-3 lines]
|
||||
|
||||
[Optional: One specific example or data point]
|
||||
```
|
||||
|
||||
**Caption template:**
|
||||
```
|
||||
I spent [timeframe] learning about [topic].
|
||||
|
||||
Here are [N] things I wish someone told me from the start.
|
||||
|
||||
#[N] is the one most people get wrong.
|
||||
|
||||
Which one resonates most? Drop a number in the comments.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 3: Story / Before-After
|
||||
|
||||
**Best for:** Personal narratives, transformation stories, lessons from failure
|
||||
**Structure:** 8-10 slides
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | "How [situation] changed everything I knew about [topic]" |
|
||||
| 2 | Setting | "[Timeframe] ago, I was [situation]." |
|
||||
| 3 | Problem | "The problem: [specific challenge in 2-3 lines]" |
|
||||
| 4 | Turning point | "Then [event/realization] happened." |
|
||||
| 5 | What changed | "I started [new approach]. Here's what shifted:" |
|
||||
| 6 | Result 1 | **Before:** [old state] → **After:** [new state] |
|
||||
| 7 | Result 2 | **Before:** [old state] → **After:** [new state] |
|
||||
| 8 | Result 3 | **Before:** [old state] → **After:** [new state] |
|
||||
| 9 | Lesson | "The real lesson: [insight in 2-3 lines]" |
|
||||
| 10 | CTA | "Has this happened to you? I'd love to hear your story." |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
[Time period] ago, I [starting state].
|
||||
|
||||
Today, [current state].
|
||||
|
||||
Here's what changed.
|
||||
```
|
||||
|
||||
**Before/After slide formula:**
|
||||
```
|
||||
BEFORE:
|
||||
[Specific old behavior or result]
|
||||
|
||||
AFTER:
|
||||
[Specific new behavior or result]
|
||||
|
||||
The difference: [one-line insight]
|
||||
```
|
||||
|
||||
**Caption template:**
|
||||
```
|
||||
[Timeframe] ago, I made a mistake that [consequence].
|
||||
|
||||
Looking back, it was the best thing that could have happened.
|
||||
|
||||
Swipe through for the full story and the lesson I learned.
|
||||
|
||||
What's a mistake that turned into your biggest learning?
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 4: Comparison / vs.
|
||||
|
||||
**Best for:** Tool comparisons, approach differences, myth-busting, framework contrasts
|
||||
**Structure:** 8-10 slides
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | "[Option A] vs [Option B]: Which one actually works?" |
|
||||
| 2 | Context | "Everyone argues about [topic]. Here's what the data says." |
|
||||
| 3 | Dimension 1 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 4 | Dimension 2 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 5 | Dimension 3 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 6 | Dimension 4 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 7 | Dimension 5 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 8 | Summary table | Side-by-side with checkmarks/scores |
|
||||
| 9 | Verdict | "My recommendation: [nuanced answer based on context]" |
|
||||
| 10 | CTA | "Which one do you use? Agree or disagree with my verdict?" |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
[Option A] vs. [Option B]
|
||||
|
||||
I tested both.
|
||||
Here's what I found.
|
||||
```
|
||||
|
||||
**Comparison slide formula:**
|
||||
```
|
||||
[Criteria name]
|
||||
|
||||
[Option A]: [Rating or description]
|
||||
[Option B]: [Rating or description]
|
||||
|
||||
Winner: [A or B] (because [one-line reason])
|
||||
```
|
||||
|
||||
**Caption template:**
|
||||
```
|
||||
"Should I use [A] or [B]?"
|
||||
|
||||
I get asked this [frequency]. So I compared them across [N] dimensions.
|
||||
|
||||
The answer isn't what you'd expect.
|
||||
|
||||
Swipe through for the breakdown. My verdict is on slide [N].
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 5: Framework / Mental Model
|
||||
|
||||
**Best for:** Original frameworks, decision matrices, thinking models
|
||||
**Structure:** 8-10 slides
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | "The [Name] Framework: How to [outcome]" |
|
||||
| 2 | Problem | "Why most [audience] fail at [topic]" |
|
||||
| 3 | Overview | Visual diagram or named components of the framework |
|
||||
| 4 | Component 1 | **Name** + What it means + How to apply |
|
||||
| 5 | Component 2 | **Name** + What it means + How to apply |
|
||||
| 6 | Component 3 | **Name** + What it means + How to apply |
|
||||
| 7 | Component 4 | **Name** + What it means + How to apply |
|
||||
| 8 | Example | "Here's what it looks like in practice: [specific scenario]" |
|
||||
| 9 | Quick-start | "Start here: [simplest first step]" |
|
||||
| 10 | CTA | "Save this framework. Tag someone who needs it." |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
The [Name] Framework
|
||||
|
||||
[One-line promise of what it enables]
|
||||
|
||||
[Optional: diagram or visual representation]
|
||||
```
|
||||
|
||||
**Component slide formula:**
|
||||
```
|
||||
[Component Name]
|
||||
|
||||
What: [Definition in 1 line]
|
||||
Why: [Why it matters in 1 line]
|
||||
How: [Actionable step in 1-2 lines]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Caption Best Practices
|
||||
|
||||
Carousels need strong captions because the caption appears alongside the cover slide. A weak caption means no one swipes.
|
||||
|
||||
**Caption structure:**
|
||||
1. **Hook** (first line): Question, bold claim, or surprising stat
|
||||
2. **Context** (1-2 lines): Why this matters to your audience
|
||||
3. **Swipe prompt**: "Swipe through for..." or "Slide [N] is the one most miss"
|
||||
4. **Engagement CTA**: Question that invites comments
|
||||
5. **Hashtags**: 3-4 maximum, at the end
|
||||
|
||||
**Do:**
|
||||
- Reference a specific slide to create curiosity
|
||||
- Ask which point resonated most
|
||||
- Tell them to save it for later
|
||||
|
||||
**Don't:**
|
||||
- Write a long caption that says everything the slides say
|
||||
- Use "link in comments" (carousel IS the content)
|
||||
- Add more than 4 hashtags
|
||||
|
||||
## Carousel Quality Checklist
|
||||
|
||||
- [ ] Cover slide has a clear promise or question
|
||||
- [ ] Each slide has one point (not multiple ideas)
|
||||
- [ ] Text is readable on mobile without zooming (24pt+ body)
|
||||
- [ ] 8-10 slides total (not 4, not 20)
|
||||
- [ ] Last slide has a clear CTA
|
||||
- [ ] Caption hooks attention and prompts swipe
|
||||
- [ ] Consistent font, colors, and layout across all slides
|
||||
- [ ] Exported as PDF, under 100 MB
|
||||
|
|
@ -0,0 +1,330 @@
|
|||
# LinkedIn Article Template
|
||||
|
||||
Use this template when creating LinkedIn Articles (long-form content, 1,500-2,500 words).
|
||||
|
||||
## Article Metadata
|
||||
|
||||
```yaml
|
||||
title: "[60-80 characters, keyword-rich]"
|
||||
target_length: 1500-2500 words
|
||||
reading_time: 8-12 minutes
|
||||
primary_keyword: "[main search term]"
|
||||
secondary_keywords: ["keyword2", "keyword3"]
|
||||
target_audience: "[specific reader profile]"
|
||||
article_goal: "[what should reader do/feel/know after reading]"
|
||||
```
|
||||
|
||||
## Article Structure
|
||||
|
||||
### Title (60-80 characters)
|
||||
|
||||
**Format options:**
|
||||
- How to [achieve outcome] (Without [common obstacle])
|
||||
- The [Number] [Things] That [Outcome]
|
||||
- Why [Common Belief] Is Wrong (And What to Do Instead)
|
||||
- What [Time Period] Taught Me About [Topic]
|
||||
- [Topic]: The Complete Guide for [Audience]
|
||||
|
||||
**Your title:**
|
||||
```
|
||||
[WRITE TITLE HERE]
|
||||
```
|
||||
|
||||
**Checklist:**
|
||||
- [ ] Contains primary keyword
|
||||
- [ ] Promises clear value
|
||||
- [ ] Under 80 characters
|
||||
- [ ] Not clickbait
|
||||
|
||||
---
|
||||
|
||||
### Opening Hook (First 2-3 paragraphs, 150-250 words)
|
||||
|
||||
**Purpose:** Grab attention, establish why this matters NOW, preview value
|
||||
|
||||
**Template:**
|
||||
```
|
||||
[Opening hook - surprising stat, bold claim, or compelling question]
|
||||
|
||||
[Why this matters to the reader - what problem does it solve?]
|
||||
|
||||
[What the reader will learn/gain from this article]
|
||||
|
||||
[Brief credibility statement - why you can speak on this]
|
||||
```
|
||||
|
||||
**Your opening:**
|
||||
```
|
||||
[WRITE OPENING HERE]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Context Section (200-400 words)
|
||||
|
||||
**Purpose:** Provide background needed to understand the main content
|
||||
|
||||
**Template:**
|
||||
```
|
||||
## The Background You Need
|
||||
|
||||
[Brief history or context of the topic]
|
||||
|
||||
[Current state of affairs]
|
||||
|
||||
[Why now is the right time to address this]
|
||||
|
||||
[Any key definitions or concepts needed]
|
||||
```
|
||||
|
||||
**Your context section:**
|
||||
```
|
||||
[WRITE CONTEXT HERE]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Main Content (1,000-1,800 words)
|
||||
|
||||
**Purpose:** Deliver the core value - insights, framework, how-to
|
||||
|
||||
**Structure options:**
|
||||
|
||||
**Option A: Numbered sections**
|
||||
```
|
||||
## 1. [First Main Point]
|
||||
|
||||
[Explanation of point]
|
||||
|
||||
[Example or evidence]
|
||||
|
||||
[How to apply this]
|
||||
|
||||
## 2. [Second Main Point]
|
||||
|
||||
[Repeat structure]
|
||||
|
||||
## 3. [Third Main Point]
|
||||
|
||||
[Repeat structure]
|
||||
```
|
||||
|
||||
**Option B: Problem-Solution**
|
||||
```
|
||||
## The Problem
|
||||
|
||||
[Detailed problem description]
|
||||
|
||||
## Why Traditional Approaches Fail
|
||||
|
||||
[Analysis of common approaches]
|
||||
|
||||
## A Better Approach
|
||||
|
||||
[Your solution/framework]
|
||||
|
||||
## How to Implement
|
||||
|
||||
[Step-by-step guidance]
|
||||
```
|
||||
|
||||
**Option C: Narrative**
|
||||
```
|
||||
## The Beginning
|
||||
|
||||
[Story setup]
|
||||
|
||||
## The Challenge
|
||||
|
||||
[What happened]
|
||||
|
||||
## The Turning Point
|
||||
|
||||
[Key realization]
|
||||
|
||||
## The Result
|
||||
|
||||
[Outcome and lessons]
|
||||
|
||||
## The Broader Application
|
||||
|
||||
[How readers can apply this]
|
||||
```
|
||||
|
||||
**Your main content:**
|
||||
```
|
||||
[WRITE MAIN CONTENT HERE]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Conclusion (150-250 words)
|
||||
|
||||
**Purpose:** Summarize, synthesize, and call to action
|
||||
|
||||
**Template:**
|
||||
```
|
||||
## What This Means for You
|
||||
|
||||
[Brief recap of key points - 2-3 sentences max]
|
||||
|
||||
[The bigger picture / why this matters]
|
||||
|
||||
[Specific next steps the reader can take]
|
||||
|
||||
[Call to action - discussion question or invitation to connect]
|
||||
```
|
||||
|
||||
**Your conclusion:**
|
||||
```
|
||||
[WRITE CONCLUSION HERE]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Article Footer
|
||||
|
||||
```
|
||||
---
|
||||
|
||||
[Optional: About the author section - 2-3 sentences]
|
||||
|
||||
[Optional: Related articles or resources]
|
||||
|
||||
[Tags/hashtags: 3-5 relevant]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Pre-Publication Checklist
|
||||
|
||||
### Content Quality
|
||||
- [ ] Title is compelling and keyword-optimized
|
||||
- [ ] Opening hooks the reader immediately
|
||||
- [ ] Main content delivers on the title's promise
|
||||
- [ ] Examples are specific and relevant
|
||||
- [ ] Conclusion has clear takeaways
|
||||
- [ ] Word count is 1,500-2,500
|
||||
|
||||
### SEO Optimization
|
||||
- [ ] Primary keyword in title
|
||||
- [ ] Primary keyword in first 100 words
|
||||
- [ ] Keywords naturally distributed throughout
|
||||
- [ ] Subheadings are descriptive
|
||||
- [ ] Images have alt text
|
||||
|
||||
### Formatting
|
||||
- [ ] Short paragraphs (3-4 sentences max)
|
||||
- [ ] Clear section headings
|
||||
- [ ] Bullet points for lists
|
||||
- [ ] Tables for comparisons
|
||||
- [ ] White space for readability
|
||||
- [ ] Mobile-friendly formatting
|
||||
|
||||
### Attribution
|
||||
- [ ] All sources credited
|
||||
- [ ] External links working
|
||||
- [ ] Quotes properly attributed
|
||||
- [ ] No plagiarism
|
||||
|
||||
---
|
||||
|
||||
## Promotion Timeline
|
||||
|
||||
### Pre-Publication (1 week before)
|
||||
|
||||
**Day -7:**
|
||||
- [ ] Tease the topic in a post (generate interest)
|
||||
|
||||
**Day -3:**
|
||||
- [ ] Second tease post (share one insight from article)
|
||||
|
||||
**Day -1:**
|
||||
- [ ] Engage actively with your network (5x5x5 method)
|
||||
|
||||
### Publication Day
|
||||
|
||||
**Morning (publication):**
|
||||
- [ ] Publish article
|
||||
- [ ] Create promotional post (not just a link)
|
||||
- [ ] Share key insight with article link in comments
|
||||
|
||||
**Throughout the day:**
|
||||
- [ ] Respond to all comments on article
|
||||
- [ ] Respond to all comments on promotional post
|
||||
- [ ] Thank people who share
|
||||
|
||||
### Post-Publication (1-4 weeks after)
|
||||
|
||||
**Week 1:**
|
||||
- [ ] Create 2-3 derivative posts from article content
|
||||
- [ ] Each post links back to full article in comments
|
||||
|
||||
**Week 2:**
|
||||
- [ ] Create carousel version of key points (if applicable)
|
||||
- [ ] Reference article in relevant conversations
|
||||
|
||||
**Week 3-4:**
|
||||
- [ ] Continue derivative content
|
||||
- [ ] Update article if new information emerges
|
||||
|
||||
### Ongoing
|
||||
|
||||
- [ ] Add to Featured section on profile
|
||||
- [ ] Reference in future relevant posts
|
||||
- [ ] Update quarterly if evergreen topic
|
||||
|
||||
---
|
||||
|
||||
## Promotional Post Template
|
||||
|
||||
Use this to promote your article (don't just share the link):
|
||||
|
||||
```
|
||||
[Hook - the most valuable insight from the article]
|
||||
|
||||
[Why this matters - 2-3 sentences]
|
||||
|
||||
[What the reader will learn - bullet points]
|
||||
- Point 1
|
||||
- Point 2
|
||||
- Point 3
|
||||
|
||||
[Tease - hint at something unexpected in the article]
|
||||
|
||||
[CTA - read the full article, link in comments]
|
||||
|
||||
---
|
||||
Comment #1: Full article here: [Link]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Article Ideas Starter
|
||||
|
||||
Generate article ideas by combining:
|
||||
|
||||
| Your Expertise | + | Format |
|
||||
|----------------|---|--------|
|
||||
| AI implementation | | Complete guide |
|
||||
| Low-code automation | | Step-by-step tutorial |
|
||||
| Public sector AI | | Lessons learned |
|
||||
| Microsoft ecosystem | | Comparison/analysis |
|
||||
| RAG architecture | | Framework/methodology |
|
||||
|
||||
**Example combinations:**
|
||||
- "AI Implementation: The Complete Guide for Public Sector Leaders"
|
||||
- "5 RAG Architecture Patterns I've Used Across 20+ Projects"
|
||||
- "Why Public Sector AI Projects Fail (And How to Fix Them)"
|
||||
- "Copilot Studio vs Power Automate: A Practical Comparison"
|
||||
- "Building Your First RAG System: A Step-by-Step Tutorial"
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
- Articles get less initial reach but longer lifespan
|
||||
- Optimize for search (keywords in title, headings)
|
||||
- Link internally to your other articles
|
||||
- Update evergreen content quarterly
|
||||
- Feature best articles on profile
|
||||
|
|
@ -0,0 +1,249 @@
|
|||
# My Custom Post Templates
|
||||
|
||||
Save your proven post structures here. When you find a format that works consistently, document it so Claude can replicate the pattern.
|
||||
|
||||
---
|
||||
|
||||
## Template 1: [Name - e.g., "My Framework Introduction Template"]
|
||||
|
||||
**When to use:** [e.g., "When introducing a new framework or model I've developed"]
|
||||
|
||||
**Structure:**
|
||||
|
||||
```
|
||||
[HOOK - Counterintuitive stat or bold statement]
|
||||
(1-2 lines, <110 characters)
|
||||
|
||||
[CONTEXT - The problem this framework solves]
|
||||
(2-3 lines explaining why people struggle)
|
||||
|
||||
[FRAMEWORK INTRODUCTION]
|
||||
"I developed [Framework Name] to solve this."
|
||||
(Brief one-line description)
|
||||
|
||||
[COMPONENT BREAKDOWN]
|
||||
Stage 1: [Name]
|
||||
→ [Key characteristic in one line]
|
||||
|
||||
Stage 2: [Name]
|
||||
→ [Key characteristic in one line]
|
||||
|
||||
Stage 3: [Name]
|
||||
→ [Key characteristic in one line]
|
||||
|
||||
[IMPLICATION]
|
||||
"Most organizations are stuck at Stage 1.
|
||||
Here's what moving to Stage 2 unlocks..."
|
||||
(2-3 lines on practical value)
|
||||
|
||||
[CTA]
|
||||
"Which stage is your organization in?"
|
||||
```
|
||||
|
||||
**Why this works for me:**
|
||||
- [Reason 1 - e.g., "My audience loves actionable frameworks"]
|
||||
- [Reason 2 - e.g., "The diagnostic question always generates 15+ comments"]
|
||||
|
||||
**Example posts using this template:**
|
||||
- [Link to post 1]
|
||||
- [Link to post 2]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template 2: [Name - e.g., "My Before/After Transformation Story"]
|
||||
|
||||
**When to use:** [e.g., "When sharing case study or project results"]
|
||||
|
||||
**Structure:**
|
||||
|
||||
```
|
||||
[HOOK - The transformation in numbers]
|
||||
"6 months ago: [painful metric]
|
||||
Today: [improved metric]"
|
||||
|
||||
[THE BEFORE]
|
||||
[Organization] was struggling with [specific problem].
|
||||
(Paint picture of pain - 3-4 lines)
|
||||
|
||||
[THE TURNING POINT]
|
||||
We decided to [key decision].
|
||||
Most teams choose [alternative]. Here's why we didn't...
|
||||
|
||||
[THE APPROACH]
|
||||
"Three things mattered:
|
||||
• [Element 1]
|
||||
• [Element 2]
|
||||
• [Element 3]"
|
||||
|
||||
[THE AFTER]
|
||||
Results:
|
||||
→ [Metric 1]: [Before] → [After]
|
||||
→ [Metric 2]: [Before] → [After]
|
||||
→ [Metric 3]: [Before] → [After]
|
||||
|
||||
[KEY LESSON]
|
||||
"The real breakthrough wasn't [expected thing].
|
||||
It was [non-obvious insight]."
|
||||
|
||||
[CTA]
|
||||
"What's been YOUR biggest lesson in [topic]?"
|
||||
```
|
||||
|
||||
**Why this works for me:**
|
||||
- [Reason 1]
|
||||
- [Reason 2]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template 3: [Name - e.g., "My Contrarian Take"]
|
||||
|
||||
**When to use:** [e.g., "When challenging conventional wisdom in my field"]
|
||||
|
||||
**Structure:**
|
||||
|
||||
```
|
||||
[HOOK - Bold contrarian statement]
|
||||
"Everyone says [conventional wisdom].
|
||||
I think that's wrong."
|
||||
|
||||
[THE CONVENTIONAL APPROACH]
|
||||
Most [target audience] believe [common belief].
|
||||
(Explain the mainstream view fairly - 2-3 lines)
|
||||
|
||||
[WHY IT FAILS]
|
||||
But here's the problem...
|
||||
(2-3 specific reasons with examples)
|
||||
|
||||
[THE ALTERNATIVE]
|
||||
Instead, try this:
|
||||
→ [Alternative approach 1]
|
||||
→ [Alternative approach 2]
|
||||
→ [Alternative approach 3]
|
||||
|
||||
[EVIDENCE]
|
||||
"I've seen this play out across [X] projects:
|
||||
[Specific result/pattern you've observed]"
|
||||
|
||||
[NUANCE]
|
||||
"To be clear: [conventional wisdom] works if [specific condition].
|
||||
But for [your context], [your approach] is better because..."
|
||||
|
||||
[CTA]
|
||||
"What's your experience? Am I missing something?"
|
||||
```
|
||||
|
||||
**Why this works for me:**
|
||||
- [Reason 1]
|
||||
- [Reason 2]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template 4: [Name - e.g., "My Failure Lesson Post"]
|
||||
|
||||
**When to use:** [e.g., "When sharing what didn't work to build trust"]
|
||||
|
||||
**Structure:**
|
||||
|
||||
```
|
||||
[HOOK - Admission of failure]
|
||||
"[Approach] should have worked.
|
||||
It failed spectacularly."
|
||||
|
||||
[SETUP]
|
||||
We were trying to [goal].
|
||||
The plan: [what you intended to do]
|
||||
On paper, perfect.
|
||||
|
||||
[THE FAILURE]
|
||||
"Here's what actually happened..."
|
||||
(Specific description of what went wrong - 3-4 lines)
|
||||
|
||||
[WHY IT FAILED]
|
||||
Looking back, three mistakes:
|
||||
1. [Mistake 1] - We assumed [wrong assumption]
|
||||
2. [Mistake 2] - We underestimated [factor]
|
||||
3. [Mistake 3] - We ignored [warning sign]
|
||||
|
||||
[THE PIVOT]
|
||||
"So we tried [different approach] instead.
|
||||
That worked because..."
|
||||
|
||||
[THE LEARNING]
|
||||
"Key lesson:
|
||||
[Non-obvious insight that only came from the failure]"
|
||||
|
||||
[CTA]
|
||||
"Have you failed at [topic] too? What did you learn?"
|
||||
```
|
||||
|
||||
**Why this works for me:**
|
||||
- [Reason 1]
|
||||
- [Reason 2]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template 5: [Name - Your custom template]
|
||||
|
||||
**When to use:** [Context]
|
||||
|
||||
**Structure:**
|
||||
[Your proven structure]
|
||||
|
||||
**Why this works for me:**
|
||||
[Analysis]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template Performance Comparison
|
||||
|
||||
| Template | Avg. Likes | Avg. Comments | Avg. Reach | Best Use Case |
|
||||
|----------|-----------|---------------|------------|---------------|
|
||||
| Framework Intro | [X] | [Y] | [Z] | [When] |
|
||||
| Before/After | [X] | [Y] | [Z] | [When] |
|
||||
| Contrarian | [X] | [Y] | [Z] | [When] |
|
||||
| Failure Lesson | [X] | [Y] | [Z] | [When] |
|
||||
|
||||
**Insights:**
|
||||
[What these patterns tell you about your audience preferences]
|
||||
|
||||
---
|
||||
|
||||
## Template Selection Guide
|
||||
|
||||
**Use Framework template when:**
|
||||
- Introducing new model/system
|
||||
- Teaching actionable process
|
||||
- Want high saves (reference value)
|
||||
|
||||
**Use Before/After template when:**
|
||||
- Have strong results to share
|
||||
- Building credibility
|
||||
- Want case study authority
|
||||
|
||||
**Use Contrarian template when:**
|
||||
- Challenging assumptions
|
||||
- Positioning unique POV
|
||||
- Want engagement/debate
|
||||
|
||||
**Use Failure template when:**
|
||||
- Building trust/authenticity
|
||||
- Sharing hard-won lessons
|
||||
- Want vulnerable connection
|
||||
|
||||
---
|
||||
|
||||
## Update Log
|
||||
|
||||
- [Date]: Created template 1 based on [successful posts]
|
||||
- [Date]: Refined template 2 after [pattern observation]
|
||||
- [Date]: Added template 3 for [new content type]
|
||||
|
|
@ -0,0 +1,525 @@
|
|||
# Post Type Templates
|
||||
|
||||
Quick-start templates for common LinkedIn post types. Copy, customize, and post.
|
||||
|
||||
---
|
||||
|
||||
## Template 1: Reaction Post
|
||||
|
||||
**Use when:** News drops, something changes in your industry, you see a trend emerging.
|
||||
|
||||
```
|
||||
[Industry event/news - state what happened]
|
||||
|
||||
My take: [Your perspective in 1-2 sentences]
|
||||
|
||||
[Question for audience OR prediction about what this means]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Tech news reaction:**
|
||||
```
|
||||
OpenAI just announced [feature].
|
||||
|
||||
My take: This matters less for the tech and more for
|
||||
what it signals about where the industry is heading.
|
||||
|
||||
What do you think - genuine innovation or
|
||||
incremental improvement?
|
||||
```
|
||||
|
||||
**Industry change reaction:**
|
||||
```
|
||||
Microsoft dropped a new Copilot update yesterday.
|
||||
|
||||
Here's what caught my attention: [specific feature]
|
||||
finally addresses [common complaint].
|
||||
|
||||
Has anyone tested it yet? Curious if the reality
|
||||
matches the promise.
|
||||
```
|
||||
|
||||
**Trend reaction:**
|
||||
```
|
||||
Third announcement about [trend] this week.
|
||||
|
||||
Either this is genuinely the next big thing,
|
||||
or we're all drinking the same Kool-Aid.
|
||||
|
||||
I'm cautiously optimistic. Where do you land?
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 2: Quick Tip Post
|
||||
|
||||
**Use when:** You learned something useful, found a shortcut, discovered a fix.
|
||||
|
||||
```
|
||||
[Bold claim about the tip]
|
||||
|
||||
Here's why: [Brief explanation - 1-2 sentences]
|
||||
|
||||
[How to apply it OR invitation to share their version]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Tool tip:**
|
||||
```
|
||||
Stop manually formatting your LinkedIn posts.
|
||||
|
||||
I use [tool/technique] and it takes 30 seconds
|
||||
instead of 10 minutes.
|
||||
|
||||
Here's the exact workflow: [1-2 steps]
|
||||
|
||||
What's your time-saving hack?
|
||||
```
|
||||
|
||||
**Process tip:**
|
||||
```
|
||||
The 2-minute rule changed how I handle [task].
|
||||
|
||||
If it takes less than 2 minutes, do it now.
|
||||
Seems obvious, but I resisted for years.
|
||||
|
||||
Now my [specific result] is [specific improvement].
|
||||
```
|
||||
|
||||
**Mindset tip:**
|
||||
```
|
||||
Before any important meeting, I ask one question:
|
||||
|
||||
"What's the one outcome that makes this worth everyone's time?"
|
||||
|
||||
Sounds simple. Cuts meeting time in half.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 3: Observation Post
|
||||
|
||||
**Use when:** You noticed a pattern, saw something interesting, made a connection.
|
||||
|
||||
```
|
||||
I've noticed [pattern/trend].
|
||||
|
||||
[Evidence or example - specific, concrete]
|
||||
|
||||
Anyone else seeing this?
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Industry observation:**
|
||||
```
|
||||
I've noticed that the AI projects that actually
|
||||
ship have something in common:
|
||||
|
||||
They start with a problem, not a technology.
|
||||
|
||||
Simple, but I see the opposite approach fail
|
||||
constantly. Anyone else?
|
||||
```
|
||||
|
||||
**Behavioral observation:**
|
||||
```
|
||||
Interesting pattern in my calendar this month:
|
||||
|
||||
The meetings that produced results had fewer
|
||||
than 5 people. The ones with 10+ produced... documents.
|
||||
|
||||
Starting to say no to large meetings.
|
||||
What's your threshold?
|
||||
```
|
||||
|
||||
**Market observation:**
|
||||
```
|
||||
Three companies in my network just paused
|
||||
their AI initiatives.
|
||||
|
||||
Not because of budget. Because they don't
|
||||
know what problem to solve.
|
||||
|
||||
Strategy before technology. Always.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 4: Hot Take Post
|
||||
|
||||
**Use when:** You disagree with common wisdom, have a controversial opinion, want to start debate.
|
||||
|
||||
```
|
||||
Unpopular opinion: [Your take]
|
||||
|
||||
[Why you believe this - 1-2 sentences]
|
||||
|
||||
Change my mind.
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Industry hot take:**
|
||||
```
|
||||
Unpopular opinion: Most "AI strategies" are
|
||||
just vendor slide decks with your logo added.
|
||||
|
||||
Real strategy requires understanding your
|
||||
problems before browsing solutions.
|
||||
|
||||
Fight me.
|
||||
```
|
||||
|
||||
**Process hot take:**
|
||||
```
|
||||
Hot take: The problem with [common practice]
|
||||
isn't that it doesn't work.
|
||||
|
||||
It's that it works just well enough that
|
||||
we never question if there's a better way.
|
||||
|
||||
What "works" for you that might be holding you back?
|
||||
```
|
||||
|
||||
**Career hot take:**
|
||||
```
|
||||
Controversial: The best career advice isn't
|
||||
"find your passion."
|
||||
|
||||
It's "get really good at something useful,
|
||||
and passion often follows."
|
||||
|
||||
Agree or disagree?
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 5: Failure/Mistake Post
|
||||
|
||||
**Use when:** Something went wrong, you made an error, you learned from a mistake.
|
||||
|
||||
```
|
||||
I made a mistake with [topic/project].
|
||||
|
||||
Here's what went wrong: [Brief explanation]
|
||||
|
||||
Lesson learned: [What you'd do differently]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Project failure:**
|
||||
```
|
||||
Launched a Copilot agent last month.
|
||||
Adoption rate: 12%.
|
||||
|
||||
The mistake: We built what we thought users
|
||||
needed instead of asking them.
|
||||
|
||||
Rebuilding with actual user input this time.
|
||||
```
|
||||
|
||||
**Decision mistake:**
|
||||
```
|
||||
Spent 3 weeks optimizing the wrong metric.
|
||||
|
||||
Got so focused on [metric A] that I missed
|
||||
[metric B] collapsing.
|
||||
|
||||
Now I check the dashboard before the details.
|
||||
```
|
||||
|
||||
**Communication mistake:**
|
||||
```
|
||||
Sent a message that came across completely wrong.
|
||||
|
||||
What I meant: [intention]
|
||||
What they heard: [interpretation]
|
||||
|
||||
Learning to re-read everything from their perspective.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 6: Question Post
|
||||
|
||||
**Use when:** You want to spark discussion, gather perspectives, learn from your network.
|
||||
|
||||
```
|
||||
[Context-setting statement]
|
||||
|
||||
[Specific question]
|
||||
|
||||
I'll share my thinking in the comments.
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Industry question:**
|
||||
```
|
||||
Talking to a lot of AI teams lately about
|
||||
governance frameworks.
|
||||
|
||||
Genuine question: How do you balance
|
||||
"move fast" with "don't break things"?
|
||||
|
||||
Share what's working (or not).
|
||||
```
|
||||
|
||||
**Career question:**
|
||||
```
|
||||
At what point does "being a generalist"
|
||||
become "not being an expert in anything"?
|
||||
|
||||
Genuinely wrestling with this.
|
||||
Where do you draw the line?
|
||||
```
|
||||
|
||||
**Tool question:**
|
||||
```
|
||||
Looking for recommendations:
|
||||
What's your go-to tool for [specific task]?
|
||||
|
||||
Currently using [current tool] but feeling
|
||||
like there's something better out there.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 7: Curation Post
|
||||
|
||||
**Use when:** You found something worth sharing, want to add your perspective to existing content.
|
||||
|
||||
```
|
||||
[What you found/read/watched]
|
||||
|
||||
[Your specific takeaway - not just "it was great"]
|
||||
|
||||
[Link in comments or tag the creator]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Article curation:**
|
||||
```
|
||||
Read [Author]'s piece on [topic] three times.
|
||||
|
||||
The part that stuck: [specific quote or idea]
|
||||
|
||||
This explains why [your connection to your work].
|
||||
|
||||
Link in first comment.
|
||||
```
|
||||
|
||||
**Creator curation:**
|
||||
```
|
||||
[Creator name] nailed something I've been
|
||||
trying to articulate for months:
|
||||
|
||||
[Paraphrase their key point]
|
||||
|
||||
If you care about [topic], follow them.
|
||||
```
|
||||
|
||||
**Resource curation:**
|
||||
```
|
||||
Best thing I've read this week on [topic]:
|
||||
|
||||
[Brief summary of the insight]
|
||||
|
||||
Saving this for the next time I [relevant situation].
|
||||
|
||||
[Tag creator or link placement]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 8: One-Liner Post
|
||||
|
||||
**Use when:** You have a punchy insight that doesn't need explanation.
|
||||
|
||||
```
|
||||
[Single powerful statement]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Wisdom one-liner:**
|
||||
```
|
||||
The best processes are invisible.
|
||||
The worst processes require training.
|
||||
```
|
||||
|
||||
**Observation one-liner:**
|
||||
```
|
||||
Every "AI transformation" I've seen succeed
|
||||
started with spreadsheets and post-its.
|
||||
```
|
||||
|
||||
**Contrarian one-liner:**
|
||||
```
|
||||
The companies with the best AI strategies
|
||||
are the ones not talking about AI.
|
||||
```
|
||||
|
||||
**Note:** One-liners work best when you've built enough credibility that people trust your perspective without explanation. Use sparingly - maybe 1 in 10 posts.
|
||||
|
||||
---
|
||||
|
||||
## Expertise-Specific Examples
|
||||
|
||||
### For AI/Tech Professionals
|
||||
|
||||
**Reaction:**
|
||||
```
|
||||
New Claude update just dropped with [feature].
|
||||
|
||||
First impression: This changes how I think
|
||||
about [specific use case].
|
||||
|
||||
Testing it today. What are you most curious about?
|
||||
```
|
||||
|
||||
**Observation:**
|
||||
```
|
||||
Noticed something in every successful AI pilot
|
||||
I've been part of:
|
||||
|
||||
The team spent more time on change management
|
||||
than on the technology.
|
||||
|
||||
Tech is the easy part.
|
||||
```
|
||||
|
||||
**Quick Tip:**
|
||||
```
|
||||
Prompt engineering tip that took me too long to learn:
|
||||
|
||||
Start with the output format you want,
|
||||
then work backwards to the instruction.
|
||||
|
||||
Sounds obvious. Changed everything.
|
||||
```
|
||||
|
||||
### For Leaders/Managers
|
||||
|
||||
**Hot Take:**
|
||||
```
|
||||
Unpopular opinion: Most leadership advice
|
||||
is written by people who haven't led in years.
|
||||
|
||||
Theory is important.
|
||||
So is what's actually working right now.
|
||||
|
||||
Who are you learning from?
|
||||
```
|
||||
|
||||
**Failure:**
|
||||
```
|
||||
Gave feedback yesterday that landed completely wrong.
|
||||
|
||||
My intention: Help them grow.
|
||||
Their experience: Felt criticized.
|
||||
|
||||
Working on leading with curiosity, not conclusions.
|
||||
```
|
||||
|
||||
**Question:**
|
||||
```
|
||||
Leaders: How do you create psychological safety
|
||||
in a remote team?
|
||||
|
||||
Genuine question.
|
||||
The old playbook doesn't quite translate.
|
||||
|
||||
What's working for you?
|
||||
```
|
||||
|
||||
### For Consultants/Advisors
|
||||
|
||||
**Curation:**
|
||||
```
|
||||
Best framework I've encountered this month
|
||||
for [specific challenge]:
|
||||
|
||||
[Brief description]
|
||||
|
||||
Changed how I approach [type of engagement].
|
||||
Full breakdown in comments.
|
||||
```
|
||||
|
||||
**Observation:**
|
||||
```
|
||||
Pattern I'm seeing across clients:
|
||||
|
||||
The ones moving fastest on AI started
|
||||
with their biggest pain point, not the
|
||||
most impressive use case.
|
||||
|
||||
Simple beats sexy.
|
||||
```
|
||||
|
||||
**One-Liner:**
|
||||
```
|
||||
The best consultants make themselves unnecessary.
|
||||
The worst ones create dependency.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## The 3-Line Post Formula
|
||||
|
||||
For most quick posts, use this structure:
|
||||
|
||||
**Line 1: Hook (under 140 characters)**
|
||||
Creates curiosity or makes a statement
|
||||
|
||||
**Line 2: Context or Evidence (1-2 sentences)**
|
||||
Explains the "why" or provides supporting information
|
||||
|
||||
**Line 3: Insight or Question (the "so what")**
|
||||
Actionable takeaway or engagement prompt
|
||||
|
||||
**Character Target: 150-500 characters**
|
||||
|
||||
Quick posts should be SHORT. The goal is engagement and presence, not depth. If you're over 500 characters, consider whether this should be a full workflow post instead.
|
||||
|
||||
---
|
||||
|
||||
## Angle Selection Guide
|
||||
|
||||
| Angle | Opening Pattern | Best For |
|
||||
|-------|-----------------|----------|
|
||||
| Contrarian | "Everyone says X, but..." | Challenging assumptions |
|
||||
| Validating | "Here's proof that X works..." | Reinforcing with evidence |
|
||||
| Curious | "I've been wondering why..." | Opening discussion |
|
||||
| Helpful | "Here's something that saved me..." | Practical value |
|
||||
| Surprised | "I didn't expect this, but..." | Discovery sharing |
|
||||
| Frustrated | "Can we talk about why..." | Calling out problems |
|
||||
| Excited | "Just discovered..." | Genuine enthusiasm |
|
||||
| Reflective | "After X years, I've learned..." | Wisdom sharing |
|
||||
|
||||
---
|
||||
|
||||
## Converting Quick Posts to Full Content
|
||||
|
||||
When a quick post performs exceptionally well, consider expanding:
|
||||
|
||||
**Signals a quick post deserves expansion:**
|
||||
- Comment depth (people asking follow-up questions)
|
||||
- Save rate is high (people want to reference later)
|
||||
- You have more to say that wouldn't fit
|
||||
- It connects to other ideas you've shared
|
||||
|
||||
**Expansion options:**
|
||||
- Turn into carousel (break insight into 6-8 slides)
|
||||
- Write the full story behind the observation
|
||||
- Create a framework around the tip
|
||||
- Develop a post series exploring the theme
|
||||
- Save for newsletter deep-dive
|
||||
|
||||
**Tracking for expansion:**
|
||||
Keep a simple list of quick posts that outperformed. Review monthly. These are your best candidates for full content development.
|
||||
|
|
@ -0,0 +1,317 @@
|
|||
# Weekly Content Calendar (2-3 Posts/Week)
|
||||
|
||||
Templates for planning low-frequency, high-quality LinkedIn content.
|
||||
|
||||
## Weekly Schedule Templates
|
||||
|
||||
### Option A: 2 Posts/Week
|
||||
|
||||
**Minimal viable presence for busy professionals**
|
||||
|
||||
| Day | Slot | Content Type | Purpose |
|
||||
|-----|------|--------------|---------|
|
||||
| Tuesday | 8:00 AM CET | Core Expertise | Peak engagement day |
|
||||
| Thursday | 8:00 AM CET | Story/Commentary | Personality building |
|
||||
|
||||
**Time investment:** 3-4 hours/week
|
||||
|
||||
| Activity | Time | When |
|
||||
|----------|------|------|
|
||||
| Content creation | 90 min | Weekend or Monday |
|
||||
| Pre-post engagement (5x5x5) | 30 min | Before each post (2x) |
|
||||
| Post engagement | 60 min | After each post (2x) |
|
||||
| Daily maintenance | 25 min | 5 min/day other days |
|
||||
|
||||
---
|
||||
|
||||
### Option B: 3 Posts/Week (Recommended)
|
||||
|
||||
**Balanced presence for sustainable growth**
|
||||
|
||||
| Day | Slot | Content Type | Purpose |
|
||||
|-----|------|--------------|---------|
|
||||
| Tuesday | 8:00 AM CET | Core Expertise | Authority building |
|
||||
| Wednesday | 12:00 PM CET | Quick Post/News | Maintain presence |
|
||||
| Thursday | 8:00 AM CET | In-depth/Story | Engagement driver |
|
||||
|
||||
**Time investment:** 4-5 hours/week
|
||||
|
||||
| Activity | Time | When |
|
||||
|----------|------|------|
|
||||
| Content creation | 120 min | Weekend or Monday |
|
||||
| Pre-post engagement | 45 min | Before each post (3x) |
|
||||
| Post engagement | 90 min | After each post (3x) |
|
||||
| Daily maintenance | 25 min | 5 min/day non-post days |
|
||||
|
||||
---
|
||||
|
||||
### Option C: 2 Posts + 1 Article/Month
|
||||
|
||||
**For established professionals building depth**
|
||||
|
||||
**Week 1:**
|
||||
| Day | Content |
|
||||
|-----|---------|
|
||||
| Tuesday | Regular post |
|
||||
| Wednesday | Article publication |
|
||||
| Thursday | Article promotion post |
|
||||
|
||||
**Weeks 2-4:**
|
||||
| Day | Content |
|
||||
|-----|---------|
|
||||
| Tuesday | Regular post |
|
||||
| Thursday | Regular post (or article derivative) |
|
||||
|
||||
---
|
||||
|
||||
## Monthly Planning Grid
|
||||
|
||||
### 8-Post Month (2x/week)
|
||||
|
||||
| Week | Tuesday | Thursday | Notes |
|
||||
|------|---------|----------|-------|
|
||||
| 1 | Expertise deep-dive | Personal story | Foundation |
|
||||
| 2 | Framework/how-to | Industry commentary | Education |
|
||||
| 3 | Case study | Trend analysis | Credibility |
|
||||
| 4 | Tool/resource share | Reflection/lesson | Value |
|
||||
|
||||
### 12-Post Month (3x/week)
|
||||
|
||||
| Week | Tuesday | Wednesday | Thursday |
|
||||
|------|---------|-----------|----------|
|
||||
| 1 | Expertise deep-dive | Quick news take | Personal story |
|
||||
| 2 | Framework post | Commentary | Case study |
|
||||
| 3 | How-to guide | News reaction | Trend analysis |
|
||||
| 4 | Resource share | Quick insight | Monthly reflection |
|
||||
|
||||
---
|
||||
|
||||
## Content Type Rotation
|
||||
|
||||
### For AI-Focused Creators
|
||||
|
||||
**Monthly mix (8-12 posts):**
|
||||
|
||||
| Type | Count | Examples |
|
||||
|------|-------|----------|
|
||||
| AI News/Commentary | 2-3 | New releases, announcements, trends |
|
||||
| Implementation How-to | 2-3 | Patterns, tutorials, lessons |
|
||||
| Strategy/Leadership | 1-2 | ROI, governance, decisions |
|
||||
| Tools/Resources | 1-2 | Comparisons, shares, templates |
|
||||
| Personal/Story | 1-2 | Experiences, reflections |
|
||||
|
||||
### Content Pillars Grid
|
||||
|
||||
Map your posts across pillars:
|
||||
|
||||
| Pillar | Week 1 | Week 2 | Week 3 | Week 4 |
|
||||
|--------|--------|--------|--------|--------|
|
||||
| AI News | X | | X | |
|
||||
| Implementation | | X | | X |
|
||||
| Strategy | | | X | |
|
||||
| Tools | | | | X |
|
||||
| Personal | X | | | |
|
||||
|
||||
---
|
||||
|
||||
## Weekly Workflow
|
||||
|
||||
### Sunday (30 min)
|
||||
|
||||
**Planning session:**
|
||||
- [ ] Review next week's calendar slots
|
||||
- [ ] Assign topics to each slot
|
||||
- [ ] Note any timely content opportunities
|
||||
- [ ] Check for relevant news to comment on
|
||||
|
||||
### Monday (90-120 min)
|
||||
|
||||
**Batch creation:**
|
||||
- [ ] Write/finalize all posts for the week
|
||||
- [ ] Prepare visuals if needed
|
||||
- [ ] Draft first comments (links, etc.)
|
||||
- [ ] Schedule or save drafts
|
||||
|
||||
### Posting Days (45-60 min each)
|
||||
|
||||
**Pre-post (15 min before):**
|
||||
- [ ] 5x5x5 engagement on target creators
|
||||
|
||||
**Post (2 min):**
|
||||
- [ ] Publish post
|
||||
- [ ] Add first comment with link (if applicable)
|
||||
|
||||
**Post-engagement (30-45 min after):**
|
||||
- [ ] Stay online for first hour
|
||||
- [ ] Respond to every comment
|
||||
- [ ] Engage with commenters' profiles
|
||||
|
||||
### Non-Posting Days (5-10 min)
|
||||
|
||||
**Maintenance:**
|
||||
- [ ] Check for comments to respond to
|
||||
- [ ] 3-5 quick engagements on feed
|
||||
- [ ] Note content ideas
|
||||
|
||||
### Friday (15 min)
|
||||
|
||||
**Week review:**
|
||||
- [ ] Check post performance
|
||||
- [ ] Note what worked/didn't
|
||||
- [ ] Capture ideas for next week
|
||||
- [ ] Update monthly tracking
|
||||
|
||||
---
|
||||
|
||||
## Monthly Planning Template
|
||||
|
||||
### Month: _______________
|
||||
|
||||
**Goals this month:**
|
||||
- Growth target: _____ new followers
|
||||
- Engagement target: _____ average comments
|
||||
- Content focus: _____
|
||||
|
||||
### Week 1: ___ to ___
|
||||
|
||||
| Date | Day | Topic | Type | Status |
|
||||
|------|-----|-------|------|--------|
|
||||
| | Tue | | | [ ] |
|
||||
| | Wed | | | [ ] |
|
||||
| | Thu | | | [ ] |
|
||||
|
||||
Notes: _____
|
||||
|
||||
### Week 2: ___ to ___
|
||||
|
||||
| Date | Day | Topic | Type | Status |
|
||||
|------|-----|-------|------|--------|
|
||||
| | Tue | | | [ ] |
|
||||
| | Wed | | | [ ] |
|
||||
| | Thu | | | [ ] |
|
||||
|
||||
Notes: _____
|
||||
|
||||
### Week 3: ___ to ___
|
||||
|
||||
| Date | Day | Topic | Type | Status |
|
||||
|------|-----|-------|------|--------|
|
||||
| | Tue | | | [ ] |
|
||||
| | Wed | | | [ ] |
|
||||
| | Thu | | | [ ] |
|
||||
|
||||
Notes: _____
|
||||
|
||||
### Week 4: ___ to ___
|
||||
|
||||
| Date | Day | Topic | Type | Status |
|
||||
|------|-----|-------|------|--------|
|
||||
| | Tue | | | [ ] |
|
||||
| | Wed | | | [ ] |
|
||||
| | Thu | | | [ ] |
|
||||
|
||||
Notes: _____
|
||||
|
||||
### Month-End Review
|
||||
|
||||
- Total posts: _____ / planned: _____
|
||||
- Average engagement rate: _____%
|
||||
- Best performing post: _____
|
||||
- Follower growth: _____
|
||||
- Lessons learned: _____
|
||||
|
||||
---
|
||||
|
||||
## Engagement Schedule
|
||||
|
||||
### Posting Days
|
||||
|
||||
| Time | Activity |
|
||||
|------|----------|
|
||||
| 7:45 AM | 5x5x5 pre-engagement |
|
||||
| 8:00 AM | Publish post |
|
||||
| 8:00-9:00 AM | Active engagement with comments |
|
||||
| 12:00 PM | Check for new comments, respond |
|
||||
| 5:00 PM | Final comment check |
|
||||
|
||||
### Non-Posting Days
|
||||
|
||||
| Time | Activity |
|
||||
|------|----------|
|
||||
| 8:00 AM | 5-minute feed scan |
|
||||
| 12:00 PM | Check for comments on recent posts |
|
||||
| Any time | Note content ideas when they occur |
|
||||
|
||||
---
|
||||
|
||||
## Quality Standards Checklist
|
||||
|
||||
**For low-frequency posting, each post must:**
|
||||
|
||||
- [ ] Contain genuine insight (not just observation)
|
||||
- [ ] Have a compelling hook (first 140 chars)
|
||||
- [ ] Be well-structured and formatted
|
||||
- [ ] Demonstrate clear expertise
|
||||
- [ ] Include engaging CTA
|
||||
- [ ] Connect to core topic areas
|
||||
- [ ] Be worth saving (the save test)
|
||||
|
||||
**If a post doesn't meet these standards, don't publish it.** Skip a slot rather than post mediocre content.
|
||||
|
||||
---
|
||||
|
||||
## Tracking Template
|
||||
|
||||
### Weekly Metrics
|
||||
|
||||
| Week | Posts | Avg Views | Avg Likes | Avg Comments | New Followers |
|
||||
|------|-------|-----------|-----------|--------------|---------------|
|
||||
| 1 | | | | | |
|
||||
| 2 | | | | | |
|
||||
| 3 | | | | | |
|
||||
| 4 | | | | | |
|
||||
|
||||
### Monthly Summary
|
||||
|
||||
| Metric | Target | Actual |
|
||||
|--------|--------|--------|
|
||||
| Posts published | | |
|
||||
| Average engagement rate | | |
|
||||
| Total new followers | | |
|
||||
| Best post (topic) | n/a | |
|
||||
| Opportunities generated | | |
|
||||
|
||||
---
|
||||
|
||||
## Adaptation Guidelines
|
||||
|
||||
### When to increase frequency
|
||||
|
||||
- Consistently exceeding engagement targets
|
||||
- Have more time available
|
||||
- Building toward specific goal (launch, event)
|
||||
- Growing faster than expected
|
||||
|
||||
### When to maintain 2-3x
|
||||
|
||||
- Meeting targets consistently
|
||||
- Time-constrained
|
||||
- Quality > quantity preference
|
||||
- Sustainable long-term pace
|
||||
|
||||
### When to decrease
|
||||
|
||||
- Quality suffering
|
||||
- Burnout signs
|
||||
- Major life/work demands
|
||||
- Better to pause than post poorly
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
- Low frequency requires HIGHER quality per post
|
||||
- Engagement time matters more than posting time
|
||||
- Consistency matters more than frequency
|
||||
- Skip a post rather than post poorly
|
||||
- Review and adjust monthly
|
||||
Loading…
Add table
Add a link
Reference in a new issue