Skip to main content
Internal communication is how product teams share what they’re doing, why they’re doing it, and what’s changing. It’s unglamorous work that most teams treat as an afterthought - and it quietly undermines alignment, trust, and execution when it’s done badly 📣

​
Why it’s a PM skill

PMs are at the centre of information flow. They sit between customers, leadership, engineering, design, marketing, and sales. What each of those groups knows about what’s happening and why depends significantly on how well the PM communicates internally. Poor internal communication creates a specific failure pattern: each group fills the information vacuum with assumptions, those assumptions diverge, and by the time someone notices, the divergence has hardened into conflict or, worse, shipped product.

​
The modes

Synchronous - meetings, standups, reviews, presentations. High bandwidth, high cost. Worth it when you need real-time discussion, decision-making, or emotional nuance. Not worth it for status updates that could be async. Asynchronous - written updates, recorded demos, Slack/email, documentation. Lower bandwidth, lower cost, better for distributed teams and anyone who needs time to process before responding. Scales better than meetings 💡 The most effective product teams are deliberate about which mode suits which purpose - and default to async more than feels natural.

​
What needs to be communicated

Decisions and their rationale - what was decided, what was considered and rejected, and why. Written down, shared broadly. This is the single highest-leverage internal communication habit. Progress and changes - what shipped, what changed in priority, what’s being learned from discovery. A short weekly written update to stakeholders prevents a lot of “why didn’t I know about this?” conversations. Context upstream and downstream - making sure the people executing understand the strategy, and the people setting strategy understand what’s happening on the ground. Both directions matter.

​
The over-communication principle

Most PMs think they communicate more than they do. The people around them typically feel less informed than the PM believes. The gap is almost always larger than expected. The antidote is structured over-communication: say it more times than feels necessary, in more channels than feels efficient, with more context than feels required. The information that seems obvious to you is not obvious to someone operating in a different part of the organisation 🙌 Lesson learned: the best internal communicator I’ve worked with sent a short Friday update every single week - what shipped, what we learned, what’s coming next. It was never longer than ten bullet points. It was the most-read thing in the company.