Project managers, Operations leads, Startup teams, Team leads, Consultants
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt. 2. Paste it into your AI tool. 3. Replace the "Required Inputs" 4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are an operations specialist. Your task is to create a complete project communication plan that ensures clear, consistent communication across stakeholders.
###Required Input
Project Overview: [Brief description, e.g. “Website redesign for SaaS product”]
Project Duration: [e.g. “8 weeks”]
Team Structure: [List roles, e.g. “PM, Designer, Developer, Marketing”]
Stakeholders: [Internal/external, e.g. “CEO, Clients, Partners”]
Communication Goals: [e.g. “Ensure alignment, reduce delays, improve visibility”]
Key Milestones: [List major checkpoints, e.g. “Design approval, Beta launch”]
Communication Channels: [e.g. “Email, Slack, Meetings, Dashboard”]
Reporting Frequency: [e.g. “Weekly updates, daily standups”]
Risks or Constraints: [e.g. “Remote team, timezone differences”]
###Input Validation
Review all inputs before generating output. If any input is missing, vague, or unclear, ask specific clarification questions. Pause and wait for clarification before proceeding.
###Instructions
Define communication objectives
Translate goals into 2–4 clear communication objectives
Map stakeholders
Group stakeholders by role and involvement level (e.g. core team, decision-makers, observers)
Define what each group needs to know and when
Define communication types
List key communication types (e.g. status updates, risk alerts, milestone reviews)
Assign purpose and audience to each
Assign channels and formats
Match each communication type with the most appropriate channel
Specify format (e.g. async update, live meeting, report)
Set cadence and ownership
Define frequency for each communication type
Assign clear owner for sending and maintaining updates
Create milestone communication plan
Map communication activities to key milestones
Include pre-, during-, and post-milestone communication
Address risks and constraints
Adjust communication approach based on risks (e.g. async-first for remote teams)
Ensure clarity and consistency
Standardise tone, format, and expectations across all communication
###Output
Communication Objectives (2–4)
Stakeholder Communication Map
Communication Types Table (type, purpose, audience)
Channel & Format Plan
Communication Cadence & Ownership جدول
Milestone Communication Plan
Risk Adjustments
Ensure the plan is practical, concise, and immediately usable.
Make the communication plan more proactive by including escalation triggers for delays or risks.
Project Overview: End-to-end Brand Identity & E-commerce Platform Build for “Aura Wellness.”
Project Duration: 12 weeks.
Team Structure: Project Manager (PM), Senior UX/UI Designer, Lead Full-Stack Developer, Content Strategist.
Stakeholders:
Internal: Agency Director, Creative Lead.
External: Aura Wellness Founder, Marketing Director, Third-party Logistics Partner.
Communication Goals: Eliminate “scope creep,” maintain high transparency on technical hurdles, and ensure rapid feedback loops.
Key Milestones: Discovery & Moodboards, Prototype Approval, Development Sprint 1 Completion, Final QA & Launch.
Communication Channels: Slack (Daily), Notion (Documentation), Zoom (Weekly Syncs), Loom (Video Walkthroughs).
Reporting Frequency: Daily internal syncs, weekly external status reports.
Risks/Constraints: Client is 8 hours ahead (GMT+8 vs GMT); highly visual project requiring precise feedback.
Synchronize Feedback: Centralize all design feedback within 24 hours to prevent development bottlenecks.
Radical Transparency: Provide the client with real-time visibility into the “Health” of the project via a live dashboard.
Minimize Meeting Fatigue: Prioritize asynchronous video updates (Loom) for non-critical status check-ins.
Core Team (PM, Designer, Developer, Content):
Need: Detailed daily tasks, technical blockers, and asset delivery.
When: Daily.
Decision-Makers (Agency Director, Client Founder):
Need: Budget health, milestone approvals, and high-level timeline risks.
When: Weekly/Milestone-based.
Observers (Logistics Partner, Marketing Director):
Need: Launch dates and integration requirements.
When: Bi-weekly.
Daily Standup:
Purpose: Address immediate blockers and task alignment.
Audience: Core Team.
Weekly Pulse Report:
Purpose: Summarize progress vs. budget/timeline and flag upcoming needs.
Audience: Decision-Makers & Core Team.
Risk Alert:
Purpose: Immediate notification of any event impacting the “Go-Live” date.
Audience: All Stakeholders.
Creative Review:
Purpose: In-depth walkthrough of design/UX iterations.
Audience: Client Founder & Creative Lead.
Slack: Real-time messaging; used for urgent queries and internal banter.
Notion: The “Single Source of Truth.” Houses the project schedule, meeting notes, and asset links.
Loom: Asynchronous video demos. Used for “walking through” designs before a meeting to allow stakeholders time to process.
Zoom: Reserved for high-value strategic discussions and milestone sign-offs.
Internal Daily Sync
Frequency: Daily (Mon–Fri)
Channel: Slack (Threaded)
Owner: Project Manager
External Status Update
Frequency: Weekly (Every Friday EOD Client Time)
Channel: Notion Dashboard + Email
Get access to all workflows, across every sector, with structured systems built for better results.