Daniel Lenhart: Turning Product Owner fears into better collaboration tools

PO’s can be overly prescriptive when they feel unsure about certain aspects of the product. In this episode, we share tips about how to turn those fears into collaboration boosters.

The Great Product Owner: Setting boundaries to encourage the teams to make decisions on their own

Good PO’s are able to communicate the vision and ideas behind the stories in a way that the teams will even repeat their words when discussing how to implement the stories they work on. But great PO’s are also available to the team then the team needs and is able to say “no, that’s your decision, not mine” to the teams that feel insecure and try to get the PO to make all the decisions, even implementation technical details. 

The Bad Product Owner: Turning PO fears into better collaboration tools

A Product Owner with technical knowledge can be a blessing for a team that requires more support when creating their User Stories, however, that’s not always the case. In this segment, we talk about the Technical PO that could not stop telling the team “how” they should work and develop the solutions the PO had in mind. In this segment, we talk about how we can work with those Technical PO’s and help them turn their fears and anxieties into tools for better collaboration with their teams.

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Daniel Lenhart

Daniel never knew what his dream job would be, but now that he is a Scrum Master, he loves it. I studied Biology in university and switched fields to software development. This really showed me the importance of cross-disciplinary learning and looking into new areas of interest. 

You can link with Daniel Lenhart on LinkedIn and connect with Daniel Lenhart on Twitter.

Leave a Reply

Your email address will not be published. Required fields are marked *