Crisis and Creative October 20, 2009
Posted by Jenica Rogers in Leadership, Libraries, Management, Musings, Project Management, work life.3 comments
A personal obligation — doctor’s appointment — kept me from attending a meeting at the library this morning. I was busily feeling bad about that until I had a conversation with one of our IT staff as I grabbed a breakfast sandwich on my way to my office. We were just chatting about learning curves and transitions and deciding when things are a crisis and when they’re just going to have to be handled by someone else…
And I flashed to this post, The Crisis and The Creative, by Rands in Repose, that I read last week. He starts by saying, “If you polled my team about my daily agenda, they’d say, “He’s either running to meetings or in meetings.” Glancing at my calendar confirms this: 14 meetings this coming Monday – double-booked for five of them. Sweet.” Okay, yes. I’m hooked. That’s me. I read on.
The part I liked most when I read it last week was:
Whether it’s Crisis or Creative, activities in these buckets run hot. Whether I’m making sure that someone isn’t going to quit or I’m jump-starting a brand new project at a time when no one has a free second, when I’m working the edges, it’s fast and furious. The issue is that I’m responsible for a lot more than just the work that’s running hot.
See those boring lines in the middle between Crisis and Creative? That’s an important part of the model. Items in the middle are the silent non-Crisis, non-Creative responsibilities that are my team just making it happen. It’s all very important work, but it’s work that occurs with very little investment from me because I’ve hired, manage, and work with competent people who excel at what they do. The middle isn’t responsibilities that I’ve delegated and need to check up on, this is work the team just does, and to understand how to get the work there, you need to understand the edges.
And what I realized as I stood there, waiting for my sausage-and-cheese-on-an-english-muffin-please, is that today’s meeting, unavoidably double-booked with my doctor, is about something that I had delegated (or my predecessor had, actually) that had reached a crisis and needed checking up on — but I didn’t have to be at the meeting to do it. I needed to declare that this crisis could be solved by someone else, people who are competent and excel at what they do, so long as they reported it back to me when they’d figured it out.
Because, really? I need to finish some Creative work. I really really really need to finish some creative work. Performance goals. Vision and mission planning. Strategic reorganization. Service and communication plans.
And I’m the only one who can do those things. I’ll need help, and will be consulting and revising and editing for a while — but I can’t consult, revise, or edit unless I have the things down on paper. And I can’t put them on paper if I’m hopping from crisis to crisis. I have to trust the middle, and I have to let the middle handle some of its own crises.
And I do trust them; I work with wonderful people who are very good at what they do. But I suspect we’re all testing each other’s boundaries a bit, figuring out where The New Boss wants to be involved, needs to be involved, and is willing to be involved. So I’m going to set a boundary for myself. Let the middle work. Ask the middle to manage some of its own crises. Divide my time more evenly between Crisis and Creative. It’s the only way to make it work, I think.
And the giant piece of paper covered in marker-ed post-it notes that represent the possible ways we might reorganize our administrative structure won’t get more interesting on it’s own, so I need to give it some love.
follow-up on chalk notes September 23, 2009
Posted by Jenica Rogers in Leadership, Libraries, Management.3 comments
Over on FriendFeed, Dorothea Salo asked for a follow-up.
Jenica, I’m going to make bold to ask for a follow-up post. You are Head of Libraries. You answer to the Provost, who presumably has many more things to worry about than chalk on sidewalks. So, serious question: if your Head of Public Service (presuming you have such a position) had done this without consulting you, what would you have thought, said, and done? What if it had been a rank-and-file reference librarian?
Interesting questions.
First, yes. I am the Director of Libraries, and I do answer to the Provost, who absolutely has more to worry about than chalk on sidewalks. However, I happened to have an Academic Cabinet meeting on Monday afternoon, which is the Provost, the Deans, and me. I mentioned this issue as we were discussing our local issues, and roughly outlined my intended response. It seemed both fair and appropriate to offer the chance for my efforts to be redirected or informed by the opinions of that group. As a result, I learned that the music school student association had raised similar concerns about our music library, and so I’m planning a response there, as well.
Also of note is that we have the world’s flattest library hierarchy. There is no Head of Public Services to speak of, but we have many engaged and dedicated public services staff. So, if one of the librarians or staff here had chosen to do this, I would have, first and foremost, applauded the efforts toward honest outreach and communication, because they’re principles I value. The people on the front lines are also in a unique position of awareness of our users, and poised perfectly to do that kind of outreach.
But secondly, had they chosen to do this without consulting me, I would have been frustrated. My frustration would likely have come from the fact that while I appreciate initiative and innovation, as Director of Libraries, I will be front-and-center for any fallout that comes of public actions made by The Libraries. I want to find myself, in an ideal world, in a position where I can always back up the decisions and actions of library staff, and both defend and explain those actions as needed. If I’m not informed of public statements and actions, then I’m left both blindsided by any reaction to them and also likely to be unable to defend and explain them effectively.
Therefore, though I did this quickly, if someone were to go to the Provost to complain about it today, I hope she would feel that she’s able to say that she knows that I consulted current and historical data about our hours before responding, and that I was attempting to be forthright and prompt in my response to sincere concerns from our users, and that she would be able to do that without double-checking with me first, because she and I already had a brief conversation to that effect.
So that’s what I would think, based on how I’d like to see our libraries operate on this particular campus. What I’d say and do? Would depend on the person, and the public-facing action, honestly. If I disagreed with the action or the message, I’d request that we change it, probably ASAP, and engage the staff member in a discussion of why that was their response, and what I think is a better response, and why. Regardless, however, I’d be likely to ask for a heads-up the next time there was a need for outreach, and explain my desire to be kept in the loop for all of our public-facing actions. And I’d explain my reasons for that desire — it’s not about micromanagement or message control or the usurpation of the traditional roles and responsibilities of any one position, but about being the one who’s ultimately responsible for our presence on campus, and for supporting the efforts of all library staff. The more I know, the better I can do that, and, yes, sometimes direct it, if that’s what I think is necessary.
How’s that for an answer?
Managing geeks September 10, 2009
Posted by Jenica Rogers in Leadership, Libraries, Management, Technology.1 comment so far
This article from Computerworld — Opinion: The unspoken truth about managing geeks — is specifically and explicitly talking about IT pros, but hey, I’m a geek. I like lots of people who are geeks. I work with a bunch of them, too… and I found as I read this that a lot of it resonated. I’ve never found any “management” article or book that I thought was 100% on-point, but this one has some interesting observations in it. A few:
“Few people notice this, but for IT groups respect is the currency of the realm. IT pros do not squander this currency. Those whom they do not believe are worthy of their respect might instead be treated to professional courtesy, a friendly demeanor or the acceptance of authority. Gaining respect is not a matter of being the boss and has nothing to do with being likeable or sociable; whether you talk, eat or smell right; or any measure that isn’t directly related to the work. The amount of respect an IT pro pays someone is a measure of how tolerable that person is when it comes to getting things done, including the elegance and practicality of his solutions and suggestions. IT pros always and without fail, quietly self-organize around those who make the work easier, while shunning those who make the work harder, independent of the organizational chart.”
and
“…if you’ve managed to hire well in the lower ranks of your IT group, the staff already know how to manage things. Unlike in many industries, the fight in most IT groups is in how to get things done, not how to avoid work. IT pros will self-organize, disrupt and subvert in the name of accomplishing work. An over-structured, micro-managing, technically deficient runt, no matter how polished, who’s thrown into the mix for the sake of management will get a response from the professional IT group that’s similar to anyone’s response to a five-year-old tugging his pants leg.
What IT pros want in a manager is a technical sounding board and a source of general direction. Leadership and technical competence are qualities to look for in every member of the team. If you need someone to keep track of where projects are, file paperwork, produce reports and do customer relations, hire some assistants for a lot less money.”
I don’t care if the author thinks he’s talking about IT professionals. Sounds like my tribe, to me. Which is probably why we’re bouncing it around the social networks at each other.
Edited to add: Interesting discussion happening here.



