linkedin-studio/assets/case-studies/case-study-template.md
Kjell Tore Guttormsen d15ffa4e03 fix(linkedin-studio): S29d terminology-scrub — "thought leadership" → neutral (skills/config/assets/hooks-test)
Fourth sub-pass of the S29 plugin-wide terminology scrub: the banned brand phrase
"thought leadership" (FORM A) removed from the remaining surfaces — skills, a config template,
shipped assets, and a test fixture. 8 edits across 6 files. Vocabulary consistent with
S29a-S29c: "thought leadership angle(s)" -> "content angle(s)"; the "Value Test" family ->
"Authority Value Test"; "Standard Thought Leadership Post" -> "Standard Post" (matches the
S29a/S29c "Standard Post Structure" equivalent).

Edits: skills/linkedin-content-creation (3) "Identify Thought Leadership Angles" -> "Content
Angles", "Standard Thought Leadership Post" -> "Standard Post", "The 8 Thought Leadership
Angles" -> "The 8 Content Angles"; skills/linkedin-strategy:176 phase-focus cell "Thought
leadership, cross-platform" -> "Signature content, ..." (avoids the Authority-phase column
echo); config/user-profile.template:35 "Build thought leadership & authority" -> "Build
authority & influence"; assets/checklists/quality-scorecard:136 "Passes thought leadership
test" -> "Passes Authority Value Test"; assets/case-studies/case-study-template:173 "Best for:
Thought leadership" -> "Authority content"; hooks/scripts/__tests__/clipboard-helper.test:61
unicode fixture "Thought leadership" -> "Authority" (emoji + arrow retained; coverage unchanged).

Scope (operator-locked, inherits S29a-S29c): FORM A only. FORM B = 8 untouched -- the 5
buzzword-denylist entries MUST list the banned word ("thought leader"), plus 3 role usages
(linkedin-networking x2, README "niche thought leaders"). The 21 thought-leadership-angles.md
filename pointers deferred to S29e. No anchor links to the changed headers anywhere in the
plugin. Forward-looking docs already clean.

Verify: FORM A in scope = NONE; FORM B unchanged (8); filename pointers unchanged (21);
clipboard-helper test 13/0; gate 81/0/0; counts 29/19/26/6 + v0.5.0 unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qgzo6rxthw7KuxHjn5vyE
2026-06-20 06:19:10 +02:00

5.8 KiB

Case Study: [Project Name / Organization]

Real examples from your work provide credibility and specificity that generic scenarios can't match. Use this template to document case studies Claude can reference in posts.


Case Study Overview

Project name: [e.g., "RAG Implementation at [Organization]"]
Organization type: [e.g., "Large public sector organization, 5000+ employees"]
Industry: [e.g., "Government / Transportation"]
Timeline: [e.g., "January - June 2024 (6 months)"]
Your role: [e.g., "AI Advisor, led implementation"]

One-sentence summary: [e.g., "Implemented contextual retrieval RAG system that reduced manual document processing time by 40% while improving answer accuracy."]


The Challenge

Business Context

[What was happening in the organization that created the need?]

  • [Context point 1]
  • [Context point 2]

Specific Problem

[What specific pain point were you solving?]

  • Symptom 1: [Observable problem]
  • Symptom 2: [Observable problem]
  • Root cause: [What was actually driving the symptoms]

Why It Mattered

  • Impact on operations: [How problem affected daily work]
  • Cost/time implications: [Quantifiable impact if available]
  • Strategic importance: [Why leadership cared]

Previous Attempts

