Culture • Innovation • Leadership

IT Leaders as Catalysts

IT Leaders as Catalysts

This is an audio conversation from the CIO Talk Network podcast. The timestamps in the chapters and transcript below refer to the audio recording.

About this conversation

A CIO Talk Network conversation with Dr. Jonathan Vester (Nash Community College), hosted by Sanjog Aul.

What the conversation established

The conversation established that an IT leader becomes a catalyst by building trust across the organization rather than relying on one personable leader. Dr. Jonathan Vester of Nash Community College said he hires technicians who are good ambassadors so users see the whole department, not just him, and he celebrates team members publicly to push credit down. He argued that early, low-risk wins such as a uniform single sign-on build the trust needed for tougher work, and that a learning organization comes from planting seeds, like sharing a TED talk with C-level peers, so the business generates its own ideas. He gives his team room to fail early, often, and cheaply, keeps the sunk cost fallacy posted on the office wall, and said about 90 percent of the projects his team kicks off are thoroughly vetted. He also cautioned that saying yes to everything causes initiative fatigue, so a catalyst leader must get over the ego of self and be willing to say no.

Host Sanjog Aul talks with Dr. Jonathan Vester, Vice President of Technology and Chief Information Officer at Nash Community College, about how IT leaders can become catalysts rather than order-taking enablers. Vester describes humanizing the IT department so technicians act as ambassadors and the business learns to trust his team, not just him. He explains earning that latitude through small early wins, giving his team room to fail early, often, and cheaply, and planning projects until about 90 percent of them are thoroughly vetted. Aul presses on how a CIO can think like a CEO, paint a vision, and spark ideas so the business brings them back to IT.

Contributors

  • Dr. Jonathan Vester, Vice President of Technology and Chief Information Officer, Nash Community College

Host: Sanjog Aul, Founder and Host, CIO Talk Network

On this page: Key takeaways · Chapters · Explore more · Transcript

Key takeaways

  • Dr. Jonathan Vester, CIO at Nash Community College, argues that IT leaders stay stuck as enablers because business leaders own their processes and guard their silos, and because a CIO’s time gets consumed jumping from meeting to meeting. He says becoming a catalyst means getting involved in the actual work, not just supervising it.
  • Dr. Jonathan Vester of Nash Community College says the way to disarm territorial business leaders is to humanize the IT department. He hires technicians who are personable ambassadors so users and other departments trust the team to help rather than set them up for failure.
  • Dr. Jonathan Vester, CIO at Nash Community College, warns new technology leaders against bold early projects and recommends small incremental wins such as a uniform single sign-on. He says those easy-for-IT but visible changes build the trust that earns a leader the next, tougher project.
  • Dr. Jonathan Vester of Nash Community College gives his team room to fail early, often, and cheaply, and keeps the sunk cost fallacy posted on the office wall. He says a culture where it is safe to identify problems is what seeds and sustains innovation across the college.
  • Dr. Jonathan Vester, CIO at Nash Community College, plants seeds with C-level peers, bringing an article or a TED talk to weekly meetings so colleagues generate their own technology ideas. He says about 90 percent of the projects his team kicks off are thoroughly vetted before they start.
  • Dr. Jonathan Vester of Nash Community College cautions that saying yes to every request creates initiative fatigue and burns out IT staff. He says a catalyst CIO must get over the ego of self, push back, and be willing to say no to protect the team’s capacity.

Chapters

  • 0:00 Introduction: IT leaders as catalysts not enablers
  • 2:48 Why business ownership and time block the shift
  • 5:35 Humanizing IT to earn business trust
  • 9:04 Changing IT’s perception beyond one person
  • 11:11 Building team culture and small early wins
  • 16:12 Escaping break-fix to make time to lead
  • 24:35 Thinking like a CEO and sharing a vision
  • 29:30 Reaching across the organization through strategic planning
  • 36:16 Sparking ideas so the business brings them in
  • 41:52 The Steve Jobs question on what is possible
  • 44:58 Sustaining momentum and avoiding initiative fatigue
  • 49:08 Avoiding overcapacity and learning to say no

Explore more

Transcript

Introduction: IT leaders as catalysts not enablers 0:00

Sanjog Aul [00:00:22]:
And the topic for today is IT leaders as catalysts. So when we look at the organizations all over and globally, we see IT leaders playing the role, a very important role for how an organization grows and becomes profitable and becomes innovative. That’s great, but then most of the times, IT leaders would self, not exactly self inflict, but they will assume the role of an enabler, more taking not exactly orders, but kind of waiting for business to tell this is what we need to accomplish, and then they would kick it off. What we wanted to explore is what about taking IT leaders and helping elevate them or they themselves elevate them so that they play the role of a catalyst where they go and energize the whole organization, the business unit leaders, the staff, and not just their own staff, the business users, and make sure that everything is moving forward, almost playing the role of a CEO or other leader and not just an enabler. What does it take? So to discuss that, I have Dr. Jonathan Vester, who’s the Vice President of Technology and Chief Information Officer with Nash Community College. Hey, Jonathan. How are you?

