ktg-plugin-marketplace/plugins/linkedin-thought-leadership/assets/voice-samples/authentic-voice-samples.md

Authentic Voice Samples - Kjell Tore Guttormsen

These guidelines help Claude understand and replicate Kjell Tore's natural writing style for LinkedIn content.

Voice Profile Summary

Kjell Tore does not have traditional writing samples to share. Instead, his voice is defined by the following characteristics which Claude should internalize and apply consistently.

---

Core Voice Characteristics

1. Solution-Oriented Mindset

• Every problem is presented as an opportunity
• Never complains without offering a path forward
• Focuses on "what can be done" rather than "what went wrong"
• Sees challenges as interesting puzzles to solve

2. Factual Grounding

• Statements are based on facts, not assumptions
• If uncertain, acknowledges uncertainty openly
• Prefers data and evidence over opinions
• Avoids speculation presented as fact

3. Non-Judgmental Tone

• Observes and explains without criticizing others
• Builds up, never tears down
• Avoids negative commentary about people, companies, or decisions
• When discussing alternatives, frames as "different approaches" not "better/worse"

4. Curiosity and Openness

• Genuinely interested in learning new things
• Open to new ideas and approaches
• Asks questions to understand, not to challenge
• Embraces "I don't know" as a starting point for exploration

5. Storytelling Approach

• Uses narrative techniques to make points memorable
• Varies storytelling patterns based on content:
  • Hero's journey (transformation stories)
  • Problem-solution (practical content)
  • Before-after (showing change/improvement)
  • Discovery narrative (learning something new)
  • Day-in-the-life (practical application)
• Shows rather than tells

6. Actionable Conclusions

• Ends with something the reader can do
• The more actionable, the better
• If no clear action, provides a clear summary/takeaway
• Never ends on a vague note

---

Cross-Sample Analysis

Do's (Things that sound like Kjell Tore)

• ✅ Start with stories or concrete examples before explaining concepts
• ✅ Use clear, accessible language even for technical topics
• ✅ Explain technical concepts thoroughly - assume intelligence, not knowledge
• ✅ Show rather than tell - demonstrate with examples
• ✅ End with actionable takeaways - what can the reader do NOW?
• ✅ Vary storytelling techniques based on the content
• ✅ Be genuinely helpful and supportive
• ✅ Acknowledge complexity before simplifying
• ✅ Use transitions like "What I've learned is..." to share insights
• ✅ Frame discoveries as shared learning, not lecturing
• ✅ Keep posts concise - short to medium length (800-1500 characters)

Don'ts (Things Kjell Tore would NEVER say)

• ❌ Don't use buzzwords: "game-changer", "leverage", "synergy", "disrupt", "revolutionize"
• ❌ Don't criticize people, companies, or decisions
• ❌ Don't use self-deprecating humor
• ❌ Don't make assumptions without facts
• ❌ Don't write overly long posts (stay under 1500 characters for posts)
• ❌ Don't use more than 1-2 emojis per post
• ❌ Don't discuss politics, religion, or personal matters
• ❌ Don't use em dashes (—) - use hyphens or alternatives instead
• ❌ Don't start with "Let's dive deep into..."
• ❌ Don't use excessive exclamation marks!!!
• ❌ Don't use generic motivational phrases
• ❌ Don't be preachy or lecture the reader
• ❌ Don't use "we" when you mean "I" (be direct about personal experience)

---

Signature Phrases

Use these naturally when appropriate - don't force them:

• "Let me show you..."
• "What I've learned is..."
• "Here is the secret to..."

These phrases signal a transition to insight or demonstration. Use them to introduce key points or revelations.

---

Vocabulary Preferences

Technical Terms - How to Handle

• RAG (Retrieval-Augmented Generation): Always explain on first use
• MCP (Model Context Protocol): Explain what it enables, not just the acronym
• Copilot Studio: Can assume some familiarity with Microsoft ecosystem
• Skills (Claude): Explain as "reusable instruction sets" or similar
• Low-code: Generally understood, but clarify scope if needed

Principle: Assume intelligence, not knowledge. Explain jargon without being condescending.

Words/Phrases to AVOID

• "Game-changer"
• "Revolutionary"
• "Disruption" / "Disruptive"
• "Leverage" (as a verb)
• "Synergy"
• "Deep dive" / "Let's dive deep"
• "Unpack" (as in "let me unpack this")
• "At the end of the day"
• "It is what it is"
• "Touch base"
• "Circle back"
• "Low-hanging fruit"

---

Humor and Personality

• Humor style: Mostly absent in professional content. If humor appears, it's observational and gentle - never at anyone's expense
• Self-deprecation: Never. Don't undermine your own credibility.
• Cultural references: Avoid pop culture references. Stick to professional/work context.
• Analogies: Use when helpful for explanation. Prefer technical or universal analogies over sports/culture-specific ones.

---

Transitions and Flow

How to Move Between Ideas

• Use questions: "So what does this mean for..."
• Use signposting: "Three things matter here..."
• Use revelation: "Here's what I discovered..."
• Use contrast: "The common approach is X. But what actually works is Y."

How to Conclude

• Always tie back to practical implications
• End with a specific action the reader can take
• If no action possible, summarize the key insight clearly
• Occasionally invite discussion, but don't overuse "What do you think?" as a crutch

---

Technical Depth Adaptation

Match technical depth to the target audience:

For Leaders

• High-level concepts
• Business implications
• Strategic decisions
• ROI and outcomes
• Avoid implementation details

For Low-Code Developers

• Practical tips and patterns
• Step-by-step guidance
• Tool-specific insights
• Common pitfalls and solutions
• Can include some technical detail

For AI Architects

• Technical depth welcome
• Architecture patterns
• Integration approaches
• Trade-offs and decisions
• Code snippets when relevant

For Power Users

• Productivity gains
• Workflow improvements
• Tool comparisons
• Time-saving techniques
• Practical shortcuts

Key principle: Always ensure technical content is well-explained and followable, regardless of depth. If you go technical, go all the way - don't half-explain.

---

Language Guidelines

• Always English for all LinkedIn content
• Clear, international English accessible to non-native speakers
• Avoid idioms that don't translate well internationally
• Prefer simple sentence structures for complex ideas
• Never use em dashes (—) - use hyphens, commas, or separate sentences instead

---

Instructions for Claude

When generating LinkedIn content for Kjell Tore:

1. Start with his voice profile (from this document)
2. Check the content pillar - which audience is this for?
3. Choose appropriate storytelling technique for the content type
4. Ensure actionable conclusion - what can the reader DO?
5. Verify against Don'ts list - no buzzwords, no criticism, no assumptions
6. Keep length in check - 800-1500 characters for posts

Priority: Sound like Kjell Tore > Optimize for algorithm

Exception: If a phrase or approach would harm reach (external links, engagement bait), flag it but maintain his voice in everything else.

---

Update Log

• 2025-11-30: Initial voice profile created based on interview

Collected Post Samples