[What had they tried before that didn't work?]

  • Attempt 1: [What they did] → [Why it failed]
  • Attempt 2: [What they did] → [Why it failed]

The Approach

Initial Assessment

[How you diagnosed the situation]

  • Key finding 1: [What you discovered]
  • Key finding 2: [What you discovered]
  • Strategic decision: [Based on findings, what approach did you choose?]

Solution Design

[What you built/implemented - be specific]

Architecture:

  • [Component 1 and why]
  • [Component 2 and why]
  • [Component 3 and why]

Key decisions:

  1. [Decision 1 - e.g., "Used Azure AI Search vs. building custom"]

    • Why: [Rationale]
    • Trade-off: [What you gave up]
  2. [Decision 2]

    • Why: [Rationale]
    • Trade-off: [What you gave up]

Implementation Timeline

  • Week 1-2: [Phase 1 activities]
  • Week 3-6: [Phase 2 activities]
  • Week 7-12: [Phase 3 activities]
  • Ongoing: [Maintenance/iteration]

Challenges Encountered

Challenge 1: [What went wrong]

  • How we addressed it: [Solution]
  • Learning: [What you'd do differently]

Challenge 2: [What went wrong]

  • How we addressed it: [Solution]
  • Learning: [What you'd do differently]

The Results

Quantitative Outcomes

  • [Metric 1]: [Before] → [After] ([X%] improvement)
  • [Metric 2]: [Before] → [After] ([X%] improvement)
  • [Metric 3]: [Before] → [After] ([X%] improvement)

ROI: [If calculable - cost vs. benefit]

Qualitative Outcomes

  • User feedback: [What people said]
  • Process improvements: [Non-quantifiable benefits]
  • Capability development: [New skills/capacities gained]

Unexpected Benefits

[Things you didn't anticipate but that emerged]

  • [Benefit 1]
  • [Benefit 2]

Key Learnings

What Worked

  1. [Tactic/approach]: [Why it was effective]
  2. [Tactic/approach]: [Why it was effective]
  3. [Tactic/approach]: [Why it was effective]

What Didn't Work

  1. [Approach that failed]: [Why + what you learned]
  2. [Approach that failed]: [Why + what you learned]

Non-Obvious Insights

[The lessons that only came from doing the work]

  • [Insight 1]
  • [Insight 2]
  • [Insight 3]

Replicable Patterns

[What from this case can transfer to other contexts?]

  • [Pattern 1]
  • [Pattern 2]

LinkedIn Post Angles

Angle 1: Results-First Post

Hook: "We reduced [metric] by [X%] in [timeframe]. Here's the system we built..."

Structure:

  • Lead with compelling result
  • Brief context (the challenge)
  • High-level solution overview
  • 1-2 key decisions that mattered most
  • CTA: Ask if they face similar challenge

Best for: Building credibility, attracting similar opportunities


Angle 2: Before/After Transformation

Hook: "Six months ago, [organization] was [painful situation]. Today, [transformed situation]. Here's what changed..."

Structure:

  • Paint the before picture
  • Turning point / moment of decision
  • The intervention
  • The after state
  • Key enabler of transformation
  • CTA: Ask where others are in similar journey

Best for: Storytelling, emotional engagement


Angle 3: Single Decision Deep-Dive

Hook: "The decision to [specific choice] was controversial. Here's why it was right..."

Structure:

  • The decision point
  • Arguments against
  • Why we chose it anyway
  • How it played out
  • What we learned
  • CTA: Ask what others would have done

Best for: Authority content, showing expertise


Angle 4: Failure Lessons

Hook: "[Approach] should have worked. It didn't. Here's what we learned..."

Structure:

  • What we tried that failed
  • Why we thought it would work
  • What actually happened
  • The pivot
  • The learning
  • CTA: Ask if others have failed similarly

Best for: Authenticity, building trust through vulnerability


Confidentiality & Permissions

Public information: [What can be shared freely] Anonymized information: [What can be shared if org name removed] Confidential: [What cannot be shared] Permission level: [What you've been cleared to discuss publicly]

Client approval: [Date if you got explicit permission to use as case study]


Supporting Materials

Screenshots/diagrams: [If available, note location] Metrics dashboard: [If you have data visualization] Testimonials: [If you have quotes from stakeholders] Press coverage: [If project was publicly recognized]


Update Log

  • [Date]: Initial case study documentation
  • [Date]: Added outcome metrics after 6-month mark
  • [Date]: Updated with long-term results