Therefore, successful Product Managers learn to lead through influence. The creators of Scrum, Jeff Sutherland and Ken Schwaber, had the foresight to grant special powers to the Product Owner so they would not suffer a similar fate as the Product Manager. In Scrum, the Product Owner has explicit authority to prioritize the product backlog and thus determine the order of the work to be done.
The team may call foul that the executives are not respecting the Scrum process. In these situations, before looking outward for blame, teams should first look inward. If the Product Owner is not the true expert regarding customer needs and if in fact the executives know more about the customer and the market place, then the Product Owner influence and ultimately his or her authority will be compromised. This is because prioritizing a list of user stories is relatively easy.
To have authority, the Product Owner needs to facilitate trade-off discussions, bring market evidence to the table, tie the prioritization into the company’s strategic objectives, and socialize prioritization discussion. These are a necessary but often overlooked part of the Product Owner role.
This not only applies to the role of the Product Owner but also holds true for managers, vice presidents, and even CEOs. Explicit authority can make your job easier. If you want people to follow you, you need to lead through influence.
Want to learn more about ways that the Product Owner can influence their team?
Check out our new training course: Agile for Product Managers and Product Owners, available in-person or as an online course.
Most product teams don’t fail because they can’t ship. They fail because product discovery didn’t do its job. As product managers and product leaders, we’ve all lived this
Product management feels harder than it should It’s not because teams are lazy. Not because PMs
By the time a product launches, most teams feel like they’ve crossed the finish line. In reality, that’s where