Dr. Jonathan Vester [00:01:50]:
I’m doing great. Thanks.

Sanjog Aul [00:01:52]:
So, Jonathan, you heard what we are trying to do here. So let’s first of all talk about the current way IT leaders typically front end. They talk about we are enablers and if that’s the mindset then they would enable and that’s where they will feel they’ll be evaluated and that’s where they would stop. I’m not saying everyone does it, but that’s what the majority has been doing lately. What do you think is preventing them from actually jumping forward and saying, folks, that’s boring. Yeah. I can enable left hand’s eyes closed in my sleep. Let’s go to the next level. Let’s become catalyst. Let’s be instrumental in accelerating growth and innovation. Why are we not doing it and what’s missing?

Why business ownership and time block the shift 2:48

Dr. Jonathan Vester [00:02:48]:
I think one of the things that I have observed is ownership of the business processes can be one of the many, I think, barriers to overcome. When you get to the C-suite, you do have people who have been very competitive usually to get to that part of the organization, and so they have a lot of ownership and a lot of their personality wrapped up into their operations, and so when someone like myself comes in and says there is an idea that I have or my team or your team even has come to me about an idea, and I wanna help you do that, they can see that as a threat because it’s now you’re encroaching on their silo in the organization. So that’s one of the key things is to have an organizational culture that accepts that you can have cross pollination of ideas and it’d be okay, and that should be something that’s promoted within the organization. On top of that, I think that just the general time of the CIO is at a premium. We usually are, even when we try to innovate, we’re doing many roles at one time, and so having the opportunity to be that catalyst, which means that you are engaged in whatever initiative it is or project it is at a level that you’re not just supervising human resources, but you’re actually getting involved in the process. That takes the time that usually we don’t have because we’re jumping from meeting to meeting and really not doing any other work than just scheduling the next meeting.

Sanjog Aul [00:04:22]:
So the two areas let’s kinda dig deeper and at least start with the first one, the one which you mentioned, where the business unit leaders are territorial almost. Right? We are saying that they are territorial or they fall in love with the way they run it, and anything which is introduced or suggested to them, they see that as threat. So is this something which is global, or is it a function of how we present a case to them so that they see it as a threat? Are we essentially labeling any business unit leader as someone who has low self esteem that anyone else who’s gonna come and give them idea is actually coming across as someone who’s gonna be threat and is gonna take the job away? If that’s the case, if at all that the case, isn’t the onus on the leader, the IT leader him or herself, to not come across as a threat and innovate and evolve their approach to how they build relationship with that business user so they see you as a friend first and then someone who is a CIO or an IT leader?

Humanizing IT to earn business trust 5:35

Dr. Jonathan Vester [00:05:35]:
Absolutely. One of the things that I have striven to do within my department and then have that flow outward is the humanizing of IT, the IT department in general. A lot of times we can be pigeonholed into being just these very nearly focused, narrow skill set kind of people, and we don’t have that personalization that is I think required to have the communication across the organization, and so one of the things that I have found to be successful over the years is to take my technicians and make sure that I have technicians that are personable, and that can be good ambassadors for my department within the organization. Because when the users see the technician, that’s the person they see the most. That’s the interface of the department by and large. If they feel as though they are welcome and open to their ideas and they don’t just treat them as a user, that begins this culture pushing outward to be more acceptable to an idea coming from my department or to come to my department to ask for help. For example, this business office, which is another closed vacuum usually inside the organization, if they see that we welcome their ideas and they can trust our opinions on things, they can trust that we’re not gonna set them up for failure. They’re more willing because they’ve worked with our technicians and with our programmers to come to me from the manager side of the house, not the CFO, but the manager of that department, and say, I’ve got an idea. Can you help me champion this? Because my boss, the CFO, doesn’t like to have ideas thrown at her that are gonna be a challenge to her authority, and so over the years, that’s what I have, fortunately for me, successfully done at my college right now is show that we can work together. No one needs to feel threatened because, one, I don’t wanna be the CFO by no means, but also that I can take the skill set and talent that’s in my department, and they can be used to make other departments better, not to show that my department is better than yours, but I can make your department better by working in conjunction with mine, and over the years, that has worked really well. We have a lot of people that stop by the office now with ideas or they’ve seen something at a conference, and they say, can we do this here? Or how can we do something similar here? And that’s a great thing to have because in the past and other places that I’ve been, it was just kept to themselves, and years down the road, you’ll hear, well, at a conference, I saw that, and I thought that we might do it, but I didn’t think that you all would be interested in anything like that. You were just too busy. Having that relationship become part of that culture inside the organization, that’s what I think one of the catalysts that the CIO can do because we do operate across all parts of the organization, and so if again, if we can be good ambassadors for the intelligent use of technology and the systems that we have in place or ones that are available to us, I have seen that the users at large and the other C-suite individuals look to us as a resource for that change and not as a burden to them that they’re gonna have to overcome.

