IT Leadership

Governance for the New Guy

We spun up 3 major projects almost right off the bat following my arrival here at Muhlenberg. We were to replace the Student Information System (SIS) with an Enterprise Resource Planning (ERP) solution, the email system, and our Learning Management System (LMS). All 3 are pretty big, and any one would make for a busy year (the ERP in particular is a really huge, multi-year effort).

One of the first challenges I faced was how to build proper governance on these projects. Governance is a two-way street. It keeps people involved, it keeps the community informed, but it also asks the community for input, and is a way for the project to respond to such information and adjust. While I could certainly be such a conduit myself and I could use our existing faculty-based College Committee for Technology and Digital Learning (CCTDL), I did not feel this was the best approach so soon after starting here. I definitely wasn’t going to make any executive decisions or recommendations without a great deal of input, either. Who was I to say I “knew” what the college needed? That such and such product was the “right” one for Muhlenberg (I say this in general – that was I so new I was still getting lost on campus compounded the fact).

So I created committees. Lots of them.

For the LMS and email projects, they each had a committee that included staff from multiple different departments and faculty. The LMS one was, not surprisingly, a bit more heavy on the faculty side and there was an emphasis on instructional technologists from the staff population. The email project had a broader cross-section of the community. The former was chaired by a faculty member, and the latter by our Library Director, who had been involved in a similar project at another institution. CCTDL members sat on both committees.

I formed 3 separate committees for the ERP project alone. The Selection Committee was a small, 7-person group of key operational staff that could move quickly through the process of gathering requirements, developing a Request for Information (RFI), schedule demos and interact with the vendors. This group included representatives from Advancement, Admissions, the Registrar’s Office, the Office of Residential Services, the Library and the Controller’s Office, headed up by a project manager from OIT.

A Steering Committee “governed” the Selection Committee. Departmental directors and other key management staff made up this group. VP of HR, the Registrar, the Controller, the Director of Financial Aid, Athletic Director, Director of Campus Safety, and the AVP for Advancement were among those included in this group. It was much larger – 17 total members. A member of CCTDL was the faculty representative and the Dean of our Wescoe School chaired it.

The Steering Committee was charged with both making sure the Selection Committee was doing what was needed/headed in the right directions as well as making sure they would be successful. If a group was slow in getting requirements back to the Selection Committee, then the Steering Committee had the responsibility to get things back on track. At the same time, it was ultimately the responsibility of the Steering Committee to write up the final recommendation.

Finally, the Executive Committee was made up of the college Senior Staff (those that report to the President). This group held the ultimate decision-making authority. As part of the Executive Committee, I worked with other members to help push down various initiatives as well as make certain high level decisions. We concluded, for instance, that we would go with an “off the shelf” and “plain vanilla” installation, adapting our business processes to the product, rather than pursuing customization. We also discussed policy on cloud hosting and SaaS delivery options, for instance. It was critically important to have this kind of executive sponsorship – the entire senior staff.

With the exception of the Executive Committee for the ERP project, I have stepped completely away from all the other committees. I didn’t attend meetings, I didn’t ask for notes or report-ins, and I only occasionally checked-in on progress for general reasons, not to keep tabs. With the LMS and email committees, I met with them at least once for general guidelines. I did join in on a couple of joint Selection/Steering Committee meetings for the ERP project. But overall I’ve kept my distance. I think it was very important that I let the committees do their work.

While we haven’t completed everything yet (I used the past tense just to keep things consistent, but the ERP project in particular is still ongoing), the LMS launch has already gone well, and email is closing in with the start of the new year. ERP will be another 1-2 years. But what I’ve discovered is that, through judicious use of committees, you can get involvement of the community in ways that are impossible as an individual. It’s also brought legitimacy to the process in ways that I hadn’t even expected.

startups and higher ed IT

When we bought our house 4 years ago, we invested in some improvements. One was to lease a solar panels for our roof, from a quasi-startup that worked specifically in cities with sizable solar rebates.. At the time, the notion of leasing panels rather than buying and installing outright was pretty controversial. You didn’t own them, you didn’t get the rebate, and you are dependent on another company for maintenance, etc. The way I saw it, at the time, was that since I didn’t have $30,000 lying around for an install, not getting the rebate was moot. We would get a significant energy savings, so it seemed like a win-win. One of those situations where a solution that is sub-optimal to many was actually pretty okay for us.

