Most organizations have something called an executive or senior leadership team that typically ranges in size from 6-15 people. It consists of the CEO,  COO, and functional and business unit heads. General responsibilities for top teams include setting strategy, defining organizational structure, determining key roles staffing , setting performance targets, making policy, and managing the business. Because of their unique membership and responsibilities there are some interesting observations about teams at the top that are worthy of additional discussion.

1.  Who is on the Team? Richard Hackman reported that only ten percent of the 120 top teams he researched had agreement on team membership. This finding fits in with our observations on senior leadership teams  -- inclusivity often trumps efficiency and effectiveness. These findings suggest that many top teams have “loose” boundaries and may not be as tightly aligned as one might think.

2. Top Teams are often too big to be Effective. Because top teams tend to be more inclusive than exclusive, most are too big to be effective. Since the number of relationships to manage increases exponentially with each member, top teams bigger than ten members typically suffer from efficiency, effectiveness, speed, alignment, and communication problems. Organizations tend to be more successful when CEOs use a top team of 5-7 key leaders to deal with key challenges, make decisions, and manage day-to-day affairs and a more extended team to help set strategy, review quarterly business results, etc.  

3. Should Teams at the Top Operate as a Group or a Team?  As described in The Rocket Model: A Practical Guide for Building High Performing Teams, the tasks should dictate if an individual, group, or team is the most effective way to operate. Yet top teams rarely if ever have this discussionsince the CEO usually dictates what he or she is comfortable with and leads accordingly).  Although it is well within the prerogative of CEOs to determine how they want to manage their top teams, team efficiency, effectiveness, and, ultimately, organizational performance suffers whenever there is a mismatch between the CEOs’ leadership approach and the tasks to be performed by their top teams.

4. How do Top Team Members Define Their “First Team”?  Because top team members have their own organizations to manage, oftentimes C-Suite executives define their “first team” and the function or business unit they manage. In other words, their primary loyalties lie with the HR function or EMEA business unit rather than with the top team. If the CEO is managing direct reports as a group then this is not a big deal, but these divided loyalties will cause major problems if the CEO wants to build a high performing top team. CEOs can minimize this problem by having an explicit discussion about whether direct reports should operate as a group or a team (or when it is appropriate to do so).

5. Artificial Harmony. Top team members rarely complain in team meetings, even thoughthey may suffer from divided loyalties, be unsure of who is or is not on the team, have a team too big to be effective, and/or be under a CEO using the wrong managing approach.  Many members come to meetings with “their lips sealed” and refuse to bring up controversial issues. As a result, top teams suffer from artificial harmony and talk about how wonderful everything is in meetings only to complain to their staffs. Rather than hashing out disagreements in team meetings, top team members often use proxies to fight their battles. Organizations whose top team members heap praise on their peers, yet suffer from a “silo mentality,” are often victims of artificial harmony.

6. The Cascade Effect. It is important to remember that top team dysfunction has a ripple effect across the rest of the organization. Open warfare between the heads of R&D and Marketing, Marketing and Sales, Sales and Operations, or Finance and IT will play out in major battles between the departments. CEOs need to explicitly manage artificial harmony and open warfare if they want to create a fully engaged workforce and a high performing organizational culture.

Every group and team operates in a specific context. The situation faced by a U.S. Navy SEAL team in Afghanistan is different from that faced by a team drilling for gas in North Dakota. Context is interesting because (a) it is very complicated and (b) existing research is not very helpful in telling us how context affects team success. Yet, contextual factors critically impact the success or failure of a team. The extent to which leaders can control  situational factors affecting their teams and groups varies greatly. Some situational factors can be directly influenced, others can be influenced only indirectly, and many cannot be controlled at all. Because contextual factors have a profound impact on group dynamics, getting team member alignment on these factors is a critical responsibility for leaders. All too often team members have different assumptions about customers, suppliers, or competitors.  Their well-intended, but misaligned, actions can inadvertently destroy team morale and sub-optimize team efficiency and effectiveness.

One noteworthy aspect of team context is the implicit nature of team member assumptions—team members rarely if ever articulate their assumptions about key stakeholders. In order to make the implicit more explicit, team members should work together to identify the key constituencies that affect the team. These entities might include key customers, competitors, other teams, regulatory agencies, vendors, the parent organization, etc. Team members should then discuss and agree on the top three to five assumptions they have for each constituency. Gaining alignment on team context makes it much easier to determine the purpose and key goals for the team;  reviewing team assumptions about key constituencies can also help new members get integrated into the team more quickly. 

There is no universally accepted model for transforming collections of individuals into high performing teams. There are four more common models used to improve team performance, which include Tuckman’s Stage Model, Hackman’s Inputs-Processes-Outputs Model, Lencioni’s Five Dysfunctions of a Team, and Curphy and Hogan’s Rocket Model. Although each of these frameworks offers unique insights into team dynamics, The Rocket Model has several distinct advantages over the others.

