What makes a group of people a team, per the definition used in this lesson?
Choose an answer, then check it.
Management & Leadership · Foundations
Teams
On this page 9 sections
In 30 seconds
More than a Group A collection of individuals who share a setting but do not share a goal or mutual accountability; the label applies to any gathering, team or not. Full entry →, a Team A group of people with complementary skills who work toward a shared goal and hold themselves mutually accountable; the definition this lesson follows Katzenbach and Smith as presented by OpenStax. Full entry → is a set of people with complementary skills who work toward a shared goal and hold themselves mutually accountable — the definition this lesson follows Katzenbach and Smith, as presented in OpenStax's Principles of Management. Organizations use teams because complex work needs many hands and minds. The main team types are functional, cross-functional, and self-managed. Teams work best with a clear goal, clear roles, trust, and communication — but building one takes coordination time, and conflict happens.
Why this matters
Organizations keep assigning work to teams because complex work needs many hands and minds — and because a well-tuned team can produce results no single member could. But teams fail as often as they succeed, and the difference is rarely talent. It is structure: a shared goal, defined roles, trust, and honest communication. Understanding what a team is — and is not — lets you see when a 'team' is only a collection of people wearing a label, and why some teams click while others stall. The same test applies whether you join a study group, a volunteer committee, or a workplace project: complementary skills, a shared goal, and Mutual accountability The condition in which each member answers for the team's collective results, not only for their own piece of the work. Full entry →.
The college version
More than a group: the working definition
Few words in management get used as loosely as 'team.' A company's directory calls every department a team; a project that never meets calls itself one. This lesson needs a working definition, and it follows Katzenbach and Smith, whose Harvard Business Review article 'The Discipline of Teams' is the classic account, as presented in OpenStax's Principles of Management. OpenStax lists the five elements that make a team function: a common commitment and purpose, specific performance goals, complementary skills, commitment to how the work gets done, and mutual accountability. This lesson condenses those five into three that carry the same meaning: complementary skills, a shared goal, and mutual accountability. Consider the night shift at Northgate Bakery: a baker, a decorator, a packer, and a delivery driver. Each brings a different skill; all four share the goal of getting the morning shipment out; and if the shipment fails, all four answer for it together. That is a team. Members discuss, decide, and do real work together, and they measure success by their collective output.
Team versus group: the distinction
The test for 'team' is whether the people share a goal and hold themselves mutually accountable — not whether they share a room, a shift, or a label. OpenStax contrasts a team with the classic Working group A set of individuals under a leader whose performance is the sum of separate individual efforts, with no collective work product. Full entry →: a working group has a focused leader, individual accountabilities, and individual work products, and its purpose is whatever slice of the broader mission it was handed. Katzenbach and Smith put the distinction sharply: in an ordinary working group, performance is a function of what members do as individuals, while a team's performance calls for both individual and mutual accountability. Two examples make it concrete. The five nurses on the 7 a.m. shift at Riverside Clinic each care for their own patients, report to their own supervisors, and share nothing but a break room — a collection of people, a group. The hospital's discharge-improvement committee — a nurse, a pharmacist, a surgeon, and an administrator — shares one goal, depends on one another's expertise, and answers together for the result. Same building, different animal. One honest corollary from Katzenbach and Smith: if a task does not demand joint work, a working group is often the more effective choice.
Why teams: many hands and many minds
Organizations form teams because the work outgrew the individual. Building a new store, launching an app, or redesigning a patient discharge draws on skills no one person holds — design, finance, operations, marketing — and on more hours than one person has. OpenStax opens its chapter on teams with the old saying, credited to Aristotle, that the whole is greater than the sum of its parts: a team creates a synergy that the members alone cannot produce. OpenStax's Introduction to Business makes the same point about project teams built from different functions: pooling the skills of various specialists increases creativity and innovation and lets an organization tackle more complex tasks. Teams also multiply minds on a problem — more perspectives, more chances to catch a flaw before it ships. That is the core argument, and it is simple: when the work is complex, many hands and minds beat one.
The team types: functional, cross-functional, and self-managed
Management practice recognizes three common shapes of teams. A Functional team A team whose members all come from the same department or function and do that department's work together. Full entry → is made of people from the same department doing that department's work together — the four loan officers at Meridian Credit Union who share a supervisor, process the same portfolio of applications, and cover for one another in busy weeks. A Cross-functional team A team that draws its members from different departments or functions to work on one shared project. Full entry → draws members from different departments to work on one shared project. OpenStax's Introduction to Business describes the matrix structure this way: it brings together people from different functional areas — manufacturing, finance, marketing — to work on a special project. Summit General's discharge committee is cross-functional: a nurse, a pharmacist, a surgeon, and an administrator, each from a different function, all on one project. A Self-managed team A team that organizes its own work — schedules, task division, and quality checks — without a traditional supervisor. Full entry → organizes its own work — schedules, task rotation, quality checks — without a traditional supervisor. OpenStax's Principles of Management mentions self-directed work teams on manufacturing floors; the four-person assembly crew at Alder Appliance, which divides its own tasks and calls the plant manager only about supplies, is one. These three are the common shapes, not an exhaustive catalog — organizations also spin up temporary project teams and virtual teams as needed.
What makes teams work — and what it costs
The research OpenStax reports points to four conditions that make teams work, each sayable in one line. A clear goal: teams work best when they have a compelling reason for being, with demanding performance standards and direction. Roles: members should be chosen for their skill and skill potential, and everyone should know who does what — role clarity was among the strongest collaboration factors in the Gratton and Erickson research OpenStax cites. Trust: OpenStax notes that time spent together builds camaraderie and trust, and Patrick Lencioni's The Five Dysfunctions of a Team, quoted in OpenStax, puts absence of trust first — without it, members fear conflict and never debate honestly. Communication: teams need explicit rules of behavior, fresh facts, and positive feedback; the mechanics of communication get their own topic. Then the honest costs. Coordination takes time: agreeing on schedules, rules, and how decisions get made is real work, and OpenStax quotes a turnaround manager saying that building an environment for teamwork takes time. Conflict happens: OpenStax lists communication breakdowns, competing goals, power struggles, and personality clashes as routine sources, and badly handled conflict breeds distrust and stalls progress. The reality check: a team is a machine that needs tuning, not magic. Five talented people in a room do not form a team by themselves — the goal, roles, trust, and communication have to be built, and maintained.
Eli explains
The same idea, in plain words
Explain it like I’m 10
A team is more than a bunch of people in the same room. It is a group that shares a goal, brings different skills, and answers for results together. Teams exist because complicated work — a new product, a big event, a hospital process — needs more skills and more minds than any one person has. There are three common kinds: functional teams (same department), cross-functional teams (different departments on one project), and self-managed teams (the team runs itself). A team works when it has a clear goal, clear roles, trust, and communication. The honest part: building a team takes time — meetings, rules, arguments — and conflict happens even in good teams. Five talented people do not make a team by themselves; the team has to be built.
Picture it like this
Think of a rowing crew: eight rowers and a coxswain. Each rower has a position and a skill; they share one goal — crossing the finish line first — and if one rower stops pulling, the whole boat slows, so everyone answers for the boat's result. They practice together until the stroke is smooth. A crew that simply put eight strong athletes in a boat and pushed off would lose.
Where the picture stops working
The analogy has limits. A rowing crew is picked for one purpose, trains for months, and rows one kind of race, while workplace teams form around changing problems, with members coming and going. A crew's success is measured by a single finish line; a work team is judged by many interdependent results over time. And a coxswain steers from outside the work — most teams must coordinate themselves, with leadership shared.
Worked example
Watch one team form at Solstice Gear, an outdoor-equipment maker. Management wants a new backpack line in stores in eight months — complex work spanning fabric sourcing, design, costing, and marketing. The company assembles a cross-functional team: a designer, a materials buyer, a cost analyst, and a brand marketer. First they agree on the goal: a $120 pack, 30,000 units, shipped by March. Then roles: the designer owns samples, the buyer owns fabric, the analyst owns pricing, the marketer owns the launch. Early meetings move slowly — that is the coordination cost. When the designer and the buyer clash over a fabric, they settle it with a prototype test instead of an argument. Small milestones build trust. The line ships on time — not because the four were brilliant, but because the machine got tuned.
Key takeaway
A team is more than a collection of people: it is a group with complementary skills, a shared goal, and mutual accountability — and like any machine, it needs a clear goal, roles, trust, and communication, plus regular tuning, to perform.
Quick check
3 questions here, of 5 in this lesson’s practice set. Answers stay hidden until you check.
Five nurses at Riverside Clinic work the same shift and share a break room, but each cares only for her own patients and reports to her own supervisor. The clinic calls them 'the day team.' Why is the label inaccurate?
Choose an answer, then check it.
Summit General Hospital forms a committee to redesign patient discharges: a nurse, a pharmacist, a surgeon, and an administrator, each from a different department. What type of team is this?
Choose an answer, then check it.
Study tools & related lessonsYou’ll learn to · Common mistakes · Easily confused · Key vocabulary · Related
You’ll learn to
- State the working definition of a team — a group of people with complementary skills working toward a shared goal with mutual accountability — attributed to Katzenbach and Smith as presented in OpenStax's Principles of Management.
- Distinguish a team from a group, applying the shared-goal and mutual-accountability test to workplace examples.
- Explain why organizations use teams: complex work needs many hands and minds working together.
- Name the three team types — functional, cross-functional, and self-managed — each with an original example.
- Identify what makes teams work (a clear goal, roles, trust, and communication) and name the honest costs (coordination takes time; conflict happens).
Common mistakes
Calling any collection of people a team.
A label does not make a team. Test for the definition: complementary skills, a shared goal, and mutual accountability. People who merely share a shift or a department are a group.
Assuming talent is enough.
Five strong employees in a room do not form a team by themselves. Katzenbach and Smith's practices — a compelling purpose, skill-based roles, rules of behavior — have to be put in place deliberately.
Expecting teams to be free.
Coordination takes time: agreeing on schedules, roles, and how decisions get made is real work. OpenStax quotes a manager who says building an environment for teamwork takes time.
Treating conflict as proof the team is broken.
Conflict is a normal cost of teamwork — OpenStax lists competing goals and personality clashes as routine sources. Handled constructively, conflict can strengthen a team; avoiding it entirely erodes trust.
Easily confused
Group vs. Team
A group is a collection of individuals who share a setting; a team shares a goal, complementary skills, and mutual accountability. The Riverside nurses are a group; the discharge committee is a team.
Functional team vs. Cross-functional team
A functional team's members all come from one department; a cross-functional team pulls members from different departments to work on one shared project — like Summit General's discharge committee.
Key vocabulary
- Team
- A group of people with complementary skills who work toward a shared goal and hold themselves mutually accountable; the definition this lesson follows Katzenbach and Smith as presented by OpenStax.
- Group
- A collection of individuals who share a setting but do not share a goal or mutual accountability; the label applies to any gathering, team or not.
- Mutual accountability
- The condition in which each member answers for the team's collective results, not only for their own piece of the work.
- Functional team
- A team whose members all come from the same department or function and do that department's work together.
- Cross-functional team
- A team that draws its members from different departments or functions to work on one shared project.
- Self-managed team
- A team that organizes its own work — schedules, task division, and quality checks — without a traditional supervisor.
- Working group
- A set of individuals under a leader whose performance is the sum of separate individual efforts, with no collective work product.
- Cohesion
- The interpersonal bond among team members that keeps them motivated and committed to the team's goals.
Sources & references
- Principles of Management, Chapter 15 Introduction: Managing Teams — OpenStax, Rice University
- Principles of Management, Section 15.1: Teamwork in the Workplace — OpenStax, Rice University
- Principles of Management, Section 15.3: Things to Consider When Managing Teams — OpenStax, Rice University
- Principles of Management, Section 15.4: Opportunities and Challenges to Team Building — OpenStax, Rice University
- 7.2 Contemporary Structures — Introduction to Business — OpenStax (Rice University)
- The Discipline of Teams (Katzenbach, J. R., & Smith, D. K., Harvard Business Review, March 1993) — Harvard Business Review
- Team Cohesion — What It Is and Strategies to Develop It — Corporate Finance Institute (CFI)
EliExplains lessons are original prose written from the open, credible references above. See Copyright & Licensing.
Researched 2026-08-22
Educational content only. It is not medical, legal or professional advice. Found an error? Tell us.