Leadership: Training or Development?

by Virgil R. Carter

As a CEO, do you have a group of senior leaders in your organization that you’d like to help grow into your organization’s next generation of executive?  What about supporting your senior staff to become mature executive?  If so, what do you do?  Well, of course, you put them through some training, right?  Wrong!

In a recent article, “Training vs. Development, by Mike Myatt, Chief Strategy Officer, N2growth, you don’t train leaders you develop them.  According to Myatt, “Leadership training is alive and well, but it should have died long, long ago…”

Myatt says that the problem with training is it presumes the need for indoctrination on systems, processes and techniques.  Moreover, training assumes that these systems, processes and techniques are the right way to do things.  The dilemma, describes Myatt, is that training is “often a rote, one directional, one dimensional, one size fits all, authoritarian process”, imposing static, outdated information on people”.

The solution to the leadership problem, he says, is to scrap it in favor of development.  “Don’t train leaders, coach them, mentor them…and develop them, but please don’t attempt to train them”.  Development strives to focus on the unique and differentiate by shattering the status quo.  Myatt has a list pointing out some of the differences between training and development, including:

·          Training focuses on the present—Development focuses on the future
·          Training focuses on technique—Development focuses on talent
·          Training focuses on maintenance—Development focuses on growth
·          Training focuses on the role—Development focuses on the person
·          Training focuses on efficiency—Development focuses on effectiveness

Myatt concludes saying, “If what you desire is a robotic, static thinker—train them.  If you’re seeking innovative, critical thinkers—develop them”. 

For a copy of the full article, go here:  http://www.n2growth.com/blog/training-isnt-dead-but-it-should-be/

0 komentar:

Post a Comment

Blog Archive