Hi there, product person here. Due to the nature of the role I have to create meetings to agree on approaches, align on directions and communicate often. Very v

Hi there, product person here. Due to the nature of the role I have to create meetings to agree on approaches, align on directions and communicate often. Very very, keen not to waste anyones time, so I try my best to email first and be present when facilitating meetings. Two quick frameworks that you might find helpful: 1) The POST method, to give clarity at the beginning of a meeting: Purpose: What is the purpose of the meeting? Objective: What are you trying to achieve in the meeting, and what does success look like? Structure: What is the structure of the meeting we are having? Timing: How much time is allocated to the meeting? https://gist.github.com/aaronbuchanan/2dcf936daceab925da61 https://gist.github.com/aaronbuchanan/2dcf936daceab925da61 I like this because it helps give quick context, also the mnemonic is quite handy. 2) Try to structure your meeting around other people's questions: - Going from basic what questions working up to why we need to make a decision, how they might be impacted etc. - I wrote a short post about it here: https://www.logikblok.com/supporting-asking-questions https://www.logikblok.com/supporting-asking-questions I like this because it focuses your communication around your audience/user needs. Aside from that and keeping everyone on the same track of discussion / time / documenting agreements all help out. Hope that helps.