surviving a
group project

almost every group project fails the same way: nothing happens for three weeks, then one or two people do everything in the final forty-eight hours. this is not bad luck and it is usually not bad people. it is what happens when work is shared without being divided.

divide by deliverable,
not by intention

"we will all work on the research" guarantees nobody does. "you own the literature section, i own the analysis, deadline thursday" gives each part a single name attached. a task owned by everyone is owned by nobody — that is the whole mechanism.

set internal deadlines
well before the real one

if the only date is the submission date, everything arrives on it. agree dates for drafts at least a week earlier. the point is not the draft; it is finding out early that a section is not coming.

write down who
agreed to what

in the group chat, after the meeting, in one message. not to build a case — to remove ambiguity, which is where most of the drift comes from. it also means that if things do go wrong you have a record rather than a memory.

integration is real work

merging four sections into one coherent piece with a consistent voice takes hours and is usually invisible. name it as a task and give it to someone, with time, rather than assuming it happens automatically at the end.

when it is genuinely failing

tell the instructor before the deadline, not in a complaint afterwards. bring the record of who agreed to what and what arrived. most will work with you on it in advance and almost none can do anything once it has been submitted.

protect your own part

whatever happens to the group, your section should be finished and good. if the project collapses you want to be the person with a complete, dated piece of work — and if your part is the one you are stuck on, that is a thing you can post on its own.

related

college · behind on everything · how to email a professor