All the attendees at least a day before the meeting. Include a link to the . Proposal deck, and give any additional context people might need—this is a higher signal to . Folks that it's an important meeting and reminds them to prepare in advance.Here's a template . I've used in slack: [project name] Kick-off meeting reminderdate: [date], t-[x] Daysdeck: [link] (please review . Ahead of time if you can!) attendees: @ , @ , @additional context:---running the meetingthis . Is actually the easiest part, assuming you've done solid prep work and that public speaking .
Doesn't make you nauseous. Make sure you have malta dataset someone taking notes, and (I'm going to . Write this in all caps to make it clear how important it is) leave time . For discussion. I recommend allotting ⅔ of the meeting for discussion (so minutes of an . Hour-long meeting). It may seem like a lot, but since you're asking for space on . The roadmap, you're likely to get lots of questions and hopefully a lively debate.No one . Will be mad if you finish early, but if you're not able to finish in .
The allotted time, it might start things off on a frustrating note for everyone.Following up . After the meetingwithin hours after the meeting, send a follow-up to everyone who was there. . There are two things you need to accomplish at this point:summarize the next steps.Schedule the . Next touchpoint.Here's an example of a message you might send. @[tag all attendees] Thanks for . The time yesterday! We covered a ton of ground across product, engineering, and marketing. We're . Energized to press on toward [project] And explore how we can make this work for .
|