Takeuchi and Nonaka have written an article on Leadership in the Harvard Business Review. The latest issue.

Since they are the godfathers of Scrum, one feels compelled to discuss leadership in the context of Scrum.

First. we must note this is a big topic, and with somewhat different issues depending on the size of the firm. Also, leadership is separable from lean-agile-scrum.

Within the context of Scrum, let’s over-simplify and consider leadership at three levels. Within the team, immediately around the team, and top-level leadership.

Within the team.

We find that the most important thing that a team does is create knowledge. (Knowledge creation has been one of the main topics for Takeuchi and Nonaka throughout their careers.)

We find that power and knowledge creation do not go well together. Let’s mention some words that go with knowledge creation: innovation, invention, creativity, discovery, seeing new, finding creative unexpected solutions to tough technical problems, intuition, prescience, sympathy.

And the innovation, the new new product, must be not only clearly new, but also relevant to the customers. And, usually, something that can also make money for the firm. And we want all three of these (new, for customer, brings bucks) to the utmost degree.

So, inventing a new product is somewhat like magic. Certainly in some degree, it is magical when successful.

So, perhaps you can see now why power and creativity do not work well together. We want all the team to contribute together, to try to see, like blind men, the full elephant together. Acting from power, or even just perceiving power, can inhibit this creativity. Or so it can usually. And the inhibition is hard to see or feel.

Leadership and power are not the same thing. Of course. Although they are often thought to be related.

The Product Owner and the ScrumMaster are often thought to be leadership roles. And I would agree. This means, when things must happen or when decisions must be made, they should make them. Typically, each in his own sphere. (We won’t go here into the distinctions between the two roles.)

As Yogi Berra said: When you come to a fork in the road, take it. Or, as Ken Schwaber has said: Few things are worse than not taking the decision. It is almost always better to take the decision and learn from the results. (Not always, but almost always.)

We also recommend each member of the team consider himself or herself a leader in some area (typically, the area where he or she is strongest). Depending on who each team member is, this may not be realistic, but I suggest it is almost always realistic to some degree. In any case, we suggest that team members consider that they are all responsible for the success of the team. This means that. when they see something that should be exploited more, or a problems that must be addressed, that they each have the right and the responsibility to step up and lead in addressing that issue.

The standard leadership style recommended with Scrum is what Robert Greenleaf called Servant Leadership. The simplest version of that is the ScrumMaster who asks the team ‘what is your biggest impediment now?’ and then goes about getting it addressed.

The more complex version involves a few things:
* caring for the team (so that the team know it)
* trying to help the team be more successful, both in their immediate effort (the new product goal), but more broadly as a team and as individuals, each in his own life.
* being willing to sacrifice himself for the benefit of the team
* respecting the team

Let us stop for today on this difficult and interesting topic.
More soon.

Share on facebook
Share on twitter
Share on linkedin

Leave a Reply

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

Recent Posts

Six Actionable Nuggets of Advice for Becoming a First-time Technology NED

If the pandemic has taught companies anything it’s that tech is not something that you put off and think about ‘later’. The last year has seen organisations go through huge digital transformations, whether planned or otherwise. And for those that aren’t technology-based companies, getting the right board-level advice can not only be hard to find, but the difference between success

Read More »

Culture, Skills, and Capabilities // How to become a more data-driven organisation

In our whitepaper “How to become a more data-driven organisation”, we wrote about the five steps that an organisation would need to take, which are: Outcomes: Defining goals and metrics to ensure clear and measurable outcomes Analytics: Implementing and sharing the analytics to improve data-driven decision making Innovation: Testing assumptions through hypothesis testing and learning Data Platform: Gaining new insights

Read More »

Data Platform // How to become a more data-driven organisation

This is the fourth article in our series on “How to become a more data-driven organisation”, and we are going to be focusing on Data Platforms. It is at this point that most people start to dive deep into the technical aspects of Data Lakes vs Data Warehouses, but we want to bring us back up a level and ask

Read More »

Search the Blog

Agile Management Made Easy!

All About Agile

By Kelly Waters

“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”

Kelly Waters

Agile 101 is available to purchase. GAME ON!

Agile 101

Emma Hopkinson-Spark

“Whilst there are lots of ways you can vary the game depending on the teams you have and the learning outcomes you want, the basic flow of the game play is common to all.”
Emma Hopkinson-Spark

Why did we make the game?

How to play the game?


101 Ways Limited
145 City Rd
United Kingdom


101 Ways BV
Weesperstraat 61-105
1018 VN Amsterdam

Contact Us

If you would like to get in touch with one of the team at 101 Ways, then please fill out the form below or email us at contact-us@101ways.com.