Skip to main content

Book Review: The Wisdom of Teams



Introduction:  What We Have Learned

Originally written in 1993, this edition written in 2003 has additional insights from 10 years of working with teams.  The authors see more pragmatism on the subject, less thoughtless rushes to a fad movement.  Top leaders are seeing that teams also apply to themselves, at the top of the business.  They see the core aspect as discipline, not the management fad du jour.  The discipline for team performance has 6 basics: team size, complementary skills, common purpose, performance goals, commonly working agreements, and mutual accountability.  The desire to be a team is not sufficient - one must have performance centric outcomes as the objective.  Leadership is more important at the beginning - but not the primary determinant of success.  Most organizations have untapped potential in team performance.  The organizations performance ethic makes the difference between one-off success and widespread organizational team performances.

The authors develop an explicit terminology, to distinguish commonly misunderstood phrases when discussing groups and teams.  The Y-Chart (p. XXI) helps explain the taxonomy of groups (Effective Group vs Performance Units; Single-Leader Unit vs Real Team).  They define an abstract Team Performance Curve, noting time as the major factor in achieving high (extra-ordinary) performance.  The decision of which type of team; single-leader unit vs team is dependent upon 3 factors: need for collective work products integrated in real time by two or more people, shifting leadership roles for situational awareness, need for mutual accountability in addition to individual accountability.  Setting outcome-based goals is essential to achieving high performance (as apposed to activity-based goals).  Real teams require more time and leadership capacity than single-leader units.  Process support for multiple team opportunities across broad programs is essential to scale the team success from one-to-many.

Prologue:  A Note About What to Expect

The book notes the obvious concepts but also the subtle nature of language used to describe the concepts are required to be precise in defining the discipline.  The authors find that it is difficult to apply common sense to teams.  Expect failure when: building the team for its own sake is the goal (rather that demanding performance challenges), the discipline of “team basics” is overlooked, many areas for teams are left unexplored in organizations (teams: recommend things, do things, run things), teams at the top of organizations are the most difficult, individual accountability is the norm (as apposed to team/group accountability).

Uncommon-sense findings: strong performance standards seem to spawn more teams than teaming-for teaming sake; high-performance teams are extremely rare; hierarchy and teams go together well; teams naturally integrate performance and learning; “teams are the primary unit of performance for increasing numbers of organizations” (p. 5).

Part One:  Understanding Teams

Focusing on Team Basics - figure 1-1 (p. 8)

Apex:  Performance Results; Collective Work products; Personal Growth
Sides:  Skills (Performance results - Collective work products)
Accountability ( Performance results - Personal growth)
Commitment ( Collective work product - Personal growth)
Internal:  Skills - Problem solving, technical function, interpersonal
Accountability - Mutual, team size, individual
Commitment - Specific goals, common approach, meaningful purpose

Chapter 1:  Why Teams?

The authors have learned that although many executives understood the argument for using teams many didn’t extract the real potential from the teams or the opportunities to use teams.  Many times because of unwarranted assumptions and poor knowledge.
Key lessons:
  • “Significant performance challenges energize teams regardless of where they are in an organization.”  Performance is the primary objective.  A team is the means - not the end.
  • “Organizational leaders can foster team performance best by building a strong performance ethic rather than by establishing a ream-promoting environment alone.”  Focus on customer satisfaction performance rather than teamwork performance.
  • “Biases toward individualism exist but need not get in the way of team performance.”  Turn individualism, self-preservation, and self-centered objectives to the benefit of the team.
  • “Discipline - both within the team and across the organization - creates the conditions for team performance.”  “Groups become teams through disciplined action.  They shape a common purpose, agree on performance goals, define a common working approach, develop high levels of complementary skills, and hold themselves mutually accountable for results.”

Teams are made up of individuals with complementary skills - build on strengths, not to cover weakness.  Define clear goals, via team communication. Build real-time problem solving skills and initiative, allow adaptive behavior.  Provide social dimension to enhance work - teams fundamental nature are people interactions.  Fun is part and parcel of the process - encourage it.

