Designing and Building Effective Work Teams, Explained

UPI Study › Courses › Foundations of Leadership › Free lessons › Lesson 10.4 Free with a free account

Designing and Building Effective Work Teams

Foundations of Leadership · Chapter 10: Teams ModuleSection 10.4 · lesson 68 of 9012 min · free with a free account

← High-Performing TeamsNext lesson: Virtual Teams →

Earn 3 college credits for Foundations of LeadershipRecommended for credit by NCCRS · Business 205 · self-paced · one payment, lifetime access
Enroll in Foundations of Leadership · $250 →Download the syllabus (PDF)

In this lesson

Composing, configuring and orienting a team toward the work it has been given.

  • Treat team design as a deliberate act with consequences
  • Compose for skill, cognitive diversity and size
  • Set purpose, goals and norms explicitly
  • Build psychological safety through specific behaviours

Free study notes

Get this lesson's notes by email

The key points and 4 practice questions with answers, in your inbox. One email, free.

One email. Unsubscribe in one click.

Transcript

Everything said in the video, section by section (1,637 words). Read along, or search it.

Teams Module

Designing and Building Effective Work Teams

In most organisations, nobody actually decides who is on a team. Membership carries over from the last project, or falls to whoever happens to be free. Norms get discovered by accident, several months in. And then the team is judged on results that its design made unlikely. This section treats team design as what it is. A deliberate act with consequences. Composition, orientation, decision architecture, and psychological safety. The aim is to move team-building from a tacit art into an explicit discipline. One that any practising manager can actually apply.

By Default

The Most Consequential Decision Nobody Makes

Start with how teams form when nobody designs them. By inheritance. Members from a previous project carry over to the next. By availability. Whoever is free gets assigned. Or by reputation. Whoever is best known to the manager gets chosen. Each is a reasonable-sounding shortcut, and each produces a team built by organisational accident. Not the requirements of the work in front of it. Recall Hackman's finding from the previous section. Team effectiveness is largely determined by design conditions before the team begins. Which means deliberate design is not a luxury for leaders with time on their hands. It is the highest-leverage action available to them. And it is almost always available at the moment when it is cheapest to take.

The Sequence

From the Work Outward

Deliberate design runs in a rough order, and the order matters. It begins with the work, not with the people. What must this team produce, and over what time horizon? Composition comes second. Skill matched to the work, cognitive diversity, and the smallest workable size. Orientation comes third. Purpose, goals, and norms made explicit. Then decision architecture. Which mode, for which category of decision. And renewal, which is not a final step but a recurring one. Skipping a stage does not remove the work it represents. It defers that work to a moment when the team is under pressure and rework is expensive.

Start Here

Questions Obvious in Print, Skipped in Practice

Designing from the work means answering a specific set of questions first. What is the team being asked to produce? What kinds of expertise does that work require, and how should they be combined? What is the time horizon, and is membership stable across it? Which decisions must the team make collectively, and which can be made by individuals? Who must the team interact with externally, and what does that require of its composition? These questions look obvious written down, and are routinely skipped, because the work is waiting. But the team that answers them at the outset is doing work that cannot be avoided. The team that skips them does the same work later, mid-project, under pressure. With the cost of rework added on top.

Composition

Skill Match and Cognitive Diversity

Composition deserves attention on three dimensions. Take skill first. The team needs the skills its work requires. Not the most prestigious skills available, and not the ones the manager can most easily get. The common error is over-selection on technical skill. At the expense of complementary capability in process, integration, or external engagement. A team of brilliant engineers may need a translator to the customer. A team of strong analysts may need someone who can actually drive a decision. The second dimension is diversity, and the research here is consistent. Anita Williams Woolley and colleagues at Carnegie Mellon studied collective intelligence in teams. Teams with greater cognitive diversity outperform homogeneous teams on complex work. Different mental models, different ways into a problem, different relevant experience. The mechanism is not mysterious. Diverse perspectives surface more options and expose blind spots. But note the distinction. Cognitive diversity is correlated with demographic diversity, not identical to it. A team can be demographically diverse and cognitively narrow, or the reverse. So selection has to attend to how candidates think, and not only to their credentials.

