# Async Meeting about Async and Realtime Meetings ```yaml Meeting organizer: Tom Participation timeframe: Wed, Thu, Fri (1/25-1/27) ``` ## Purpose - To gather team members' input regarding ways we can more effectively communicate and ultimately make some decisions about some goals, policies, tools that we'd like to try out ## Agenda - [ ] get input from engineering team members - [ ] input from Tom - [ ] input from John - [ ] input from Dusan - [x] input from Michael - [x] input from David - [ ] discuss merits of various points - [ ] compile a list of things we'd like to try ## Prompts to respond to (choose any or all) 1. What is working well/isn't working well for you with our current team communication practices, policies 2. Are there any **high-level** goals that you think we should aspire to/attempt to align around? 3. Are there any **specific** things/tools/practices that come to mind that we could collectively consider as a means to increasing our productivity, communication bandwidth, collective intelligence, decision-making capability ## Initial thoughts ### (Tom) > (IN PROGRESS, wait to read) - (high-level thoughts) - for discussions I think we should - try to be more organized in our tool use - try to be more explicit about - whether a topic of discussion requires 'real-time' vs 'async' discussion - what the purpose/desired output is and when appropriate, some sort of agenda or tentative agenda - - generally assume that people aren't always fully available at the same time and make it easier for someone to get up to speed on a discussion more easily ### (John) > (IN PROGRESS, wait to read) - ### (Dusan) > (IN PROGRESS, wait to read) - ### (Michael) - Second everything David said - On slack, please only include relevant people when messaging. It should be pretty obvious after a few message who is relevant to a thread - Stack meetings when possible. Example if there is a meeting and then an hour break and then another meeting, its likely I won't be able to do any concentration work between that hour - If product can be more opinionated about what they want and why they want it, it would help in terms of not having to dissect what a feature is in every meeting - I think it makes sense that once a slack convo is started, if you are mostly working with just one person in that convo then just slack them directly until you have a more cohesive thing when talking to a group of people ### (David) Objectives: - Minimize the time spent in meetings by - Not going on tangents - Breaking off any sub-discussion that lasts more than a few minutes - Only inviting people who need to be there - Make the meeting end explicit - Not trying to "fill" spare time in a meeting ## Discussion > (after we have some input) ## Conclusions > (after we have some discussion)