Ideas for May 2nd SAT

1. What types of discussions or announcements should be held at SAT?

By identifying the type and scope of the discussions we expect, service owners and support staff alike will be better prepared for upcoming SAT meetings. The goal here is to identify what we’d like on the SAT agenda and to provide consistency of content and delivery.

• Information about planned outages should be be communicated through infoboard instead of SAT (gmoore02)

2. What sort of presentation format & content do we (as a team) request at SAT?

Are there core pieces of information/process that any service change, or policy recommendation, or brainstorming discussion should follow? In attaining the first goal of defining types of discussions, it will be important to help provide some guidelines to both foster a richer discussion and a better inform our IT community.

3. How do we make information dissemination from SAT more effective?

I attend SAT because I believe, given the communication structures we have today, it is one of the best ways to ask questions of the entire IT community, and learn about upcoming initiatives. That being said, it is often hard to ensure that we as an IT community are coordinated beyond the 90 minute monthly SAT meeting. How can we utilize the structure and format of SAT to help spread awareness and information through other tools at our disposal?

• With few exceptions, detailed notes should be added to the agenda prior to the meeting to encourage people to come prepared to discuss topics (gmoore02)
• People should review the meeting minutes afterwards to ensure they are comprehensive and accurate or the minutes should be ratified after each meeting (gmoore02)
• SAT minutes should be shared with the FSP elist and added to ITKB, including relevant ITKB links when applicable (gmoore02)