Stakeholder Communication & Change Management

This document defines stakeholder mapping, communication cadence, phase transition protocols, and change management for editorial operations.

Stakeholder Map

Group	Interests	Cadence	Channel
Executive Leadership	ROI, risk, timeline	Monthly	Executive summary (dashboard)
Editorial Team	Workflow impact, training	Weekly (during change)	Team meeting + Slack
Development	Technical decisions, blockers	Daily	Standup + Slack + Issue tracker
Marketing	Launch dates, features	Bi-weekly	Email + demos
Finance	Budget, spend	Monthly	Budget report
Legal/Compliance	Data privacy	As needed	Meetings

Communication Cadence

• Weekly: Team standups, progress notes in channel
• Bi-weekly: Sprint demos to stakeholders, retrospectives
• Monthly: Executive dashboard (progress vs plan, budget, risks)
• Quarterly: Roadmap review and go/no-go decision for next phase

Phase Transition Protocol

Before each phase starts:

• Kickoff meeting (goals, scope, success criteria)
• Risk assessment presentation and mitigations
• Confirm resources, budget, timeline

During each phase:

• Weekly progress updates (done/next/blockers)
• Monthly demos of working functionality

After each phase:

• Completion report (deliverables, KPIs, lessons learned)
• Post-mortem and adjustments

Editorial Change Management (Phase C)

• 3 months before: Introduce new admin, weekly demos, collect feedback
• 2 months before: Hands-on training (workshop), documentation/videos, identify editorial champions
• 1 month before: Parallel content creation in both systems, daily check-ins
• Launch week: On-call support window, daily check-ins, issue triage
• Post-launch (4 weeks): Weekly feedback, continuous improvements, satisfaction survey

Success Metrics

• Editorial satisfaction > 80%
• Time-to-publish same or faster vs WordPress
• Error rate (publishing) < 5%
• 100% training completion