Recommendation:
Conducting 5-15 minute leader calls Sunday or Monday evenings.
Rationale:
Small-group calls aren’t particularly effective, especially given a small-group meeting is held in class, a leadership check-in may serve to be more insightful. Being held a day or two before Tuesday is suggested in order to provide time to digest the latest updates and developments occurring in your respective departments.
Practice being concise and straightforward. Limit yourself to 2-4 minutes of updates. If you’re unable to express the progress in 4 minutes or less, you’re either unsure of what’s happening and are rambling or require further practice in verbal expression. Both are good to hone while you still can as students, and leader calls could help to improve those communication skills.
Meeting minutes are recommended to be recorded by the producer, who can then print and digitally share a copy to Nikki and the other group leaders at the start of the next work session. Then allow group leaders to filter that information as it pertains to their team during small-group meetings (need-to-know basis).
If this approach is taken, this could serve as a replacement for large group meetings, which tend to be group leaders noting progress to other group leaders with the remaining team in the background -- time that could be spent working on the project. Small-groups in-person are still useful, but those 5-10 minutes at the start of class might better be spent before class.
But should there be concern for providing a open forum for peers to ask questions, direct the team to use the requests-functionality channel via Discord. It was created for that very purpose. Sure, asking something in-person while everyone is present can be helpful, but not everyone needs to be present. Nor are questions offered often enough to warrant the in-class big meetings.
Note: this is a suggestion and does not need to be put into practice.
Recommendation: Conducting 5-15 minute leader calls Sunday or Monday evenings.
Rationale: Small-group calls aren’t particularly effective, especially given a small-group meeting is held in class, a leadership check-in may serve to be more insightful. Being held a day or two before Tuesday is suggested in order to provide time to digest the latest updates and developments occurring in your respective departments.
Practice being concise and straightforward. Limit yourself to 2-4 minutes of updates. If you’re unable to express the progress in 4 minutes or less, you’re either unsure of what’s happening and are rambling or require further practice in verbal expression. Both are good to hone while you still can as students, and leader calls could help to improve those communication skills.
Meeting minutes are recommended to be recorded by the producer, who can then print and digitally share a copy to Nikki and the other group leaders at the start of the next work session. Then allow group leaders to filter that information as it pertains to their team during small-group meetings (need-to-know basis).
If this approach is taken, this could serve as a replacement for large group meetings, which tend to be group leaders noting progress to other group leaders with the remaining team in the background -- time that could be spent working on the project. Small-groups in-person are still useful, but those 5-10 minutes at the start of class might better be spent before class.
But should there be concern for providing a open forum for peers to ask questions, direct the team to use the requests-functionality channel via Discord. It was created for that very purpose. Sure, asking something in-person while everyone is present can be helpful, but not everyone needs to be present. Nor are questions offered often enough to warrant the in-class big meetings.