I’ve had to revisit this decision recently, and it occurred to me that it’s not unlike the times I’ve worked with startups while here at Menlo. At face value, it seems really dangerous to work with a company that has 10 employees and is a year old. These companies can go through ups and downs. The obvious one is going out of business, but there can be severe changes in direction due to market forces, abrupt adjustments to planned features quarter by quarter, and a seeming rotating pool of sales folks (if they have a sales force at all). Ironically, the one consistent thing has been negotiating pricing – these companies want to get into the higher education market, so they are usually willing to talk until we find something mutually beneficial not only now but also for at least a few years down the road. I can’t exactly adopt something now at an affordable price then pay ten times that amount in year two.

At the same time, all institutions should be looking to take advantage of new technologies and solutions and especially here in Silicon Valley there are many options around if one has an open mind. We can do some really interesting things with security, management, and monitoring based just on some recent agreements that we’ve made. And not so long ago, when I was still at Santa Clara Law School, I was working with “start ups” like Box, which is definitely a lot more than a fledgling company now.

There are many reasons to pursue partnerships with startups. One of course is that we’re a small college, and they are flexible on terms because they want to get into our market. These are companies that are hungry and of course must create compelling solutions to problems. They are there to be a David to the existing Goliath, and to aim that sling-shot with great accuracy. We have come upon some truly stunning products from these companies that have greatly enhanced our abilities. Of course we have been careful in the solutions we’ve pursued. We need to consider the benefit from multiple angles (will this provide not only superior results and features, but also at a reduced management load?) and of course the risks. Sometimes we have to look at what stage of venture capital funding they are at and the valuation established by investors along with the technology itself.

In the end, though,what has mattered is having the open mind to consider such solutions and the organizational ability to take advantage of them. We must be open to the idea that, perhaps because of certain aspects unique to Menlo College, taking a calculated risk makes sense. Just as how leasing those panels, at that time, made sense for us in our particular situation. While we missed out on $10,000 in rebates, we never could have gotten them anyway, and we’re still getting an energy savings every month that far exceeds the lease payment we have to make. In the case of start-ups at Menlo, we may not get the benefits of working with a larger company with its substantial infrastructure, but we get at times a better (or better-fitting) solution with fewer strings attached.  Even if a company goes in a different direction with some tool we’ve adopted, as long as we’ve gotten what we need out of it and haven’t entangled our operations with the solution such that it’s a chore to undo, it’s probably been worth it. And we’ve shown again that we as an organization are agile enough to take a calculated risk here and there. In many ways I value that agility that we’ve developed and the mindset that propels it more than anything else.

In the long run, this agility plays out in more traditional ways. Some new next-generation security option comes up, and we’re able to act on it faster than one might expect. There might be a new technology that is actually quite hard to master, but because we have placed an emphasis on the ability to adapt and learn, we can go through that adoption process sooner than others and perhaps get ahead of the curve. We’ll make our mistakes, but perhaps we can rebound from those, too, without as much pain because we’re accustomed to such changes from taken risks. Or perhaps we’re just going through a “normal” infrastructure refresh that involves servers, storage, and our virtualization layer. Perhaps we’re able to handle that kind of stress better, too. No matter what, agility and a mindset that appreciates that flexibility is invaluable.

I’m not saying that I’m going to be reaching out to start-ups and taking risks – calculated or otherwise – at Muhlenberg. But I do hope we can achieve the kind of agility that we’ve found here at Menlo. And if we are able to buck a trend here and there and do something new and impressive, then that certainly wouldn’t hurt.

staying focused in the face of interpersonal adversity

There are certainly a lot of posts, articles, tweets, almost anything that deals with how to stay focused when there is some kind of adversity around.Hopefully you find something useful in what I”m providing.

I’ve been dealing with some interpersonal stuff at work lately. It’s a professional relationship, but the adversity is purely interpersonal. I don’t want to go into details, but I personally feel there have been some inaccurate portrayals, that we (the department) have been thrown under the bus a bit, and that all in all we’ve gotten a seriously short end of the stick. Maybe the nub. I’m not saying we are not without fault in this – it’s not a baseless set of comments. But it’s not a collaborative one, either.

