How do you communicate product management updates and activities to the rest of the company?

At the company level, there are a few different methods of communications to keep everyone abreast of updates: Product Notification emails (Ad Hoc) - These emails have a set template and allow product teams from around the company to share updates to their areas in a digestable format as major features go out of the door.  Product Newsletter emails (Weekly) - The weekly newsletter summarized major product updates and initiatives to all product team members.  Quartery Business Review meetings (Qu ...Read More

There are different types of updates that need to be communicated to the rest of the company and how those get communicated is different Vision/Roadmap: At least annually, live at the annual kickoff to the company.  A recording should be available at all times, as well as part of the sales enablement and onboarding materials.  A vision is high level and helps internal teams get excited about our direction and share that excitement with prospects and customers Major launches: Major launches typic ...Read More

Great question, and it doesn't have a single answer. One thing that is important is having a consistent, accessible, forum/location for people to see: What's been released; What's coming up; Metrics; Issues/outages/major bugs. The details of how you do this will depend on a few factors: Size of your company Whether you're distributed, in-person, or hybrid The type of space/collaboration tools you use The team culture For example, a very small, in-person team might rely on a weekly Iteration Plan ...Read More

At Atlassian - and I know this is true for other product organization with a strong writing culture - we invest a lot into internal comms about PM updates and activities. My general recommendation is a ratio of 80/20 for sharing updates async (think in writing or recorded form) vs sync (think enablement calls for your sales/customer success teams). My favorite examples of async updates that keep the team informed, and their frequency that has worked best for my teams: Weekly Loom updates (or any ...Read More

Communicating as a product manager is probably 90% of the job. I would say you need to make sure you establish clear chains of communication, both internally and externally, especially as a pertains to product roadmap delivery updates. My favorite method of doing this is to create a safe, publicly available, published version that you can distribute internally and externally so that everybody’s on the same page regarding the major milestones that you’re hoping to accomplish. This can also be coo ...Read More

I leverage different channels & format of communication depending on what I am communicating and who the audience is. Here is few different types of updates I use consistently: Product Execution Updates: A summary of how execution to executives/VPs is going with high level status update emails periodically ( weekly/monthly) with metrics/insights charts. A more deep-dive for major milestones / releases / events where I cover wide range of topics including PR updates, perceptions around releas ...Read More

What product management updates get shared with the rest of the company and how they get shared will vary based on the size of the company and the function of the company. The goal for communication, however, remains the same and that is to keep everyone aware of what is happening with the product and how it fits into the overall goals of the company.  Here are a few activities that I think help drive better alignment and transparency across the organization. I am a big fan of maintaining and ma ...Read More

It is important to tailor your communication methods to your company's culture, teams, projects and their needs. Here are some of my favorites ones: Slack (messaging) Updates: Send out regular email updates to relevant stakeholders via short but sweet Slack messages. These updates can recent product launches, upcoming features, and any significant metrics or even challenges. Town Hall Meetings: Hold regular meetings to share updates. This could be a weekly, bi-weekly, or monthly meeting where yo ...Read More

Updating product management activities to the rest of the organization involves communicating changes, updates, and progress made by the product team to the wider company. This helps to keep all stakeholders informed about the product's direction, the features that are being developed, and any changes that may affect the company or its customers. The content of the updates may vary depending on the company's needs and objectives. Some possible elements of product management updates could include ...Read More

This varies a lot based on the size and stage of the company - so it's important to think about: Which audiences you want to communicate updates to What level of detail each audience needs What frequency each audience needs What existing mechanisms and forums exist where you can make these happen Once you do this analysis, I would recommend starting with the most detailed and frequent need (perhaps it is to the other teams in your pillar who need good detail every week). Then use this to create ...Read More

There are 3 dimensions here - the size of the company, the audience and the type of update. At the current size we have the ability to connect with the entire company on a regular basis so the updates can be delivered live as needed. From a content standpoint (which also controls your content), if this is a strategy/roadmap update then quarterly refresh is what I recommend. If this is a Show & Tell (what got released in the sprint) then its up to the squad but I would recommend every sprint. ...Read More