Difference between revisions of "Staff Meetings"

From The Bike Kitchen
Jump to: navigation, search
(created mostly from input from Rafi and Brian)
(No difference)

Revision as of 17:45, 26 July 2009

Thoughts on how to run a good staff meeting:

  • Have a good agenda:
    • The meeting coordinator should get mature items to present to the group for discussion, rather than the "I like / I think - discuss" model. There should be a clear point that needs to be "yeh-ed" "neh-ed" or edited, rather than trying to formulate a proposal during the meeting. Ideas in their early stages should be discussed over the email list. One month before the staff meeting, the meeting coordinator should send a meeting reminder so that brewing agenda items can be solidified.
  • Reaffirm a few things at the beginning of the meeting:
    1. explain the stack.
    2. ask people stay on-topic.
    3. explain that we have an agenda with time allotments.
  • Have someone take minutes (preferably directly on the wiki so they are immediately available).
  • Have an active facilitator:
    • The facilitator keeps the stack. Motion to the facilitator to get on the stack so you can speak when your turn comes. The facilitator has to be a hard ass when it comes to moving the discussion along. Pushing forward is key. Don't just go down the list and let the conversation roll. The facilitator should remind people to keep on topic and should close the stack when the conversation digresses too much.
    • Keep each topic to its alloted time. When time is up, vote on whether to add more time to the topic. Be a vocal presence and interject, even if it is annoying at times.
  • No stack on update agenda items.
  • Encourage everyone to give input so that the conversation isn't dominated by a few, vocal people.
  • Limit the dinner break to 15 minutes.