My point is not to complain nor to vent. My point is about how and upon what to stay focused in such a situation. At least for me.

Own up to mistakes

Without a doubt, we’ve fallen flat on a few things. We missed one deadline several months ago by a few weeks, and it was a doozy of a deadline. There was miscommunication, work done in the wrong direction, a huge shift in direction and too much time taken to get something done. I’ve owned up to this. It is critical to accept blame where it is due. And of course I don’t mean in a way that generates a defensive stance, nor in a combative way. Just accept that things went wrong. No excuses (not because there aren’t good reasons, but because no one wants to hear them).

Don’t blanket accept blame, either

The first point doesn’t mean that you should just accept any negative comment that comes your way. Again, no reason to make it a confrontational situation. That’s counter productive. But accept fault for what is truly something you let fall through, but don’t just waffle under pressure on other points. But don’t get angry, either, in defending yourself. Keep it calm.

Write lots and lots of drafts. Then don’t send them and just see someone in person.

If a lot of the conversation (and misrepresentation) is done over email, don’t get sucked into that. This is a serious bad habit of mine, I admit. But whatever you do, write lots and lots of drafts of a reply before you even consider sending. Tone it down each time. Then, when you think you’re ready to send, don’t do it. Don’t send it. Just get up and walk over to that person’s office and have a face to face. Heed points 1 & 2- do’t go in there and just agree to whatever the other person says. Lay out your case, address, in a calm manner, what you agree with and don’t agree with. And then get out of there with your head held high.

You’re there for to provide solutions to users. Always remember that.

What matters, in the end, is that we are solution provision groups. Ideally, our relationships are collaborative and we’re about working together to find solutions that will help the institution in general. But at the very least we’re here to help. And never, ever, let interpersonal matters distract from this. Maybe a specific email on one topic is a bit heated, but all others are balanced and even, as they should be. All other interactions are about getting things done. Stay focused, and you’ll remember your real purpose.

Short and sweet. Well, short anyway. I leave it to you to decide if it has any sugar (worth).

 

on second thought…

Let’s be honest – I tend to get pretty introspective around the new year. Not in a dark way, but certainly many of my thoughts are dedicated to what I have done but many more of them are focused on what I have not accomplished, or sub-optimal results. It’s my nature to be more critical than not. I have spent a lot of energy the last year or so trying to celebrate the positives, and with my friends in the SIGUCCS tribe I have made a lot of progress, but I still have a long way to go. One thing the Tribe has helped me do, though, is to turn these critical moments and make them points for improvement or at least lessons learned rather than merely negatives with which to obsess. Considering I came to Menlo College with the fundamental goal to learn about being a CIO (and an institutional leader and manager, of course), let’s see how I’ve done.

The Best Advocate for You (and your school) is You

I like to work on relationships with our partners and even vendors. I like to cultivate connections with someone like our Value-Added Reseller (VAR) where they understand our needs and appreciate my expectations. I hope that vendors – actual manufacturers – will work with us on deals and pricing that show appreciation for our small institution and staff. I’ve also spent a lot of time building partnerships around campus, with other leaders, department heads, faculty and staff. In many ways I hope that these local relationships will yield strong voices of support. For example, I have tried to reach a point with a VAR where, when a project comes up, my priorities (do things the “right way,” and don’t presume that I want the easy way just because we’re small) are their priorities. I had begun to believe that vendors would go the extra mile for us on implementations and installations. I’d also started hoping that partners around campus would speak up for us when appropriate and helpful to all parties.

This was a stupid and naive approach.

At the end of the day, the only person (or group) that can effectively advocate for your vision, your priorities, and your needs is YOU (or your department). The only one that can always ask “wait, but what’s the right way to do that, not just the ‘small college’ way?” is going to be the person paying for those services. The only one that will even consistently notice that things have not been done that way is going to be you – outside groups will not be reliably pro-active to pursue the path that you prefer or even need. At the very least, one must be vigilant for any presumptions made and constantly verify that everyone is on the same page. You are the owner of your processes and solutions, plain and simple.

And regardless of how strong that relationship is with a partner on campus, even if all parties are seeking progress and there is no pettiness or personal gain issues at play, no one can truly take your place at the table. We all work hard to get to the table, and we need to be there when the questions come up.