Changing IT’s perception beyond one person 9:04

Sanjog Aul [00:09:04]:
So when you discussed relationship, you did, of course, say that, okay, if I go as Jonathan going to a business counterpart and take them into confidence and build relationships, that’s where you start getting them to thaw a little bit and are more acceptable to the ideas. Similarly, people who report to you, who go to their corresponding counterparts in business, if they could do the same, then that relationship or the possibility of IT becoming a catalyst will happen. Now what this strategy is doing, and I’m just trying to play devil’s advocate, is putting the onus on that individual. So if Jonathan is a good people person or those three people who report to you are good people person, they have that personality that they are very personable as you said, then they will move it forward. Now what you’re doing is you’re fighting against a perception that IT folks are just geeks and they are not personable etcetera etcetera. So is there a possibility of doing a parallel or putting in a parallel effort to also changing the perception which is not connected? So IT should not be Jonathan. IT should be a department. How do you change the perception so that you have less of an uphill battle? Because as soon as you approach them, first they don’t know Jonathan. They know this person belongs to IT. They look at your role, but if that perception was a little more positive and looked at, okay, IT always is there to help me, then you would not have that uphill battle. That’s number one. Number two, it’ll not be as dependent on Jonathan’s propensity and approach and attitude and the talent to be personable. So if anybody else comes tomorrow, you’ll win a lottery. It should not be dependent. IT’s perception on what you get done and IT to become a catalyst should not be dependent on Jonathan. I’m laying this out for you and then yeah, so if you had to do this, then what’s holding us back? Why can’t we work on the perception?

Building team culture and small early wins 11:11

Dr. Jonathan Vester [00:11:11]:
I do work on that perception personally. One of the ways that I do that is through my hiring of my employees, and to build a culture through the employees for the users to look to them as the sum total of the department, and I try very hard actually to fight the idea that my employees are an extension of myself. That’s something that I think that many CEOs, particularly I think new CEOs have that problem of wanting to have the individuals in the department of IT be extensions of their abilities and what they can do, and so, I do assign tasks to my employees. When someone comes to me and says, hey. I want to do x, y, and z. I will say, you need to talk to someone in systems or someone on operations side, and not I’ll take care of that for you because I take great pride in the talent pool that I have, and I’m very vocal about that. When we have successes, you know, I am sure that I celebrate successes publicly with those in the department that need the credit. That’s something that we again, that’s the ego part that you had to let go of from leadership. You had to separate yourself from that ego too, and yes, it’s great to have people give you accolades, but it’s better from a leadership standpoint for you to push that down because you’ve already achieved great things as your CEO, and you’ve been placed in the right position, then you’ve already achieved enough to where you want to spread that back out, and I think that altruistic attitude is one of the things that the organization proper picks up on. When you say, you know, this is not me doing this. This is Brian doing this, or this is whomever doing this. When they see you do that and distribute the responsibility and the good and the bad, both the successes and failures, that becomes part of that culture of it’s not just me, and I think that one of the ways that you can also do that is when you do come in right off the street, as your first month or first quarter as CEO, don’t try to make very bold moves. Don’t think of very bold projects even if those are ones that have been sitting on the shelf from your predecessor. I think small incremental successes builds that respect and that trust in your ability and your ability to lead your team. Now this isn’t and I wouldn’t say this as take on something that’s just very, very simple, to you, but you can find projects that are easy for your team to accomplish, but from the outside user standpoint, it’s revolutionary. You know, things like if you have not implemented Active Directory and have a uniform single sign-on. Well, those things can really ease the burden off of workload on your users. Now, they don’t understand it. Once you set that up and it’s cared for and maintained correctly, it’s just gonna be there forever, but that’s a big jump in the right direction of, you know, Jonathan came on board. He appraised what our needs were, he talked to us, and one of the pain points was that we had all these different systems, and he helped us uniform that. So if he can do that kind of project and says he can do it and do it on the correct timeline, then maybe I can trust him and his team to do the next thing, and then you ease into the tougher projects, but you demonstrate that you can trust the leadership coming out of my office, but also trust the abilities of the team, and that’s how you redistribute not just the labor, but also the trust and consensus across the organization that it’s not just one guy in that office. It’s this team that’s being led by that guy in the office.

