Fri

25

Jun

2010

Teamwork and Leadership

Teamwork.  When teams are productive, the results can be almost magical.  At best, team members take turns bringing good ideas, polishing old ones, helping one another think. 

I left class today wondering how well the class teams are "gelling."  I know I can't see it all - there could easily be problems under the surface. What is my role in all this?

As I write this I wonder if, once again, I am failing to "practice what I preach."  Today we talked about the myth of the "almighty leader" - the idea that a leader-hero can solve all problems.  We discussed the complexity of adaptive problems and the power (and tenacity) of a system.  "The leader can only solve problems on his/her own," I suggested, "when the problems are technical - when the leader knows the answers."

Team success, however, requires adaptation. Team adaptation.  People must learn to build a common vision, design a team process, and share information productively.  People must learn to trust one another and encourage one another. It's hard work.  I cannot solve team problems on my own any more than I can "make" someone learn.

So what should I do? Should I let it go? Leave people to their own devices? Hope for the best?

As I write this blog I realize that leaving people to their own devices would represent an abdication of leadership.  So no - I probably shouldn't ignore any warning bells. What I probably should do is bring this to the balcony.  The class as a whole could embrace one more opportunity for leadership. One more chance to use the class as a laboratory for real life.

Note to self: Next balcony (a.k.a. class) we examine teamwork! And perhaps... who was it that offered moderation services? Negotiators and moderators, you're about to take on a new project!

Trackback URL for this article


Trackbacks / Pingbacks 0

Write a comment

Comments: 0

  • loading
About | druckversionPrint Version | Sitemap
(c) Cris Wildermuth, 2009. All rights reserved. To reproduce any of the documents contained in this site, please contact the author.