Stakeholder Communication

---
name: stakeholder-communication
version: "1.0"
description: Frameworks and templates for stakeholder-specific communications. Covers tone calibration by audience, escalation memos, decision requests, status updates, meeting follow-ups, and Japanese business communication conventions.
tags: ["communication", "stakeholders", "memos", "email"]
---

# Stakeholder Communication Skill

## When to use this skill

Use when drafting any communication that goes to a specific stakeholder: emails, memos, updates, decision requests, or meeting follow-ups. The right tone and structure depends on the audience.

## Communication framework by influence level

### Decision makers (influence: decision_maker)

These people have limited time and full authority. They need:
- **Lead with the ask or decision** - first sentence, not buried in context
- **Situation in 2-3 sentences** - what changed or what is at stake
- **Options** (if applicable) - two minimum, with a clear recommendation
- **Your recommendation and rationale** - one paragraph, direct
- **Next step from them** - one specific action, with a deadline

Length: one page maximum for written communications.

### Influencers (influence: influencer)

These people shape decisions without formal authority. They need:
- **Acknowledgment of their perspective** - show you understand what matters to them
- **How this affects their area** - direct relevance, not general context
- **Your recommendation** - with an invitation for their input before it is finalized
- **What you need from them** - specific, time-bound

Length: conversational. Prefer brief and direct over comprehensive.

### Informed stakeholders (influence: informed)

These people receive updates but do not decide. They need:
- **Summary only** - the outcome and what it means for them
- **What (if anything) they need to do** - be explicit if nothing is required
- No detail they did not ask for

Length: short. Often a single paragraph or 3-4 bullet points.

### Executors (influence: executor)

These people carry out decisions. They need:
- **Clear action and deliverable** - exactly what is expected
- **Timeline and deadline** - specific dates
- **Owner and escalation path** - who to contact if blocked
- **Success criteria** - how they know they are done

Length: brief and unambiguous. Bullet format preferred.

### Sponsors (influence: sponsor)

These people have made a commitment and need accountability. They need:
- **Progress against commitment** - specific, measurable
- **Any risks to the commitment** - surfaced early, not when it is too late
- **What you need from them** - only if relevant; otherwise reassurance is enough

Length: brief update format. Monthly or at major milestones.

## Communication templates

### Escalation memo

```
TO: [Recipient]
FROM: [Sender]
SUBJECT: [Topic] - Decision Required by [Date]
CONFIDENTIALITY: [level]

SITUATION
[2-3 sentences: what happened and why it matters]

DECISION REQUIRED
[One clear question the recipient must answer]
Deadline: [Date]

OPTIONS
Option A: [Description] - [Key implication]
Option B: [Description] - [Key implication]

RECOMMENDATION
[Option] is recommended because [1-2 reasons, specific to this person's priorities].

NEXT STEP
Please confirm your decision by [date] to [sender] so we can [consequence of decision].
```

### Decision request

```
SUBJECT: Decision needed: [topic] - by [date]

[Name],

I need your decision on [topic] by [date] to keep [project/initiative] on track.

Background (30 seconds): [2 sentences max]

Options:
- Option A: [description + key trade-off]
- Option B: [description + key trade-off]

My recommendation: Option [X] because [one reason tied to what matters to this person].

If I do not hear back by [date], I will proceed with [default action].

[Sender]
```

### Status update

```
SUBJECT: [Project] update - [date]

[Name],

Quick update on [project]:

Status: [GREEN / AMBER / RED]
- [Milestone]: [Done / On track / At risk] - [1 sentence]
- [Milestone]: [Done / On track / At risk] - [1 sentence]
- [Milestone]: [Done / On track / At risk] - [1 sentence]

[If AMBER or RED]: [What is at risk and what we are doing about it - 1-2 sentences]

Next update: [date or trigger]

[Sender]
```

### Meeting follow-up

```
SUBJECT: Follow-up: [Meeting name] - [date]

[Name],

Thank you for the time today. Key outcomes:

Decisions made:
- [Decision 1]
- [Decision 2]

Actions:
- [Action] — [Owner] — [Due date]
- [Action] — [Owner] — [Due date]

Open items (no decision yet):
- [Item] — revisit on [date]

[Sender]
```

## Tone calibration by audience

| Audience | Tone | Avoid |
|----------|------|-------|
| Board / C-suite | Crisp, confident, data-backed | Hedging, excessive caveats, jargon |
| Peers / direct reports | Clear, direct, collegial | Overly formal language, passive voice |
| External clients | Professional, client-centric | Internal jargon, assumptions |
| Japanese counterparts | Formal, deferential to seniority | Directness that skips context, blunt refusals |

## Japanese business communication notes

When communicating with Japanese colleagues, partners or clients:

### Keigo (敬語) register
- **Sonkeigo (尊敬語)**: Use when speaking about the actions of someone senior to you
- **Kenjōgo (謙譲語)**: Use to describe your own actions humbly when addressing someone senior
- **Teineigo (丁寧語)**: Standard polite form (desu/masu); appropriate for most business written communication

### Nemawashi (根回し)
Before a formal decision is requested, key stakeholders should be consulted individually and informally. This process of building consensus in advance is expected and skipping it can be perceived as disrespectful. For any significant decision involving Japanese stakeholders, plan for a nemawashi phase before the formal request.

### Practical conventions
- Open with a seasonal greeting in formal letters: 「時下ますますご清栄のこととお喜び申し上げます」
- Use the recipient's name with "san" (さん) or their title for senior executives
- Do not open with personal pleasantries in email; go to substance after the greeting
- Avoid direct refusals; use softened language that conveys the difficulty without a blunt "no"
- Confirm understanding explicitly; do not assume silence is agreement