Sanjog Aul [00:15:14]:
The other thing which you mentioned was we don’t have the time. Right? So let’s take a step back and think about what do we not have the time for? Are we too busy saying yes to any and every project that comes our way so we are ripping at our seams and we’re not doing the right thing? It’s like Mark Twain said, I did not have the time to write a shorter letter so I wrote a longer one. So where are we? My question is when you know that your effectiveness, your team’s effectiveness, the quality of the projects, and your ability to increase your perception and everything else will only depend and you will be able to get to a much better elevated state of influence is when you spend time on these things, but if you don’t spend time on these things and we take glory in just finishing another project, do you think we will ever change the status we are in, which is often enabler, often order taker?

Escaping break-fix to make time to lead 16:12

Dr. Jonathan Vester [00:16:12]:
Right, and you get into the mindset of break-fix, which is a really bad place to be from an IT department standpoint. You should be looking to do things in a better format so that you’re not always doing break-fix it all. Eventually, even from my desk, I get wrapped up in that is that things aren’t working where they should, and I’m having to get into the weeds of fixing people’s problems instead of looking at ways to have avoided those or mitigated those problems from the get go. One of those things, but the time, I think that time is just a resource. Just from the standpoint of being a lifelong learner in technology and when you become a CIO, I think that you need to expand your interest into things like organizational behavior. That’s something that’s an interest of mine, but it’s also helped me immensely in understanding how departments and people work together or don’t work together, or what’s been tried before and what’s failed. Expanding your interest in areas not just solely on technology. Now, I would definitely say if you can get out to conferences that are gonna challenge the way you think about business operations or technologies that you may have heard a little bit about that may have some influence on your business operations. If you can get to those, get out there and allow yourself to think a little freer so that when you come back, you can show that with your team and with the organization. That’s something that I think that’s missing a lot of times. So at least from my standpoint, I don’t have time to go to week-long conferences. That’s just not something that’s on my radar, but what I do try to do, that list is when there are projects that I know that I can have a positive influence on and can contribute, I dedicate myself to the team project and I’m there. Having a leader that’s not present, but it’s supposed to be present, can be detrimental, I think, to the team dynamic, and what I have seen in the past is if you jump into a project and say, hey. I’m gonna be here with these weekly meetings, and I’m gonna help you develop x y z, and you don’t, then you begin to build a little bit of resentment from the team of them not trusting you, and so if that happens, then you’ve kinda poisoned the water there on trying to build a culture of camaraderie and of trust and respect because your team if your team can’t trust you, they’re gonna be more than likely, the opposite of advocates when it comes to the public, or the user side. Describing the department and saying, well, my boss, you know, he tries to do things, but he never delivers or he’s never there, when we need him. Those things can really hurt the change you try to affect later on. So do I think that when you have the time, to help bake into the corporate culture that reciprocal respect, not only within your department, but then, going outside of the department. That’s gonna help. I really think help you find time to assign tasks to your high flyers in the department. You look at succession planning. That’s one of the things that I try to do a lot of is to find projects that maybe the staff that don’t really have an idea that they can do these things. Give them a task to do that that I feel as though they can accomplish. If they can’t accomplish, I need to be ready to step in and help them and mentor them through the process so that the next time that comes around or something similar comes around, they have a better self perception of their ability to do it, and again, that’s part of that culture, and that culture feeds upon itself in a positive way, and as other departments see that mentoring work, you will usually see other C-level individuals ask you how do you do that? I have that here. How do you mentor people? What are your tips on how to mentor people? Because I’ve been very fortunate in that my team has come with me on this journey from just being a break-fix IT shop to a source for creativity and innovation and pushing the institution forward because they know they had that latitude. I give my team lots of room to fail. I follow the old adage of fail early, fail often, and fail cheaply. That’s when my team knows I will support them as long as they let me know when it’s starting to go sideways. I’ll help them pull back out. There’s a fallacy, a logical fallacy called the sunk cost fallacy. I’m not sure if you’ve heard about this or not, but it’s basically when you refuse to change what you’re doing because you’ve got a lot of time and really a lot of ego wrapped up into the creation of the thing, and so you don’t back out of it. I actually have this posted on the wall in our office for the team to be reminded of is that you can step out of a project at any time, but don’t let that project or whatever it is that you’re doing, it’s something we’ve been doing forever. Don’t let that stand if you did that. If we change, things will be better in the long run. So we have the ability up here to see things in that fashion, and that’s also something that I refer to when I talk to other executives here at the college or other users is that if you see a problem, it’s okay to identify it. You’re not gonna be punished for it, and that begins that culture of it’s okay to be open and honest about things that you see because when they see the negative things, it also lends them to seeing things that can be changed, and so that’s how you get yourself involved in that innovation is that they know that you’re not gonna scold them for trying to do something that fails because we are all about, do you have an idea? Let’s try it out and test it, and we know that pretty much everything that we do now in any business, any modern business is gonna be related to technology. It is gonna be software in the back end. It’s gonna be infrastructure to get one device talk to another. It’s gonna be some kind of software that talks around in via email or some kind of thing. So there are very few projects that don’t involve the IT department, and so they know that we’re not gonna let them fail later on because our mantra is gonna monitor what you’re doing, understand what you’re doing, and then kick the project off, and make sure that if it starts to go sideways, we’re gonna pull back and say, wait. Let’s stop. Retool. It’s okay to get this wrong the first time. Just go back at it, and that’s how that innovative culture gets to be seeded and gets to be sustained is when you know that it’s okay if you fail because the IT shop’s gonna work until we get it right with you. If we’ve already gone through the planning process and worked through the entirety of the workflow, tried to troubleshoot what might go wrong, and we’ve already accommodated for that, more likely than not, I’d say that about 90% of the projects that we kick off up here now have been thoroughly vetted through the department and through the department that’s asked us to help them, and so I have to say we have very high success on the projects that we do take on because we are, and so my peers would say that I’m a little bit too much of a stickler for planning but we plan things until it’s very hard for it to get outside of that project plan, and that’s again one of those things about innovation that yes it’s free flowing sometimes, but when it comes to getting it done, you have to kick back into the old business model of plan, budget, do, monitor. Because you can’t just have a blank check of funds and time and resources to get innovation done. You have to demonstrate that it’s not gonna be this sinkhole of time and effort and money and other resources.

