On this page
You can't choose your group, but you can choose what kind of teammate you are.
What makes someone a good team member in a group project?
When Google studied 180 of its own teams in Project Aristotle, it found that how people worked together mattered more than who was on the team (Google re:Work). Psychological safety came first: team members feel they can take a risk, such as admitting a mistake, without it being held against them. Dependability came second: on dependable teams, members reliably complete quality work on time. One of Google's survey statements for it is plain: when my teammates say they'll do something, they follow through with it.
Those were office teams, not classrooms, but a 2010 study in Science points the same way for small groups. Across 699 people working in groups of two to five, a group's collective intelligence, its ability to do well on a wide range of tasks, was not strongly linked to the average or highest intelligence of its members; it was higher when members were more socially sensitive and shared conversational turns more equally (Woolley and colleagues, Science). The topper does not make the team; the way you work together does. That comes down to three habits: keep commitments, make progress visible, and disagree about the work, never the person.
How do you keep your commitments in a group?
Social loafing is the tendency for people to put in less effort when working collectively than when working alone, and a review of 78 studies found it across many tasks and groups of people (Karau and Williams, 1993). The fix is to make each person's part specific and visible, starting with your own.
Commitments break when they are vague. "I'll do the research" has no finish line. A meta-analysis of 94 tests found that if-then plans, which spell out when, where and how you will act, had a medium-to-large effect on reaching goals (Gollwitzer and Sheeran, 2006). Turn every task you take into one line:
What: draw the circuit diagram and write the method section
By when: Thursday, 8 pm
Where it lives: the shared document, section 2
If-then: if I'm stuck by Tuesday night, then I message the group before school on Wednesday
Promise only what fits around your own tests and tuition.
How should you update your team on progress?
Silence makes teammates anxious. Post a short update twice a week in three lines: Done, Next, Stuck.
For example, four Class 11 students have two weeks to write up a simple pendulum experiment. On day five, Aanya posts in the group chat:
Done: timed 10 swings for four string lengths; readings are in the sheet
Next: repeat the 60 cm and 80 cm readings by Saturday
Stuck: my timings for 80 cm don't match each other; can someone check my method on Friday?
Said on day five, a Stuck line is easy to fix; found on day thirteen, it is a crisis. If your team keeps its work in one file, our guide to online group projects and shared documents covers who edits what.
If your Stuck line is about a concept you only half understand, the Fermi Concept Library has a lesson for every concept in physics, chemistry, biology, mathematics and computing, so you can come back to the group with an explanation instead of a guess.
How do you handle disagreements in a student team?
A meta-analysis of team conflict research found that, on average, both relationship conflict and task conflict were negatively related to team performance and member satisfaction, and conflict hurt more on complex work such as projects and decision making (De Dreu and Weingart, 2003). The same study found that disagreeing about the task did less harm when it was only weakly linked to personal conflict.
So keep disagreements about the work, and short. A script:
Name the shared goal: "We all want the model to work on demo day."
Make your view a proposal with a reason: "I think we should use cardboard, because it holds glue better."
Ask for theirs: "What makes you prefer thermocol?"
Agree how to decide: a quick test, the teacher's rubric, or a vote by a set time.
Once it's decided, back the choice fully, even if you lost.
Avoid "you always" and "you never". If someone has stopped contributing altogether, see what to do when group project teammates aren't working. For practicals, our piece on working with a lab partner covers sharing an experiment fairly.
A one-week team plan you can copy
Day 1: list every task, give each an owner and a deadline, and write them in the shared document.
Day 3: everyone posts a Done, Next, Stuck update.
Day 5: second update; reassign anything still stuck.
Day 6: put the parts together and read the whole thing as a group.
Day 7: keep it free for printing, fixes and surprises.
Pick one habit from this page and use it from day one of your next project.
