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 coordinated with marketing to help create marketing launch activities around it. As a product manager, I hope that you’re working iteratively working with engineering in a way that requires you to pivot and think about problems strategically. As a result, you may completely scrappy roadmap next quarter from what you originally published, but all you need to do is update to publish version and make sure you have a disclaimer that says these are not commitments, and they are subject to change.
As far as distributing this published version, I have had success distributing it on social media, newsletters to customers, or having just a subscription to the page so people get updates, whenever the pages are updated.
At the company level, there are a few different methods of communications to keep everyone abreast of updates:
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.
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:
The details of how you do this will depend on a few factors:
For example, a very small, in-person team might rely on a weekly Iteration Planning Meeting and some physical information radiators on the wall. A very large, distributed team might use a monthly all-hands for high-level updates and a formal product roadmap that everyone can access.
As your company grows, you'll also want to collaborate with other teams on sharing updates. For example, Customer Support or QA teams may handle centralized communications about bugs and issues that affect customers, and Product Marketing may create a customer-facing product roadmap for got-to-market teams to use.
Selecting the tools, forums and cadence that best support your team's needs, and then being prepared to change them as your team grows, is the most important thing.
There are different types of updates that need to be communicated to the rest of the company and how those get communicated is different