I've been hollering (politely, of course) about this at my own university since late last week after dozens of messages from separate sys-admins trickled and then poured in over the last few days, and we set up a web page to gather all our information. I asked for someone to coordinate on the technical side of the house. As I said to my boss on Friday,
This is one of those, "I've been doing this for ten years and something isn't hitting the right note," things. It's a big impact, there are a lot of patches that will have to happen, and it doesn't feel like anyone has their arms around the whole situation.Later on, I explained again more succinctly:
Sometimes we see things happening where all we can do is raise a flag and make sure that everyone knows what's going on. If no other actions on their part are required, them I'm fine with it, but I want them to say it. At the very least, I would like us to check in with them and make sure there's some common dialog happening.
I'm sorry I can't explain it in more objective terms. It's a gut thing based on how the whole thing has evolved.
Basically, I see the potential for trouble, and I want someone technical to make sure there isn't any trouble or to say that it's all under control. Trouble could be anything from it doesn't go well to it's extremely uncoordinated and a lot more work that it has to be.She trusts my gut and we have someone on the technical side. It's validating to read this post in CIO.com titled Y2K Redux from February 12. I used this same example with the work folks on Friday. (Yes, I'm feeling smart today.)
CIO.com is, by the way, a valuable bit of reading for non-CIOs. If you want to become knowledgeable about the business of IT, read it. TWs have constant angst about staying valuable: understand the business you're in and what issues your bosses are dealing with.