Composition

Why Size Punishes You Non-Linearly

The third dimension is size, and it punishes you faster than intuition suggests. Team performance is inversely related to size beyond a relatively low threshold. Hackman's work found that teams of more than nine members consistently underperform smaller ones. That holds on complex collaborative tasks, which is most interesting work. The reason is coordination overhead, and it grows non-linearly. A team of four has six pairwise relationships to maintain. A team of ten has forty-five. Nobody adds those relationships deliberately. They arrive with the extra members. And many teams are made larger than they need to be for political reasons. Stakeholders are included so their concerns can be managed. The team then pays the performance cost for the entire life of the project.

Case

The Team That Was Too Large

A pharmaceutical company provides the textbook version of this failure. It assembled a fifteen-person team to oversee the launch of a new drug. Regulatory, clinical, marketing, sales, supply chain, medical affairs, finance, communications, and three regions. Every function was represented, which is exactly why nothing moved. After three months of slow progress and proliferating meetings, the leader restructured. With senior sponsorship, a core team of six was given the decisions. The remaining nine became an extended team. They received updates, contributed input asynchronously, and joined for decisions needing their expertise. Progress accelerated within weeks. The lesson is not that stakeholders should be excluded. It is that decision-making membership and informational stakeholder relationships are different things. Designing them as if they were the same is what produced the paralysis.

Orientation

Purpose, Goals and Norms Are Three Different Things

Once composed, a team needs orientation, and three orientations get confused with each other. Purpose is the team's reason for existing. Expressed in terms that connect the daily work to some consequence. Purpose is not goals. Goals are derived from purpose. A team without clear purpose can pursue its goals successfully and still miss the point entirely. Goals are the specific outcomes the team commits to, with timeframes and measures. The discipline of well-formed goals is familiar enough, so note only this. Goals drift when nobody reviews them. Teams that meet their goals tend to be teams that revisit them often enough to detect drift early. Norms are the working agreements about how the team operates. How decisions get made. How disagreement is handled. How meetings run. How feedback is given. Norms develop in any case. The only question is whether they develop explicitly or by accident. Agreed early and revisited, explicit norms prevent implicit ones accumulating against the team.

Decision Rights

Four Modes, and the Cost of Each

Few aspects of design are as consequential, or as routinely overlooked, as decision architecture. Teams make many kinds of decision, and not all benefit from the same approach. Consultative decisions suit situations where the leader holds accountability but benefits from input. The risk is that members feel consulted but not heard, when input does not influence the outcome. Consensus suits decisions the team must own and execute together. It is slow, tends toward lowest-common-denominator outcomes, and gets difficult above about seven people. Majority vote suits constrained time, where a divided outcome is acceptable. It loses the dissenting view, and used repeatedly it entrenches fault lines. Delegated decisions suit areas where one member has clear expertise or accountability. The risk is decisions made in isolation that affect people who were never consulted. Real practice is usually hybrid, and that is fine, provided the mode for each decision is explicit. Most team frustration traces not to the substance of decisions but to confusion about how they were made.

Safety

The Strongest Single Predictor

One design concern predicts more than any other, and it is not a soft one. Amy Edmondson's research at Harvard began in the nineteen nineties. It was synthesised in The Fearless Organisation, published in twenty nineteen. Psychological safety is the shared belief that members can speak up without retaliation. With questions, concerns, mistakes, or half-formed ideas. Her empirical work ran across hospitals, factories and offices. And it produced a result that looks backwards at first glance. Teams with greater psychological safety reported more errors. Because they surfaced them rather than concealing them. And they committed fewer, because surfaced errors could actually be corrected. Google reached the same conclusion independently, in its internal study Project Aristotle. Of all the factors it examined, psychological safety was the strongest.

Safety

Not Comfort, and Not Niceness

