This is the first in a series on The Basics of Organizing For Data Science.
In this series:
- Why Agendas;
- Why Prepare For A Meeting;
- Why Document A Meeting;
- Why The [ACTION REQUIRED] email tag;
- Why The Bullet Point.
- Because you want to know what the meeting will be about;
- Because you want to prepare for the meeting;
- Because you want to inform others about what to prepare for.
- In the calendar invite directly.
- When you send the calendar invite;
- Update in the calendar invite as amendments are made.
Default Berry format:
Outcome: What can be done to <arrive at a decision about something>
- What are the facts about XXXX?
- What are the feelings?
- What could we do about it?
- What are we deciding to do?
- Next Steps?
Outcome: Situational awareness
- So what’s going on with XXXX
- Next Steps?
Outcome: Increase situational awareness
- Amy updates on XXXX
- John updates
- Luc updates
- Kate feedback
- Popcorn – what do we think about XXXX
- Defer decisions?
- Next steps?
- The chair/facilitator/organizer should be setting the agenda;
- Those that are directly involved in making a decision should be invited;
- Those that are optional, may contribute or FYI’d about the meeting should be marked as optional.
- Run through the Should I Have a Meeting Checklist (Below)
- Include the expected outcome;
- If the expected outcome is from a focus question, it should begin with the word ‘what’;
- List the sequence of how the meeting would unfold, in linear order;
- Invite others to add or subtract from the agenda in advance of the meeting;
- Uncertainty increases as the number of items on the agenda increases,
- Sometimes you need to get together and talk;
- Organize the time effectively;
- Organize the sequence effectively;
- Organize the participants effectively;
- Achieve the meeting objective,