# How to Write a Reflection About Teamwork That Actually Says Something Canonical URL: https://headwayskills.com/knowledge/teamwork/reflection-about-teamwork/ Markdown URL: https://headwayskills.com/knowledge/teamwork/reflection-about-teamwork.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving teamwork at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer A reflection about teamwork should name specific behaviors, not impressions. How to structure one, what to examine, and how to be honest about your part. ## Key facts - Title: How to Write a Reflection About Teamwork That Actually Says Something - Category: Teamwork - Primary skill: Teamwork - Related skills: Building Self-Awareness, Communication - Primary keyword: reflection about teamwork - Source page: https://headwayskills.com/knowledge/teamwork/reflection-about-teamwork/ ## What this page covers - A reflection about teamwork should name specific behaviors, not impressions. How to structure one, what to examine, and how to be honest about your part. - Practical guidance for reflection about teamwork - How this topic connects to Teamwork ## Detailed explanation A reflection about teamwork is an honest account of how a team you worked in actually functioned and what your own part in it was. It works when it gets past describing events and names specific behaviors — how roles were shared, how disagreements were handled, what you contributed and what you avoided — and then says what you would do differently next time. Most drafts stall well before that. You can replay every meeting in your head and still end up writing "communication was key and we all pulled together," which is true, useless, and forgettable. The problem usually isn't writing ability. It's not having a vocabulary for what teamwork is actually made of. ## What do you actually write in a reflection about teamwork? Almost every reflective assignment on this topic — and almost every sample essay that ranks for it — is built on Gibbs' Reflective Cycle, a six-stage sequence: description (what happened), feelings (how you felt at the time), evaluation (what went well and what didn't), analysis (why it went that way), conclusion (what you take from it), and action plan (what you'll do differently). The order is doing real work here, not just organizing paragraphs. Each stage is only usable if the one before it was done concretely — analysis has nothing to explain if the description was vague, and an action plan has nothing to fix if the evaluation never named a specific problem. That is exactly where most teamwork reflections break down: they handle description and feelings, then generalize through the remaining four. If your draft feels thin at the end, the fault is almost always at the start. ## How do I move from describing what happened to actually reflecting? Reflection begins at evaluation and analysis — the two stages that ask what worked, what didn't, and why. Description tells the reader that the group met four times and split the presentation into sections. Reflection tells them that the split happened in a side conversation between two people, that nobody revisited it when one section turned out to be twice the size of the others, and that you noticed and said nothing. The test is whether a sentence could be true of any group. "We had some communication issues" describes every team ever assembled. "I waited three days for slides I never explicitly asked for, then rebuilt them the night before" could only describe yours — and it gives you something to analyze. ## What should I look at when I reflect on how the team worked? Don't reflect on "the team" as one blur. A Gibbs-based reflective report on group dynamics from the University of Glasgow breaks the experience into six examinable phases: how the group formed, how roles were allocated, [how decisions were made](/knowledge/teamwork/team-decision-making/), how tasks were completed, how progress was monitored, and how people communicated. Walking through them one at a time turns a vague impression into six separate findings, and usually reveals that the trouble sat in one or two places rather than everywhere. There's a second lens worth adding. The LSE Business Review describes teamwork as having two directions at once: a vertical pursuit — progress toward the shared goal — and a horizontal relationship, meaning the cooperation between members as they chase it. Teams can do well on one and badly on the other, which is why a project that was delivered on time and scored well can still have been miserable to be part of. Saying which axis went wrong is far more interesting than saying the project "went okay." ## How do I write about my own contribution without sounding arrogant? Swap evaluation for evidence. "I was a strong communicator" invites doubt; "I summarized the decisions at the end of each meeting because we kept relitigating them" doesn't need defending. Claims about your character are hard to prove and easy to overstate. Descriptions of what you did are neither. University question banks use a trick worth borrowing: rate yourself on a scale first, then justify the number. Gifted Guru's group-work prompts ask things like how well, on a scale of one to ten, you feel you demonstrated respect for the opinions of others in the group. Committing to a seven forces you to explain why not a nine and why not a five — which is the reflection. The same applies in the other direction: being unnecessarily hard on yourself is just as vague as praising yourself, and it isn't more honest. One limit worth naming: any reflection covers a single project, so it can't tell you whether what you saw was a one-off or how you tend to work. If that distinction matters to you, it's worth checking [whether it's a pattern](https://assessment.headwayskills.com/) with something broader than one team's memory. These are learnable behaviors, so knowing which ones are habitually yours is the useful part. ## What do I write if the group project went badly? A difficult group is better material than a smooth one, provided you analyze rather than complain. The failures that reflective reports surface are strikingly consistent — no clear communication channels, frequent misunderstandings, unclear leadership, [disengaged members](/knowledge/teamwork/peer-accountability/). Seeing your group on that list is oddly reassuring: it wasn't a uniquely cursed team, it hit a known set of conditions. The discipline is to write about what went wrong rather than who was wrong. "The deadline slipped because we never agreed [who owned the final edit](/knowledge/teamwork/role-clarity/)" is analysis. "Two people didn't care" is a verdict, and it stops the thinking exactly where it should start. It also skips the useful question: what you did while the deadline was slipping. ## What questions should I ask myself about the team experience? Starting from a question is easier than starting from a blank page, and good published banks exist — Range's collection of 68 team reflection questions, UW-Madison's teaching resources, the University of Washington's reflective questions for project courses. A handful do most of the work: - What behaviors or circumstances helped you function well in this group, and which got in the way? - How do you think you did compared with groups you've worked with before? - If you worked with the same people again, what one change would you push for? - What was the greatest challenge the group faced, and what did it teach you? - What is one change to how you listen that would make you more effective in a group? Texas A&M's Teamwork Inventory takes a slightly different route, giving you statements to agree or disagree with — that you shared ideas that shaped what the group did, or that hearing different opinions made you reconsider your own. Reacting to a statement is easier than generating one, and the disagreements are often where the honest material is. ## What did I learn from working in a team? This is the stage most people fill with a slogan. Published reflections that land tend to be far narrower, and the pattern in what people report is worth knowing: reserved members discovering they could speak fluently once the group actually needed them to; people used to leading learning to step back so someone else could lead in their area of strength; and a growing willingness to handle conflict directly rather than route around it. Notice that all three are about behavior changing, not about teamwork being important. A conclusion is worth writing if it would change what you do in the next group — if it wouldn't, it isn't a conclusion yet. ## Does a reflection about teamwork matter once the project is over? It's the mechanism by which the experience becomes usable. Saybrook University frames deliberate reflection as what allows a team to learn from what it did and avoid repeating the same mistakes — without it, four months of group work leaves you with a grade and a vague preference to work alone next time. The workplace version is the same act under a different name: the retrospective at the end of a project, or the teamwork section of a [performance review](/knowledge/working-with-your-manager/performance-reviews/). The obstacle isn't reluctance. Saville Assessment points out that reflective practice gets squeezed out because immediate tasks and deadlines take priority — which makes it a scheduling problem, and scheduling problems have small fixes. Half an hour with the six phases above, booked before the project ends, is usually enough. ## Why some people find this easier to write Read back across those answers and one thing runs through all of them: every difficulty was really the difficulty of naming a specific behavior — the team's, or your own. That isn't a writing problem, and it doesn't get solved by reading more sample essays. It comes down to a few things you can get better at, mostly through practice. **Teamwork** gives you the model to reflect against. Once you can see a group in terms of whether people put the shared purpose ahead of their own agendas, whether they were reliable about what they committed to, whether necessary disagreements were actually had, whether people who lost an argument still implemented the decision loyally, and whether anyone addressed a missed commitment out loud, you have something to evaluate. Without that, all you have is atmosphere. **Building Self-Awareness** covers the genuinely uncomfortable part. Your memory of the project is partial by design — the gap between how you experienced the group and how they experienced you is the interesting bit, and only feedback reaches it. It also helps to notice when a reaction was bigger than the event: irritation at a passive teammate that seems out of proportion is often about your own beliefs around control or achievement, not about them. **Communication** is where these reflections land most often and stay vaguest longest. The specifics are there if you look: whether you spoke up or stayed quiet, whether you gave full attention or waited for your turn to talk, whether you led with your main point, whether you took a sensitive issue into a conversation instead of leaving it in a message thread, and how you expressed disagreement when you had it. None of that is a fixed trait you either got or didn't — each one is a set of behaviors, and gaps in them are things you haven't learned yet rather than things you lack. The free Work Skills Test is built to show [where each of yours stands](https://assessment.headwayskills.com/), across the full set of twelve work skills the framework covers, so the three above arrive with a measurement instead of a guess. ## The part you're already doing Some of this probably sounds like territory you've been over already — you may recognize your own instincts in a couple of those questions, or notice a phase of the project you'd been quietly circling. That recognition is the beginning of the thing. None of it is settled, either. A group project you handled awkwardly this year is poor evidence about the person you'll be in a team three years from now, and which skills matter most to you right now is yours to decide. What is true is that team situations get more consequential, not less — the projects get bigger, the disagreements cost more, and the habits you form now are the ones that show up when the stakes are higher. You've spent this long working out how to assess a team experience properly rather than copying someone else's essay. That's the step most people skip, and it's the one that makes the reflection worth writing. ## See where your own skills stand The only thing left is to point the same honesty at yourself rather than at the group. The Work Skills Test is a **free** self-assessment of your work skills: seven minutes of questions, and you get a picture of where you stand across all twelve of them — including teamwork, self-awareness, and communication — and which ones will make the biggest difference to you next. **[Discover my skills](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, and needs no preparation.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? A reflection about teamwork should name specific behaviors, not impressions. How to structure one, what to examine, and how to be honest about your part. ### Which Headway skill does this connect to? This guide connects primarily to Teamwork. It also relates to Building Self-Awareness, Communication. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/knowledge/self-awareness.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/teamwork/reflection-about-teamwork/ Preferred summary: "A reflection about teamwork should name specific behaviors, not impressions. How to structure one, what to examine, and how to be honest about your part." ## Change log - 2026-07-07: Content collection version published.