There are a few that I consider important to set up (and refine) as you grow your team:
- Processes for top-down sharing: As your team grows, knowledge sharing becomes harder but also more critical. PMs can only do their best work when they have context about conversations and updates from across the organization. For instance, "context" could include new product updates, changes in company strategy, takeaways from executive conversations and board meetings. I'd explore ways that you can provide this context either synchronously (e.g., through a team meeting) and/or asynchronously (e.g., through a "here's what's top-of-mind" slack message or email
- Processes for upwards sharing: It's important to also think through the best ways for your team to share what they're working on (product updates), but also for them to share feedback on how the team is operating (upwards feedback). This is necessary with a smaller team too, but in larger teams becomes more challenging to do this ad-hoc and 1:1 - additional processes like a recurring survey or a shared product launch calendar. Keep in mind that this is not just important for you, but for the entire PM team and XFN partners too, so be sure to do this in a transparent way.
- Team-building processes: Often overlooked, these are important to increase the cohesion and connection that your PM team feels. I like to use a weekly meeting or a private slack channel to share wins, talk about product news, share personal updates. It should feel like a trusted space for your team to share their thoughts and get to know each other more personally. Also, in today's remote climate where team members can often feel more disconnected, you might want to think through team rituals (e.g., beginning of every meeting with a win, learn and a "smile" - something that made you smile in your personal life) and in-person bonding (e.g., as a team, we meet in person once a quarter).
A helpful tip - carve aside 30 mins each quarter to also do some "housekeeping" of your team processes. Audit what's working and what's not, which meetings are useful vs. not, what are themes from your team surveys. Iterate on your team processes just like you'd iterate on a product!