Organizational structure

In my experience RoboTeam Twente functions and should function as two distinct wings. The STEM and non-STEM.

The non-STEM part is headed by the Team Manager/General Manager and is assisted by human relations and external affairs.
From here there are two different ways of thought, an organization of this scale can structure their STEM wing as either by specialization or subsystem which is headed by a Technical Manager/Systems Engineer or both.

In the past we structured according to specialization this entails that you create and work in groups of the same field e.g. Mechanical embedded, electrical, etc.
This wasn't "bad", but created more segregations between different fields and slowing down organic communications then what would be optimal.

This is the organizational chart that was created for the year of 2025-2026:

(yes I know it has 2 mechanical sections oops)

The other option is to structure according to subsystems, hereby you divide teams from different specializations in teams according to functionality of the project. For use that would be a Mars rover so below here is an example of what I imagine an effective RoboTeam structure would be. Of course keep in mind the subsystems under the the Technical Integration Manager are just a rough outline of the idea, these systems can be broken down as specific or as broad as the size of the organization allows and the scope of that years project calls for. But within my investigations it was not quite possible to integrate the software department throughout the other STEM subsystems due to their broad work week by week.