Syntic

Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.

C-Level AdvisoryFree Safe

internal-narrative

Security Scan Summary

Status: Safe

Source: Syntic Skills registry

Automated security scan completed with no high-risk patterns detected. Manual review is still required.

About This Skill

Use when preparing investor updates, all-hands, board communications, recruiting narratives, or crisis communications, or when messaging is inconsistent across employees, investors, and customers.

Downloadable SKILL.md

Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.

SKILL.md
---
name: internal-narrative
description: Use when preparing investor updates, all-hands, board communications, recruiting narratives, or crisis communications, or when messaging is inconsistent across employees, investors, and customers.
category: C-Level Advisory
version: 1.0.0
tools: []
---

# Internal Narrative Builder

One company, many audiences, same truth — different lenses. Narrative inconsistency erodes trust. Build and maintain coherent communication across every stakeholder group: employees, investors, customers, candidates, partners.

## Core Principle

The same fact lands differently depending on who hears it and what they need. "We're shifting resources from Product A to Product B" means:
- To employees: "Is my job safe? Why are we abandoning what I built?"
- To investors: "Smart capital allocation — doubling down on the winner"
- To customers of Product A: "Are they abandoning us?"
- To candidates: "Exciting new focus — are they decisive?"

Same fact, four narratives. Maintain truth while serving each audience's actual question.

## Framework

### Step 1: Build the Core Narrative
One paragraph every other communication derives from — the source of truth.

Template: "[Company] exists to [mission — present tense, specific]. We're building [what] because [problem]. Our approach is [unique method]. We're at [honest current state] and heading toward [concrete destination]."

Good example: "Acme Health exists to reduce preventable falls in elderly care using smartphone-based mobility analysis. We're building an AI diagnostic tool for care teams because current fall risk assessments are subjective, infrequent, and often wrong. Our approach — a 10-second walking test via phone camera — needs no new hardware, no specialist. We have 80 care facilities in DACH paying €800K ARR, heading to €3M ARR before Series B."

Bad example (says nothing): "Acme Health is an innovative AI company revolutionizing elderly care through cutting-edge technology."

### Step 2: Audience Translation Matrix
Translate the core narrative per audience — same truth, different frame.

| Fact | Employees | Investors | Customers | Candidates |
|---|---|---|---|---|
| 80 customers | "We've proven the model — your work matters" | "PMF signal, capital efficient" | "80 facilities trust us" | "Traction you'd be joining" |
| Pivoted from hardware | "Honest enough to change course" | "Capital-efficient pivot, better unit economics" | "Faster, simpler way to serve you" | "We decide on evidence, not ego" |
| Missed Q2 revenue | "Here's why, here's the plan" | "Revenue mix shifted — trailing indicator improving" | usually not shared | usually not shared |
| Hiring fast | "Team growing — your network matters" | "Headcount aligned to growth" | not relevant | "Rocket ship moment" |

Rules: never contradict yourself across audiences — different framing ≠ different facts. "Told investors growth, told employees efficiency" is a contradiction to audit for. Investors and employees see each other; board members talk to your team; candidates google you.

### Step 3: Contradiction Detection
Before any major communication: what did we tell investors last month about [topic]? What did we tell employees? Are these consistent — if not, which version is true?

Common contradictions: "efficient growth" to investors + "hiring aggressively" to candidates; "strong pipeline" to investors + "sales struggling" at all-hands; "customer-first" culture + decisions that clearly prioritized revenue.

When caught: fix the less accurate version, then communicate the correction explicitly — "Last month I said X. After reflection, X isn't quite right. Here's the clearer version." Self-correction builds more trust than getting caught.

### Step 4: Communication Cadence by Audience
| Audience | Format | Frequency | Owner |
|---|---|---|---|
| Employees | All-hands | Monthly | CEO |
| Employees | Team updates | Weekly | Team leads |
| Investors | Written update | Monthly | CEO + CFO |
| Board | Meeting + memo | Quarterly | CEO |
| Customers | Product updates | Per release | CPO/CS |
| Candidates | Careers page + interview narrative | Ongoing | CHRO + Founders |
| Partners | Business review | Quarterly | BD Lead |

### Step 5: All-Hands Principles
Lead with the honest state of the company — no spin. Connect company performance to individual work ("here's how what you built contributed"). Give people a reason to be proud of working here. Leave real time for unscreened Q&A.

Failure modes: CEO speaks 55 of 60 minutes with Q&A as an afterthought; all good news all the time (employees detect dishonesty); metrics without context ("ARR grew 15%" without saying if that's good or expected); deflected questions never followed up.

### Step 6: Crisis Communication
The 4-hour rule: if something is public or about to be, communicate internally within 4 hours. Employees should never learn company news from Twitter.

Hour 0–4 (internal first): a leader sends a message acknowledging what happened factually, states what's known and unknown, what's being done, and what people should say if asked.

Hour 4–24 (external if needed): a statement only if the event is public, consistent with the internal message, with legal review if liability is involved.

Avoid: silence (rumors fill the vacuum), spin (detectable, destroys trust), "no comment" (signals concealment), blaming (audience only cares what you're doing about it).

Template: "Here's what happened: [facts]. Here's what we know: [known]. Here's what we don't know yet: [uncertainty]. Here's what we're doing: [actions]. Here's what you should say if asked: [guidance]. I'll update you by [time]."

## Narrative Consistency Checklist
Before any major external communication: consistent with what we told investors last month? Consistent with the last all-hands? Contradicts anything on the website, careers page, or press releases? Would an employee recognize the company being described? Would an investor find the internal deck inconsistent? Are we describing current state accurately, or projecting an aspiration?

## Key Questions
Could a new employee explain to a friend why the company exists? What do we tell investors about strategy vs. employees — same? If team members described the company independently to a journalist, would they agree? When did we last update the "why we exist" story — still true? What's the hardest question from each audience, and do we have an honest answer?

## Red Flags
Departments describe the mission differently. Investor narrative emphasizes growth while employee narrative emphasizes stability (or vice versa). All-hands are mostly one-way slides. Q&A is screened or deflected. Bad news reaches employees via Slack rumor before leadership communicates. Careers page describes a culture employees don't recognize.

## Cross-Functional Coordination
- Investor update prep: with the CFO, align financial and company narrative
- Reorg/leadership change: with the CHRO and CEO, sequence employees first, then external
- Product pivot: with the CPO, align customer communication with the investor story
- Culture change: ensure internal story matches external employer brand
- M&A/partnership: with the CEO and COO, control information flow, prevent narrative leaks
- Crisis: all leadership speaks with a single voice, internal first

Bundle Download

Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.

Install Targets

Syntic App

  1. 1. Create a dedicated folder for this skill in your local skills library.
  2. 2. Place SKILL.md into that folder.
  3. 3. Restart Syntic and invoke this skill on matching tasks.

Syntic Code (CLI)

  1. 1. Save SKILL.md in your local Syntic Code skills directory.
  2. 2. Keep related files in the same skill folder.
  3. 3. Run in a safe environment and validate outputs.

Source

https://github.com/alirezarezvani/claude-skills/blob/main/c-level-advisor/skills/internal-narrative/SKILL.md

Open Source Link
C-Level Advisory

Related Skills