Team Communication

Communication is a key component of product manager work. It is important to quickly understand who all stakeholders of a feature request or bug report are and to effectively communicate to solve the task at hand. Even before a task is started it is important to collect all necessary information to justify the work and understand all aspects associated. Also, communication is key after a task is completed to validate the solution and to ensure that every stakeholder is up to speed with the changes.

Slack channels

In order of priority, you should be communicating in:

Feature channels (public): temporary feature channel, archived after it’s released. Type “/s #feature-” and Enter in any channel input to search for feature channels

  • for every feature, prefixed with “feature-”

  • archived later

Product channels (public): discussions/announcements concerning each product, no discussion about a product should go to private or 1:1 channels.

  • prod-workout-app

  • prod-admin

  • prod-customer-coach-app

Team channels (private): discussion about team work, the whole product and engineering organization can be present in these channels. No one from other department should be added.

  • team-tech (former #devs channel)

  • team-product (former #product_internal channel)

  • team-design

  • optionally this can go further, for example, team-tech-backends for backend people only.

Auxiliary channels

Support channels (public): team stakeholders channels for support, requests, etc

  • support-tech

  • support-product

  • support-design

Notification channels (public): bots only, used for automatic notifications from our tools.

  • notification-tech

  • notification-product

Collecting Requirements

  • Comment on Asana ticket to clarify open questions and collect business case

  • Present business case in product prio meeting before deciding to work on it

Feature-specific Communication

  • Create user stories in confluence and get it approved by your product owner

  • Create Slack group with the name “feature-[NAME]” and invite all stakeholders (incl. Design a Devs)

  • Paste confluence link to the top of Slack group and “pin” it

  • As soon as the estimation of the user stories is done add a time frame to task in Asana and add the task to Roadmap

Release Communication

  • Create short video of new feature (as explanation for coaches/ team)

  • Create short explanation for coaches

  • Organize with CRM to create email for customers (only for marketing relevant topics - marketing decides not product)

  • Organize with Coach Mgmt to distribute video and short info text 1-2 days before release

  • Product Owner ​creates release notes for the app stores before releas

Last updated