Reasonings for roles

One president

We think having only one president is sufficient. We believe that the usual justification for having two presidents is so ideas could be bounced around with the other co-president, and there wouldn’t be as much pressure being the only person “at the top”.

However, this is exactly what the other executives are for - whoever is in the exec body should share the responsibility of being “at the top”, and the team should operate as one collective regardless.

Admin Officer

We believe that the roles of Secretary, Treasurer and Arc Delegate can be combined because:

• Dev traditionally does not run many external-facing events (where Arc room bookings would be necessary), thus the workload for Arc Delegate is minimal.

• Similarly, because there are few external-facing events, the workload for Treasurer is also greatly reduced.

If at any point the workload for admin officer becomes too high, the Treasurer and Arc Delegate roles could be delegated off to some other executive. In the future, if DevSoc does decide to run more events, the role can be split as necessary.

VP divisions

We have decided on four vice-presidents so each VP handles around 3 teams - we found that as VP Dev (and VP Internals/Externals for CSESoc), splitting our workload amongst 4-5 teams is way too high at the beginning.

From there, we decided to split up the VPs this way to ensure that each vice-president has a similar workload - for Internals, the Platform and UI/UX teams are traditionally fairly independent, so the workload is even. We also tried our best to make sure each division “made sense”.

These divisions are not permanent - the 2024 exec can change them as necessary, such that workload is spread evenly.