It’s Thursday afternoon. You’re staring at a blank Google Doc titled "Weekly Product Update." You start typing. You paste in the burndown chart for your VP. You add a list of features shipped for your cross-functional partners. You write a paragraph praising an engineer for the team to see. You hit send, blasting it to 30 people.
And almost nobody reads it.
Your VP skims for the one metric she cares about and ignores the rest. Your marketing counterpart gets confused by the technical jargon. Your engineers already know what they shipped. Your report is a well-intentioned failure. It tries to be everything to everyone and ends up being nothing to anyone.
Stop writing the one-size-fits-all update. It’s a waste of your time and everyone else’s. Effective communication isn’t a single broadcast. It’s three distinct channels for three different audiences. You need to provide a mirror for your team, a megaphone for your peers, and a map for your leadership.
The Mirror: Reflecting for Your Team
Audience: Your core team. The engineers, designers, and analysts in the trenches with you.
Purpose: To connect their effort to impact. This isn't about telling them what they did—they were there. It's about reflecting their work back to them through the lens of the customer and the business. It’s for morale, alignment, and creating a shared story of progress.
How it works: This communication is informal and frequent. It’s the opposite of a corporate memo.
- Format: A bulleted list in a team Slack channel on Friday. A five-minute share in your retro. A quick verbal kudos in stand-up.
- Content: Focus on "we" and "you." "Here's the positive user feedback we got on the feature you launched Tuesday." "That bug fix from yesterday? It cut related support tickets by 50%. Nice work, Alex." "Remember that painful refactor? It just dropped our API latency by 200ms." This is a record of accomplishment, not a status report. It’s the glue that holds a team together.
The Megaphone: Broadcasting to Your Peers
Audience: Other PMs, marketing, sales, support, legal. The people outside your immediate team whose work is affected by yours.
Purpose: To give them the tactical information they need to do their jobs. This is about managing dependencies and creating horizontal alignment. It’s purely functional.
How it works: This communication is asynchronous and event-driven. It happens when something is ready or about to change, not on a fixed weekly schedule.
- Format: A dedicated cross-functional Slack channel (#product-updates). A concise page in a shared knowledge base. A targeted email to a specific distribution list.
- Content: Be ruthlessly specific and action-oriented. "Heads up: The new onboarding flow (Project Phoenix) goes live next Wednesday. Marketing, the campaign assets are needed by EOD Monday. Support, the new training guide is attached."