Posts Tagged ‘siguccs’

27th November
2011
written by kaiyen

I find myself at a strange intersection in my professional career.

On the one hand, I have prided myself on “doing more with less” in terms of what our department has accomplished with a significantly smaller budget than comparable groups on campus (to be clear – the “more with less” motto that is often used when budgets get tight or staff are laid off is one which I am firmly against and perhaps abhor as a managerial method.  We can work on getting every last drop of productivity out of our resources, but we can never do more than 100% of capacity, and we should never ask our staff to even try).

On the other, I find myself saying bold things that I have yet to back up with my own actions.  For instance, of late I have spent much time thinking about the future of IT in higher education.  This has been stewing in my head for some time now but Theresa Rowe‘s opening plenary at the SIGUCSS Management Symposium in San Diego really crystalized things.  We simply cannot keep doing things the way we always have been.  Maintaining the status quo – including the thus far incremental improvements to our systems and services – is not sustainable.  We must radically reassess our service portfolios and even reconsider whether we have the right job descriptions – much less the right people – to meet student, staff, and faculty needs going into the next decade or more.  Are we structurally sound and prepared to meet the challenges of delivering Google and Facebook-like services and innovation on the budgets that we have?  Can we really keep trying to achieve enterprise-level performance on budgets that corporate IT departments would laugh at?  I have long asserted that we have to make tough decisions and invest in those services that give back the highest value, not just the ones we “have always done.”  Rowe gave an even clearer and more comprehensive analysis ranging from technology trends to HR to management to budgeting.

Yet…have I done this in my own job thus far?  Have I actually led my staff in the charge to reduce our service portfolio to offer only high value services?  How do I even know the value level of our current services such that I can make an assessment?

I have spent the last 4 years building up the reputation of Law Technology and Academic Computing at Santa Clara Law School.  We are not perfect and many people know that.  But few point to those deficiencies as symptoms of a dysfunctional department.  There is a faith in our department – and the effort that we put into each of our duties – that has become the fundation of our role at the school.  I am extremely proud of where we are compared to when I arrived.  It’s been a combination of marketing, professional development, management, hopefully some leadership and definitely some changes in personnel.  But it’s real.

And it’s time to take advantage of it.

2012 will be our “crash” year.  This will be when we take all of this goodwill and faith in our department, bank on it and make the potentially radical changes that address the changing needs of academia.  I am convinced that, in the long run, all of our changes will make people happy.  I am also certain that in the short run several people will be upset by the removal or alternation of some services.  But during 2012, we will assess where we are, decide in what we will invest, identify what we must cut in order to achieve those goals (and things will be cut – I will not allow our portfolio to just increase without change elsewhere), and make significant changes.  We will use personal interactions, school and university-wide marketing, a bit of political maneuvering and I’m sure some apologies.  But this will be the year.

January 3 is when we return to work.  I’m sure you’ll hear from me by the end of that week…

28th January
2009
written by kaiyen

So if Murphy’s law states that “if it can go wrong, it will,” then is his cousin the one that states “if things could possibly be incredibly frustrating, they will be?”

There are a lot of conferences every year, for all kinds of fields.  In academia, there are quite a few, too, such that overlapping or back-to-back situations happen a lot.  On the other hand, for the most part, I notice that conferences of the same type don’t usually happen at the same time.  So technical conferences – how to manage a lab, stuff like that – are in early summer, then maybe late summer, then maybe in the fall.  Management conferences – the big one in Educause – is in the fall, as well.  But people who go to Educause are not usually the ones going to the technical conferences.  

However, right now I am facing a situation where the Law School Admissions Council – LSAC – has started a new, senior IT-related conference called ESCON (electronic services conference) and is actually significant subsidizing attendance.  It’s a big move on their part.  This is law school specific, though, yet it’s also leadership/management related.  Lots of admissions officers will be there, too, but part of the goal is to get the two groups together.

Now, that is from April 1-3.  Of course, as Murphy’s Cousin’s Law dictates, while usually management conferences are going to be spread out, the ACM SIGUCCS Spring Management Symposium, which is designed for those aspiring to be higher-level managers/CIOs/etc, runs from March 30-April 1.  I have applied for a grant to attend – again, very generous and I would be incredibly grateful if I were selected.  

But…c’mon.  Seriously?  One ends on April 1 and the other begins the same day?  And I don’t find out about the SIGUCCS grant until February but I book airfare for the ESCON now, which means I might leave SIGUCCS a day early, fly back to the San Francisco area, then basically meet my wife at the airport to change the contents of my luggage and jump on a plane to fly back to the eastern time zone for the ESCON.  And obviously if I get the grant I will go to both (I also have been wanting to go to the management symposium for a while now).

And yes, both are in a the eastern time zone, so I have to factor in minor jet lag, too.

Sigh.