feat: proposal for international meetings #37
Conversation
moul
requested review from
jaekwon,
ilgooz,
zivkovicmilos,
adrianakalpa,
lbrown2007,
michelleellen and
a team
|
Adding to this proposal - Sticking to not going beyond duration of the meeting and try to wrap up the last 5 minutes with outcome and action plans. |
|
@VT-Cosmos your suggestion makes sense in general, not only for international ones; please open a PR with general meeting suggestions and then we can link the general doc from this international-specific one |
|
|
||
| Instead of favoring those who speak the loudest, we have a more democratic approach to scheduling international meetings. We suggest the following: | ||
|
|
||
| - We reserve the most precious time, 4-7pm CET from Monday to Thursday, for critical international needs. |
There was a problem hiding this comment.
So are we making official the informal rule of "no meetings on Fridays"? maybe make it explicit with another bullet point.
| #### Example of cases: | ||
|
|
||
| - Currently, AtomOne is a priority and deserves at least a weekly meeting at a convenient international time. Later, it could be held bi-weekly, monthly, or on an ad-hoc basis. | ||
| - Some team members are louder, while others are more discreet and consistently get postponed. |
There was a problem hiding this comment.
ideas:
- aside from the leader of the call, prefer using hand-raising over interjecting
- points can be pre-emptively made in chat, but they should always also be re-raised via voice through hand-raising as otherwise the POV risks being sidetracked.
| Instead of favoring those who speak the loudest, we have a more democratic approach to scheduling international meetings. We suggest the following: | ||
|
|
||
| - We reserve the most precious time, 4-7pm CET from Monday to Thursday, for critical international needs. | ||
| - We establish a queue of topics and priorities, planning two weeks in advance with leaders. |
There was a problem hiding this comment.
beware of endless burocratization with things like these. I would propose more that the topics and priorities agenda is written down in a shared HackMD or Google Docs, and is prioritised by the leader in the 2 days before the call.
the way it is currently written it seems that each team member should write to the leader to propose a topic. I propose a more direct approach of putting agenda items directly (possibly tagged with the proposer's handle/name) so that managing meeting agendas for leaders becomes a 15 minute task before the meeting rather than a constant influx of pings.
| - We use a Notion/GitHub page where anyone can propose topics or meetings. | ||
| - We hold a weekly top-management meeting to decide the allocation for the next two weeks. | ||
| - Exception: we should keep our public meetings regular. | ||
| - Anyone, can try using the unallocated slots, but there is a risk that they may be replaced by something else. |
There was a problem hiding this comment.
I would make a note to prefer sharing meeting information asynchronously through minutes, diagrams and notes rather than video recordings and transcripts. and avoid using AI tools when discussing sensitive matters.
it's very hard to play catch-up with meetings by watching full 1-hour sessions. this is a strategy that you already successfully adopted for the gno launch AMA and I think we should continue: write things down, both for those absent and for those present who want to remember what was discussed.
if the leader is not taking notes/minutes themselves, then he should elect someone to do it.
There was a problem hiding this comment.
+1 for minutes, summaries or diagrams
I suggest changing the way we handle international "VIP" timeslots.
Please provide feedback.