Should Product Owners Be Servant-Leaders?
Roman Pichler talks about the concept of servant-leadership and the benefit Product Owners can achieve if they deployed the leadership style.
Join the DZone community and get the full member experience.Join For Free
Servant-leadership means that “one wants to serve, to serve first, then conscious choice brings one to aspire to lead,” writes Robert Greenleaf, the creator of the servant-leadership model. Servant-leaders want to “make sure that other people’s highest priority needs are being served” so that they “become healthier, wiser, freer, more autonomous.”
Sounds crazy? To me, servant-leadership means leading from the heart: recognizing that the people we work with are first and foremost human beings. Caring for them and building strong relationships with them are prerequisites for achieving great things together. If we don’t care for the people we want to lead, they are unlikely to trust and follow us.
Caring for the followers, the people we work with, is present in other leadership models, too. Goleman’s leadership styles, for instance, recognizes affiliative leadership as an approach that puts people first and coaching as a leadership style that develops people. In Scrum, servant-leadership is regarded as the default approach with the Scrum Master embodying it.
How Can Servant-Leadership Benefit Product Owners?
Servant-leadership encourages us to reflect on our motivation to be product leaders. Why do we want to lead others? Is it to gain power, status, success, or money? Is it to succeed together and help the people we lead grow and develop?
There is nothing wrong with gaining respect as well as a bonus or pay rise. However, if these motivators dominate our thinking, we are in danger of no longer caring for the people we lead but seeing them as tools to advance our personal ambitions. This negatively affects our relationship with them and reduces their willingness to trust and follow us.
Servant-leadership also helps us question our approach to achieving success. Is the end — a successful product — more important than the means — how we got there? Do we expect that people just do their job, function, perform, and deliver? Are working extra hours and weekends normal to get a product release out, or do we take an interest in the people we work with, show kindness to them, and encourage the developers to go home when they look tired and worn out?
Don’t get me wrong — I am no utopian. I know that great products are the result of hard work. But if we want sustained success and a work environment that is healthy and conducive to creative work, then we must care for the people we work with and lead — the development team and the stakeholders. This starts with taking a real interest in others, making an effort to be present and engage properly.
Next time you are tempted to tell the dev team that you expect them to work extra hours, stop and reflect. Check if there isn’t room for thinning out a feature or hiring an expert that would accelerate the progress. And when this annoying programmer complains about the user stories again or the pushy sales guy reiterates that the product strategy is wrong, take a deep breath.
Recall that we all have healthy and unhealthy traits and remind yourself of the individual’s positive qualities. Then kindly but clearly share your thoughts.
Published at DZone with permission of Roman Pichler, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.