The Group Project That Stalled
Four students are collaborating on a cross-disciplinary report due in 10 days. Roles were assigned in week 1: Priya (research), Sam (data analysis), Jo (writing), and Alex (design and presentation). By day 7, Priya has done most of the research but Sam has not started analysis because the dataset only arrived on day 5. Jo is waiting for Sam's results before writing. Alex has produced slides but they are already out of date. In a 20-minute meeting, Priya says she feels she is 'carrying the group'. Sam says he was blocked and nobody asked. Jo says she cannot start without numbers. Alex says redesigning slides twice is wasted effort. The group must submit a coherent report, and 30% of the mark is for demonstrated collaboration.
1. Diagnose why the collaboration stalled, distinguishing individual failings from structural causes.
Read the worked answer
The stall is mostly structural, with some individual contributions.
Structural causes:
- The plan was sequential (research → analysis → writing → design) but treated as if stages could run in parallel. A sequential dependency means any delay cascades: Sam's day-5 dataset delay automatically blocked Jo, and made Alex's slides premature. That is a planning failure, not a personal one.
- Roles were assigned by task, not by dependency. Nobody owned the interfaces - the handover points where one person's output becomes another's input.
- No check-in rhythm. Seven days passed without a status exchange, so the block was invisible until the meeting.
Individual contributions:
- Sam should have flagged the missing dataset on day 1 rather than waiting.
- Priya's sense of 'carrying the group' is real effort but misdirected: doing more research does not unblock Jo.
- Alex redesigned slides twice because the brief was unstable; that is a symptom, not a cause.
The distinction matters because blaming individuals ('Sam was lazy') would not fix the dependency structure, and the next project would stall the same way.
2. Propose a recovery plan for the remaining 10 days that also protects the 30% collaboration mark.
Read the worked answer
The plan should convert the sequence into overlapping work with explicit handover points.
Days 8–9: Sam delivers a preliminary analysis (even partial) by end of day 9. Jo starts writing the methods and background immediately - she does not need results for those sections. Alex freezes the slide template and stops redesigning until content is final.
Day 10: 15-minute stand-up. Each person states what they need from whom and by when. This creates the check-in rhythm that was missing.
Days 11–13: Jo drafts results with Sam on call; Priya shifts from gathering more research to checking claims against sources - a genuine unblocking role.
Day 14: Alex builds final slides from frozen content; one revision only.
Days 15–17: Buffer and review; submit day 17.
Protecting the collaboration mark: the assessment rewards demonstrated collaboration, not just a finished report. The group should keep a short shared log of decisions and handovers, and each member should be able to describe their own contribution and one thing they changed after feedback. Naming the structural fix (overlapping stages, stand-ups) in the log shows reflective collaboration. Priya's concern should be addressed directly: redistribute so she is not the sole researcher, and acknowledge her effort publicly so the fix is not read as criticism.