We have 3970 guests and 1 member online

Video Spotlight

Home > Blogs > Featured Blogs > Brad Appleton's ACME Blog > The Dynamics of Leadership-Team Behavior

The Dynamics of Leadership-Team Behavior

 E-mail
Written by Brad Appleton   
Sunday, 07 June 2009 01:08

Interesting article in BusinessWeek from Jim Collins on the Dynamics of Team-Leadership Behavior. It's actually an excerpt from his latest book "How the Mighty Fall: and Why Some Companies Never Give In."

Anyway ... the Dynamics of Team-Leadership Behavior is divided into leadership behaviors of teams on the way up vs. on the way down:

Teams on the Way Down

Teams on the Way Up
People shield those in power from unpleasant facts, fearful of penalties and criticism for shining light on the rough realities People bring forth grim facts—"Come here and look, man, this is ugly"—to be discussed; leaders never criticize those who bring forth harsh realities
People assert strong opinions without providing data, evidence, or a solid argument People bring data, evidence, logic, and solid arguments to the discussion
The team leader has a very low questions-to-statements ratio, avoiding critical input and/or allowing sloppy reasoning and unsupported opinions The team leader employs a Socratic style, using a high questions-to-statements ratio, challenging people, and pushing for penetrating insights
Team members acquiesce to a decision but don't unify to make the decision successful—or worse, undermine it after the fact Team members unify behind a decision once made, then work to make the decision succeed, even if they vigorously disagreed with it
Team members seek as much credit as possible for themselves, yet do not enjoy the confidence and admiration of their peers Each team member credits other people for success, yet enjoys the confidence and admiration of his or her peers
Team members argue to look smart or to further their own interests rather than argue to find the best answers to support the overall cause Team members argue and debate, not to improve their personal position but to find the best answers to support the overall cause
The team conducts "autopsies with blame," seeking culprits rather than wisdom The team conducts "autopsies without blame," mining wisdom from painful experiences
Team members often fail to deliver exceptional results and blame other people or outside factors for setbacks, mistakes, and failures Each team member delivers exceptional results, yet in the event of a setback each accepts full responsibility and learns from mistakes


The Dynamics of Leadership-Team Behavior

Posted: 2009-06-07 09:08:00

Read Full Article
Author:Brad Appleton

Comments (0)Add Comment


Write comment

feedShow/hide comment form
You must be logged in to post a comment. Please register if you do not have an account yet.

busy
< Prev   Next >
 

Agile Marketplace - Announcements and Special Offers

Webcast:  Moving Build and Code Quality Upstream
This interactive panel discussion moderated by Bob Aiello, Editor-in-Chief fo the CM Journal brings industry experts Anders Wallgren, CTO of Electric Cloud and Gwyn Fisher, CTO of Klocwork together for a candid discussion of the cost savings, productivity and quality benefits that can be achieved by stabilizing builds and code quality as early in the development cycle as possible.
Register Now!

Collabnet -TeamForge 5.3
CollabNet TeamForge 5.3 includes Dynamic Planning—providing flexibility to model release scope and timeline in a single view. Now, you can easily manipulate/adjust release data.
Download Your Free Trial

Requirements-based testing (RBT) can help to ensure comprehensive test coverage, reducing the risk of failure and improving software quality. This white paper details how application lifecycle management can be used to more effectively implement RBT processes, offering greater collaboration, traceability and control.can help you increase efficiency, reduce project risk, and improve overall software quality. Learn how MKS Integrity for application lifecycle management enables RBT, delivering full lifecycle traceability to help ensure that project requirements have complete test planning and execution coverage.
Download the Requirements-Based Testing whitepaper

PureCM –SCM for Agile Teams
PureCM helps you to manage development in short iterations: keeping track of changes, supporting automated builds and preserving frequent snapshots of your projects.
Get the free trial now