# Stakeholder Communication — Quiz

## Question 1

The pyramid principle suggests you should:

A) Bury the conclusion at the end
B) Lead with the conclusion, then support it
C) Use only bullet points
D) Never mention risks

<!-- ANSWER: B -->
<!-- EXPLANATION: The pyramid principle means putting the most important point first. Busy stakeholders often skim; if they read only the first line, they should get the takeaway. Support with details below. -->

## Question 2

In RAG status, Amber typically means:

A) Everything is perfect
B) At risk; issues exist; we're working on them
C) Project is cancelled
D) No update this week

<!-- ANSWER: B -->
<!-- EXPLANATION: Amber = at risk. There are issues, but the team is addressing them. It needs attention but isn't yet Red (off track). Amber is common and appropriate when managing risks. -->

## Question 3

When communicating bad news (e.g., a delay), you should:

A) Wait until you have a full solution
B) Communicate early, state the fact, explain cause, share plan
C) Send it only to your manager
D) Use vague language to soften the blow

<!-- ANSWER: B -->
<!-- EXPLANATION: Bad news does not improve with age. Communicate early. Be clear: state the fact, explain why, say what you're doing, and what you need. Early communication creates more options and preserves trust. -->

## Question 4

In a power/interest stakeholder grid, a high-power, high-interest stakeholder should be:

A) Monitored only
B) Kept satisfied with minimal contact
C) Managed closely—regular, rich updates
D) Excluded from updates

<!-- ANSWER: C -->
<!-- EXPLANATION: High power + high interest = manage closely. They have influence and care. They need regular, substantive updates and involvement in decisions. Keep them informed and engaged. -->

## Question 5

An effective status update structure includes:

A) Only what was completed
B) What happened, what's next, blockers, risks
C) Jira ticket IDs and technical details only
D) A maximum of one sentence

<!-- ANSWER: B -->
<!-- EXPLANATION: A good status answers four questions: What happened? What's next? What are the blockers? What are the risks? This structure gives stakeholders a complete picture without overwhelming them. -->

## Question 6

To avoid information overload in status updates, you should:

A) Include every detail in the main email
B) Use one page max for exec summaries, bullets over paragraphs, link to details
C) Send daily 10-page reports
D) Never use written updates

<!-- ANSWER: B -->
<!-- EXPLANATION: Respect your reader's time. One page max for exec summaries. Prefer bullets over paragraphs. Link to detailed docs or tickets rather than inlining everything. Consistent format helps people scan quickly. -->