Welcome Guest, please
login
or
register
.
Welcome,
Guest
. Please
login
or
register
.
Forum Home
Help
Search
Login
Register
Programming Librarian
»
General
»
General Discussion
»
Program Planning Efficiency
Pages: [
1
]
« previous
next »
Print
Author
Topic: Program Planning Efficiency (Read 2033 times)
SNBG
Beginning Programming Librarian
Posts: 1
Program Planning Efficiency
«
on:
June 02, 2011, 08:31:54 am »
We are looking to streamline the program proposal process for our library system. Currently staff have to fill out a proposal form for each and every program/event they would like to offer, submit that to their supervisor, who then sends it further up the chain of command until it has the final sign-off. We would like to cut out many of these steps, allowing branch and department staff to offer recurring programs without having to fill out paperwork each and every time, but we of course still need to know what is going on.
What is your system's public program policy, as far as staff procedures/paperwork go? Any ideas for making things more efficient? Is there a computer software that you use, so staff can input program details electronically? We are thinking about using InfoPath.
Logged
mtc9117
Beginning Programming Librarian
Posts: 1
Re: Program Planning Efficiency
«
Reply #1 on:
June 12, 2011, 07:11:38 pm »
It depends on the chain of command. If steps appear repetitive, then more than one person is doing the same job. Those are the areas that should be streamlined. It would save time on staff too.
At my library, we generally have a program coordinator, the coordinator's supervisor, and a marketing department. The program ideas are approved by the program coordinator and his/her supervisor, and then sent to our marketing department for publicity. If the marketing department has any concerns with a programming idea, they may direct them to the director, as well as the coordinator and his/her supervisor. (Since they are in charge of branding, their concerns are well taken.)
If you are a larger library, I would suggest coordinating programs within each department and then having a smaller chain of command above them. This model could be used for the branches too, but on a smaller scale. Instead of departments, just have one person whose job it is to approve programming requests for the branch.
Does that help at all?
Logged
Pages: [
1
]
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
General
-----------------------------
=> General Discussion
Loading...