THE PREFLIGHT · GROUP WORK

When your group project goes quiet.

2026-06-08 · by Tomás L., MBA · Business & analytics

The message arrives on a Tuesday. Two people have not posted, the deliverable is due Sunday, and you are deciding whether to write all of it yourself. Before that decision, it is worth knowing which kind of quiet you are actually dealing with.

Silence has three causes and they want different answers

The instinct is to read silence as indifference, and it usually is not. Across the enquiries I read, the three causes turn up at roughly similar rates, and only one of them is the one people assume.

Make the next ask small enough to answer

Someone who is stuck cannot reply to are you going to do your section, because the honest answer is humiliating. They can reply to can you send me three sources on the intervention by Thursday, because it is finite and it requires them to admit nothing.

So shrink the request until it is answerable and attach a day to it. One small delivered piece restarts a person far more reliably than any group message about commitment, and either way it gives you something solid: a contribution, or a clear signal to build the deliverable without them.

Build it so it survives losing somebody

This part is genuinely within your control and costs almost nothing when done early. Put a skeleton of the whole deliverable into the shared file in the opening days: headings, whose name sits against each one, and roughly what belongs underneath. Not as a power move. As a map.

A modular structure turns a missing person into a hole rather than a collapse, and a hole can be filled on Saturday. An integrated one, where three people were supposed to write a single argument jointly, cannot be rescued at short notice by one. Most group emergencies I hear described are structural problems wearing a personnel problem's clothes.

What actually happens to the grade

Instructors differ, and the honest position is that one email late in the week rarely alters an outcome. What alters outcomes is a visible record: the shared document's revision history, the course group space showing who posted what and when, and a note from you sent early rather than sent desperate.

Peer evaluation, where a course uses it, matters more than students expect, and it works best written specifically and without heat. Say what was agreed, what arrived, and on what date. Leave motive out entirely, because the moment a report characterises somebody it starts reading as a falling-out rather than as evidence.

The date you stop chasing

Choose it now, write it down, and set it early enough to be useful: typically the last point at which the remaining work still fits inside the hours you personally have. Past that date you are not negotiating any longer, you are building.

That is not abandonment, and it should be said once in the group space without heat: here is what I am writing, here is what remains open, tell me today if you are taking any of it. Then write. People who set that line submit complete work and feel fine afterwards. People who chase until the last night submit something thinner and feel worse. Where it is a whole term's recurring layer drowning you rather than one project, that part can simply be handed over.

Questions people actually ask.

Nobody has posted in a week. Do I email the instructor?

Yes, and early beats desperate. Keep it factual: what was agreed, what has reached the shared file, what you have finished, and one specific question about how they would prefer you to proceed. A calm note sent early establishes a record. A frantic one the night before mostly documents your panic.

How do I ask without sounding like an accusation?

Request a small deliverable rather than an explanation. Three sources by Thursday is answerable. Are you doing your part is not, and it pushes somebody who is stuck further into hiding. Keep the request in the course group space rather than in private messages, so it stays visible without ever becoming pointed.

Should I just write the whole thing myself?

Sometimes, and it is a legitimate decision rather than a defeat. Fix in advance the date you switch from coordinating to building, choose it early enough that what remains fits your real week, and announce it once. What damages people is chasing until the final night and then writing the whole thing badly.

Does peer evaluation change anything?

More often than students assume, particularly on courses that allocate part of the mark individually. It works when it is specific and unemotional: what was agreed, what arrived, on what date. It stops working the instant it describes somebody's character, because then it reads as a dispute rather than a record.

What if I am the one who went quiet?

Send something small today rather than an explanation tomorrow. A partial draft with an honest note about what is missing reopens the door. A long apology with nothing attached does not. Groups forgive a bad fortnight readily enough. What they do not forgive is silence continuing after somebody has asked.

Tomás L.
written by
Tomás L.
MBA · Business & analytics · one of fourteen on the crew.
while you are here
Weekly discussion postsMBA coursework helpMBA cases want a decisionMore from The Preflight
Tell us what's heavy.Get a free quote