| 
View
 

Planning Team Charter

Page history last edited by PBworks 17 years, 10 months ago
Planning Team Charter
April 30, 2007
 
A charter is an agreement that clearly states why the team exists and how the team will work together to achieve results.

Purpose
Why does this team exist?
 
  • Prepare and provide training to teams from around the state, with overall goal of improving library services in each county and state
  • Establish and measure outcomes for ourselves as a team
  • Help library staff understand and use the 5 principles—help staff continue to learn and use the principles in their work
  • Encourage networking among participants
  • Ensure staff at all levels have an opportunity to influence their organization
  • Provide logistical support for the workshops
  • Be the connectors with LFAP
Rules and Roles
What are the key operating principles or codes of conduct that will guide how the team operates?
 
 
 
 
·         Be on time
·         Review at end of meeting all action items with assignments, deadlines, etc.
·         Try F2F Meeting software, with conference call system as a backup—use CCPL Merlin logins for application sharing
·         Put all questions, etc. on the table—not personal
·         What’s said here stays here—except when it’s a planned ‘news relase’
Accountability
To whom should the team be accountable?
 
  • DLDS
  • Staff
  • Public
  • Each other
  • MAPLA
What are the commitments that individual team members are expected to honor?
 
 
 
 
  • Do what you agree to do
  • Participate
  • Support each other
  • Help with the workshops
  • Post to the team wiki (Gail will start one)
Who is the team leader?
 
  • Gail
  • Nini ($$ for supplies, meals, DLDS liaison, coordinate legislation)
What are the team leader’s responsibilities?
 
 
 
  • Convene meetings
  • Document meetings (wiki, etc.)
  • Facilitate trainings (according to team’s plan)
  • Keep team on track
  • Support team with things like marketing pieces
Decision Making
How will the team make decisions and resolve issues?
 
 
  • Everyone has an opportunity to speak—all voices are heard
  • 80% solution constitutes consensus for our team
  • If absent, member can still have input on decisions—and is responsible to read notes in timely fashion and raise issues
  • Silence = consent
How do we decide – the process?
 
 
See above
What constitutes consensus for our team?

Low
High
Moderate
Level of Consensus
Low – My voice was heard; This is not my preference; I will not oppose the decision.
Moderate – My voice was heard; The decision process was fair; I can live with the decision.
High – I fully support this decision.
 

 
 
 
 
 
 

See above
Communications
What is the process and frequency for sharing relevant information with appropriate internal and external stakeholders?
 
 
 
·         Wiki for team to use
·         Reports at MAPLA
·         Decide at end of each meeting—any key points to share with MAPLA? BULLET POINTS only!
·         Post dates on statewide calendar EARLIEST
·         Keep Staff Development people in the loop
 
Logistics
How will acquisition and coordination of facilities, materials, and support that are needed to succeed be accomplished?
 
 
  • Team members will coordinate regional meetings—secure facilities, refreshments, equipment—and setup
  • Nini will provide registration and marketing (generic) support
 

Comments (0)

You don't have permission to comment on this page.