The Reflective Paper

The reflective paper is the individually-written second piece of Component 3, worth 10 marks and up to 800 words. It addresses AO2 (Reflection) — reflecting on the effectiveness of the team's collaboration and on your own learning and contribution. Component 3 is the only component in 9239 where collaboration/teamwork is assessed, and this paper is where those marks are earned.

Performative: "Our team worked really well together and everyone contributed." — generic; it could describe any team and shows no real reflection.

Genuine: "When we disagreed about the problem statement, I suggested narrowing it, which broke the deadlock and taught me to resolve disagreement early." — specific moment, what happened, and what it taught.

The difference: genuine reflection is specific and substantiated (a real moment + what it taught you); performative reflection is vague, generic praise. AO2 rewards the former and rejects the latter.

"Our team's collaboration was effective once we organised it, but it took a difficult start to get there. In the first two weeks we had no agreed roles, and two of us unknowingly researched overlapping angles, which wasted time. The turning point came when we agreed clear responsibilities and a shared timeline: after that, each member owned a distinct perspective and we met deadlines reliably. Disagreements still arose — for example, over how ambitious our proposed solutions should be — but we resolved them by returning to our shared problem statement and asking what actually served it. On reflection, what made the difference was structure: our early problems came from leaving roles informal, and agreeing them explicitly transformed how we worked. This taught me that in a team, clarity about who does what prevents most conflict before it starts."

This is specific (overlap, the turning point, a real disagreement), honest (it admits the difficult start), and reflective (it identifies why things improved and what it taught the writer).

"At the start of the project I was confident in my research but reluctant to rely on others — I preferred to control the work myself. My main contribution was researching the economic perspective and proposing a deposit-return scheme, which I developed thoroughly. However, the project changed how I work. When a teammate's environmental research exposed a trade-off in my solution that I had missed, I realised that relying on others actually strengthened my proposal rather than weakening it. I responded by actively seeking my teammates' input on my later work, and our final solutions were more rounded as a result. On reflection, my key learning was about myself: I had mistaken independence for quality, when in fact the collaboration improved my thinking. I would carry this into future group work by involving others earlier rather than presenting finished work for approval."

This shows a clear before (reluctant to rely on others), a specific trigger (the teammate's research exposing a trade-off), and an honest after (a changed approach), with genuine self-insight.

A high-scoring reflective paper (structure + what makes it reflective):

1. Brief framing (≈60 words). One or two sentences naming the project and my perspective — just enough context. (Kept short so the words go to reflection, not narration.)

2. The team's collaboration (≈250 words). Reflect on how effectively we worked together:

• our difficult start (no agreed roles → overlapping research) and the turning point (agreeing clear responsibilities and a timeline);
• how we resolved a specific disagreement (about solution ambition) by returning to our shared problem statement;
• the lesson: structure prevented conflict — informal roles caused our early problems, explicit roles fixed them. (Reflective because it identifies causes and lessons, with specific moments — not generic praise.)

3. My own learning and contribution (≈250 words). Reflect honestly on my role and growth:

• my contribution (researching the economic perspective; proposing and evaluating a deposit-return scheme);
• a before → after change: I began reluctant to rely on others, but a teammate's research exposing a trade-off in my solution taught me that collaboration strengthened my work;
• a candid weakness: I tended to dominate discussions, and learning to draw quieter members out improved our decisions. (Reflective because it shows genuine self-insight and change, not self-praise.)

4. What worked, what didn't, what to improve (≈200 words). Evaluate:

• worked: distinct perspectives (once fixed) gave a rounded set of solutions; returning to the problem statement resolved disputes;
• didn't: the unstructured start wasted two weeks; we underused each other's research early on;
• to improve: agree roles, deadlines and a check that perspectives are distinct in the first meeting; involve others earlier in individual work. (Reflective because each improvement is specific, causal and something I would genuinely carry forward.)

5. Short close (≈40 words). The single most important thing I learned about collaboration and about myself.

What makes it high-scoring: it is specific (real moments throughout), honest (admits the difficult start and my own weakness), reflective not narrative (focused on causes, lessons and change), balanced across collaboration and personal learning, and within 800 words by keeping narration minimal. It draws on a collaboration log kept during the project, which is what makes it specific rather than vague.

Four weaknesses, all limiting AO2:

1. Narrating the project step by step.

• Why it fails: narration is not reflection — the paper marks reflection and evaluation, not a retelling of events.
• Fix: cut the narration to the minimum context needed, and use the words to reflect on collaboration and personal learning.

2. 'Everyone worked well and contributed equally' (performative).

• Why it fails: generic praise that could describe any team; examiners explicitly reject it.
• Fix: reflect on specific moments — a disagreement, a turning point, an uneven patch — and what they revealed and taught.

3. Self-praise ('the hardest worker').

• Why it fails: self-praise is not reflection; it shows no self-insight or learning.
• Fix: reflect honestly on the writer's contribution and limits/growth — e.g. a weakness noticed and changed (before → after).

4. 'We could improve communication' (vague).

• Why it fails: no cause and no concrete change — it could be said of any project.
• Fix: give a specific, causal, actionable improvement ('unclear roles caused duplicated work, so next time I would agree roles and deadlines up front').

Overall: the paper currently narrates, praises and generalises instead of reflecting. Fixing all four — minimal narration, specific honest reflection on collaboration and self, and concrete evaluation of what worked/didn't/could improve — turns it into the substantiated AO2 reflection the reflective paper rewards.