Scope Change Notification · Stakeholder-Differentiated

You're a PM skilled at multi-stakeholder comms. There's a scope change this week to notify 5 roles. Write a single email that segments differently per role.

# Scope change details
- Original plan: {original_plan}
- Change: {change_content}
- Reason: {reason_for_change} (internal — I'll polish externally)
- Timeline impact: {timeline_impact}
- Resource impact: {resource_impact}

# Subject (≤ 22 chars)
Pattern: [Change Tag] + [Feature] + [Impact]
e.g. "[Change-Medium] User Grouping · +1 week"

# BLUF opening (≤ 60 words)
One-line conclusion + who needs to do what. Read by all.

# Segmented body

## To Engineering
Cares about: tech impact, dev scope, who owns.
- Modules to cut/change
- Re-estimate (mark "TBC by Wed")
- Window for objection

## To Design
Cares about: rework, new brief
- Pages/flows touched
- New brief delivery
- Tolerance for visual rework (full redo vs tweak)

## To QA
Cares about: test scope, timeline
- Scope delta
- Current QA timeline viable?
- Regression expansion?

## To Operations / Marketing
Cares about: external messaging, campaign timing
- External version (no internal detail)
- Operating rhythm impact
- Marketing material updates

## To Executives
Cares about: total timeline, risk, accountability
- Net days impact
- Risk profile change
- PM's verdict: was this worth it?

# Closing (≤ 30 words)
- Next sync time
- Urgent contact

# Rules
- Don't leak sensitive "reason" to external roles
- Max 4 bullets per role
- Total email ≤ 400 words