Tuckman’s Stage Model. Tuckman noted that leaderless discussion groups seemed to go through four distinct phases: forming, storming, norming, and performing. Groups do not become highly effective until they reach the performing stage. The model provides advice to leaders for helping groups transition through the four phases. Although these phases can readily be seen in volunteer groups, they rarely occur in corporate settings since work groups are usually brought together for some purpose, have better defined roles, and have some sort of pecking order.

Hackman’s Inputs-Processes-Outputs Model. According to Hackman, inputs are the raw materials available to a group or team, and include team members, raw materials, equipment, etc. Processes are the procedures or systems team members use to do work, and outputs are the end products. The inputs-processes-outputs model is based on sound research, but is too vague to be of much use.

Lencioni’s Five Dysfunctions of a Team. Lencioni developed a team stage model that includes: (a) absence of trust; (b) fear of conflict; (c) lack of commitment; (d) avoidance of accountability; and (e) inattention to results. The model provides some useful insights into team dynamics, but is not based on sound research, and although it seems to make intuitive sense, in many cases it is simply wrong.

Curphy and Hogan’s Rocket Model. The Rocket Model capitalizes on the advantages of the previous frameworks in that it is based on research from hundreds of teams and provides sound, practical advice for improving group and team performance. The Rocket Model consists of eight components, which include context, mission, talent, norms, buy-in, power, morale, and results. Context concerns gaining team member agreement on the challenges facing the team; mission is setting team goals and benchmarks; talent focuses on the number, roles, and skills of team members; norms pertain to the rules by which team members operate; buy-in is all about fostering employee engagement; power concerns acquiring needed authority and resources; morale pertains to the level of team esprit-de-corps and conflict, and the accomplishments attained fall in to the results component.

The Rocket Model can be used to diagnose current team functioning and launch brand new teams. It can also be applied to co-located and virtual teams and groups. Because it is based on a foundation of research and provides practical advice for improving team and group performance, we believe The Rocket Model is superior to the other three frameworks.

By Gordon Curphy
Curphy Consulting Corporation
Guest blogger and author of The Rocket Model

The terms team and group are often used interchangeably, but there are some differences between these two concepts.

We define teams as consisting of three to 25 people who:

• Work toward a common set of goals
• Work jointly
• Share common leadership
• Hold joint accountability for performance
• See themselves as being part of a team with common goals and shared fates

This definition of teams is somewhat different from the usual definition in three ways. First, according to this definition dyads are not teams. The dynamics between any two people are much simpler than those between three or more people. Second, this definition assumes people share a “mental model” about the teams to which they belong. In other words they identify themselves as being members of a particular team and tend to have common interpretations of events. And third, teams tend to be fairly small—usually less than 25 people. Larger groups may call themselves teams (such as a professional football team) but in reality they are usually groups made up of various sub-teams (the offensive unit, defensive unit, etc.). Common examples of teams might include commercial aircrews, crews of firefighters, United States Army platoons, product development teams, manufacturing shift workers, fast food restaurant crews, research and development teams, and soccer teams. The individuals in each of these examples share common goals, depend on the help of the other team members, share leadership and common fates, and most importantly, identify with their teams.

Groups are clusters of people that do not share these five characteristics to the same extent as teams. A regional sales team responsible for selling insurance and other financial services to local citizens would be a prototypical group. In this so-called team, each sales rep has individual revenue and profitability goals for an assigned geographic territory. An individual’s ability to achieve these goals does not depend on what the other sales reps do; instead it is completely dependent upon that person’s own performance. Although individual efforts contribute towards the region’s revenues and profitability goals, the region’s performance is merely the sum of each rep’s individual efforts. If a regional sales manager wants to increase revenues, then he or she could add reps, expand territories, increase prices, or change the product mix; requiring the reps to work more closely together would have little if any impact on the region’s financial performance.

This is not to say that leaders play passive roles when managing groups. In fact, far from it! Leaders in charge of groups need to ensure that the members operate under the same assumptions regarding customers and competitors, possess the right skills, stay motivated, share information, have adequate resources, achieve their individual goals, and get differences quickly resolved. Contrast these leadership demands with those of a head surgeon of a cardiovascular surgical team. The head surgeon would have many of these same leadership responsibilities but would also needs to ensure that their fellow surgeons, anesthesiologists, nurse practitioners, and physician assistants shared common goals, cooperated, used common work processes, had seamless task handoffs, shared a common fate, and identified with the team as they put stents and pacemakers into patients. Thus, the leadership demands on people in charge of teams are more extensive (and consequently more difficult to master) than the demands on people in charge of groups.  

By Gordon Curphy
Curphy Consulting Corporation
Guest blogger and author of The Rocket Model