Psychological safety is frequently misunderstood as comfort, or as niceness. It is neither, and the confusion causes real damage. A psychologically safe team is often characterised by more disagreement, not less. Because members surface their concerns rather than withholding them. The quiet, agreeable team is frequently the unsafe one. So the leader's role is not to remove difficult content from the conversation. It is to make it safe for difficult content to be raised. That is built through specific, unglamorous behaviours. Responding constructively when a concern is voiced, rather than defensively. Modelling acknowledgement of your own errors. Soliciting input from the members who would otherwise stay silent. And protecting the member who challenges the consensus. None of those is dramatic. Their cumulative effect over months is decisive.

Consolidate

Design Once, Renew Repeatedly

A well-designed team at its outset is not a well-functioning team in perpetuity. The work evolves. Members come and go. The organisation changes around the team. Teams that do not renew themselves decay in predictable ways. Norms calcify, purpose drifts, and skills become stale. And the assumptions the original design rested on quietly stop holding. So renewal is a regular discipline, not an occasional reset. Review purpose against the work the team is actually doing now. Review skill composition against current needs rather than past ones. Revisit norms, and explicitly retire the ones that no longer serve. And bring new members in so they test the team's patterns, rather than being absorbed into them. One more discipline is worth adopting at the very start. The pre-mortem. Before any work begins, the team imagines the project has failed, and discusses why. It surfaces gaps in skill, unclear decision rights, unrealistic timelines, conflicting incentives. Ninety minutes, and three or four practical adjustments nobody would otherwise have made. The teams that perform for years are not the ones with a perfect original design, but the ones that renew reliably.

About Foundations of Leadership at UPI Study

Foundations of Leadership (Business 205) is a self-paced online course of 90 video lessons in 12 chapters, from the roots of leadership theory and the trait, situational and transformational approaches to power, decision-making, communication, teams, conflict, diversity and global leadership. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Business courses Every course with PRO →

Compare: Management and leadership courses · Foundations of Leadership vs Leadership and OB

Why take it here

Why students take Foundations of Leadership with UPI Study

What makes people follow a leaderFoundations of Leadership covers the main theories of leadership and how leaders use power, make decisions, communicate, build teams and handle conflict. It is a common course in business, management and organizational leadership degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Foundations of Leadership carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Designing and Building Effective Work Teams

How do you design an effective work team?
Effective team design starts with the work, not the people. First define what the team must produce and over what time horizon. Then choose composition, matching skills to the work, seeking cognitive diversity and keeping the team as small as workable. Next make purpose, goals and norms explicit, then decide which decision method applies to which kind of decision. Finally, renew the team regularly by reviewing purpose, skills and norms as the work changes.
What is the ideal size for a work team?
Smaller teams usually perform better on complex collaborative work, and Richard Hackman warned that teams larger than about nine members tend to underperform. The reason is coordination overhead: the number of pairwise relationships equals n times (n minus 1) divided by 2, so a team of four has six relationships while a team of ten has forty-five. Separating a small decision-making core from a wider group that is kept informed can help large projects.
What is psychological safety in a team?
Psychological safety is the shared belief that team members can speak up with questions, concerns, mistakes or half-formed ideas without fear of punishment or humiliation. Harvard's Amy Edmondson, who defined it for teams in 1999, had earlier found in hospitals that better teams reported more errors because they surfaced them, letting those errors be corrected. Google's Project Aristotle also found it the strongest factor it studied. It is not niceness; safe teams often disagree more openly.
What decision-making methods can teams use?
Teams commonly use four decision methods: consultative, consensus, majority vote and delegated. Consultative decisions suit cases where the leader is accountable but wants input. Consensus suits decisions the whole team must own, but it is slow and gets harder above about seven people. Majority vote is fast but loses dissenting views. Delegation suits areas where one member has clear expertise. Most teams mix methods; the key is making clear which method applies to each decision.

About the Foundations of Leadership course

How many college credits is Foundations of Leadership?
Foundations of Leadership (Business 205) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Foundations of Leadership cost and what is included?
$250, paid once, with lifetime access: all 90 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Foundations of Leadership take?
It is self-paced with no deadlines. The 90 lessons total about 16 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Foundations of Leadership.

90 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Foundations of Leadership →Download the syllabusEvery course with PRO →
Foundations of Leadership
3 credits · NCCRSEnroll →