Thinking like a CEO and sharing a vision 24:35

Sanjog Aul [00:24:35]:
So you had a very thorough response to my question. Now the one sentiment I see prevailing throughout is we are somewhere looking at leadership or calling it or perceiving it as synonymous to getting projects done. Whereas, if you want to energize people, they don’t think projects. They think what’s ahead, how we become better as a business, and here, it’s not about just energizing your own people because they might see you’ll see twinkle in their eyes when you show them a cool little infrastructure project you’re gonna kick off. Here, we’re talking about influencing the rest of the organization. So think like a CEO. A CEO and CIOs are not much different in terms of their knowledge and understanding of how the whole business works by design. Right? But then a CEO is not thinking a project. The person is thinking where are we today in context of where the market is going and where we could be going or we could lead the market and we start painting a vision, sharing that vision and getting people to come back to us with ideas, and there is energy created. What would it take for CIO to start adopting that aspect and they could start leading from the middle, they could wear a CEO’s approach, projects will anyways get done. Right? There will be mess or there will be, you know, great projects. Those will keep happening. That’s business as usual, but can CIOs abstract themselves from that the grind that we’re going through and take themselves or elevate themselves as a CEO? And if yes, what would it take? What would it take for them to not 100% sever their ties with the projects, but kind of step above those projects to see there is far more value to be created by being in the role of CIO.

Sanjog Aul [00:27:48]:
So, Jonathan, we would rather have a CIO, especially that top role, be someone who is not working or coming first thing in the morning and looking at their project list and say, what problem do I need to solve today? Or what mess do I need to help the business get over? Then we come across and he’s rightly said that labels you as someone who’s a break-fix, but even when we talk about us getting a seat at the table or we talk about things which are more to get the permission, if you will, to think strategically. We keep fighting a battle and try to feel as if we are tired warriors. What would it take for you to not seek permission and say I am going to see what it takes to energize people, to influence people? Sometimes it’s better to ask for forgiveness than for permission, but are CIOs and IT leaders playing safe and that’s why they don’t do it and that’s why they don’t take risks in giving some revolutionary ideas or doing things which will wow the CEOs and executive management and the board, and then the others will see this person has the chops and they will be influenced and will be ready to be led by the CIO. You see where I’m going? This is a totally different level at which a leader, an IT leader can play, but they don’t usually do that. What holds us back? And how do you fix it?

Reaching across the organization through strategic planning 29:30

