Group dynamics and team dynamics: what they are, with 12 examples at work

What is group dynamics?

Group dynamics is both the study of how people behave in groups and the name for the patterns themselves. Social psychologist Kurt Lewin is usually credited with coining the term in the 1940s, and in 1945 he founded the Research Center for Group Dynamics at MIT. His central point still holds: put the same person in a different group and they behave differently, so a group’s patterns are worth studying in their own right.

The patterns form fast. Within a few meetings, a new group has settled who speaks first, how late is too late and which topics are safe. Most of it is never discussed, which is why a manager who learns to see it has a real advantage.

Team dynamics definition: how it differs from group dynamics

Every team is a group, but not every group is a team. The difference is a shared goal and work that depends on each other:

• A group

  • Any set of people who interact: a committee, a department, a class, a project kickoff.
  • Members may have separate goals and separate work.
  • Group dynamics: the patterns in how they talk, decide, conform and clash.

• A team

  • A group with a shared goal and work that depends on each other.
  • Success or failure is collective, so the patterns matter more.
  • Team dynamics: group dynamics applied to how a team gets its work done together.

So team dynamics, defined simply, are the forces that shape how a team works together: how its members communicate, decide, divide roles and handle conflict on the way to a shared goal. Strong team dynamics are one of the marks of high-performing teams.

Group dynamics theory: 8 ideas managers use

The research behind group dynamics goes back more than a century. These are the ideas that hold up best in day-to-day management, each with where it comes from and what to do with it.

1. 1. Behavior depends on the situation, not only the person

   Kurt Lewin, 1930s and 1940s

   Lewin summed up his field theory as B = f(P, E): behavior is a function of the person and their environment.

   Use it: Before deciding someone is the problem, look at the setup around them: the incentives, the meeting format, who they report to.

2. 2. Groups develop in stages

   Bruce Tuckman, 1965; adjourning added with Mary Ann Jensen in 1977

   Groups move through forming, storming, norming and performing, and finally adjourning when the work ends. Many practitioners add that groups can slip back a stage when people or goals change.

   Use it: Expect friction after a team forms or reorganizes, and lead differently at each stage.

   Our guide to the stages of team development covers each stage and how to lead it.

3. 3. People take on team roles

   Meredith Belbin, 1981

   Belbin's research on management teams led to his team roles: eight in the 1981 book, nine once he added Specialist, grouped today as action, people and thinking roles. He noticed that teams made up only of the sharpest individuals often did worse than balanced teams, which he called the Apollo syndrome.

   Use it: Look for the missing role, such as nobody who finishes or nobody who challenges, rather than hiring more of the same strength.

4. 4. Groups create unwritten rules

   Muzafer Sherif, 1930s

   In Sherif's experiments, people judging something ambiguous moved toward a shared answer, and the group's answer stuck with them later. Every group forms norms like this: how late is late, who may interrupt whom, what gets said out loud.

   Use it: Write your important norms down on purpose, or the group will settle on some by accident.

5. 5. Cohesion pulls a group together

   Leon Festinger and colleagues, 1950; later Albert Carron

   Cohesion is the set of forces that keep members in a group: commitment to its goals (task cohesion) and to each other (social cohesion).

   Use it: Build commitment to the shared goal first; shared success tends to build the social side more than the other way around.

   More in our guide to team cohesion, which includes a 10-question check.

6. 6. Conflict about the work differs from conflict between people

   Karen Jehn, 1990s

   Jehn separated task conflict, about what to do and how, from relationship conflict, about personalities. In her studies, relationship conflict hurt groups, while moderate task conflict could help on complex, non-routine work.

   Use it: Keep disagreements about the plan, and step in early when they start to sound personal.

7. 7. People put in less effort when it can't be seen

   Max Ringelmann, rope-pulling studies published in 1913; named social loafing by Latané, Williams and Harkins in 1979

   Ringelmann, a French agricultural engineer, found that people pulling a rope together each pulled less hard than they did alone. Later researchers showed the drop came largely from lower effort, not just poor coordination, and called it social loafing.

   Use it: Give each task one named owner, keep groups small and make each person's contribution visible.

8. 8. Close groups can stop thinking critically

   Irving Janis, 1972; the word was coined by William H. Whyte in 1952

   Whyte used the word in a 1952 Fortune article. In Victims of Groupthink, Janis developed it into a theory, describing how tight groups under pressure suppress doubts to keep the peace, and make poor decisions as a result.

   Use it: Have the leader speak last, assign someone to argue the other side and bring in outside views on big calls.

12 examples of group dynamics at work

Six healthy and six unhealthy group dynamics examples, each with the pattern it shows. Most teams will recognize a few of each.

How to read your team's dynamics: an observation checklist

Pick two or three meetings and watch instead of steering. Note what you see, not what you assume, and look for patterns that repeat.

How to improve group dynamics: 10 ways

Most poor dynamics come from how a group is set up, not from bad people. These change the setup.

1. Set norms on purpose. Write down how the group meets, decides and disagrees, and revisit it when people join.
2. Let the leader speak last. On big decisions, hear everyone before the most senior person gives a view.
3. Decide how you decide. Say up front whether the leader decides, the group votes or you need consensus.
4. Give every task one owner. Shared ownership quietly becomes no ownership.
5. Keep working groups small. When everyone's contribution is visible, effort stays up and coordination stays simple.
6. Balance airtime. Open with a quick round, or collect written input before discussion so quieter people are heard.
7. Make disagreement a job. Assign someone to argue the other side, and thank people who raise doubts.
8. Keep conflict about the work. Talk about the plan and its effects, never about what kind of person someone is.
9. Watch the edges. Pull remote, new and quieter members into the conversation on purpose.
10. Review how you work, not only what. Spend ten minutes a month on the group's process: what helped, what got in the way.

