-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Language logistics role #37
Comments
Coming from me, having this rotating logistics lead for each study groups would be super helpful, and allow us to plan out ahead and preempt last-minute cancellations. It could also be a way for leads who cannot come to the study groups to be involved for that month by helping to organize. |
I agree. This role can basically be the single poc for all study group leads. I especially like the "assign 1 lead to prepare the topic/activity for each week" |
I brought this up in the Algorithms channel: I don't think the logistics person needs to necessary do each of these points (for example "update the meetup details"), so long as that task is "delegated" and the responsibility still falls on the logistics person. The example for them is that @aag6z will be making the meetup.com event but Kajari is ultimately responsible for it if Amy doesn't for some reason. Would love thoughts on that, though |
So does the idea of planning for these a couple weeks out mean that the logistics person for, say, October does that two weeks into November, or just whoever's on for the month does what they can for that month, and then whoever's on for the next month does whatever's available and needs to be done for that month. |
For updating the meetup - the amount of time that it takes to ask someone else to do it, is the same amount of time that it takes to change! (5-15 seconds) So I think it's a better "just update it" task than a delegated task. So if Kajari sees something wrong from Amy's meetup, she should change it and then let Amy know. Basically, I just don't think anyone should ask another person to update the meetup if they know something should be changed. It creates a bottleneck for something that really only takes a couple of seconds. And idk @kdmcclin - I think monthly might be easier to remember? It's weird this month since we didn't get this message out before it started, so that makes it a little harder for October. (but I don't think too hard?) So say you were putting together the October months. Zuri would start planning for November in the middle of October, but you would still be the point woman for the rest of October. Not sure if that makes sense... And that would just be so that every lead has experience being in this role. Once everyone has led a month, the responsibility will fall on the newest lead so that it is a sustainable model! |
Although I did just change it to "make sure the meetup details are updated for" because it does make sense for the responsible lead to update the description. I just find the title/location so important/quick to change. It's sometimes not updated for weeks after we know the information because no one feels responsible for it |
This semi-relates to the "before" section of the meetup here. I was thinking the logistics lead is responsible for the "bigger picture" per month and they would work with @SuWKim to make sure hosts are happy for the month. This frees up the other language leads to focus on making their events successful for that month.
Logistics Role:
Ultimately, I don't think this will take more than 1 extra hour a week, but really help with our communication and efficiency throughout the group!
The text was updated successfully, but these errors were encountered: