Stakeholder Communication Prompt Templates

Executive Status Update
CRM Implementation

Date: October 15, 2024
Status: 🟡 AT RISK

---

**BOTTOM LINE**

We may need to delay go-live by 1 week OR add training resources. Decision needed by Friday to stay on track.

---

**STATUS SUMMARY**

| Workstream | Status | Notes |
|------------|--------|-------|
| Data Migration | ✅ Complete | 100% of records transferred, validated |
| System Configuration | ✅ Complete | All workflows built and tested |
| User Training | 🟡 Behind | 1 week delay due to trainer availability |
| Go-Live Prep | 🟢 On Track | Contingent on training completion |

---

**KEY UPDATES**

✓ Data migration completed successfully, 2M records transferred with 99.8% accuracy
✓ Vendor support issue (ticket delays) resolved, escalation was effective
✗ Training delayed 1 week, external trainer had scheduling conflict

---

**RISK**

| Risk | Impact | Mitigation Options |
|------|--------|--------------------|
| Training delay affects go-live | Go-live slips from Nov 1 → Nov 8 | Option A: Delay go-live 1 week<br>Option B: Add second trainer ($5K) to compress schedule |

---

**DECISION NEEDED**

To maintain November go-live, we need approval by Friday (Oct 18) for one of:

**Option A: Delay go-live to November 8**
- Cost: None
- Impact: 1 week delay to realizing CRM benefits

**Option B: Add training resources ($5K)**
- Cost: $5,000 for second trainer
- Impact: Maintains Nov 1 go-live

**Recommendation**: Option B, the cost is minor compared to a week's delay in CRM adoption.

---

**NEXT UPDATE**: October 22 (or sooner if decision changes timeline)

---

Questions? Contact [PM Name] directly.

Subject: CRM Project, Budget Discussion Needed

Hi [Sponsor Name] and [Finance Lead],

I need to discuss the CRM project budget with you. We're projecting a $50,000 (25%) overrun, and I want to walk you through what happened, what options we have, and get your guidance.

**The Situation**

Our original budget was $200,000. Current projection is $250,000.

| Category | Original | Current | Variance |
|----------|----------|---------|----------|
| Software licenses | $80,000 | $80,000 | $0 |
| Implementation services | $70,000 | $95,000 | +$25,000 |
| Data migration | $30,000 | $45,000 | +$15,000 |
| Training | $20,000 | $30,000 | +$10,000 |
| **Total** | **$200,000** | **$250,000** | **+$50,000** |

**What Happened**

Three factors drove the overrun:

1. **Data migration complexity** (+$15K): Our legacy data had more inconsistencies than the initial assessment identified. Cleaning this data took 50% longer than planned.

2. **Additional customization** (+$25K): During configuration, we discovered that two workflows weren't possible with standard features, requiring custom development.

3. **Extended training** (+$10K): User proficiency testing showed we needed an additional training round, which we added to ensure adoption.

**What I Could Have Done Differently**

I should have flagged the data migration issue earlier. We saw signs in week 3 but didn't escalate until week 5. Earlier escalation would have given us more options.

**Our Options**

| Option | Description | Pros | Cons |
|--------|-------------|------|------|
| A: Approve additional $50K | Continue as planned | Full scope delivered, on timeline | Budget impact |
| B: Reduce scope by $50K | Cut custom workflows, reduce training | Stays in budget | Reduced functionality, adoption risk |
| C: Delay go-live by 4 weeks | Spread costs across quarters | Partial budget relief | Delays benefits realization |

**My Recommendation**

Option A. The customizations address real workflow needs, and cutting training risks the adoption we need to see ROI. The $50K overrun is significant but represents 8% of the annual value we project from this system.

However, I want your input before proceeding.

**Next Steps**

Can we meet Thursday to discuss? I can walk through the detailed numbers and get your decision.

I'm available:
- Thursday 10am or 2pm
- Friday 9am

I take responsibility for not escalating sooner and am committed to tighter monitoring for the remainder of the project.

[PM Name]
[Phone]

Subject: Product Launch Date, Alignment Needed by Friday

Hi [Engineering Lead], [Marketing Lead], and [VP Product],

We have a conflict on the product launch date that we need to resolve this week. I'm writing to ensure we're all working from the same information and can make a joint decision.

---

**THE MISALIGNMENT**

| Stakeholder | Position | Basis |
|-------------|----------|-------|
| Marketing | November 1 | Press release drafted, influencer briefings scheduled, ad spend committed |
| Engineering | November 15 | Current velocity, remaining work, QA time needed |

Gap: 2 weeks

---

**WHAT'S DRIVING EACH POSITION**

**Marketing's constraints:**
- $30K in ad spend committed for Nov 1-7 window
- Press embargo lifts Nov 1 (rescheduling has relationship cost)
- Black Friday timing depends on Nov 1 launch

**Engineering's constraints:**
- 3 critical features incomplete
- QA needs 5 days minimum (non-negotiable for quality)
- Team already at 110% capacity

---

**OPTIONS**

| Option | Description | Cost/Risk |
|--------|-------------|----------|
| A: Delay marketing to Nov 15 | Align to engineering timeline | $30K ad spend reallocation, press reschedule |
| B: Add engineering resources | Bring in 2 contractors | $25K + quality risk from new team members |
| C: Reduce launch scope | Ship with 2 of 3 features | Feature Y launches in v1.1 (Nov 22) |
| D: Accept risk | Launch Nov 1 with compressed QA | Quality risk, potential customer issues |

---

**MY RECOMMENDATION**

**Option C: Reduce launch scope**

Rationale:
- Feature Y is the lowest-impact of the three (usage data from beta)
- Allows Nov 1 launch protecting marketing investment
- Gives engineering achievable timeline without burnout
- Feature Y follows 3 weeks later, still before holiday peak

I've validated with engineering that Features X and Z can ship Nov 1 with full QA if we defer Y.

---

**WHAT I NEED FROM EACH OF YOU**

- **[Engineering Lead]**: Confirm Nov 1 is achievable for Features X and Z with standard QA
- **[Marketing Lead]**: Assess whether launch messaging works without Feature Y
- **[VP Product]**: Make the final call on scope if we can't align

---

**PROPOSED PATH TO RESOLUTION**

- **Today (Tues)**: Engineering and Marketing confirm constraints above
- **Wed 10am**: 30-minute meeting to discuss options (invite attached)
- **Wed EOD**: Decision made
- **Thursday**: Update all teams on confirmed plan

Please reply confirming you can attend Wednesday or suggest an alternative.

[PM Name]

Subject: Launching Website Accessibility Project, What to Expect

Hi team,

I'm kicking off a project to make our website fully accessible to users with disabilities. This email explains what we're doing, why it matters, and how it might involve you.

---

**WHAT WE'RE DOING**

Over the next 12 weeks, we'll audit our website against WCAG 2.1 AA accessibility standards and fix any issues we find.

**Timeline:**
- Weeks 1-3: Audit (automated scans + manual review)
- Weeks 4-10: Remediation (fixing identified issues)
- Weeks 11-12: Validation and documentation

**Target completion:** January 15, 2025

---

**WHY THIS MATTERS**

1. **Legal compliance**: Accessibility lawsuits in our industry increased 300% last year. Proactive compliance protects us.

2. **Better user experience**: Accessibility improvements benefit everyone, clearer navigation, better mobile experience, improved SEO.

3. **Market reach**: 15% of users have some form of disability. Accessible design reaches more customers.

---

**WHO'S INVOLVED**

| Role | Name | Responsibility |
|------|------|----------------|
| Project Lead | [PM Name] | Overall coordination, reporting |
| Technical Lead | [Dev Name] | Code remediation |
| Design Lead | [Designer Name] | Design updates, color contrast |
| Content Lead | [Content Name] | Alt text, content structure |
| Legal Liaison | [Legal Name] | Compliance validation |

---

**HOW THIS MIGHT AFFECT YOU**

**Marketing**: We may need to update some images and documents. We'll coordinate any changes that affect live campaigns.

**Content teams**: You'll receive guidelines for creating accessible content going forward.

**Department heads**: Your web pages will be audited. We'll share findings and may need your input on prioritization.

**Everyone**: Training on accessibility basics will be offered (optional but encouraged).

---

**WHAT TO EXPECT FROM ME**

- **Weekly email updates** (Fridays) with progress summary
- **Monthly stakeholder meeting** for detailed review
- **Direct outreach** if we need your input on specific pages

---

**HOW TO GET INVOLVED**

1. **Questions or concerns**: Reply to this email or contact me directly
2. **Pages to prioritize**: If you have high-traffic pages that need attention first, let me know
3. **Accessibility training interest**: Let me know if you'd like to attend the optional training session (November TBD)

---

**NEXT STEPS**

No action needed from you right now. The audit begins next Monday, and I'll share initial findings in the Week 3 update.

If you have questions before then, my door is open.

[PM Name]
[Email] | [Phone] | [Calendar link for office hours]

Subject: New Expense System Launching Nov 1, Training Required by Oct 28

Hi everyone,

Starting November 1, we're replacing our paper expense process with a new digital system. This email covers what's changing, why, and what you need to do.

---

**TL;DR**

- **New system launches**: November 1
- **Old process ends**: November 15
- **Action needed**: Complete 15-minute training by October 28
- **Result**: Reimbursements in 3 days instead of 2 weeks

---

**WHAT'S CHANGING**

| Aspect | Old Process | New Process |
|--------|-------------|-------------|
| Submission | Paper forms + receipts | Mobile app or web portal |
| Receipt handling | Physical copies | Photo upload from phone |
| Approval | Email chains | In-app approval workflow |
| Reimbursement time | ~2 weeks | ~3 business days |
| Expense tracking | Manual spreadsheets | Real-time dashboard |

---

**WHY WE'RE MAKING THIS CHANGE**

The current process has pain points for everyone:
- **For you**: Slow reimbursements, lost receipts, confusing forms
- **For managers**: Approval requests buried in email
- **For finance**: Manual data entry, reconciliation errors

The new system addresses all of these while also improving our expense visibility and policy compliance.

---

**TIMELINE**

| Date | What Happens |
|------|-------------|
| Oct 21 | Training module available |
| Oct 28 | Training completion deadline |
| Nov 1 | New system goes live |
| Nov 1-15 | Transition period (both systems available) |
| Nov 15 | Old paper process ends completely |
| Nov 15+ | All expenses must use new system |

---

**WHAT YOU NEED TO DO**

✅ **By October 28**: Complete the 15-minute training module
 - Link: [Training Link]
 - Takes 15 minutes, can pause and resume
 - Includes practice submission

✅ **By November 1**: Download the mobile app (optional but recommended)
 - iOS: [App Store Link]
 - Android: [Play Store Link]

✅ **After November 1**: Submit all new expenses through the new system

---

**COMMON QUESTIONS**

**Q: What about expenses I haven't submitted yet?**
A: Submit any outstanding expenses through the old process by November 15. After that, you'll need to use the new system even for older expenses.

**Q: What if I don't have a smartphone?**
A: The web portal works on any computer. You can also use a scanner for receipts.

**Q: Will my expense history transfer?**
A: Yes, all historical expense data will be available in the new system's reporting.

**Q: Who do I contact if I have problems?**
A: Finance Help Desk ([email]) or the #expense-help Slack channel. Extra support will be available Nov 1-15.

---

**SUPPORT RESOURCES**

- Training module: [Link]
- Quick-start guide (PDF): [Link]
- Video walkthrough (5 min): [Link]
- FAQ: [Link]
- Help Desk: [email] or Slack #expense-help

---

We know change can be inconvenient, but we're confident this will make expense reporting much easier. The training is short, and most people find the new system more intuitive once they try it.

Questions? Reply to this email or post in #expense-help.

Thanks,
[Finance Team Lead]