This might seem pretty obvious, and in many ways I hope it is to most people. My point is a more nuanced one. We have faith in our efforts to form partnerships, and we pursue them so that we are working together more often than one for one another. We can and should still try to establish these relationships and invest the time needed to maintain them. But its naive to believe that you can let things just go on their own way without constantly checking on things. And remembering that at the end of the day – every day – you are the one that has to be the advocate for your institution’s or department’s needs.

Don’t Under-Manage your Projects. Ever.

You can never put too much effort into project management. Whether the project is small or big, oversight and management must be consistent and run from start to finish. Even informal projects need regular attention. More importantly, don’t get distracted. If you’re doing too many projects, then find a way to spread out the load. If you’re not a formal project manager and your “regular” work gets in the way, then keep yourself on target with the project first and manage your daily duties accordingly, or give that project to someone else.

This might seem easy for me to say – of course project management is important, and of course we all wish we can shift things around or give projects to others, but that’s just not realistic, right? The way I see it, it is my job, as a manger and leader, to help my team keep projects balanced, and to manage expectations of those around campus. Whether it’s our web applications developer, our social media & marketing manager, or our actual project manager, I am there to help things stay balanced. I am there to enable them to do their work, to be successful. I am there to run interference if one project has to bump another one off the list. That’s what I do, so that we can keep the project management capacity we need to keep things on track. Because, again, you can never have too much project management capacity. That means that there has to be someone constantly moving things around to keep capacity at a maximum.

And one other thing I learned – of all the folks on the team, I’m perhaps the one that has the hardest time shifting my attention away from my “regular” duties (like…supporting the team in their own project management needs). So I probably shouldn’t take on big projects. Definitely learned this in a rather rough way.

Take Your Professional Networks to the Next Level

I’m sure everyone puts a lot of energy into building professional networks. At conferences, through attendance at webinars, participating on mailing lists, or via some other means, we work hard to meet others and to establish at least some kind of meaningful bond that could bear fruit of some kind or another down the road. Whether it’s literally our LinkedIn network or merely and generically the network of people with whom we are linked, it is important that we put energy into development and maintenance.

However, if you can take it one step further – interaction at a human level – then things really change. This could be going out to dinner or for a drink with folks in your network – rather than just lunches (that occur during the business day anyway) – or, if people are remote, setting up a chat room for regular interaction. It could even still take place at a professional event, like a conference, but the interaction itself is more personal. Yes, I’m at the bar networking with others, but I’m there spending time on a human level with others as well. We aren’t just talking about the job, nor are we just making small talk. The difference can be very subtle – asking for professional advice is one thing. Being comfortable enough to bluntly complain about a situation in a candid way before asking for that advice is something deeper.

I’ve spent a lot of time networking at conferences the last several years, building my network. I’ve done just about every leadership and management program that EDUCAUSE offers, and I’ve become involved with SIGUCCS at an organizational level. After all this investment, it’s been just the last year or so that my interactions have gone to the more human level. Several of us meet online on a regular basis. Some of us are in an always-on chat room where we indeed do complain about things now and then, yet always also ask for advice. Some of us are even talking about going hiking or backpacking together at some point.

I can’t really quantify and can only vaguely qualify the impact of this difference. But it’s been meaningful, certainly, and people I considered peers became more than acquaintances and are now bona fide friends.

choosing to take the back seat

Last summer, I attended one of the EDUCAUSE Leadership Institutes.  I attended two different ones but I’m choosing not to identify which one this particular post pertains to.

One exercise that seems common among the various leadership programs from EDUCAUSE is that we write a card to ourselves.  Stuff we want to remind ourselves to do afterwards, or perhaps an important lesson we might forget that we need a reminder on.  One thing I did last time, for instance, was to design a staff retreat using certain principles we had learned.

In one of the two institutes I attended, we also had to write a card to the person sitting to our left.  Which meant that, 6 months later, I got a card with a suggestion from someone else, who had observed me during the week.  To paraphrase, this card said that I had

lots of great ideas and energy, but need to slow down and ask others for their opinions before speaking up.  You need to include others.  Only then would I be successful

