How do product managers work with other teams?
Effective product managers lead cross-functional teams to launch and improve products that customers love. You sit at the epicenter of an organization. You are the connection between what customers are asking for and what is launched into the market. You have a vested interest in the teams who build, market, sell, and support what you envision. And so you need to develop deep relationships with those colleagues.
Delivering lovable products requires that product managers empathize with others. How will this release or feature impact the work of other teams? What does a particular team need to do to prepare for an upcoming launch? What do they need to know to be successful?
Addressing these questions with the cross-functional team will create loyalty, trust, and internal excitement for what you are building. This is the perfect foundation for creating customer love and it starts with clear communication.
Facilitating cross-team communication
Product managers have significant responsibilities without the benefit of explicit authority. Your work guides and impacts many others, but you do not manage those teams. So it is critical that you can build the trust and influence you need with colleagues from different functional groups to drive your product forward.
There are a few basic tactics that product managers can take when facilitating cross-team communication:
Plan: Building a well-defined product roadmap establishes a clear direction and ensures that people understand the product strategy and can see how their efforts will support it.
Listen: Solicit feedback — especially from those who are customer-facing. These folks can help you better understand and solve real problems your users face. Make it easy to submit requests with an ideas portal.
Understand: Take the time to get to know your colleagues and understand how other departments operate. Learn to speak their language and understand their goals. This will help you work with them more efficiently.
Communicate: Interruptions and unforeseen changes happen. The larger team will need to know if major dates or scope of work changes so they can adjust their timelines accordingly. Do not leave anyone in the dark.
Adjust: Your colleagues will gather valuable feedback from customers, partners, and the market. Maybe they notice something about the functionality or time frame that does not quite make sense. Stay flexible and open to feedback so you can deliver the best experience to your customers.
Working with a cross-functional product team
Product management maturity varies by organization. But you will typically be responsible for guiding a cross-functional product team. This group — called a product team — is responsible for choosing what gets built, marketing what is new, supporting the new customer experience, and measuring the performance of it all. While every company and team structure is unique depending on your industry, product, and customer base, you will usually find representatives from engineering, product marketing, design/UX, and customer support on a product team.
But you can extend the concept of the product team beyond the core group working on each release. This includes working with:
Product managers work with teams of engineers on the development work. This includes defining the features, estimating work, and planning sprints and releases. Product managers should provide their engineering teams with well-defined features that clearly tie back to the team's goals. The best product managers keep engineers focused, productive, and clear of obstacles.
The finance team at any organization is tracking a wide variety of metrics — from customer acquisition cost to average revenue per user and lifetime value of customers. Product managers work with finance teams to better understand these metrics and optimize them for business growth. They also need to align on backend systems and processes to support new business models.
As product managers define their product offerings, they involve legal teams to ensure that new experiences and technologies meet compliance requirements. This is especially important in heavily regulated industries to minimize risks while enabling the business to evolve.
The marketing team is responsible for attracting, converting, and retaining customers. Their work is the first touch-point and gets a product or service in front of potential customers. They need to be experts in communicating the unique benefits of a product. To do this effectively, the product manager needs to collaborate with marketing on buyer personas, go-to-market timelines, and how to communicate new product features.
Program managers exist to improve operational efficiency and performance. They create a program roadmap that includes multiple projects serving a broader company initiative. Product managers work closely with program managers to ensure delivery of their initiatives are on time and on budget.
Project managers are similar to program managers, but they operate at an individual project level instead of managing multiple projects within a specific program. Product managers work with project teams to track resource allocation, risks, and potential bottlenecks.
Salespeople are charged with helping prospective customers become buyers. Effective salespeople do this by identifying the best possible value exchange for the customer they are working with. They discover whether the product or service is a good match for what the customer needs. Salespeople can share back insights on what is resonating during their sales conversations — and what customers are asking for. In return, product managers need to help the sales team understand what is new and why it will benefit customers.
The support team is closer to customers than any other group — and deeply understands customer pain points and needs. Listen in on customer calls to support to learn about customer challenges. And proactively communicate new functionality with support so they can help customers be successful.
A product is more than what you directly sell. It is the entirety of the relationship you and your customers share — the Complete Product Experience (CPE). As guardians of the CPE, everything you do should be focused on bringing value to customers. This includes how you interact with other teams.
It is helpful to think about the broader impact of your roadmap and how you share it across all groups within your organization. Some product managers use static spreadsheets and documents to manage cross-functional work. It can become difficult to keep track of updates, timelines, and deliverables when those inputs are scattered across multiple locations.
Mature product teams use purpose-built product management software to set strategy, define features, build roadmaps, and keep stakeholders informed of progress. Roadmap software like Aha! provides a single source of truth for communicating product plans.
Set strategy, capture ideas, and prioritize work. Start a free trial today.
- What is a business model?
- What is customer experience?
- What is the Complete Product Experience (CPE)?
- What is a customer journey map?
- What is product-led growth?
- What are the types of business transformation?
- What is enterprise transformation?
- What is digital transformation?
- What is the role of product management in enterprise transformation?
- What is a Minimum Viable Product (MVP)?
- What is a Minimum Lovable Product (MLP)?
- What is product vision?
- How to set product strategy
- What is product-market fit?
- What is product differentiation?
- How to position your product
- How to price your product
- What are product goals and initiatives?
- How to set product goals
- How to set product initiatives
- What is product value?
- What is value-based product development?
- 10Ps marketing matrix
- 2x2 prioritization matrix
- Business model
- Customer journey map
- Lean canvas
- Porter's 5 forces
- Segment profile
- Strategic roadmap
- SWOT analysis
- Collections: Business model
- Collections: SWOT
- Collections: Objectives and key results (OKR)
- Collections: Product positioning
- Collections: Market positioning
- Collections: Marketing strategy
- 2x2 prioritization matrix
- Kanban board
- Feature requirement
- Market requirements document (MRD)
- PI board
- Pros and cons
- Release roadmap
- ROAM board
- User story map
- Collections: Product development process
- Collections: MRD
- Collections: PRD
- Collections: Gantt chart
- Collections: User story and mapping
- Collections: Feature definition checklist
- Common product development methodologies
- Common agile development methodologies
- What is agile product management?
- What is agile software development?
- What is waterfall product management?
- What is agile transformation?
- Agile vs. lean
- Agile vs. waterfall
- What is an agile roadmap?
- What is an agile retrospective?
- Best practices of agile development teams
- What is a burndown chart?
- What is issue tracking?
- Introduction to agile metrics
- Agile glossary
- What is scrum?
- What are scrum roles?
- What is a scrum master?
- What is the role of a product manager in scrum?
- What is a sprint?
- What is a sprint planning meeting?
- What is a daily standup?
- What is a sprint review?
- Product release vs. sprint in scrum
- Themes, epics, stories, and tasks
- How to implement scrum
- How to choose a scrum certification
- What is a product?
- What is product development?
- What is product management?
- What is portfolio product management?
- What is product operations?
- What are the stages of product development?
- What is the product lifecycle?
- What is a product management maturity model?
- What is product development software?
- Why product teams need virtual whiteboarding software
- Introduction to marketing
- What are some marketing job titles?
- What is the role of a marketing manager?
- What is the role of a product marketing manager?
- How are marketing teams organized?
- Which tools do marketers use?
- Interview questions for marketing managers
- Typical salary for marketing managers
- How to make a career switch into marketing