Over a million developers have joined DZone.

The Importance of Sharing Knowledge for Participatory Leadership

How sharing knowledge ultimately helps team leadership improve.

· Agile Zone

Reduce testing time & get feedback faster through automation. Read the Benefits of Parallel Testing, brought to you in partnership with Sauce Labs.

participatory-leadershipThe virtue of sharing knowledge is something I’ve touched upon on this blog many times over the years.  Most of these discussions have revolved around innovation, but sharing can also have an impact on leadership.

In complex environments it is increasingly accepted that employees need to take on responsibility for delivery and even strategy.  Leaders might determine what is required, but staff are encouraged to determine how that is achieved themselves based upon their own assessment of the environment.

Participatory Leadership

A recent study highlights how this more participatory approach to leadership can be encouraged, with knowledge sharing fundamental to your attempts.

The paper reveals that employee performance grows considerably when managers share and discuss the crucial information they have when making decisions and forming judgements.

This is because when we suspect our leaders aren’t being transparent with information, we interpret their attempts at collaboration as simply increasing our workload with little upside for us.

Their recommendation therefore is to go the whole hog and not embark in participatory leadership in a half-hearted way.  Doing this is immediately spotted by employees and buy-in then becomes very hard to achieve.

With innovation increasingly open in our organizations, eliciting input from employees is growing in importance and frequency, so this provides a telling insight into how this can be achieved.

Why We Might Hoard Information

Of course, this doesn’t always happen, and a recent study found that we’re often too self-interested to share information with our peers.

The paper reveals that teams are often not playing particularly well with each other, with employees typically withholding information if they felt it would harm their own prospects.  This was especially so when it came to determining how much funding was received for particular teams, projects or departments.

“Most organizations must make decisions about where best to allocate resources,” the authors say.“Pharmaceutical companies as a whole need to regularly reassess their research and development portfolios and decide which projects have the greatest potential; for example they might choose to improve an existing drug or develop a new one. Such decisions are often made by executives who rely on information provided by the project managers. But individual project managers do not necessarily give accurate information to the boss if they think it will cost them the resources that fund their projects.”

The paper found that our likelihood to share information depended on the fit between the type of project and the incentives in place.

For instance, in small companies, there’s more of a collective responsibility, so rewards work best when they focus on this collective element of success.

As companies grow however, there is more of a singular approach to responsibility, with outcomes becoming less risky.  In such a scenario, people tend to follow their individual agenda, with individual performances rewarded by management.

All of which is food for thought if we want our teams to be participating widely in the leadership of our organizations.

The Agile Zone is brought to you in partnership with Sauce Labs. Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure.


Published at DZone with permission of Adi Gaskell, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}