0% found this document useful (0 votes)
31 views2 pages

Reflective Report

Uploaded by

iam.ishanij
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
31 views2 pages

Reflective Report

Uploaded by

iam.ishanij
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Reflective Report on My Group Work

Experience
Our recent project was a team effort where each member had a specific role to play. The work
was divided so that no one was overloaded and the final outcome could reflect everyone’s
contribution. I was responsible for collecting information along with Aadya, while the rest of the
group took care of designing and typing the PowerPoint. This division made the process
organized and efficient. It also helped us bring together different strengths—research skills on
one side and creativity and technical skills on the other—so that the presentation could be both
informative and engaging.

My personal role in the project was focused on research. I had to search through sources,
identify relevant points, and organize the information so that it could be easily used for the
presentation. Instead of simply collecting everything I found, I made sure to filter the content and
highlight the points that directly supported the topic. I worked carefully to avoid unnecessary
details, because too much information would have made the slides confusing. This process
required me to think critically and make decisions about what was important. I also collaborated
closely with Aadya to cross-check our findings and ensure accuracy. Once we were satisfied,
we handed the material to the rest of the team so they could shape it into slides. This approach
kept the workflow smooth and allowed the design team to focus on their part.

Like any group project, we faced some challenges. The first issue was scheduling—everyone
had different routines, and it was not always easy to find a common time to work. This
sometimes caused delays in progress. Another challenge was the difference in working styles.
Research naturally took more time because we had to verify facts, while the design team
preferred quick inputs so they could finish the slides faster. At times, this mismatch led to
frustration. There was also a feeling of imbalance in workload, since research required more
effort than we initially expected. To solve these problems, we agreed on smaller internal
deadlines instead of one big final date. This allowed everyone to stay on track without waiting
too long. To handle the working style issue, we decided to share the main points with the design
team early, so they could start formatting, and then we added details later. Finally, when the
workload felt uneven, I openly communicated about it, and the rest of the team supported by
proofreading and helping with small edits. These adjustments made the process more
manageable.

This project taught me several lessons. I learned that teamwork depends heavily on
coordination—each part, whether research or design, is linked to the other. I also realized the
value of simple, regular communication; short updates often prevented confusion and saved
time. From the design team, I learned the importance of visual presentation. Even strong
content can lose impact if not presented well, and I picked up useful tips such as keeping slides
clear, concise, and visually balanced. Most importantly, I understood that group work is not just
about dividing tasks but about helping one another so the final result feels collective. Overall,
this experience improved my research skills, made me more aware of how to communicate in a
team, and gave me practical knowledge I can use in future projects.

You might also like