To be honest, at first this was rather hard to take.  I felt a bit insulted and hurt; I wouldn’t be successful until I changed something?.  Of course, I soon realized that the person didn’t intend it in mean-spirited way at all, and that, in fact, he was right.  I do tend to let my enthusiasm and energy overwhelm the need to be thoughtful and inclusive.  Oddly enough, I also tend to be inclusive overall, wanting to keep everyone involved.  The two forces conflict, and the energy one sometimes wins out, such in this case.  This particular institute, I found myself on the minority of ideas a lot, and therefore caused some tension now and then.  I was frustrated by my group, overall, and even apologized to them in the end.  So yes, the part of me that gets overly excited to the point of excluding others became an issue.  This card reminded me of that.

Here I am today, at the EDUCAUSE Leading Change Institute, and I’m working hard at asking others for their opinions and letting others do the talking and presenting.  I’m not saying I’m doing a good job of it – but I am definitely letting others talk.  And I have to admit that it’s been really tough.  I want to say every idea I have, and I want to be the one to present it to the attendees.  I want everyone to know that I’m a presenter, comfortable talking with people, affable and funny.  I feel this especially at an event like this because I don’t know the other attendees very well.

But I know I need to let go, and I need to trust in others.  I have been trying really hard, with mixed success (as I was writing this sentence, I interrupted someone just out of enthusiasm.  Definitely still working on it).

It will be a good thing in the long run and I still have a ways to go.  I am determined to reel myself in for the rest of the week, and ask others for opinions and actively listen as much as possible.  I want to be thoughtful.

Not easy, but an important skill, without doubt.

embracing ignorance

I have been working on this post forever – well over a month.  My apologies.

Back in November, I was returning from a conference and was on the shuttle ride with two women from the UK.  They were here on business and had only 1.5 days to see San Francisco.  I gave some tips about what major sites to visit or, if they preferred the less crowded spots, some ways to finding the more hole-in-the-wall restaurants, etc.  Overall a good conversation.

At one point, though, I demonstrated a remarkable level of american-centric ignorance.  I mentioned how, at the conference, I was at the snack area between sessions and ran into someone from the UK who was confused about why there was honey available by the tea selection.  Showing some poor judgment, I presumed that while sugar and milk were staples of tea in the UK, honey must not be used at all.  I commented to my two shuttle-mates that this was a great example of differences in culture, even down to how we drink our tea.  I thought I was being pretty intelligent and insightful.

Of course, I was immediately informed that many, many British tea drinkers use honey, and that I just happened to be speaking with someone from a family that did not.  I felt rather foolish.  Why would everyone in the UK drink tea exactly the same way?  Why would I make such a presumption?  How could I let my ignorance rear its head so dramatically and embarrassingly?

As I slowly let myself off the hook for this, I realized that this was an important lesson and reminder about dealing with one’s ignorance.  In a social setting, one probably wants to avoid looking so poorly.  Best to know your stuff before opening your mouth.  But in a professional setting, where one is managing a disparate array of services, you have to embrace the fact that you will be relatively ignorant of at least some of those areas.  You have to push past that and still ask the questions that need to be asked, even if you look like an idiot.

As I’ve embarked on a few new projects lately, it’s become clear that I am really short on detailed knowledge ins some areas.  I’m not a systems person in general, have never managed anything beyond Windows Server 2000 in my life, and am a completely blank slate when it comes to networking.  It would be easy for me to either shy away from these topics or, at a bare minimum effort, just delegate it out to others and be hands-off.

The first scenario isn’t an option.  These are important topics (especially since networking goes out into security) and they cannot be ignored.  The second option – just letting others take care of things with a form of blind faith – is a truly bad idea because it involves completely detaching myself from potentially core operations (which, in turn, affect long-term strategy).

I have no desire to manage our network, but I’m going to ask questions.  I don’t want to know which Cisco switch is the right one, but I want to know why we want this feature vs. another.  And perhaps why we shouldn’t consider a different brand altogether.  I’m going to propose alternatives, even if those ideas are completely ludicrous and excellent examples of my lack of knowledge in the area.

