It’s your job to say “no” as well as “yes!”
- We already have enough “yes-people.”
- Bad ideas are everywhere, even in the boss’s office.
- And for trips to Abilene, as well.
- Question assumptions.
PLEASE RESPOND TO BLOG POSTS ANONYMOUSLY OR USING A PSEUDONYM
Sometimes it is hard to say no. It can be unpopular.
a cultural shift needs to happen in most libraries to make this work. there is a fine line between giving permission to challenge bad ideas and creating a culture of “no, we can’t do that. what would happen if we succeeded?”.
But you can’t kust say “No.” You must be prepared to say why you are saying No. Your reasoning is a valuable source of information for all involved in a discussion.
It can take courage to say, “No”, but it’s better than saying, “Let me think about it” and then never coming back to the topic.
I recently had a staff librarian state in a meeting that as long as the staff knows “why” something gets a “No”, then they can accept it. I agree and disagree with this statement. Some staff will accept a “No” answer if they believe the reasoning is sound. Others will challenge the “No” response regardless of the reasoning because it may directly impact them and result in change. Those that push back tend to fall into the “it’s all about me” syndrome, and have a difficult time accepting what’s in the best interest of the department.
It’s important for library administrators (which I am) to say “no” to their administrators sometimes too. However, I have to be very well prepared with data and sound reasons — and it still doesn’t always work. I think it’s essential for me to speak up for what I believe is right — whether it’s my staff or my boss. I encourage my staff to speak up too at meetings or one-on-one. I do remind everyone to be professional and courteous in their disagreements — something I wish the news media could learn, too!