A few articles ago, we speculated on the different ways an IT client can motivate a remote team. This time, we decided to look into the question deeper and wondered: what is the most effective way for product managers to work with a development team? Which character traits should they display? How should product managers distribute roles in a team?
We thought that the best way to get answers to these questions would be to ask those who are at the frontier, working with product managers on the client side: Zoolatech product owners. To do so, we compiled a survey with more than 15 questions and asked ten Zoolatech product owners to complete it.
Now that we have the results, we can picture the ideal product manager on the client side and the ideal communication between the product owner and the developers.
So, here are our seven tips for collaborating with a development team that every product manager should follow.
1. Be Passionate, Systematic and Honest
Our team agrees that outstanding product managers are passionate about their product, exercise a systematic approach, and build a trusting relationship with the development team.
Product owners are expected to drive the team and ignite them with passion about the product. If you don’t, team members will feel deflated and are unlikely to work to their full potential. How can you spark them?
- Tell them who your product is for
- Share your product vision and strategy
- Figure out high-level requirements and pass them on to the team in advance
The right product is the product that solves the right problem. When a product manager has a strong business background, then he/she knows what problems are usually faced in this domain (by customers or by businesses). Knowing the audience as well as business nuances helps to focus only on what is really important. Daria Iarchevska, Product Owner, Zoolatech3. Juggle Different Cooperation Styles Some product managers may take a strict, supervisory approach, some are Scrum Masters, and others might leave the team to their own devices. The best scenario is in between. When asked which cooperation style product owners prefer product managers to have, 40% voted for self-organization and 50% favored a mix between strict management and self-organization. Our product owners seem to agree that managed self-organization helps the team members feel like co-authors of the product. It’s also a sign of trust and a healthy relationship. This win-win type of relationship supposes that product managers announce their expectations, while the team decides on the best ways to reach the set goals. This has nothing to do with telling people how to do their jobs and assigning tasks. On the contrary, the product manager should display trust in the professional expertise of the development team. Remember: Product managers manage a product, not a team. 4. Collaborate with the Development Team at All Stages of Product Development The reality is that remote development teams are usually not involved in the pre-development stages like user research, product roadmap, and strategy development. The very nature of remote teams dictates this situation. However, it’s virtually impossible to develop the right solution without understanding the product context. For this reason, it’s okay to involve the remote team in the product discovery work, or in creating the release and sprint goals. This will not only generate better technical decisions, but it will also ease the workload: understanding the bigger picture allows team members to be more self-sufficient. To prove the point, 70% of Zoolatech product owners expressed their interest in participating in other—non-typical—development processes.
My key advice to product managers would be to treat a remote team as a part of their team. It’s really important to share your culture and product development strategy with them. It’s also crucial to communicate the short-term and long-term objectives, upon which the development team has a direct influence. Olena Yatsenko, Product Owner, Zoolatech5. Keep in Touch and Provide Timely Feedback This point appears to be a constant headache in the development process. Busy as they are, product managers often let important notifications pass them by. However, in a Scrum context, it’s vital to keep in touch with the team and provide timely feedback.
- Agree on the acceptable degree of communication frequency at the onboarding stage
- Save dates for sprint planning and sprint reviews
- Choose the preferred means of communication