Latest / CIO Unscripted / CIO Unscripted with Eric Hawley — Getting Invited Back
Transcript
- Sam Linton: So ⁓ today with Eric, we talked a lot, we talked primarily about relationships of trust, how to build them, how to form them, how to retain them, and how to be the person that gets invited back to the next meeting and the next meeting and the next meeting. And pretty soon you're invited to everything, which is kind of where that's how you know you're successful. Also, that really interesting concept about the how to manage and deal with and plan for the experimentation of the edge. I think that's really timely given where. organizations are today with AI. Cause I think a lot of technology leaders and organizations are struggling with where do we mandate, where do we impose, what do we corral? Do we corral? It's it's an interesting time in in the world of technology Welcome to CIO Unscripted, the podcast where technology leaders get real about what it takes to lead IT in a modern organization. ⁓ We're joined today by Eric Hawley. Eric Hawley is the Chief Information Officer at Utah State University, a reasonably sized university and an R1 research university, which has its own distinction. ⁓ I've known Eric for a long time. Consider him a friend. I don't know if he considers me a friend, but I consider him a friend. Totally and completely we're we're happy to be joined by Eric today. So, Eric, I don't want mess up the sequencing, but let's dive into the first question. So I'm going to recap and then we'll get into a more detailed explosion history. You started in IT as a student at Utah State University many years ago. I'm not going to say how many years, but it was, you know, right after Al Gore metted the internet kind of time frame. ⁓ yeah, it was it was it was 1994. And that was the commercial consciousness start of the internet. Like AI was a couple of years ago. Nobody was talking about it than they were. Yeah, in 1994, that was the that was the thing for the internet. And if you could stare authoritatively at a keyboard in '94, you got a job in IT. So what were you doing at the time when the university said, Hey, can you do this thing? I was emptying trash cans, cleaning toilets, and setting up chairs in the Eccles Conference Center. Okay. And quite literally someone walked up to me and just said, Can you set up a Novell network server? And I said, I'm sure I can. I my entire career started with a lie because of course I'd never even touched the thing before, but I figured at that time it had to come with an instruction manual. Plus I had an older brother who worked at Novell, so I knew I could call somebody on the phone if I if if I ever got stuck. I guess I did I guess the career didn't start with a lie, because it turned out I actually could, which has sort of been a a theme throughout. Give it a try. Find help if you need it. Figure out what people want and kind of pull it off. So it started a trend. So from that very auspicious beginning then of your career, how has your career progressed from that start to what where you are now? ⁓ gosh. by invitation. So what do you mean by invitation? You know, in In technology and in IT, we're always working with servers and buttons and wires. But the thing with servers and buttons and wires and websites and protocols is they actually don't invite you and they don't need you around. But people do. Literally every single opportunity that I've ever had started or progressed because Someone, I guess, didn't mind having me around. Servers or wires didn't care, but apparently the people did. ⁓ and you know, a b a big part a big part of it was sort of being able to work through the technology pieces and help advise people in a non-technical objective to sort of get there to to to t to be a partner and ⁓ you know a I guess right up front, I'll give you my one metric to rule them all, which is sort of the underpinning, you know, storied all. This is this is where you put the subtitle right here. You you you flash it, you flash it's it's basically this. How often are you invited back to a meeting a second time? That's it. Not not because you're the only person holding the keys to the closet someone else needs to get into. ⁓ but but because they want you on you know on on the journey with them. And and so, you know, from From decentralized IT to centralized IT, and boy, there's a whole story and all of that. Do people want you along the way? ⁓ and and do you want to invite and bring people with you? Because it's not just me, right? Yeah. That's an interesting metric. Do they 'cause I was so helpful in that meeting, right? Like you do yeah, do do won't do they won't be back a second time. Especially with security people. That that's a tough job. Are people gonna want you back in the room a second time ⁓ to advise? Or or are you someone they want to work around? That's a that's an interesting thought. Are you are you the security person who's in the no business? Or are you the security person in let's do it right? Let's do it person. Yeah. I love that. So okay, so you s you you've started so you've you've Be invited as your role has changed. Now I've only applied for one job in my life, and that was cleaning toilets. Everything else has been invitation, quite quite honestly, which is a little unusual. Yeah. So a lot of universities, especially larger universities, have a much more central decentralized model in their lives where departments and colleges can kind of do things. And I get the impression USU started that. How has that changed and how did you affect the changes? ⁓ gosh, the whole the the whole centralization and decentralization ⁓ you know perspective. All technology and all innovation, I think most people who watch this may have heard of or or are familiar with the hype cycle idea, you know, sort of sort sort of the experimentation, the RD, higher ⁓ higher education. higher education at its best facilitates broad playing and experimenting at the early part of of of of that hype cycle. And at that when technology is at that that entry part, it's not ready for centralization, standardization and commodi in in commodity. And so a lot of these things begin in higher education at the edge. There's a small research group or a college or a department or a program that has a unique edge need. And they'll look at technology and tools and say, or or programming languages and people, can we build this? Can we try this? Can we do this? And it starts organically, like a weed. Out in the field, and before you know it, you've got 154 separate and uniquely managed email domains that you had Utah State University because you know everybody sort of started, ⁓ this is cool, and this is cool. And at some point, at some point, wow, everybody's doing the same thing, but completely separately. And so when you think about centralizing and decentralizing, there's there's an inflection point. Right? Where it shifts from edge experimentation to, hey, wait, this is a service that we could all use and we would be better served by a more unified, coordinated effort. And it's important to understand that inflection point and when that's not the case and when it is. Because if that inflection point is too early, when the technology isn't mature enough, ⁓ Then you get into troubles trying to centralize it too fast, ⁓ too early. ⁓ you know, again, if you wait, even if you wait too late, then you don't have ⁓ the efficiencies and in in and you drive that. And so ⁓ a lot of it has has been around timing, not getting in the way of edge experimentation, but knowing when and how to to sort of time that inflection point where you can start saying, Hey, this is far enough along. Maybe we should do this across the USU now. Does that make sense as sort of a general principle? It it does it makes a ton of sense, but I I got a couple of questions. How in a large decentralized or well, an organization l fairly large that is doing this air experimentation at the edge, how do you become aware of enough of what's going on to know it's getting to that inflection point? How do you o how do you create some awareness? Is that where the relationships you've built across the organization matter, where people aren't hiding stuff from you, but informing you of to what they're doing? I j I'm curious about that. How you know what's going on? And one of the challenges and opportunities is the massive breadth of stuff that's happening here. You know, ⁓ hundreds of departments. ⁓ you know, everything from spider silk knee replacements to electrified roadways to department of dis defense spy stuff that nobody can talk about. y get around and get to know units and unit leaders and get them to tell stories. Neil, you're so good at finding people and like bringing people on things like this. And just hearing what they have to say. Go talk to people and hear about what they're trying to get done. Not the IT technical stuff. What software are you using? What tools are you using? Nah, nah, none of that stuff. What's what's what are in your dreams? What are the cool things that are the that are going on? Spend some time to go talk with a college, talk with a unit. ⁓ you know, that listen. Just just talk with people and you kind of figure out what what's what's what's going around and ⁓ in in and and what's happening and where you can help help them achieve that. And then they're like, ⁓ hey, I know this guy. And I guess that ties back to the other point where if you've got if you're if you're curious like that and helpful like that, that's how you get invited back to talk to him again. Right. Yeah. And and it's not because of well, you know, there's here's the other bumper sticker. No such thing as an IT project. Right? Somewhat facetious, of course. Yes, there's technical work to be done. Got it, but all of that should achieve a a human objective or or or a business objective. And if you can be curious and understand that, and then say, Hey, I know some people, or maybe we could help do this, or what are you doing over there? Wow, that's cool. We even offer that centrally. Last thing I'm gonna do is get in your way. Let me sort of watch and see it see how I could help. Maybe at some point this will be cool enough. We could, you know, we we we could scale this and you know and and let other people do that. So be curious, create relationships, don't get in the way of edge experimentation. and offer help. Is there another side to this though where ⁓ if things get to that inflection point and you're gonna standardize an offering? Where people feel like you've chosen something that's not what they were using or what they're used to. How do you deal with the that transition for people who, ⁓ well, no ⁓ I okay, go ahead, USU, you do that, I'll keep doing my thing. There are seventeen million ways to to to to to solve a problem. ⁓ I'll mention at least two that you can take on this. So We'll we'll we'll use something as stupid and non-strategic as email in this situation. When Utah State University had a hundred and you know, fifty some odd independently managed email domains. At some point, at some point it's like, you know what? This is this is not differentiating. any email system can sort of do any of this. It's remarkable. Because any technology you know sort of sort of goes religious. Are are are you Mac or are you or are you Windows or or or or are you Linux? Do you like Gmail or or or do you like Exchange? And people people are become religious adherents to to that particular brand. But if you're gonna commoditize, you kinda gotta pick it. Is is it gonna be Gmail? Is it gonna be Exchange? the new president of Utah State University. ⁓ Ca came from a Google shop and moved into exchange. It's like, ⁓ no, we we're we're forcing someone to change their religion. And in that case, someone is gonna have to change. in in the way I've worked at it is I don't generally start with the biggest people who don't want to change. But there's a path where we're That may not be a bad approach. I I think, Neil, you you may have taken some ⁓ taken some change approaches where where you start with some of the people who are most opposed to it and bring them over. So pick pick a starting point. ⁓ work with the people in the cases in in the case of email, we we worked with the people who sort of understood it and and got it. And and when we got to sort of the 80%, it was harder for the the for the remaining 20% to hold on. Because because their justification for not joining had been solved in the discussion with the other eighty percent. And they and they started running out of excuses. So we left the biggest, angriest, ours is the most unique problem to the very last. Because by the time we got to them, ⁓ our systems and services maturity were were were enough that the that those ex the those excuses had it had had been done. There there may be a call to do it the other direction, Neil. Would you would you argue for the other direction? You know, I think it's very situational. I've I've done it both ways. I tend to look for a a soft beach rather than a hard beach. That's me too. I would say I choose a hard beach just 'cause I like to reduce the number of casualties, right? I like to I I've chosen a hard beach a few times. Because I thought the situation required it and it was the right approach. But how did I know it was the right approach? Because I n I had relationships with everyone and kind of knew what would work. You know, I I just I don't think you can separate knowledge from the decisions like this. But in general, I always like to take a ⁓ land on a soft beach, rather than crash onto the into the w into the cliffs. I It's hard to recover from a clash into the crib a crash into the cliffs. Full agree. And at some point, and here's another inflection point. Maybe we'll call that the theme of this interview. Yeah, at at some point there's an inflection point where IT is no longer the advocate because the first one, two, or three that are bond into it cle see clearly the the the advantages and they become the advocates. And it's easier for peers convert and talk with peers than for than for outside IT people to do it. I in in sort of to that point, always at Utah State University, I've tried to be involved in the real business of why Utah State University exists. And that's been sort of key to the change here. We're involved in teaching and research. And so when when Stan Albrecht offer offered me the CIO position, gosh, 15 years ago this July. ⁓ I I told him I wouldn't take the position unless he let me keep teaching a little bit. because I wanted to be involved in the real business of Utah State University. ⁓ you know, drink your own champagne, eat your own dog food a little bit, because it's so much easier if you're faculty with faculty or with students to say, Hey, you want to try this new thing? Hey, what's your experience? Rather than some rather than some IT punk who isn't seen. As a researcher or as a faculty member, trying to teach a faculty member how to teach differently using technology, that becomes a hard beach because you aren't in their context. And so finding a way to get out of your tech shoes a little bit and getting into the real business of why the group whom with you work is there, one is both fun and motivating for me personally and professionally, but it it enhances change management. Yeah, I agree. Yeah, it's you know, we could we could spend a lot of time on this topic of creating relationships of trust and what it takes to create relationships of trust and really how how relationships of trust are just this incredible lubricant that makes everything go better. If they know you understand their lives and care about their lives, they believe that because it's true. It's really easy to say, Have you thought of this? Yeah. I when When when you look at communities or groups, ⁓ my my my my wife and I we we cycle a lot, we always have. We we we met cycling. We went on a mountain bike pedal from the top of Bear Lake all the way down Blacksmith Fork. It was forty-two miles. She wrote my wedding ring, 42 miles to forever, because we've always been cycling. When you find some common interests, even though we're very different people, or or or you find a common community, ⁓ you know, some point. That that you're working together on something common. ⁓ you can find second, third, and fourth things to work on, and and and that community grows. What's the common point as a technology leader between you and the business units that you support that isn't just IT? If you can't answer that, you're kind of a no offense, a VAR. You're you're selling stuff with a catalog and people are like, Yeah, I don't want to take your meeting. It's you know, I've I've I myself have gone through several centralization, federated, decentralized, and yeah, I tell me they're this is my favorite Now you're helping a VAR. Yeah, and now and this is my f this is my favorite ⁓ consultant joke. You hire a consultant, they show up, they say, Eric, are you centralized or decentralized? And Eric says, we're centralized. That's your problem. Pay me enough money and I'll decentralize you. Okay. Then I come back a year later. I say, Eric, what's your biggest problem? Well, we're decentralized. That's your problem. Pay me enough money and I'll centralize you. Yeah. Yeah. But it's good answer is there's a reason for both and don't mess it up. but it's interesting just the the dynamics of centralization, decentralization, federation. And I and I really like your approach, this this concept of experiment at the edge, and then at some point the economics there's a there's a rational business reason, not a technology reason to standardize on something. And then you still gotta decide the support model. Do we centr s support that in a centralized way or a decentralized way? Because you can standardize without centralization. And can you still provide some choice in that? Exactly. Yeah, ⁓ so I don't want to lose it, but I want to come back to it. So I'm thinking about this edge innovation. Now, apparently there's something around called AI. I'm not sure what it stands for, but it seems to be a thing. So, from a university perspective, how are you approaching AI? Because you've got, I'm sure you've got researchers doing AI research. You've got Researchers that want to use AI. You've got a university that wants to use AI, both for operations and for education. So, how does this edge experimentation work with something like AI? It's been interesting. When AI came out, the first thing institutions, and by institutions, I'm sort of thinking the overall bureaucratic governing body of institutions are like, we must have an AI policy. Give me an AI policy. Can you imagine 1994? The internet is now commercial. We're like, We need an internet policy. A policy that will govern the internet. ⁓ y Neil, you're laughing because it I mean it's preposterous. How many of us have an internet policy? In twenty twenty six. I mean it's you know what what is this thing? You know, it would have been a terrific mistake in nineteen ninety-four to even tried to fully standardize or create this comprehensive internet policy. Because we freaking knew nothing. We were two-year-olds on what could or would happen in in the world of technology. I submit that we are two-year-olds every dang week of the year in technology. Now eventually we figure stuff out. ⁓ and that leads to that leads to some maturity. And so if great, if we have an AI policy, then maybe the AI policy should be: don't be afraid to try it out. Maybe the policy is go try this stuff and have an objective in mind and measure how this helps achieve the objective or not. Maybe the policy should talk about where the accountability is. I've used a phrase ⁓ before the civil engineer doesn't get to blame the calculator when the dam breaks. The accountability is on the civil engineer, not the tools the civil engineer uses. Civil engineer, be creative, find cool new things to solve your problems better and faster. Be bold, you know, teach a researcher, try AI, but recognize the accountability for the output is yours. So if that's the policy. Great. The accountability for great teaching is yours. The accountability for great sustainable compliance secure research is yours. And don't be afraid to try AI. Let's talk about how we can experiment, use it, and not blame AI, but do the critical thought so that we know when it's working and not an adjust in an agile fashion. So any policy should ex should should support. and encourage the experimentation at the edge towards the human or business objectives in an agile way and make sure people understand where the accountability is so that so so that people just can't blame the tool when AI hallucinates. So let me think of an example. So ⁓ and maybe this is a poor example, but people are going to try different things, right? They'll try copilot, they'll they'll corrupt plot try claw, they'll do whatever. Yeah, yeah. At some point there'll be some level of critical mass that says we validated how we're how some of us can use this. Sure. Is that when you step in and say this now becomes a service that's part of our service portfolio as part of the technology team at Utah State University? Is that how works? I mean there there are there are all sorts of, you know, what what what ingredient makes the cake? You know, flour, egg, sugar, or water. The the answer is all of them. And when we start listing the ingredients that contribute to to an inflection point, ⁓ you know what one of us contractual negoti negotiation and configuration. You know, if we start offering an enterprise service, we can review and negotiate the contracts to make sure that we've covered HIPAA use, to make sure that we've covered FERPR student, you know, or student compliance. You know, if people are just swiping their purchasing cards and using consumer accounts, then then then then that becomes an issue. And so I can see that that carries with it a certain amount of institutional risk. Right. And so so so evaluating risk, contractual and compliance drives towards ⁓ an inflection point, towards an enterprise service. But it doesn't necessarily mean, okay, which of these models are we gonna pick? And this is the one model we're gonna use ⁓ you know, for for AI, ⁓ because these, you know, the the these services are leapfrogging every week. and so deciding what centralization means, which is, okay, what should what should good centralization do to help people out? Faster, better compliance. ⁓ mo more more assurance of of a ⁓ of a secure ⁓ configuration even if there's ⁓ even if there's choice in model faster and easier ⁓ to to to acquire and control costs ⁓ ways that we can analyze and produce data to inform the next step towards centralization who's using what tools for what well if we start offering distributed varied tools centrally give people lots of choice. Some people think centralization equals less choice. That that that doesn't have to be the case. We we widen the choice but then use that for central data collection to inform the next agile you know i iteration of centralization where we may say, you know what, maybe we don't need this tool anymore. Maybe maybe we start you know, trimming these things down. Maybe we don't need Zoom and Teams and Google Meets and as we evolve, maybe we can start standardizing over time because centralization can drive data analysis to help think of the next in or is it iteriz it next iteration of what centralization may look like. Yeah, that's a really good point because it's hard to pick a winner when we're in the cloud of dust phase. And we may be in the cloud of dust phase for a long time when it comes to AI. And that's something we can always do centrally, which is if there's a cloud of dust, can we look at the data to see who's using what for f even in decentralized environment, can we find a way to figure out who's using what for what to produce some data to inform another cycle of discussion? And data now is a I'm not gonna call it control. But some level of I'm gonna I ⁓ maybe compliance, because there are rules you have to follow as an institution. And that at least makes it a little safer from a compliance perspective that somebody's not outdoing something or choosing a technology that doesn't have the proper safeguards in place. And if we aren't moving fast to do that, well guess what? They're doing it without you anyway. Right. Which which is an which is an interesting balance because sometimes it can be so slow to get through the legal contractual negotiations because people are people are so nervous about that. But if we take too long, our institutional risk is actually greater because people are doing it without us. Yeah, that's true. Which brings up another point is this notion of ⁓ kind of the frictionless customerslash employee experience. How do you how do you deliver services in a in a way where they absolutely love doing business with you. So they're not trying to bypass you. Yeah. Yeah. I can imagine, you know, if if if somebody from their third party risk management process said it takes me six weeks to review a contract. Would wait for you. They'll just go do it. People will quietly go do it. And so and so in our attempt to control risk, we've created more risk. Yeah, exactly. It's a line to to to navigate on this. So And maybe we'll kind of wrap up with this because I don't want to take too much of your time because I know, you know, it's the summer break and you're probably incredibly busy and have a a a a a few hundred miles of bike riding to do before, you know, five PM. I've always thought you operate in a I'm gonna call it not a difficult, but a complex environment. You've got a lot of constituents to support. Some of those constituents like their independence. They don't like being told what to do. They want to do things themselves. Colleges are loosely affiliated independent nation states, embassies, trade agreements, wars. To what do you ⁓ just talk to me? What has helped you be successful in this environment? What are the sw what are the things that you as you look back and think about it, why did they ask you to be the CIO? Why for the last fifteen years have you have you able to accomplish what you've accomplished? You know, what about you? What about your team? What about your approach? Just g what do you think? Use the I word a little bit. ⁓ but the we word works well. The best we is where we, however we define we, can work through anything. So Neil, this is you know I I I f I feel like this is a relationship that I have with you. There's literally nothing that Eric and Neil couldn't work through together. I mean you know, that n it doesn't matter how hard or simple or or or what it is. If Eric's being a jerk, Neil and Eric can still work through it. If Neil's being a jerk, Eric and Neil can still work through it. Because we sort of got that that you know that that relationship to be able to say. In various scopes within the IT ⁓ leadership group. Can I look around the room at you know at all of the directors and leaders in IT and say, you know what, there's literally nothing we we can't work through. We don't have to tiptoe. We there's literally nothing we can't work through. To be able to say that within within IT is super, super powerful. Then scale that up one organizational level. You know, with myself, with vice presidents for for for research, with with provosts, with deans, to be able to to to say, hey, look, the seven of us, to be able to say to your general counsel, your illegal counsel, you know what, there's literally nothing we can't work through. I I I'm tot I I'll I'll pick up the phone and talk with you about anything. I'm I'm not nervous that you're gonna blow up or feel threatened or Or that we're playing poker and and I don't want to hide, I'm gonna have to hide my cards with this individual. Find that group. As you even even if it's a small start, what are those people who you can talk about or do anything, work through anything and not feel threatened, ⁓ you know, as as a group? Then start growing it. Before you know it, you've got this this this this table of trust. This group of people who's like, doesn't matter what it is. End of the world. Cool. I bet we can work through it. Find those people and then start growing those people and adding to it. That doesn't mean you know not everybody falls into that place. But if you start growing that and that group becomes larger and more powerful, man, you you can work through anything. And then those people get promoted. Dang, I'm I'm I'm I'm wearing I'm wearing the shirt of my of my current department head, ⁓ Chris ⁓ Chris ⁓ Corcoran, who's the department head in data analytics and information systems ⁓ department, he just got the job as provost. He's one of those people who I can work through anything with, no matter how ugly big or ⁓ it is, and I I I know he feels the same with me. And so that relationship will extend into the into the overall university academic leadership. Even though we fostered it at a different point in our careers. You know, it's interesting when I think about that in the context of some of potentially ch difficult conversations, those crucial conversations about, let's say, de centralization or decentralization. But if you've got this relationship where we can work through everything, then you work through it, right? Without hard feelings, without acrimony, without people feeling like somebody won and somebody lost. That makes a ton of sense. Yeah, ⁓ a hundred percent. That that's also the only place I want to work. If I if if if I don't have I'll I'll I'll go somewhere else. Fortunately, that's been the case at USC. So looking back fifteen years, do you think that is why the university president came to you and said, Eric, they invited you. Eric, we'd like you to be I the CIO because you had built that reputation, built those relationships and built that approach. I mean, yes, I'd I'd I'd go back to those people and say, Why the heck did you why did you do that? And do you regret it? Is this one of your Yeah, it's it's you know, and it's it's also being able to speak people's language, right? Nobody wants to be overwhelmed with the geekiness of IT or the inability to sort of translate that in in in into human stuff. I think sadly some technology professionals like to create an air of mystery around technology. They can hide behind the the mystery of technology. And nobody wants to work with you if you know it's you know how often are you invited back to a meeting a second time and not because you're the only one holding the secret key to the thing they think they need. Yeah. That's mafia. Yeah, that is. That's they have to go through you. That's the Stockholm syndrome. Yeah, yeah. And that's I that's not great for long term relationships. That's not great for we can work through anything no matter what it is. I also don't think it's great for just the ability to move quickly when we need to move quickly. That's right. That's right. That's right. If something's mysterious, then we can hide behind it and say, no, we can't do that. Can't do that. Why can't you know? We just can't. Yeah, yeah, yeah. We yeah, yeah, we we just can't, which and that's that's one of the things that's sort of been ⁓ you know successful. One one of my mentors, ⁓ pr the previous CIO, didn't know a lot about IT, but had forty-nine and a half years of relationships a at Utah State Universities. He would admit that one of his weaknesses was he didn't know when a technician or someone was blowing smoke. But he knew that was a hole in his portfolio and he had me to help fill that hole. ⁓ and so even if you don't have it all, find others who who you can trust and empower, you know, who who can help be you can help be the judge for that team. And then together, two, three, four of you, we can work through anything. Well, Eric, I appreciate your time. I really do. ⁓ I've always respected you and what you've done at Utah State because I just it's ⁓ it's an interesting environment. Higher ed's an interesting environment. ⁓ it's a completely interesting and wild fun. You've got a lot of compliance, a lot of regulations, a lot of demands. There's a lot of luck. Yeah. There's a lot going on in higher ed. And ⁓ it's just it's fa it's a fascinating world to live in. Neil, always a pleasure. Always a pleasure and you know what? There's nothing we can't