Apply today for a FREE subscription to CIO Magazine!
Mon, Jan 15, 2007 23:43 EST

|
Posted by: Michael Hugos Blog: Doing Business in Real Time
Current Rating: |
There are two kinds of leadership; one depends on orders and supervision; the other depends on training and trust. One kind of leadership values control and the other kind values responsiveness. If you are trying to create an agile organization which kind of leadership would you use?
The first kind of leadership is what we are most familiar with. It is where the person in charge tells people what to do and watches to make sure they do as they are told. It is leadership characterized by high visibility, issuing orders, and getting personally involved in lots of details. This style of leadership is needed when people aren't sure what to do. This is explicit leadership because it is exact and unequivocal; people are expected to listen carefully and then do as they are told.
The other kind of leadership is implicit leadership. This style is characterized by leaders who adopt a low profile, who seek consensus, and who delegate details to others. Leaders who use this style are clear about what they want but they do not say how they want it done. They provide their people with lots of training and let them decide how to do what has been asked of them. People are trusted to figure things out for themselves.
The agile organization is an organization that can handle high change situations; that can assess new situations quickly and then act fast to achieve its goals. So you would think explicit leadership is what you need to create agility. Yet, actually, implicit leadership is what you need. This seems counter intuitive at first but think about it.
In my experience explicit leadership works for only a short time (usually not more than 12 months) before people start to turn off; "leader fatigue" sets in. Explicit leaders work harder and harder for less and less response. People become numb; they don’t think for themselves; they do nothing at all unless told to. This is not agile behavior. Explicit leadership becomes like welfare; over time it robs people of their drive and self-initiative.
Explicit leadership has its place but it is only effective for short periods. So the question becomes how to use implicit leadership most of the time; even though we live in a fast-paced world where situations are always changing. Don’t confuse implicit leadership with slow, bureaucratic managerial practices or with leadership by committee. There is actually a very active side to implicit leadership but it is more in the nature of teaching and encouraging people to think and act for themselves instead of telling them what to do. Give a person a fish and they will eat tonight; but teach them to fish and they will eat for life.
Agility is a way of working, not just a passing fad. And implicit leadership is the best style of leadership for organizations over the long haul. Implicit leadership starts by setting meaningful goals that are clear and stable. Meaningful goals are statements of intent; they are descriptions of what an organization strives to accomplish. They do not change even though the situations an organization encounters change all the time. When goals and the performance objectives needed to achieve those goals are clear then people understand what is expected of them and they become skilled at figuring out how to achieve those goals.
When people learn to think and act for themselves without waiting to be told what to do then they can be agile. Although it may seem slow at first, implicit leadership is what fosters agility.
Great article! Implicit leadership is all about equipping and enabling people to do their job. This means no micromanagement, clear and consistent instruction and protection (as much as possible) from political and other interfering influences. If your team knows what they are working towards, have the tools to do it and look upon you as a steadfast and helpful leader you’ve got yourself a team people will want to be a part of.
Explicit Leadership sounds like what I would call management. You tell people what to do, and then they do it. Management requires the manager to get into the details of each and every thing. This, of course, causes managers to lose focus of the bigger picture.
Leaders, on the other hand, usually don't need to manage. They inspire people to self manage, so that the leader can actually lead.
Most managers are not strategic. Leaders, on the other hand, have the opportunity to actually be strategic. While the manager is back in the office making sure the variables in the program being written have the right prefix, the leader is out making a deal showing the software to potential customers.
Great article Mike!
The insights are right here, Michael, as you write, “There are two kinds of leadership; one depends on orders and supervision; the other depends on training and trust.†The references to TRAINING are important for leaders to consider.
All performance requires some form of learning, discovery, skill development, and assessment of processes to see if the performance is delivering results. The leader needs to be a teacher-trainer. The leader needs to know how to support learning by others so those other people can build successes.
I’m currently facilitating a course for Walden University exploring “Effective Teaching Using Learning Styles & Multiple Intelligences†related to classroom work by Teachers. Leaders in the workplace also need an understanding of how people learn, differences between learners and learning styles, and how to confirm if learning has resulted in desired outcomes.
A leader becomes a QUALITY RESULTS SPECIALIST as they look into teaching-learning activities as a core part of their responsibilities.
Now we come to the realization that many leaders don’t really think through their style of leadership - - they just do it. Now, it is necessary for leaders to discover what they may need to know about teaching and training.
Michael, while I strongly agree with what you have said, I don't think you have gone far enough. I've worked with numerous teams and organizations to apply agile methods. These methods have some pretty core ideas and you have hit one two of them: self organizing teams and planning to learn. However there are a number of other ideas:
- delivering valuable results frequently
- powerful communication
- testing everything
- measuring value
- and clearing the path or removing obstacles
(Full explanation of these ideas can be found here: http://tinyurl.com/3dp6t4 )
That last one is really critical and it is where leadership really makes or breaks an agile organization. A servant leader is someone who works tirelessly to remove the obstacles that are preventing teams from delivering valuable high quality results quickly.
A really simple example comes with approval processes. Many organizations love to "empower" teams, but forget that planning is not as powerful as doing. So they get a team together, let the team formulate a plan, and then the team waits while management reviews and approves the plan. In an agile organization, the team simply goes ahead and executes... and sometimes, they fail!!!
But with either failure or success, it is critical to allow for a learning process to take place, and this can only happen by allowing a team to go ahead and _do_ something.
The leader then becomes a follower unless he or she embraces the idea of servant leadership. This is the person who sees the direction of the team, hears their concerns, knows the organization and the competitive environment and can respond and sometimes anticipate to obstacles that the team is going to encounter.
Great article!
I agree with the manager vs. leader comparison, where the manager practices explicit leadership and the leader practices implicit leadership.
Leaders set direction, managers plan and budget.
Leaders align people, managers organize and staff.
Leaders motivate, managers control.
(don't remember where I heard this)
To me implicit leadership shares the same values as coaching i.e. creating awareness, taking responsibility, being committed and spreading motivation.