At the reference desk
On the reference desk - both fast and slow. It never rains but it pours ... not really, the pace is often manageable, but there are times when no one comes to ask me anything and other times when they are stacked three deep at the desk while people are trying to get my attention on chat. +1 LibChat.
I notice fast pace when I have more than 2 patrons ask a question.
Working on LibChat. Springshare is more stressful when multiple patrons ask questions.
Collaboration
Push and pull when working together - sometimes people want things fast from me, sometimes I find I want things faster from others.
During evaluation time there is frequently not enough time to do the job I want to do on evaluations.
When I need to meet someone else's deadline on collaborative projects or when someone from another area of the library reaches out for help or information. Helping colleagues always makes me feel like I need to respond quicker than I would if it were just my own workflow. +2
Responding to faculty outside the library tends to take priority over my own projects.
Responding to short notice requests for instruction from faculty (requires fast response because they aren't considering that I need time to plan for instruction on top of my other workload) +1
It feels especially fast if you can find a collaborator to bounce the ideas off of & get excited together.
Multitasking
My pace at work is often fast when I have reports due, projects to work on, multiple student reference appointments, or need to balance instruction sessions with meeting obligations, collection development decisions, and evaluating long-term projects and where they're at. If I have a large amount of work on my plate back-to-back, that momentum causes me to work more quickly and with more urgency.
Looking at my calendar and how fully booked it is. This time of year is a welcome relief from the packed schedule of the academic year. +1 Agreed!
I don't feel like I have many "fast" times. I am always juggling priorities and so my schedule and thoughts feel like they are always starting and stopping. After stopping, it's harder to pick up and start again.
Research and creativity
Research process (IRB, writing, etc.) can feel slower than publishing/deadlines/editing (not enough time because of conflicting things, so very fast)
When I have an idea that feels good and I can picture the steps and I can pursue it or at least outline it for later revisiting, curiously that process feels fast, dynamic. +2
Moving really fast at the beginning with excitement, then gradually slows with other commitments coming in or losing steam from needing to put effort in other places +2 so true, the rhythm then is fast, dynamic, then stop, without fruition.
Seasonal rhythms
Over the course of the academic year, some weeks are very busy with instruction/reference/other tasks, some are very slow, and even after a few years I feel like I'm still surprised sometimes. +4
October and April! +1 April is rough, for sure!
During ACRL [statistics] collection time +1
Online reference, cataloging of purchased books being ordered, committee or other deadlines, RPT time.
Technology
Anything involving AI is fast. Too fast. I second this! Expectations of librarian expertise with new technology -- fast.
Resource decisions
Decision making - when top down, it is sudden/fast; in shared governance, it can feel slow. +1
Funding for the library -- slow. +3!!
Practice setting boundaries
Stop multitasking +1
Communicating boundaries early, before they need to be enforced.
Your emergency is not my emergency (your lack of planning is not my emergency)
Setting boundaries and expectations for work tasks: not always being available, not always able to get the work done now (maybe ties into the no individualistic time management point) +1
Also, if you manage, by taking it out of your hide, to put in 60 hour weeks to get it done, then 60 hour weeks will be the expectation in the future. They won't hire more people if they do not have to. 100%
Broad and intentional communication
Communication across different departments / with colleagues +1
Intentional check ins to avoid silos or assumptions from both sides of tech teams and colleagues in the library. +1
Intentionally include those who you don't think are impacted, odds are that they will be behind the eight ball since they were left out of initial discussions. +1
Invite and include community, beyond campus.
Set expectations for reciprocal respect
Build a relationship with campus IT departments that centers on respect for both sides.
Respect that people have different working hours and lower expectations for a quick response via email or one outside their schedule. +2
I include a note in my email signature: "My workday may look different from yours. Please read, act or reply at a time that works for you." +2
Delay implementation until reflection has occurred
Taking the time to determine the objective first before selecting a technology tool, if any. Rather than starting with the tool and trying to develop projects based around using it. +2
Not rushing to be the first to implement a new tool or tech, but thinking holistically and longterm about the impact the new tech has on us as workers and our users. +1
Taking the time to learn together (new tech, software, etc.)