Resistance to teams come from 3 primary concerns: ”lack of conviction”, “personal discomfort and risk”, and “weak organization performance ethics” (p 21-23). 

Teams do not solve all problems, they are not the answer to every problem.  They require discipline and practice.  Organization culture may be opposed to teams if a strong individualistic performance is reward in spite of team performance.

Chapter 2:  One Team: A Story of Performance

As a basic unit of performance a team blends the knowledges, skills and abilities of several people strengthening the overall performance of individuals.  Many people having once experienced the power of a high performing team long for the experience again.  Burlington Northern launched the Intermodal Rail era after deregulation in 1981.  Largely the result of a core team of 7 individuals, with an extend group of 45 people.  This team was largely self selective, all were interested in the new prospects of intermodal rail and saw the value even in face of large corporate resistance and hostility.   The team started small and grew as needed, bringing in and fostering the required skills.  A positive attitude that the goal was possible was shared by all.  Hard work and long hours were the norm for the group.  When the group’s proposal was approved but with the worst pilot project locations the group saw the opportunity to prove the concept and jumped right into it.  The core group shared leadership roles and had strong affinity of tacit information on specific skill sets.  They assumed a ask for forgiveness rather than permission attitude, and resolved impediments quickly.  The results was a change in the business model for the industry, intermodal rail is now common place and well established business process for the rail industry. 

Ch 3 Team Basics A Working Definition and Discipline

Teams are a “powerful vehicle for performance” (p. 43)  many companies are embracing teams as a unit of performance.  There are differences in understand of what a team is and what constitutes a performant team.   Teams work well when they have specific results to achieve, and the performance ethic of the organization demans those results.

“A team is a small number of people with complementary skills who are committed to a common purpose, performance goals, and approach for which they hold themselves mutually accountable.” (p. 45)

Small number - in the Agile community we say 7 +/- 2  ( 5 - 9 members).  Reasoning is the tacit knowledge of each other (the group) and the intercommunication of the team.  The larger the number the lower the accountability for success.  Large numbers have logistical problems not seen in smaller groups (space to meet, etc.).  See Also: Choosing the Team Size in Scrum by Agile Pain Relief

Scrum (software development process) offers a way to scale teams to very large (hundreds) numbers.

Complementary skills - we call this a cross-functional team.  A team must have a person with the required skills to solve the problem, and it will take many skills to solve most any complex problem.   Many successful teams realize they lack certain skills, and become self reliant on learning or acquiring the skill set.

Committed to common purpose and performance goal.  Teams must see the purpose for their existence, be motivated to achieve the goal.  The best teams spend significant time discussing their purpose, reshaping it and refining that purpose over their lifetime.

Committed to a common approach.  Agreement on the approach, process to solve the problems is a key,  they may spend considerable time on this issue also. 

Mutual accountability.  Teams must hold each other accountable for the achievement of the goal, the quality of the products, and the process.  They must be capable of defining their own standards for performance and encouraged to raise the bar.  


Ch 5 The Team Performance Curve

A team does not start out at super high performance, it takes time to reach this goal.  Many teams never reach their potential.  Experts say that if a team does reach high-performance that it should not be disbanded but kept together, and given a new purpose.  The performance curve describes this growth to high-performance.

Work groups are not teams, though they may develop into a team.  One difference is the focus either on team performance or individual performance & accountabilities.

Pseudo-teams never agree on purpose, or accountability of the group, they get stuck in rituals and avoid rather than engage each other.

Ch 8  Teams, Obstacles and Endings:  Getting Unstuck

Every team will encounter obstacles, high-performing teams develop tools for overcoming these obstacles.  Teams lower of the performance curve may need help to over come obstacles of all natures.  Teams may become stuck, and not develop the tools to resolve their obstacles, then it is time for serious help.  Stuck teams: lack energy, or enthusiasm, have a sense of helplessness, lack identity, lack purpose, members are cynical, and have a high degree of mistrust.

A weak sense of direction - the team needs to create common goals, take joint responsibility.

Insufficient commitment to performance - team needs accountability for the problem and the solution, based in performance measures.

