When Mr. Chen announced the group project for our history unit on ancient civilisations, I felt a familiar flutter of excitement. I loved research and organising information, and I already imagined myself leading the research team. But then he handed out the role cards. Each group had to have a presenter, a researcher, a designer, and a coordinator. I watched as my friends eagerly grabbed the roles they wanted. By the time the card reached me, only one was left: coordinator. My heart sank. Coordinator meant I had to keep everyone on track, manage deadlines, and deal with arguments. It was the role nobody wanted, and now it was mine.

For the first few days, I tried to pretend the role didn't matter. I let the researcher take charge of the topic selection, and I let the designer decide the layout of our poster. But soon, chaos crept in. The researcher and the designer disagreed on whether to focus on Egypt or Rome. The presenter kept forgetting to bring her notes. Our group meetings became a mess of cross-talk and frustration. I sat there, biting my lip, wishing I could just do the research myself. But then I remembered what Mr. Chen had said: a coordinator's job is to listen, organise, and keep the group moving forward. I realised I had been avoiding my responsibility.

So I called a proper meeting after school. I brought a notebook and a printed calendar. I asked each person to share their strengths and what part of the project they cared about most. The researcher loved digging into primary sources; the designer had a talent for drawing timelines; the presenter was great at speaking clearly under pressure. I wrote everything down and then proposed a schedule: research by Wednesday, design by Friday, practice presentation by Monday. I also set a rule: if someone disagreed, we would vote, and the majority decision would stand. To my surprise, everyone agreed. The tension in the room eased.

I let the researcher take charge of the topic selection, and I let the designer decide the layout of our poster.

Over the next week, I sent gentle reminders each morning. I checked in with the researcher to see if she needed extra sources. I helped the designer find images that matched our topic. I even practised the presentation with the presenter after school, timing her and giving feedback on her tone. Slowly, the project started to take shape. Our poster looked professional, with clear headings and colourful illustrations. The research was thorough, covering daily life in ancient Egypt. And the presenter knew her script so well that she could look at the audience instead of her notes. I felt a quiet pride watching it all come together.

On presentation day, our group went last. As the presenter spoke, I noticed the class leaning forward, interested. When she finished, there was a round of applause. Mr. Chen smiled and said our project showed excellent teamwork and organisation. After class, the researcher came up to me and said, 'Honestly, without you keeping us on track, we would have been a disaster.' The designer nodded. I realised then that the coordinator role wasn't just about bossing people around. It was about making sure everyone's strengths were used and that the group worked as one. I had done that.

Looking back, I am grateful I got the role I did not want. It taught me that sometimes the jobs we avoid are the ones that help us grow the most. I learned to listen, to plan, and to lead without being bossy. I also learned that a group can achieve much more when each person feels heard and valued. Now, when I join a new team, I don't grab the flashiest role. I think about what the group actually needs. And sometimes, I even volunteer to be the coordinator. Because I know now that it is not a boring job. It is the glue that holds everything together.