Dr. Jonathan Vester [00:29:30]:
I think one of the things that would hold you back in that regard is if you have an organizational culture that allows for you to reach out, and I think demonstrating your ability to think beyond your department is one of the ways in which you do that, which you do demonstrate competency, and then you can reach for that next goal or that next vision that you see from the organizational level, which you should be getting from being involved in things like your strategic planning. Strategic planning is a very big thing when it comes to knowing where the organization wants to go. So if you know the strategy for getting to the vision that’s been set up by the CEO or by the controlling board, if you know what that is, you already understand the inner workings of the organization, because your group is thoroughly baked into everything that’s going on. I think that developing the ability to see what you’re doing and how it impacts the success of the organization, and then stepping out of that, you have to know what’s the tolerance level when it comes to the strategic plan. So if we have a list of things that we know that the organization wants to do, that they may not be related to IT, but we know that we can have a piece of that in some regard. I think when you reach out to either other C-level employees or if you can just start something up from your own office reaching across the organization, you begin to become a resource for the innovation. Again, not just in your department, but when someone has a reach, they can stretch their goals and their thoughts about what the organization can do, and then you become the resource and the champion for projects that may not be IT related, but in the end, you know it’s gonna land in your department. So having people acknowledge your ability to think about things in a large scope way by interconnectivity of individual departments or multiple departments across the organization, I think that’s how we demonstrate our ability and then you continue to grow upon that success. So success leads to differences and new successes. I think that taking a measured approach early on is a better idea than jumping in to a large scale organization wide strategic plan or change, but I think that when you demonstrate the ability to coordinate different parts of the organization, you do step into that CEO realm of things, and as long as your CEO is okay with you not usurping their power, but by sharing their power, which is what we should be doing inside our own departments, that culture lends itself to being one of change and innovation, and then to get your other point about us taking time to do that and not trying to do break-fix, I think that when you develop inside of your department that same kind of culture of it’s okay for my employees to do things that may not be what I want them to be doing all the time. They may decide to step out and try something new. Me being okay with that and rewarding that and giving that praise out, which is what I’d hope that my CEO would be doing to me. Me pushing that culture down from within my department helps me be able to say, okay. I’ve got this idea. I’m gonna give this to you three. I want you to do it. Let me know how it works out. You know, I had to appraise the ability of those people to do it, and to carry it forward and to integrate it across the organization, but they know that if something does need my assistance or my opinion, they can come to me and I not scold them for not being able to do it on their own. So it’s a culture of being able to let go and being okay with some solution, if they come up with it the same way that if I have an idea that can help, say, our business office or our print shop do something different, meeting with them directly and saying, I got this idea. Let’s try this and then present it to the CFO as either a completed initiative that’s already been in play and they just didn’t know it was in play or as we’re gonna take this off, we’ll make you aware of it. Here’s the benefit. Here’s the why of this change, and then letting them see that it’s not me trying to step into their role as leading the print shop or the business office. It’s that I am their partner in making things better.

Sanjog Aul [00:34:17]:
So based on what you said, you will clean the house inside IT, feel confident that if you do go out and put your neck out and say, okay, we can do A B C or I would like to share some innovation and it to your parallel, if they do say yes, your people can deliver. Am I correct?

Dr. Jonathan Vester [00:34:36]:
Right, and that’s the same thing with going to the other parts of the organization. It would not be me taking on the change in the business office or in their processes. It would be me going to them and say, my team would like to assist you with this idea. What do you think? And then handing that off to my team members, not it would not be me going meeting with the business office every week for an update meeting. I would allow my group to take care of that project to help the business office. In that way, I’m building that relationship we talked about earlier about them being able to trust the judgment and the expertise inside the department and it not be just me, not just Jonathan as the focal point of all things, integration wise. There is this group out there inside the organization called technology that will help me do things. Now they may bounce things off of me, and it’s great for the CIO, and I can’t stress this enough, to be a trusted sounding board that will give you clear and concise but also very candid responses to the questions or to your ideas, but to be able to trust in that and that I’m not gonna knock you down or make you leave my office if it’s something that doesn’t strike the interest of my core interest of the technology being a technologist. That’s one of those things again that the culture has to be accepting to those kind of changes and those kind of initiatives that are coming from the outside of the departments.

Sparking ideas so the business brings them in 36:16

Sanjog Aul [00:36:16]:
Let me share another take on this and tell me if that’s possible. One is where you take the ideas to the business leaders and tell me what you think and then they tell you whether they want it or not want it and then you take two more ideas. Another is to create excitement by communicating your vision from your position as a CIO but thinking like a CEO and say, this is what is happening around the world today and if this was tried in our area, then these are the possibilities and we can go beyond what we are doing today, and you do it in different ways and what you do then is you spark interest. You create energy among the business leaders and the business users where they start coming up with ideas and since you would have already sparked those ideas in the direction where they know they will need to use technology, then you will get the inbound requests to say, can you guys do this with us? Now what you’ve done here is different than you taking the idea from your side whereas if the business is energized and they bring the ideas, the adoption is automatic because it was business’s idea and you are able to then help refine it and you don’t stop after the three ideas which were created by business and you start getting busy with the execution, for that you will have the team and business will give you the funds to scale your team, but then you can keep going at it. You keep creating energies, you keep painting vision, you keep giving them sparks of innovation or at least create those energy and the sparks so that innovation is initiated from the business side. Wouldn’t that put IT leaders in truly quote unquote a catalyst role?