When the dynamics have already turned into open friction, our conflict resolution activities give the team a structured way back.

8 exercises that reveal group dynamics

Each one makes a hidden pattern visible, then the debrief turns it into a conversation. Run them on low-stakes tasks, and never use them to single anyone out.

1. 1. Who talks to whom

   Builds: Mapping the real lines of conversation in a meeting.

   30-minute meeting plus 10 minutes to debrief · 4 to 12 people and one observer · A sheet with everyone's name around a circle

   1. With the team's agreement, one person sits out a real meeting as the observer.
   2. Each time someone responds to someone else, the observer draws an arrow between their names.
   3. At the end, the observer shows the map without comment: thick lines, empty corners, people nobody responded to.
   4. The team picks one change for the next meeting and runs the map again to compare.

   Debrief

   • Whose name do most of the arrows run through?
   • Who did we rarely respond to, and why might that be?

2. 2. First speaker test

   Builds: Seeing how much the first voice shapes a group's answer.

   25 minutes · Groups of 4 to 8 · A list of eight realistic work priorities

   1. Everyone ranks the same eight priorities alone, in five minutes, and keeps their list.
   2. The group then builds one shared ranking in 15 minutes while a volunteer notes who speaks first on each item.
   3. Compare: on how many items did the group's choice match the first speaker's view?
   4. Repeat with a new list, this time collecting everyone's written view before anyone speaks.

   Debrief

   • Did the first speaker win because of the argument or because they went first?
   • How did the second round change when views were written down first?

3. 3. Role spotting

   Builds: Noticing the roles people slip into without being asked.

   30 minutes · Groups of 5 to 8 · A list of informal roles on a slide or card

   1. Give each group a 20-minute task, like planning next month's onboarding day on one page.
   2. Show a list of informal roles first: idea generator, organizer, checker, encourager, timekeeper, challenger, finisher and quiet worker.
   3. After the task, each person writes which roles they saw each teammate play, themselves included.
   4. Share the notes, starting with how each person saw themselves.

   Debrief

   • Which role did you play that you didn't plan to?
   • Which role was missing, and what did that cost the group?

4. 4. Rotating skeptic

   Builds: Making dissent a job, so nobody has to volunteer for it.

   15 minutes per decision · 4 to 12 people · No materials

   1. Before a real decision, draw a name: that person is the skeptic for this item.
   2. The skeptic gets three minutes to make the strongest honest case against the leading option.
   3. The group answers each point before it decides.
   4. Hand the role to someone new for every decision.

   Debrief

   • Did the skeptic raise anything we would otherwise have skipped?
   • Did disagreeing get easier once it was someone's job?

5. 5. Alone, then together

   Builds: Seeing what a group adds, and loses, compared with people working alone.

   25 minutes · 6 to 12 people · No materials

   1. Pose a real question, such as how the team could spend less time in meetings.
   2. Half the team writes ideas alone and in silence for eight minutes; the other half brainstorms out loud together.
   3. Count the distinct ideas from each half, then swap methods with a new question.
   4. Compare the counts and the best three ideas each method produced.

   Debrief

   • Which method gave more ideas, and which gave better ones?
   • Who said less in the out-loud group than they wrote in the silent one?

6. 6. Three ways to decide

   Builds: Feeling the trade-offs in how a group makes decisions.

   30 minutes · 5 to 10 people · No materials

   1. Prepare three small but real decisions, like the format of the weekly update or a name for a shared channel.
   2. Make the first by having the leader decide alone, the second by majority vote and the third by consensus.
   3. Time each one, and after each, everyone rates their buy-in from 1 to 5.
   4. Compare the time and the buy-in across the three methods.

   Debrief

   • Which method do you want for our next big decision, and why?
   • Which decisions do we make the slow way when a fast one would do?

7. 7. Hidden role cards

   Builds: Seeing how one person's behavior changes the whole group.

   25 minutes · Groups of 5 to 8 · One card per person

   1. Give a group a planning task and hand each person a secret card with a behavior to play: asks lots of questions, agrees with everyone, only talks about risks, or sums up often. Leave one or two cards blank.
   2. Work on the task for 12 minutes, playing the cards lightly.
   3. Everyone guesses each person's card.
   4. Discuss which behaviors helped the group and which stalled it.

   Debrief

   • Which behavior changed the group most?
   • Which of these behaviors shows up on our real team every week?

8. 8. Named owners experiment

   Builds: Testing whether clear ownership changes what gets done.

   15 minutes to set up, then two weeks · Any team · No materials

   1. Pick the shared chores the team usually leaves to whoever has time, like updating docs or sorting incoming requests.
   2. For two weeks, give each chore a single named owner and post the list where everyone can see it.
   3. Compare what got done in those two weeks with the two weeks before.
   4. Decide which chores keep a named owner.

   Debrief

   • What changed once each chore had one name next to it?
   • Where else is work shared so widely that nobody owns it?

For exercises where a group works through a shared challenge, see our problem solving activities.

Want to see your team's dynamics in action?

A hosted session puts the team in a new situation and lets you watch the patterns play out. Improv is a live class built on “Yes, And”, storytelling and responding to the unexpected, and Team Discovery Challenge is a scavenger hunt combined with show and tell that reveals new sides of teammates. Both run on Zoom by default; book about 2 weeks ahead, see all team building workshops or get a free quote.