What communication blunders do new project managers make with cross functional teams?
I am struggling to keep our design, engineering, and marketing teams aligned. What are the most common mistakes new project managers make when handling communication across diverse departments? I feel like messages get lost in translation constantly, and some teams feel left out of key decisions, causing unnecessary friction. How can I fix this communication gap before it ruins our product launch?
2025-02-02 in Project Management by Timothy Schultz
| 8917 Views
All answers to this question.
The core mistake is using a single communication channel or style for completely different audiences. Engineers want technical details and clear requirements, marketing cares about customer impact and timelines, and executives want high-level business outcomes. New project managers often send massive, text-heavy emails to everyone, which causes people to tune out entirely. You must tailor your messaging. Create separate updates for different groups and establish a central source of truth, like a shared project dashboard, so everyone can find what they need.
Answered 2025-02-06 by Amy Johnston
Do you think holding daily standup meetings with all departments involved is an effective way to break down these silos, or does it just waste everyone's time?
Answered 2025-02-10 by Dennis Wagner
-
In my experience, Dennis, dragging everyone into a daily standup wastes time. Marketing does not need to hear daily engineering bug updates. Weekly syncs or asynchronous dashboard updates work much better for cross-functional alignment.
Commented 2025-02-12 by Timothy Schultz
New PMs often make the mistake of hiding bad news from teams until it is too late to fix the problem collaboratively.
Answered 2025-02-15 by Gregory Ortega
-
Exactly, Gregory. Bad news does not get better with age. Transparency builds trust, especially when you are managing cross-functional dependencies.
Commented 2025-02-17 by Timothy Schultz
Write a Comment
Your email address will not be published. Required fields are marked (*)