Dr. Jonathan Vester [00:38:16]:
Absolutely, and that’s something that we work on here, which is to look for the small seeds that can be used in different and novel ways. When I meet with the other C-level peers once a week, I’d actually had that as part of my usual. At least 1 time a month, when we meet weekly, I try to bring something that’s an interesting thing that you know did you know or have you seen or here’s this article, or here’s a link to a TED talk that I’m sending you or something like that that I know that they should be aware of, but they’re probably not aware of, and then in that same regard, give them context of this is similar to what we do here in this way, but different, and what do you think? I don’t force that upon them. I plant that seed of here are these tools that are out there that you may or may not be aware of. What do you think? And I try to push that forward on that lifelong learning aspect of what we should be doing as C-level executives. If we should be one expert in our field, we should always have an interest in what we’re doing career-wise, and so we should want to learn more about it, but we should also be in ourselves integrators of experiences that we’ve had across our career and taking the bat and integrating that also with what we know the organization can do in its capacity. One of the things that I’ve had to temper some of my peers to in doing is that they don’t understand what the capacity of the organization actually is because they only operate in one silo of the college, and so they don’t understand or have an appreciation for what other parts of the organization are doing, and so they have a very interesting idea, but they need context, and so being able to be a resource to apply context to things allows me to be involved at the ground floor of idea making, but also I usually challenge them if it won’t work this way, what about X, Y, or Z? What do you think about that? And then they’ll come back to me later, and that’s one of those things about creating that culture is I give them a large set of tools, a large group of opportunities that they could use, but I’m not prescriptive about what I want them to do. If it’s something now that I feel very passionate about, I may get prescriptive and say we’re gonna do this thing and you’ll see the benefit later on, but by and large, I want my organization proper to be a learning organization, and so by me wanting to do that, I have to make available to them resources and openings for them to have their own ideas, to let them percolate within themselves and then bring me not a fully formed notion of what we can do different, but a better idea of what’s feasible and possible to do with the resources that we have. That is something that I do try to do, as often as I can, which is demonstrate that there are a lot of opportunities to do new and interesting things, particularly with leveraging technology to do it, that my peers probably aren’t making it having that put on the radar.

The Steve Jobs question on what is possible 41:52

Sanjog Aul [00:41:52]:
Imagine Steve Jobs, who’s no longer with us, had gone to his people and said, you know what, there is a possibility of us putting something on a flat, thin, light piece of computing device, and it might be useful, what do you think? Do you think we would have seen iPad? The point I’m trying to make is sometimes the CXOs, the other enterprise leaders, if we give them a white sheet of paper showing them some tools, some comparable, and yes, we want them to think, and yes, we want them to have give the ideas, but could do you think IT leaders play Steve Jobs where they say what is possible and then they could say we they are not saying that only ideas that I’m bringing are the ones you should look at, but at least that’s what the word catalyst is. You start the juices flowing by sharing with them what’s possible. What holds us back from that?

Dr. Jonathan Vester [00:42:56]:
I think that given the Steve Jobs example, I think that they would maybe come to terms with what’s possible with that idea, but it would not have been at the same rate and scale that we saw because he did take control of a lot of those things because he had the ideas thoroughly crystallized in his head of what he wanted to see, and having the benefit of that from the CIO standpoint, that is an area where we sometimes have to force what we know upon the organization, but I do think that making it evident that we are partners in new ideas, and we are willing to take that leap with you, that’s something that’s a benefit to the whole organization, and I think even if it’s not evident during the time, at least I do exercise my influence and knowledge of certain things along the way. I may not express it explicitly, but if I see something that’s an opportunity during a process that I know needs to change or that it will help us later on, I will take control of what I can and influence either directly or through various channels within the organization to make that happen in the way that I know will benefit not just myself and service my ego, but will benefit the organization later on. Because sometimes others have power and authority to do their own thing, but sometimes we from our offices for good or worse, we have a better understanding of what the implications are downstream, and so I think that you can give other C-level people a long leash, but they will normally have to come back to us to make things actually happen.

Sustaining momentum and avoiding initiative fatigue 44:58

Sanjog Aul [00:44:58]:
One is to spark the idea, which we spoke about, and thanks so much for all the input you gave on how IT leaders can work with the business leaders and users to get those sparks going. Now once suppose a project does get funded or initiative does get funded, it is not uncommon for the executive management to start losing interest or steam and thus they would not be actively championing those efforts which makes it difficult for adoption or even getting ongoing funding and many other challenges start reappearing. One is that you go with that speech or, get them some great ideas, but as a catalyst, catalyst is not just sparks the interest, but catalyst accelerates the completion of that process. What can IT leaders do where they continue to rally the organization, the management, and everyone else so that we see that change initiative, that innovation, that growth related effort? We see it through and at a faster pace and in a better quality. Now that’s when IT leader will earn the role, IT leader will earn the badge of a catalyst.