I have to embrace my ignorance on these topics.  I have to embrace ignorance on a lot of topics.  At some point, if one continues to move up in an organization, he or she will be overseeing some area that is not within one’s expertise.  Ideally, you rely on your team to be the experts.  But our team is very small, and we honestly have no true networking staff available.  Even if we did have more staff, it would be unwise to completely disconnect merely because I don’t know the language.  Trust your team, but stay engaged.  Continue to ask others to explain concepts “as if you were a 4 year old.”  Read that article in the tech magazine and ask whether the big flash advertisement for some new product means anything.

We’re all basically ignorant about some topics.  At a dinner party, I’m not going to talk about firewalls and 802.11AC wireless (for more reasons than just my lack of networking knowledge…).  But at work, I’ll be the first to ask.  And the second, and the third, until someone has taken the time to explain to me to the level that I need to know.  I don’t need to know everything, but I can’t remain ignorant, either.

out with the old, in with the old

As a leader and manager, there are few times as trying on one’s…patience and personal confidence as when a project designed to improve operations is well planned, coordinated, and apparently implemented…and fails.  When one has taken a problem area, identified a solution, yet finds the institution in the same exact undesirable situation again and again.  I recently had this happen, and it has left me questioning everything from my core abilities to, at times, my sanity, it seemed.

I think that everyone hopes that, with a new year (in this case a new academic year), a new page will be turned, old problems will subside, and we will be faced only with new challenges.

I am certain that the 4-5 people that will read this are already laughing cynically at that statement.  We all wish this.  We never seem to get it.  And it’s not always that the problems are the same ones – sometimes it’s just the nature of the problem. Sadly, sometimes it is literally the exact same problem as a  year ago, with the exact same cause, and the exact same limitations in why we cannot find a better solution.  Budget constraints mean we can’t implement a new solution.  Staff issues (office politics?) stand in the way of change.  There simply isn’t a better way to get something done, within the nature of the current environment.

But occasionally there is an opportunity.  And hopefully that comes about because of good planning, strategic thinking, and months and months of wise decision-making, well-considered pros and cons, and decisive leadership (exaggeration added).  We do the right things over the summer (or even just “since the last time that process broke”).  We analyze the issues, suggest changes, get bids, and put in place a “fix.”  We use best practices.  We use proper project planning. And things still go awry.

These can be the times that are the most trying.  There are few things that can wear down someone involved in a project, from planner to implementer (and sometimes those are the same person…), than going through all the “right” steps only to have things unravel just like before.  To see an elegant fix turn out to be just another sub-optimal solution with as many problems as before. We all have our stories.  Perhaps one day we can all share them.

My next post, coming shortly, discusses the trials of trying to be a good communicator during such situations.  That’s part of good management and leadership, too.  Being present, visible, and taking responsibility.  But sometimes that means putting one’s self in the line of a lot of fire and flak just to keep a face to the organization, and that is certainly wearying, too.

Educause Institute – Learning Technology & General Leadership Programs

I have been working away at a post about my experience at the Educause Leadership Institute for weeks now.  In particular, I have been trying to contrast it to the Learning Technology Leadership Institute, a similar program from the same group, but with different faculty, curriculum, and type of attendees. I have realized that I just need to get my review out so here goes…

(more…)

Thoughts from the Educause Institute Leadership Program, volume 2

I’m a day late on this one, and I will in fat roll the last two days into just this one post.  Some of my thoughts have been formulating over a while anyway.  Plus, due to some technical issues, I am having trouble effectively composing posts from anywhere but our meeting room.  So it just hasn’t been easy.

One thing that has really impressed me, as my team has been working on our presentation to the “executive council” (played by our faculty) and while talking to other attendees, is that so many of the attendees have made these kinds of presentations already.  They have already been on the radar of their upper tiers of their organizations.  In a way, this means that this really isn’t all that hard of a task and that arguably attendees are far closer to being high-level leadership positions than perhaps I had anticipated.  I figured everyone would be high level directors, but the director of, say, all customer or systems support for some major state university is pretty high up there.  Even in terms of scope of work, what I do as CIO at Menlo College is not that far off from their work.  The only difference I’ve generally felt about my role has been its scope.  Not so much even by now, before the workshop has even ended.  It’s really impressive.

