Don’t Be a Nice Product Owner
Are you a “nice” person?
Do you always aim to please and be seen as someone kind and helpful? If so, it’s time to reconsider what is “nice” really means.
In a Scrum team, being a “nice” Product Owner might sound like a good thing, but it can hinder the success of the team.
In this episode, we’ll explore why being nice is not enough and why it’s crucial to strive for something greater.
As a Product Owner in a Scrum team, it is important to focus not only on the product itself but also on the team dynamics.
One of the challenges that teams face is the presence of a “Nice Product Owner.”
This type of Product Owner may appear to be kind and supportive, but in reality, they are not genuinely concerned with the team’s success.
So, What’s the Problem with Being Nice in a Scrum Team
In many cases, people who are considered nice are simply signaling their niceness. They may engage in seemingly selfless acts, but this behavior may be motivated by a desire to be liked or to gain recognition. The problem with this is that it can create a false sense of trust within the team.
As a Product Owner, it is important to understand that being nice is not the same as being a good Product Owner. In fact, sometimes, making tough decisions may seem harsh but necessary for the success of the team.
What type of product owner are you — Let me show you how to test yourself
Consider the trolley problem as a test of where you stand in terms of your willingness to make tough decisions.
I’m not sure if you’ve heard about this test where the person must decide whether to do nothing and let the trolley continue on its course, or take action to divert the trolley onto a different track where it would kill fewer people. The scenario is meant to provoke a discussion about ethical dilemmas, the value of human life, and the trade-offs that people are willing to make in difficult situations.
Let me give you 1 example.
Some time ago, I was faced with a difficult decision. Our team has been working on a critical feature for our product for weeks, and my developers are close to completing it. However, I have received feedback from a key stakeholder that the feature is not going to meet their needs, and they urgently need a different feature instead.
So, as a Product Owner I had 2 options: continue with the current feature and risk not meeting the stakeholder’s needs, or switch to the new feature and risk delaying the project and disappointing the developers.
This scenario presents a dilemma that is similar to the Trolley Problem Test.
The Product Owner must weigh the potential harm of staying on the current track (continuing with the current feature) versus the potential harm of switching tracks (changing to the new feature). They must consider the impact on the stakeholders, the developers, and the overall success of the project. Ultimately, they must make a decision that aligns with the values and goals of their organization and the Scrum framework.
By using the Trolley Problem Test in this way, the Product Owner can gain insights into their own moral intuitions and decision-making processes, while also engaging in a productive discussion with their team about ethical dilemmas and trade-offs in the development. OK?
Now, let’s talk about being a Good Product Owner
Being a good Product Owner means doing whatever is best for the team, even if it means making tough decisions that may not be popular. It involves sacrificing personal desires and considering the team’s needs above all else.
A good Product Owner is not afraid to make unpopular decisions or to speak up when something is not working. They are willing to walk the path alone, bring up contrarian ideas, and even become disliked by the team for the sake of the team’s success.
Elon Musk is an example of someone who sacrificed everything, worked 100-hour weeks, had a tough personality, and had an abysmal family life for ten years without recognition.
I believe he did it all for the greater good of humanity, just like Nikola Tesla.
Similarly, a good Product Owner is willing to make sacrifices for the team’s success, even if it means going unrecognized.
So, it’s time to stop aiming for “niceness” and start striving for goodness. In a Scrum team, a Product Owner who is willing to put the team’s needs first and make tough decisions is crucial for success. So, let’s break away from the superficiality of being nice and embrace the hard work and sacrifice that comes with being a good Product Owner. Remember, true heroism comes not from being liked, but from making a positive impact on the world around us.
How to start as a Product Owner?
Are you interested in starting a career as a Product Owner?
Join our Agile and Scrum Masterclass to gain a comprehensive understanding of the Agile and Scrum methodologies and learn how to effectively perform the role of a Product Owner in a Scrum team.
Our masterclass is designed to equip you with the skills and knowledge necessary to lead product development, collaborate with stakeholders, and prioritize work in an Agile environment.
Our experienced trainer will guide you through interactive sessions and practical exercises, providing you with the opportunity to apply what you learn in real-world scenarios.
By the end of the masterclass, you will have a solid foundation in Agile and Scrum, and the confidence to kickstart your Product Owner career.
Don’t miss out on this opportunity to advance your career and become a valuable member of any Scrum team. Enroll now in our Agile and Scrum Masterclass and take the first step towards your future success!
