• The University Budget Officer is the Chair of the Insight Project and the Associate Director for IR is the overall Insight Project Leader. Any questions or issues should be directed to the Project Leader.
• The Sr. Associate Director and Associate Director for IR are responsible for the overall outcomes for the office and will oversee the assigning of resources and priorities.
• The Insight Steering Committee manages the project and sets priorities. Steering members may attend and participate in any Insight discussions.
• The Insight Advisory Committee, which includes the Insight Steering Committee members, reviews proposals and advises Steering about overall impact.

• Strive to accomplish Office's operational requirements and planned Insight improvements, while remaining flexible because priorities sometimes change quickly based on issues beyond our control.
• Recognize and support individual/team contributions and accomplishments.

• Recommend representation for separate Working Groups, when appropriate, for specific initiatives; Working Groups will include those knowledgeable about the initiative, regardless of primary team membership.
• Seek input from the entire office and others, as appropriate, as new initiatives are identified.
• Provide on-going updates to the office about project progress and recommendations. Provide opportunity for review of recommendations.
• Consider ten Questions when evaluating processes:

1. Does it need to be done at all?
2. Why is it being done this way?
3. What can be done to make it better?
4. How can we change it?
5. Who needs to be involved in the change?
6. Who will it affect?
7. When can we have it done?
8. When do we need to have it done?
9. What are the benefits of doing it differently?
10. Is it worth it? (Cost / Benefit analysis)

• Provide systems to assist in overall operation of the office.
• Make recommendations about technology used to build and support application systems.
• Make recommendations about technical training, and provide training for new and existing employees when appropriate.
• Make recommendations about standards to provide consistent application of technology and consistent supporting documentation.

• Communicate information via the Insight communication methods (described below) about the activities of the Core Team.
• Seek and encourage input from team members and appropriate people regarding projects as well as contribute to projects of other groups.
• Actively seek and support collaboration among teams for cross-team initiatives.
• Work with IR Core Team members to encourage skill development and broader understanding of the systems so that each person is challenged and can contribute to the best of their ability. Team leaders set an example for others to follow.
• Actively seek and support collaboration with other offices.

• Responsible to communicate with the appropriate team leaders and supervisors about the impact of their team and cross-team assignments.
• Participate in identifying the outcomes during each meeting so the Staff Assistants can record them and remain full participants of the group.
• Discuss scheduling conflicts with the appropriate team leaders and supervisors in order to give Insight meetings the appropriate high priority.

• Internal web is a record of Insight information, progress and outcomes.
• Email is a tool for team and office communication  Note: Team Nickname lists will be maintained for office use.
• Input/ Review Opportunities:

• As new projects are initiated, input will be sought from the office.
• Review of recommendations for input and reaction will be sought from the office.
• Ideas for Insight related projects should be addressed to Core Team leaders, Insight Project Leader, and/ or Steering at any time.

• Meetings are a place for regular participation and a tool for communication. See "Meeting Recommendations" below

• Core Team / Working Group(for specific projects) participation
• Combined Staff Meeting Insight updates will be presented by the teams.
• Steering/Advisory review and discussion
• One-on-one discussions should be initiated anytime an opportunity is needed to share information or seek clarification.

• Keep number of individuals in meeting to a minimum (5-7).
• Determine the Start and End time for the meeting:

• Meetings will start and end promptly.
• Meetings should be scheduled as close to the beginning or end of the morning or afternoon as possible to leave a larger block of time available for other work. i.e. 1:30 or 11:00 start times instead of 9-11 or 2-3.
• Minimize the length of the meeting based on the topic.
• Insight team meetings will have attendance priority when there are Insight meeting conflicts as follows:

• Human Resources - Tuesday mornings (except for the IBIS Budget Management Team meetings.)
• Technology - Tuesday afternoons
• Student - Wednesday mornings
• Finance / Budget - Wednesday afternoons

• Prepare and distribute Agenda 1/2 day in advance, when possible.

• Identify topics (informative, discussion, or decision), presenters, anticipated discussion time
• Draft next meeting's agenda at end of session.

• Participants:

• Arrive promptly, are prepared, and actively participate.
• Contribute to the team results by completing outside assignments in a timely manner.
• Participate in the identification of the Key Points and Outcomes to be recorded for the session.
• Observe basic conversational courtesies.
• Observe confidentially of discussions within the meeting.
• Discourage interruptions.
• Constructively evaluate the meeting as to what can be done to improve the next meeting.

• The agenda and Key Points and Outcomes documents become part of the project record.