From my experience, I found that smaller groups being divided in task but working towards a common goal has found massive success for certain projects. Within my work on a project, I was tasked by my project manager to handle backend development of a documentation tool while my associates were responsible for the UI design and using feedback from stakeholders. With this division of labor and allocation of expertise by each member, we were able to adhere to a strict schedule with timelines for each phase of the project. A designated team leader was also responsible for scheduling meetings for regulated updates for the project and setting time with stakeholders to acquire feedback throughout the development process. With this methodology, our project had been piloted and launched within the designated timeframe and saw immediate success with all stakeholders and the company.

Understanding hiow the work is divided in a group project is crucial to ensuring both the efficiency and cohesion in the final version of the product. While assigning each individual person a separate section may promote accountability and speed, there is a possibility where it can lead to inconsistencies in tone, direction and even the overall flow of the timeline. As mentioned last week, working in smaller collaborative groups on each section could allow for shared ideas, early error detections, and a stronger alignment with the overall project vision. Although this approach may require more coordination, the improved clarity and coherence of the final report often outweigh the additional effort, especially for projects that require analytical depth and integration across multiple parts.