Skill: stakeholder-pulse

Skill: stakeholder-pulse

Purpose

Design and interpret a quick stakeholder pulse survey to measure confidence, satisfaction, and trust in the delivery team — and identify issues before they escalate.

When to Use

• After a difficult delivery or delay
• Monthly as a health check
• Before a major release or steering committee

Framework: Stakeholder Pulse Survey

Step 1 — Survey Design (5 Questions Max)

Question 1 — Overall Confidence (1–5 scale)

"How confident are you that the [release/programme] will deliver its committed outcomes?" 1 = Not confident at all → 5 = Very confident

Question 2 — Communication Quality (1–5 scale)

"How satisfied are you with the frequency and clarity of delivery updates?" 1 = Very dissatisfied → 5 = Very satisfied

Question 3 — Issue Response (1–5 scale)

"When issues arise, how effectively does the delivery team respond?" 1 = Very ineffectively → 5 = Very effectively

Question 4 — Open Text — What's Working

"What is the delivery team doing well?"

Question 5 — Open Text — Improvement

"What is one thing the delivery team could do better?"

Step 2 — Distribution

• Keep it anonymous for honest feedback
• Share via email or Confluence — 2-minute completion time
• Send on a consistent cadence (e.g., last Friday of month)

Step 3 — Interpret Results

Average Score	Interpretation	Action
4.5–5.0	🟢 Excellent	Maintain and share success
3.5–4.4	🟡 Good	Address specific concerns
2.5–3.4	🟠 Needs attention	Stakeholder 1:1s recommended
< 2.5	🔴 Critical	Immediate recovery action

Step 4 — Response Template

After receiving results, send a short "You said, we heard, we'll do" response:

"Thank you for your feedback. Here's what we heard and what we're doing:

• You said: [theme from open text]
• We heard: [interpretation]
• We'll do: [specific action]"

Output Format

1. Survey (ready to send)
2. Interpretation guide
3. Response template
4. Suggested next command: /expectations-reset or /status-update