Throughout this module, I will encourage myself to reflect more on how I collaborate. I will use a reflective module to guide my weekly reflections to help me understand my habits, strengths and areas for growth as I work with my group.
Use the buttons below or your arrow keys to navigate.
As a web developer, collaboration is central to my work, as most projects involve designers, SEO specialists and content writers. When communication is working well, collaboration can be motivating and productive. When that breaks down, I have seen duplicated work, missed deadlines and a sense that nobody is fully aligned.
This makes me assume that collaboration in the creative industries depends on clarity and shared goals. Throughout the coming weeks, I hope to improve how I navigate group dynamics and keep projects moving forward.
On my previous degree course in Music Technology, groups were formed to create a song. I ended up doing most of the work because I enjoyed taking control and wanted the final track to meet my standards. Using Gibbs’ Reflective Cycle (GIBBS, 1988) to look back, the description and feeling stages helped me notice the pride I felt with the outcome, but also the pressure it created.
In the evaluation stage, I can see that the uneven workload may have discouraged others. My conclusion is that collaboration is not measured by the quality of the outcome; it is about shared ownership. Next time, my action plan would be to create a space for others to take responsibility, even if it means letting go of some control.
Before meeting my group, I felt open-minded, but slightly unsure about how we would work together. So far, we have set up a shared whiteboard and discussed which platforms to use for communication. Some people suggested WhatsApp, but I felt uncomfortable mixing study and personal spaces, so I created a Microsoft Teams chat, so everyone has a professional place to connect.
Looking back through Gibbs, the description and evaluation stages show that this was a positive and practical contribution. For our next meeting, I hope to contribute earlier to discussions so we can agree on a structure that feels comfortable for everyone.
Listening plays a central role in how I collaborate. I usually observe and absorb before responding, which helps me to process ideas carefully. I wouldn’t say I feel attacked when others question my contributions; however, this often leads me to overthink what I say and makes me hesitate to contribute again.
This week, I discovered Donald A. Schön’s ideas about reflection in action and reflection on action (Schön, 1983). I recognise that in my website projects, I already use reflection in action by adjusting designs while I build them. Using Gibbs alongside reflection on action is helping me look back at conversations with more purpose, so I can notice when I hold back and help to be more supportive in future collaborations.
This week made me think more carefully about how I take part in collaborative discussions. I tend to begin quietly and watch how others interact before I join in. Once the group rhythm forms, conversations feel more natural. Our recent discussions have started to feel more comfortable on calls, in the chat and on the whiteboard.
Reflecting, I notice my strength lies in listening, noticing from the meetings how tone and openness shape trust in the group. My conclusion is that I would like to share thoughts earlier, even if they are not fully formed, so that I can contribute more actively to shaping the direction.
This week, the group discussed how we could keep generating ideas for our manifesto while staying organised. We recognised that the weeks were moving quickly, so we agreed that one member would help keep everyone aware of timings. I supported this decision and found it reassuring to have someone focusing on deadlines so others could focus on creative thinking.
Through Gibbs’ evaluation stage, I can see that this small bit of structure helped the group feel more aligned. Also, some members have not contributed yet, we acknowledged that personal circumstances might be involved and agreed to keep the tutor updated to nobody was left behind.
My biggest ta-da moment so far has been realising that awareness has become something I practise instead of just a theme that I study. I have started to notice more how people communicate and how different personalities lend themselves to the group dynamic. Thinking about feelings and analysis, I can see that I have become more open to feedback both professionally and personally.
Previously, I was quick to defend my ideas, but lately I have been slower to react and more willing to listen. Seeing how differently people interpret the same task shows me that feedback isn’t necessarily a criticism, but just another way of seeing things.
Collaborative production has begun to feel more comfortable as the project develops. Earlier on, I was unsure how my contributions would fit, but now, I realise that small, consistent inputs are just as valuable as big standout ideas. Working with other people has reminded me that clarity and reliability are soft skills that keep things moving.
From Gibbs’ perspective, my evaluation is that group work doesn’t always feel balanced. Not everyone contributes in the same way/pace, and collaboration involves adjusting to different working styles rather than expecting everything to be balanced.
From collaborating, I have learnt that how we work together can either make things smooth or quite confusing. Seeing how ideas move between Microsoft Teams, the whiteboard and documents has made me notice how easily messages get lost when there isn’t a clear plan. In this project, I have realised that I was often observing rather than initiating tasks once tasks were organised.
Using Gibbs to reflect, I can see that this observation has been useful for understanding group dynamics, but I feel that it has limited how visible my contribution was. I’ve concluded that I could’ve been more proactive, and next time I want to get more involved earlier by adding suggestions and ideas into our shared space.
Looking back at the first brief, I can see how my confidence as a collaborator has grown. Using Gibbs’ Reflective Cycle across these weeks has helped me step back from our group work and understand why some approaches worked better than others. It has supported me in reviewing my collaborative working for Learning Outcome 1 and how effective my contributions were to the team brief for Learning Outcome 2.
I have become more aware of how even small actions, like proposing a platform or supporting a timing plan, can shape the final manifesto. I appreciate now that it isn’t about being in control or producing the biggest contribution like I did for my Music Technology course. It is about creating a space for others and seeing value in the progress we make together. This is an action plan that I want to stick to as I move forward personally and professionally.
Looking back across the module, I can see how much my awareness has developed. I am more conscious of group dynamics, when to contribute and when to step back.
If I were advising someone new to cross-disciplinary work, I would say to be open, patient and aware of how others work, whether that is in small consistent contributions or big grand ideas. My key takeaway from our group work is that awareness is the foundation of effective collaboration and I plan to keep using Gibbs and reflection on action to improve how I work with others in the future.
I hope you enjoyed following my reflective journey.