ktg-plugin-marketplace/plugins/linkedin-thought-leadership/assets/frameworks/framework-template.md
Kjell Tore Guttormsen 39f8b275a6 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>
2026-04-07 22:09:03 +02:00

5.7 KiB

[Framework Name - e.g., "The 3-Stage RAG Maturity Model"]

Overview

One-sentence description: [What this framework does - e.g., "A diagnostic tool for assessing and advancing organizational RAG implementation from basic to advanced."]

Problem it solves: [What challenge this addresses - e.g., "Most organizations don't know where they are in their RAG journey or what to do next."]

Who it's for: [Target audience - e.g., "Enterprise architects and AI leaders implementing RAG solutions."]


The Framework

[Detailed explanation of your framework - be specific about the components, stages, or elements]

Component 1: [Name - e.g., "Stage 1: Basic RAG"]

Definition: [Clear description]

Characteristics:

  • [Key trait 1]
  • [Key trait 2]
  • [Key trait 3]

Common challenges at this stage:

  • [Challenge 1]
  • [Challenge 2]

What success looks like: [Measurable outcomes]


Component 2: [Name - e.g., "Stage 2: Enhanced RAG"]

Definition: [Clear description]

Characteristics:

  • [Key trait 1]
  • [Key trait 2]
  • [Key trait 3]

Common challenges at this stage:

  • [Challenge 1]
  • [Challenge 2]

What success looks like: [Measurable outcomes]


Component 3: [Name - e.g., "Stage 3: Advanced RAG"]

Definition: [Clear description]

Characteristics:

  • [Key trait 1]
  • [Key trait 2]
  • [Key trait 3]

Common challenges at this stage:

  • [Challenge 1]
  • [Challenge 2]

What success looks like: [Measurable outcomes]


How to Use This Framework

Diagnostic questions:

  1. [Question to determine current stage/position]
  2. [Question to identify gaps]
  3. [Question to prioritize next steps]

Implementation pathway:

  1. [Step 1]
  2. [Step 2]
  3. [Step 3]

LinkedIn Post Angle Options

When creating posts about this framework, here are proven angles:

Angle 1: Framework Introduction

Hook: "Most [target audience] struggle with [problem]. I developed a framework that [solution]."

Structure:

  • Introduce the problem
  • Present the framework overview
  • Briefly explain each component
  • Provide diagnostic question
  • CTA: Ask where they are in the framework

Expected engagement: [Medium-High for framework lovers]


Angle 2: Deep Dive on One Component

Hook: "[Stage/Component Name] is where most [target audience] get stuck. Here's why..."

Structure:

  • Focus on single component in depth
  • Common mistakes at this stage
  • How to progress to next level
  • Real example if available
  • CTA: Ask about their experience at this stage

Expected engagement: [High for people at that stage]


Angle 3: Case Study Application

Hook: "We helped [Company/Org Type] move from [Stage A] to [Stage B] in [Time]. Here's how..."

Structure:

  • Starting situation (Stage A characteristics)
  • Challenge/tension
  • Intervention using framework
  • Results (Stage B outcomes)
  • Key lesson
  • CTA: Ask what stage they're at

Expected engagement: [Very High - specificity + results]


Angle 4: Contrarian Take

Hook: "Everyone talks about [common approach]. But the framework shows that [contrarian insight]."

Structure:

  • Challenge conventional wisdom
  • Explain why most approaches fail (using framework lens)
  • Present alternative pathway
  • Evidence from your framework
  • CTA: Ask if they've experienced this

Expected engagement: [High if insight is strong]


Visual Assets

Diagram location: [Path to visual in /visual-assets/ folder if applicable]

Visual description: [Describe the diagram - useful for recreating in posts]

When to use visuals:

  • Introduction posts (show full framework)
  • LinkedIn carousel (break down each component)
  • Workshop/webinar materials

Real-World Results

Document actual results from applying this framework:

Case 1: [Organization/Context]

  • Starting point: [Where they were]
  • Applied framework: [How]
  • Outcome: [Measurable result]
  • Timeline: [Duration]

Case 2: [Organization/Context]

  • Starting point: [Where they were]
  • Applied framework: [How]
  • Outcome: [Measurable result]
  • Timeline: [Duration]

Case 3: [Organization/Context]

  • [Same structure]

Aggregate impact: [Overall statistics if you have multiple implementations]


Common Misconceptions

What people get wrong about this framework:

  1. Misconception: [What they think]

    • Reality: [Actual truth]
    • Why it matters: [Implication]
  2. Misconception: [What they think]

    • Reality: [Actual truth]
    • Why it matters: [Implication]

Evolution of This Framework

Origin: [How you developed this - gives credibility]

Refinements over time:

  • Version 1.0: [Initial version]
  • Version 2.0: [What you changed based on real-world application]
  • Current version: [Latest insights]

Future development: [Where you're taking this next]


Integration with Other Frameworks

If this framework connects to or builds on other methodologies:

Complements: [Other frameworks it works with] Differs from: [What makes this unique vs. similar approaches] Can be combined with: [Synergistic frameworks]


Credibility Markers

When referencing this framework in posts, use these credibility indicators:

  • "Developed over [X] projects with [Y] organizations"
  • "Validated through [specific results]"
  • "Based on [research/analysis] of [data set]"
  • Avoid: "Revolutionary", "Game-changing", other hype

Authority stance: [How you position yourself - e.g., "Practitioner sharing what worked, not guru claiming universal truth"]


Update Log

  • [Date]: Created framework based on [initial observations]
  • [Date]: Refined after [new learnings/applications]
  • [Date]: Added [new component/insight]