When something goes wrong on a project, the first instinct most early-career PMs have is to make sure no one is left out of the loop. So they loop everyone in on everything. More syncs, more updates, more people on every thread. The logic feels right. But that's not how communication breaks down on real projects. It breaks down because the right information didn't reach the right person at the right time in a way they could act on. And looping everyone in on everything actually makes that harder, because now the critical update sits alongside 40 things that don't matter to that person. The experienced PMs I've watched work do the opposite. They narrow the paths instead of widening them. Curious what other lessons about project communication only clicked after running enough projects.
Saving Changes...