Revision No. | Revision Date | Revision Description | Authors |
1 | Aug. 11, 2024 | Completed initial document | Michael Hanley |
Expectations
Members
Only mandatory meetings are those pertaining to your project updates (i.e. subteam check-ins, design meetings with leads).
Please let a lead know if you plan on taking an extended period of time off.
If you are assigned a project, commitment is expected to complete that project and keep your supervisor informed. Note that the amount of time commitment per project will vary based on the type of project.
Please be honest with your respective lead if you need more time or if you don’t think you can complete the project, the sooner the better!
Attend socials and engage with the team in events and on discord!
To Get Promoted to Core:
Successfully complete 1-2 projects up to the discretion of your lead.
Consistent attendance and participation in meetings for a minimum of 2 TERMS
Evident initiative in attending onsite working sessions, actively participating in meetings.
Once you have done these steps and up to the discretion of a lead, you will be added to the private #core slack channel by an existing lead/core member!
Core
Attendance to subteam check-ins are mandatory
Attending core meetings are highly recommended as we go through a lot of important topics and discussions
Help Leads with Onboarding activities at the beginning of each term and help younger members with design advice if applicable
If you need to take an extended period of time off, please be sure to let the lead/core group know because you do play a larger role on the team!
Please be honest with your respective lead if you need more time or if you don’t think you can complete the project, the sooner the better!
Attend socials and engage with the team in events and on discord!
To Get Promoted to Lead:
There’s no fixed process to becoming a lead. If a spot opens up and you volunteer to take it or you’re offered a position by a lead and you accept, congrats you’re a lead! With the new position comes new responsibilities…
Leads
Attendance to subteam, core, and subteam leads check-ins (i.e. mech leads meeting) are mandatory
Organize and/or run respective subteam onboarding for each term
Running subteam check-ins
Please inform your team if you’re going to be absent and be sure to reschedule or have someone else run the meeting in your absence
Ultimately responsible for things getting completed on your subteam, do it as you see fit
Understand how to delegate tasks to members vs. when to do a task yourself
Run consistent design reviews with members responsible for a specific task to ensure it is done on time and with good quality
Ensure that you are keeping your team on timeline and inform the PM if you’re falling behind
DO NOT GHOST THE TEAM
Do not abandon your team, you were chosen to lead your respective subteam so please ensure that everything is in a suitable position to be finished
If you’re getting burnt out, please reach out to the PM and other leads to see how you can work together to offload your work onto someone else
Knowledge Transfer
When you choose to retire, you are responsible for finding and training your replacement, if you know that you don’t want to continue the team or if you realize things you’re not a passionate as you were for the team at the beginning, please start to look at finding a successor
Reminder:
If you do need to miss mandatory sessions, please, please let someone, preferably a lead, know. Things happen in life/school/co-op/others and we completely understand. This is a student design team, not the military, but we still highly value and encourage communication.
To Get Promoted to Advisor (former leads and core):
If you’re getting into your upper years and have contributed to the team extensively as a previous lead or core member, but you aren't as energetic as you once were, it might be a sign to hang up the jersey.
As an advisor:
Be open to providing feedback, discussions, and reviews with current leads/members
Be honest about how much commitment you can provide in regards to advising projects
Be open to communications and encourage members (in whatever way) with constructive criticism