Pause TOC meetings on Thursdays for at least 3-6 weeks. Take that time to decide about how those meetings can be most effective once we resume, and how leadership will be structured.
NOTE from voting: want to make sure that communications and liaising with other groups doesn’t suffer from the lack of the TOC.
EUO wants to connect with discovery to keep tabs on their discussions around branding, etc.
Form Steering Committees for EUOS and IT consisting of:
Stacy, Melanie, Neil, and Caitlin
Dominique, Catherine, Neil, and Caitlin
Schedule steering committees to begin ASAP with a focus on:
Any immediate work for the group (i.e. communications spreadsheet or the Alma trainings)
Prep for the work plan planning in the main group
Point 1: PASS
Point 2: PASS
Point 3: PASS
3
Team Tuneup Discussion
Discuss and understand next steps for going forward with EUOS and IT groups
35
Team
Next steps include scheduling Steering meetings, understanding the schedules for main groups (are we meeting enough?) and planning the work plan work in steering: what do we want to present to the main group and when?
By end of August - both teams create a work plan for the project.
EUOS: Difficult to envision the vision and success without understanding the whole project. Getting into the work felt like I had to get into the work in order to start envisioning what I wanted to do.
→ Spending that time reaching out to local campus groups to see what that vision might look like locally, then coming together to see the bigger shape.
→ Difficult to envision out of the ether - much easier to work from something that already exists.
(Stacy) In terms of “what will it look like to succeed,” I think there are a few things: (1) end users [faculty especially] can’t say they didn’t hear about this. (2) we will communicate the value of the new system. (3) we engage the actual folks on each campus working on communications, outreach, and teaching early in the process, and know when their critical deadlines are to get communications pushed out in a timely manner [i.e. no one in any comms office is surprised].
Things that are NOT our goals:
We do not expect 100% buy-in
We DO expect that some faculty will complain
We do NOT expect to do market research on user needs ahead of time. Not only is this impractical, but we are not developing a product for our users, to be honest. We made a thoughtful decision as a system. We need to communicate that thoughtful decision to our users in language they will understand. Likely it will be in easier ILL (which I hope will be an actual deliverable, but again… I don’t know for certain yet)
We DO expect to do some user testing and make recommendations for fine-tuning, along with the Discovery FG, after the product goes live
We do NOT expect to be making custom videos, tutorials, etc for each of all 10 campuses.
We DO expect to make some reusable objects that can then be used and customized by local teams, librarians, etc for their own unique teaching, learning, and communications ecosystems (e.g. do you use Youtube or Vimeo? do you use Blackboard or Canvas? do you use Canva or Adobe? do you use LibWizard for tutorials or Articulate Storyline? do you use Constant Contact or MailChimp or something else custom? etc.)
Role of the group is to understand the landscape and needs, and be proactive in being supporting of local needs. “Work backwards from the slowest campus.”
MR: We’re going to be tapping into the IT work, because they’re doing a lot of workshops. And we want to liaise with them for Patron workshops.
IT: CB: Early on with reviewing of the charge and taking the temperature, we did do a lot of that. Personally I have a hard time connecting with visioning. I want to look at the charge and how we’re going to meet it.
DT: I find it easier, but the challenge was that I didn’t know the size of my sandbox - early on I was trying to determine how much creating of materials we were doing vs just sending out what ExL was giving us, etc. Do they need to all be consistent? Or do indv. campuses want their own customized materials?