Find where communication is breaking down on my project
Diagnoses communication gaps across meetings, channels, and teams, and gives you a simple plan to fix the flow of information.
The prompt
Help me find where communication is breaking down on my project or team.
Who is involved: [TEAMS, roles, locations or time zones]
How we communicate now: [MEETINGS, email, Teams or Slack channels, trackers, documents]
Symptoms: [e.g. "people hear about changes late", "same questions every week", "decisions get re-opened"]
Examples: [PASTE threads, notes, or describe 2-3 recent incidents]
Look for:
- Missing links: people or teams who need information but aren't in the meeting, channel, or email list.
- Decisions made without a written record, or recorded where no one looks.
- Too many channels for the same topic, so nobody knows which is current.
- Bottleneck people who relay information and slow it down.
- Handoffs between teams with no agreed format.
- Meetings that share status but don't settle anything.
- Language, time zone, or remote-vs-office gaps.
Return:
1. Diagnosis: the 3-5 breakdowns, each with evidence, who is affected, and the cost.
2. A simple communication map: what information goes to whom, through which channel, how often.
3. Fixes for each breakdown, starting with the cheapest (a decision log, one source of truth, a weekly summary post, a changed invite list).
4. A short note to the team explaining the changes.
Focus on how information flows, not on who is to blame. Base the diagnosis on my examples; mark guesses [LIKELY].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- TEAMS, roles, locations or time zones
- MEETINGS, email, Teams or Slack channels, trackers, documents
- PASTE threads, notes, or describe 2-3 recent incidents
- LIKELY
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Create an employee offboarding checklist and timelineProduces a complete offboarding checklist by owner and day for voluntary or involuntary exits, so nothing is missed.
- Plan an office, warehouse, or site moveA relocation plan with workstreams, timeline, cutover weekend, and risk checks so operations keep running through the move.
- Write a closed-won handoff from sales to customer successA complete handoff document so the customer success or implementation team starts with everything the buyer was told and expects.
- Plan stakeholder communication and engagementWho needs to know what, when, and how — and how to keep them engaged.