Everyone has survived a group assignment where one person vanished, one dominated, and the work happened at 2 a.m. on the deadline. None of that is bad luck — it is the predictable result of a group that never became a team. The difference is three practices, all learnable.
What you will learn
How to set up a group in the first meeting so it functions, how to handle the two classic problem members, and the meeting habits that keep work moving.
The guide
Practice 1 — contract before content. Spend the first twenty minutes of any group project agreeing, in writing: who does what, by when, how you communicate (one channel, not three), and what happens if someone misses a deadline. It feels overly formal. It is also the single strongest predictor of group survival, because it converts future conflicts into pre-agreed procedure.
Practice 2 — handle the two classic problems early.
- The ghost (disappears): escalate in steps — private message → group message naming the missing task, not the person's character → lecturer, with your written contract and message trail as evidence. Escalating at the last week protects no one; the trail is what makes early escalation fair.
- The dominator (does everything their way): assign ownership, not tasks. "You own the analysis section" gives someone a domain to control — which is usually what the dominator actually wants — while fencing off everyone else's.
Practice 3 — meetings that produce decisions. Every meeting ends with a three-line summary posted to the group channel: decided / doing (who + by when) / blocked. If a meeting cannot fill in the first two lines, it was a conversation, not a meeting — and the summary habit exposes that immediately.
Practice task: in your next group project, volunteer to write the contract and the meeting summaries. It takes ten minutes a week and quietly makes you the person the group cannot function without.
Reflection prompt: in your worst group experience, which of the three practices would have changed the outcome?
Why this matters for your studies
Group assignments are marked on the output, but the output is determined by the process. Students who run the process well consistently carry weaker groups to better grades — and collect the best interview stories doing it.
What next
Revisit Communication Essentials' loop-closing habit — it powers the meeting summary. Then log one evidence story from your current group.