Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Objective

State the purpose of the group in 25 words or less (brief, energizing). 

Streamline, making Alma easier to use for staff. Optimize patron/user ILL experience.

Seek harmonization (“for the good of UC libraries system wide”). Support unified patron experience.

Identify areas where workflow standardization is necessary to keep the system working smoothly for all stakeholders.

Investigate and monitor system opportunities and developments to be sure we are getting the most out of the technology being used.


Roles

What are the duties needed to get the work done? Who will take notes? Who will keep meetings on track/time? Who is responsible for tracking actions?

Meeting organizer

Note taker

[Vote wrangler - needed if we do asynchronous decision making]

Facilitator

Time keeper


What are our expectations for working together?

Create a list of statements that the team agrees to uphold. For example, ask yourself: How do we make this group a safe space for transparent discussion (knowing that it might become contentious, and avoid back-channeling)? What are our ground rules for meetings? How do we ensure everyone is engaged? How do we ensure everyone has a voice? How will we resolve disagreements?

If a vote is called for it’s your responsibility to cast a vote expeditiously/a timely manner (group determined date per decision).

Be kind and respectful to each other. Create an environment where discussing mistakes and problems is encouraged.

Preference to communicate via e-mail rather than Slack. Use Slack for quick, informational needs. Email for actionable/required communication.

Make an effort to attend meetings. Prepare for meetings as needed.

Bring problems or issues to meetings to see if it is a single campus or system wide issue.

Opt for too much communication so problems and solutions are not siloed to a single campus.

How can the group make sharing mistakes and areas of uncertainty with the wider UC resource sharing audience easier so everyone can learn?

  • No labels