I’ve been thinking about Eli Neiberger’s ILEAD keynote speech in regards to how I design programming for my library.
I am in awe of the great programming that they have been able to do, but it’s very easy to jump on the bandwagon and state, “but they are in a large system, they have a healthy sized staff, and they have a larger budget.” As much as I want to use that as an excuse to say that I don’t have time, or I don’t have enough resources, we have to look at the resources we have and make it scalable.
When designing programming, there are a few things to keep in mind.
Reflect on what you currently do: We all do excellent programming. What events are your most successful? Why is that? Is there a topic that is well enjoyed? Are you promoting it in a certain way? Taking time to appreciate what works for us, helps us find ideas for new programming. It also provides a lense for reflecting on programming that is not successful.
Your community need: Is there a topic that works well in your community?
Resources available: What do we have, and how can we use it effectively? Is there something we have that can be used in a different way? At ILEAD, Christopher Miller had us do an activity that really hit home. He had us take a deep breath. Before we exhaled, we had to take another deep breath. That second breath wasn’t useful because there was no room for it. Sometimes, in order to try something new we have to adjust our current programming.
How we market our programming to users and nonusers: Is there a way to market to the people who use our library and try and engage users who may not realize what their libraries can do for them.