How to collaborate effectively with other Product Owners

Why collaboration with other POs is important for Agile scaling

In larger organizations and complex projects, multiple teams often work on a single product or on several closely related products. Collaboration between Product Owners (POs) is then crucial to maintain a uniform vision and avoid friction. If one PO plans features that make another's impossible—or if no one oversees the overarching priorities—this can lead to inconsistencies, duplicated effort, and dissatisfied stakeholders.

‍

How do you coordinate effectively between multiple POs?

1. Regular alignment: For example, schedule a weekly or bi-weekly PO sync. Here, you discuss roadmap adjustments, priorities, and dependencies.
2. Shared Backlog Structure: When teams work on the same product, maintain one overarching Product Backlog, with sub-backlogs or epics per domain.
3. Clear division of roles: Perhaps there is one ‘Chief PO’ who has ultimate responsibility, or each has their own domain. Document this to prevent conflicts.
4. Provide feedback on each other's plans: Share updates on customer feedback or performance metrics, so others can align their own plans accordingly.

‍

Clearly define roles and responsibilities

• Lead PO (or Chief PO): Ultimately responsible for the product vision.
• POs per component/epic: Focus on their own domain, but synchronize overarching goals.
• Scrum Masters & Dev Teams: Each sub-backlog has its own team, but the POs ensure consistent guidelines.

‍

Avoiding pitfalls in collaboration between POs

• No shared vision: Each PO acts independently, leading to fragmented priorities.
• Too much hierarchy: If there are too many layers, POs lose their autonomy and speed.
• Competition between POs: Trying to 'outdo' each other in features, instead of collaborating.
• Lack of transparency: Stakeholders don't know who to approach for specific topics.

‍

Case studies: what successful collaboration between POs looks like

• Large retailer: Two POs for online and offline integration, with a monthly session to smooth out roadmap bumps. This allowed them to launch simultaneous promotions without overloading back-office systems.
• Tech company: One overarching product vision, three POs each with their own sub-domain (UX, data analysis, integrations). They held a daily short sync meeting to tackle dependencies.

‍

Checklist and tips for improved alignment

1. Create a shared roadmap: Everyone sees the big picture.
2. Set shared metrics: Are you all working towards the same KPIs? Then prioritization becomes easier.
3. Hold short sync sessions: Keep them concise, focus on what truly needs to be shared.
4. Define escalation points: When a conflict arises over priority or vision, who makes the final decision?

‍

Common mistakes and how to avoid them

• Not involving each other: “I'll handle this myself”—leads to surprises in sprints.
• No uniform Definition of Done: Different quality requirements per team lead to inconsistencies.
• Confusing communication: Stakeholders get confused when each PO has a different story about what has “higher priority”.

‍

Conclusion

Collaboration between multiple Product Owners requires clear agreements, a shared vision, and regular communication. Whether you're working with two POs on a medium-sized product or ten in a large program, the principles remain the same: alignment, transparency, and shared responsibility for one cohesive end result. By implementing structure and communicating openly, you prevent conflicts, maintain momentum, and collectively build a successful product.