As far as the workshop itself, a few things have jumped out at me.  The first is that, while we did spend time talking to our executives as prep work so that we understood that level of leadership.  So that we could separate really high level strategy from the “tactical” work we do.  This was very useful, but we haven’t really returned to the strategic during the presentations as I would have expected.  We’ve talked a lot about regulations, about what we need to worry about as leaders, and even how to manage relationships, but that’s really it.

Without an explicit, ongoing emphasis on strategy, it’s really easy for us to all get “into the weeds” and talk tactics and specific solutions during our conversations. We get out of the strategic.  There are some important points here and there.  Looking at governance from a high level (see my note below about emphasis on size of institution making these solutions less relevant to me, however).  Examining IT security as part of a general campus risk security model is a powerful one.  But those were not really the core emphasis of some of these presentations.

Also, and I’m borrowing from another attendee here, there hasn’t been a lot of talk about how to maintain innovation while handling all these other issues.  Yes, we need to care about compliance and cyber-security, but what about our responsibility to foster creativity and the ability for faculty to be free to be innovative?

Finally, there is the empahsis on large institutions.  The faculty are all from fairly large ones, and I can understand a bias.  But while it’s always diffficult for me to take ideas and apply them to an institution of our size, all the talk about deputy CIOs, relying on large staff with multiple layers, etc makes it tougher than I had thought.  I’m getting stuff out but, in the case of governance, for instance, I was generally taking information from about 1/3 of any other institution’s solutions, with full knowledge that I hav no capacity to dfo the other 2/3s.  That is truly frustrating, and more of an effort than I had anticipated.

On a more…personal interaction note, I really need to learn to shut up more.  We all have great ideas, and they will conflict at times.  It’s not quite an issue of “put 7 leaders together on a team and it’s chaos,” but if some don’t step back, it is a lot of discussing and less productivity at times.  And I personally feel that I’ve been contributing less valuable content than others.  In no way has my group made me feel like an outsider or have they ostracized me in any way.  I do feel that my opinions are contrary to the general flow perhaps more often than not, but that itself doesn’t mean I should step back.  But for the sake of getting things done, I need to sit back more and just listen.  Of course, this is a lot easier when the overall work of the team is really excellent.

The jury is still out on whether this will be a good educational experience.  I’m learning more through direct conversations with the faculty than the curriculum, it seems,  We’ll see.

thoughts on the Educause Institute Leadership Program, volume 1

A while back, I did a series of relatively short posts on a leadership program I attended.  The Learning Technologies Leadership workshop offered by the Educause Institute.  Many may wonder why I am now reviewing this program again.  In fact, this is a different one.  One month later, I find myself back at the Hilton Orrington in Evanston, IL.  This time, it’s a general leadership program, with a very different crow.

Yesterday was just a half day so my observations are more about the differences in the crowd.  I don’t think I know enough to make comments on the curriculum.  I can certainly talk about my trepidation prior to the start of the session.

Before things commenced I was very concerned about how I’d fit in.  Would everyone be from really big universities?  Even against a director, my experience at such a small college might not translate.  I might be this useless appendage.  I’d still learn just from hearing everyone’s experience but I want to contribute.

Fortunately,  my fears did not come true.  While I am a bit surprised by the number of folks that work in administrative systems (rather than customer-facing programs), but overall there is a lot of diversity, in jobs, age, years in job, and institution (or department).  I think things will work out.  More on that as the week goes by.

The team project, which was a linchpin of the LTL program, is handled a bit differently. I ‘m sure the actual presentation will be similar an the team dynamics will still be key.  But we heard about the team topics last night – we had to pick two, and therefore had no idea what we’d get.  And for me, this is especially harrowing because I don’t know if I’d end up doing a potentially big topic – but one that interests me – with really big institutions that just won’t speak on the same terms as me.

Because this is a group that are aspiring CIOs, we did spend a big section yesterday talking about the changing role.  On the one hand, this is a critically important topic and discussion (one might think differently based on my recent post about an article in Educauseu Review, but that’s because I felt that was intended for other CIOs, not aspiring ones).  On the other, I felt that we jumped a bit too far into the changing role.  We discussed the changed role – what it is now, under the presumption that we had preconceived notions.  Maybe we did.  Just an observation.

Overall, while I had a pretty full afternoon, it was not as intense as the first day of the LTL.  But I am perhaps more excited overall, and look forward to the week.