Critical skills gaps - team needs to hire experts or develop skills.  They must be capable of admitting they need help - identify the type of help and go get it.

Getting unstuck:  - 1) revisit the basic of teams, 2) build on small successes, 3) inject new information and techniques, 4) get facilitation skills & training, 5) change team membership or leader


Transitions and endings will also effect the team, may drop them back into lower stages of Tuckman model of development - allow for that, don’t expect no emotion for losses. 
Post a Comment

Most Popular on Agile Complexification Inverter

Software Development terms applied to Home Construction

Let's Invert the typically wrong headed view of Software Development project management as a construction project.  We can map it the other way just to see if it works... to have some fun, to explore the meaning of phrases we toss around quite frequently.


Normally Project Management terms come from a construction domain.  We are going to apply the lexicon of modern software to the construction of a home.  We will follow the construction project and meet some of the people doing the work.

This is a very small (8 homes from $600,000 skyward) program in my 30-40 year old neighborhood.

About 6 months ago I saw the programs landing page go up.  It gives casual observers and some of the stakeholders a general idea of the intent of the program.  And most importantly who to contact for additional information if you happen to be interested in their products.

The Refuge program has 8 product projects and has them running independently.  Yet much of their DevOps infrastructure has already b…

Where is Shakespeare When We Need Him?

We are desperately searching for a term for people that connotes the best of human kind.  The creative, sensing, combinatorial synergistic, empathic solutioning persons that have yet to been labeled with a role name that works.

Some of the old terms:
Staff, Workforce, Human Resource, My Team, Army, Company

Shakespeare created 1700 words in his time.  He mutated verbs to nouns, and vice-a-versa, transformed verbs into adjectives, and formed words from whole cloth never before heard.  This skill is rare, but there is a poet that can create the term we need in the twenty-first century.

What should this term define?

21st Century Human Resource; the generalizing specialist.

Yes, but what more?  What less?

Suggest your poetry in the comments, let us see if we cannot do 1/1700 as well as The Bard.

By-the-way; who create the phrase "coin a word"?



A TED Play List - How do you create new words
6:52
Erin McKeanGo ahead, make up new words! In this fun, short talk from TEDYouth, lexicographer Er…

a little feedback please...

some feedback please...
How do you like the new look and feel of our site?
  ___)  nah (I like the old one better - bring it back)
  _X_)  yeah (much cleaner and easy to navigate)



powered by Typeform
See Also:

One Dark and Stormy during a Hurricane

I'm from the Carolina's where legend has it that our family commonly just hunkered down in the home on the coast and waterways than to head for inland shelter. Now that's from the old school days of barely improved (read paved) roads. They counted a storms severity by how high on the back porch steps (about 15 - top to ground) the water reached.  I don't recommend this action in todays world of long range forecast and transportation options.

I do recommend a drink or two in a hotel bar, far far away.

This is the week that Harvey came ashore in Texas.  I live on a hill in the little old town of Grapevine outside Dallas and Fort Worth.  And thank you all for letting me know that a storm is coming... I didn't get out and walk Malibu before the rain hit, so I grabbed a hat and we went anyway.  Much nicer walk with the drizzle, I'd say.

I'll raise a glass to you - if you were not smart enough to do the responsible thing, at the last responsible moment.

I do re…

Innovation in the Automobile Industry

In the 1900s the automobile industry was the most important and innovation industry in the USA.  But one could question if this was good for our society in the long run.  And one could question if they actually innovated.

In the early 1900s there were few automobiles, very little infrastructure created to support the industry.  For example the road system was still designed for horse drawn wagons and the wagon wheel (remember a steal rim and wooden compression spoke wheel).  The future US Highways, or the 1950s Interstate Highway System at the cost of $425 billion were decades and many innovations away. There was no gas service station, there were however horse stables, farriers, and blacksmiths in each town along the roads.  There was no real "road map", there was no road naming system, like was created in 1926 - the United States Numbered Highway System.

The industry employees millions of people, and was a large factor in the economy of the USA.  It created or was created b…