Dr. Jonathan Vester [00:46:21]:
Exactly, and I think that demonstrating the ability to do just that, to have a goal and keep in focus with the goal that comes the next week or the next business cycle, we have to maintain the integrity of each initiative because otherwise, it’s one of those, once you talk about something enough in your mind, it actually comes already done, and I think that the CEOs particularly have this problem of having an idea or understanding something’s gonna happen, and then once that’s in their head, they think it’s done and they let go of it, and we have to have the ability to not get wrapped up in that mindset and be able to plan and coordinate our efforts and our teams and our resources around how do we integrate the next project so that we demonstrate that we can take on new things and manage the quality of services and the new services that we wanna take on, at the same level, and so one of the things that you’d have to do is as you plan things out and you know you’re gonna have a human resources deficit. If you demonstrate that you’re still continuing this project and it’s on time, on budget, but with this next thing coming, we want to do it, but I need to have someone or some device or what have you as part of it. That’s how you keep the minimum because you don’t want to overburden your employees because if they just see you as layering on innovative design, but you’re not giving them any relief of that pressure to deliver, they’re gonna revolt on you, and so you always have to be taking into consideration the burden that you’re putting on your staff if you don’t give them some kind of relief or you request that as part of these newer changes that we also understand there’s gonna be a cost of human resources or some other fund to maintain that and to kick off the next one, and I think that that’s how you also promote the ongoing change and the ongoing implementation of new ideas is to not make it so it’s a burden or I call it initiative fatigue. We have that a lot of times in my business. We start new things, but we forget about the things that we’re already doing, and so that’s something that we always have to be cognizant of is this is what we want at this high level. It requires these things, and these things are separate, but integrated into the next thing that you want to do, and having all those things on the radar and communicating that with the other C-suite people of yes, we can do that. I’ll be happy to help you do that, or we’re gonna do this thing. However, there is a trade off of time and resources and people that we all have to be very aware of and honest about before we think it’s gonna be successful.

Avoiding overcapacity and learning to say no 49:08

Sanjog Aul [00:49:08]:
So I’ve worked with organizations, IT organizations or their departments in many cases where I’ve gone in there and facilitated sessions as a part of the transformation initiative to uncover what overwhelms them, where they are detached, where they are over dependent, and where they are underprepared. If you were to really look at your organization, your IT organization’s capacity, to be able to help support changes and not lose steam and not get burnt out and you still could go out and play the catalyst, we gotta make sure that these negative areas, which is overdependence, detachment or overwhelm or under preparation, these things are on, in an ongoing basis, objectively inventoried and fixed, but most organizations don’t do it or even they try to do it from within, they are not able to because people don’t speak up because they want to look like heroes, and that makes an IT organization implode, and it prevents them from being able to create value beyond what they are able to. How do you get over this so that you are never overcapacity because of the very sheer transparency in these four areas?

Dr. Jonathan Vester [00:50:43]:
That’s a very good question about not going over capacity because I think that we, particularly in technology, we demonstrate that we have high performing individuals inside our departments. For good or not, the stereotypical IT person is a highly intelligent person. They are capable of doing lots of things, and so we want to take on new and challenging ideas, and so when we say we need help, that’s a sign of weakness a lot of times, and so one of those issues I mentioned earlier is being able to get over the ego of self, and I really do think that as a CIO, you have to acknowledge that the threats to you are not great, when it comes to your perception of yourself, and so you are able to say, we are going to achieve this in this way. I may not have the capacity or not to do this. I’m gonna make sure that my team is balanced and sometimes I could say no. It’s not the best thing to do, but I think that if we do push back, that may motivate HR or the CEO to give us those resources to not tax out our individual employees, but I do think that not wanting to say no is a big problem that we have in technology because we want to be problem solvers by nature, but sometimes we have to come to terms with we can’t do everything for everyone, and we have to ask for help in some fashion in order to get things done and do it in a way that we’re proud of at the very end.

Sanjog Aul [00:52:32]:
I have less than a minute left. What would be your recommendation for the upcoming IT leaders if they wanted to groom themselves into becoming a catalyst when they join and when they grow within the company?

Dr. Jonathan Vester [00:52:48]:
I think that having a very broad approach to organizational awareness, not just being a specialist in your field of technical interest, but being able to understand power dynamics within an organization is important to know and not learn on the job. You do not want to learn about power dynamics or corporate politics on the job. You want to study those things and know those things very well. I think that having someone who’s got broad interest beyond just technology is a good way of looking for that. If you’re looking for a successor or if you’re trying to plan someone inside your department. So broaden your horizons from an up-and-coming CIO standpoint. If you have aspirations for doing that, look beyond just technical. Look into people management, understanding how organizations work.

Dr. Jonathan Vester [00:53:45]:
And have an appreciation for doing those things along with technology.

Contributors

Dr. Jonathan Vester

Dr. Jonathan Vester, Vice President of Technology and Chief Information Officer, Nash Community College

Dr. Jonathan Vester has worked in technology for over 22 years, with 20 of those in higher education. During this time, he has held positions ranging from PC Technician to Director of Institutional Research and has consulted for many instit... More   View all posts
Add Comment
Click here to post a comment

Advertisement

AVI-SPL-Service Banner-MPU-300x250
Dr. Jonathan Vester