Latest / CIO Unscripted / CIO Unscripted: Niel Nickolaisen on Transformation and Building Trust
Transcript
- Sam Linton: I've spent my technology leader career doing transformation. And the thing I've learned is that we're now in a state of continual transformation, both at the organizational level and the technology department and leadership level. And so these are some lessons I've learned on I'm gonna call it continual transformation. Just this always knowing I need to change. No. Not I need to improve because that's what the market demands, because it's changing every day, whether I'm on order with it or not. Well, and I think absolutely you spend time listening to this. I've had a great time talking to to Neil and some of the things that he talks about specifically of how to improve a culture, how to transform ⁓ maybe lower performing IT culture to ⁓ high performing where they're asking Hey, can you slow down because you're so good at delivery? I mean that is that is amazing. And then really specifically what tools and what examples of stories of how how to do that. I just love loved our conversation and I know that people listening to this will Neil, we really appreciate you being part of the Valcom team, the Valcom ecosystem. Our our clients have been excited. I was walking around IT Exchange, which for everyone listening is our big IT event of the year, had hundreds or seven hundred people came, clients, and ⁓ your show is one of the most filled, like standing room only, or your your presentation, and so thank you for for doing that. So I'm here with Neil Nikolaysson, ⁓ Valcom's field CIO. And I mean there's other names we could have given him like IT guru or CIO consultant and ⁓ but we landed on that because it can encompass all things. And one of the things we really want to accomplish with with this podcast is really sharing experiences, I think for a couple reasons. We want people to learn, grow, understand wisdom from other CIOs. ⁓ we also want to share the experiences so people know they're not alone. I think ⁓ you we talked last time as a lonely job and and we had a technical glitch. We've already done this show once and ⁓ we used ⁓ software that that didn't work so well and so we we switched softwares and we're we're redoing it. So Neil, welcome. I have so many questions and I'm excited to do this again. first off, first question. I want to know before we get into your history and all of that, why the heck should people listen to the to our podcast? That's a great question. ⁓ I think because we're together, Mike and I are going to talk to technology leaders, CIO, CTOs, VPs of IT, CISOs, those type of people who have learned important lessons that I think we could all learn. Because as you said, it's a difficult job. Sometimes it's a lonely job. And I think one of the things that makes it lonely is to think I'm the only one going through this. And it's nice to find, I found in my career in networking with other technology leaders, we're having similar experiences, we're having similar challenges, and it's wonderful to find out, hey, somebody's done something that worked. I might try that too. And so it to me it's just the the shared knowledge, the networking, a lot of the the things that have worked for me I learn from others. And so I think this is an opportunity to share that same experience because the role is not getting less challenging. It's becoming more critical to the organization and and it's with that criticality comes new types of challenges. It's not a technology role, it's a tech it's an it's a leadership role, a tech a a business leadership role. And it's just different. And I think we'll bring more leadership lessons as long as well as the technology thinking and the technology methodologies that you've created and we're super excited to do this. So you look back on your career, you start off as mechanical engineer or something like that, and you end up in IT. We'd love that as you look through what kind of your journey and I'd love you to give the recap or how you even got to to where you're at in your journey and a couple of lessons along the way. Like what what stood out along the way as you as you pivoted and as you as you got into that IT? I think it's a fascinating story. I'd love to Okay, so ⁓ just a a bit of my background like a Mike asked. So I did not start my career in technology. ⁓ I had very little to do with information technology. I started my career in nuclear engineering. ⁓ I I in college I my bachelor's degree was in physics. I wanted to be a nuclear engineer, so I joined the nuclear navy. After four years in the Navy, I realized the Navy's a little moves slowly. They're very risk averse, which means they're action averse. And I had done, I had taken some chances that worked out. And so the Navy wanted me to stay in, and I wanted to leave. So in order to incent me to stay, they offered me, they offered to send me to MIT for master's degree. So I went to MIT, got a master's in mechanical engineering, and now I owed them time back. So ⁓ I sort of assigned myself, they said, where do you want to go? So I assigned myself to a research, Navy research lab, and I did this dates me early stage AI neural network research. We did some fascinating work with neural networks anyway. So I left the Navy and went to work for General Electric as a mechanical. engineering systems a manic mechanical systems engineering manager. So I'm a pretty young guy, but I had this team of 50 grizzled old angry bitter mechanical systems engineer. And so I'm leading this group and it was a good group. They were a little skeptical of me at first, but it they turned out okay, he's he's not an idiot. So that's my always been my claim to fame mic. I'm not very good, but I'm not an idiot. So did some I was doing well at GE. And they came to me and they asked me, so here I'm in my early 30s at this point. We want you to lead a lean manufacturing project to see what it would take to shrink the cycle time, the production cycle time for our product. I worked at a GE business that built locomotives. It took six months to build a locomotive. We could build, we were constrained by by just area. Just how long it took to build a locomotive, we're constrained to building about 300 locomotives a year. The demand for our locomotives was higher than that. We could have sold more if we could have built more. So people would place an order and they'd get their locomotive in a year or two. So they said, Neil, what if it took less than, fewer than six months to build a locomotives? So I said, okay, I'll figure it out. So it kind of mapped out the whole process, learned about lean manufacturing, and we shrunk the cycle time to Three months. Only took three months to build locomotives. So the next year we sold almost 600 locomotives. It was kind of impressive. It was a really great lesson learned. And finally, now I'm at this point I'm in my you mid-30s. What lesson did you learn? That you could do stuff that you're not knit? Like what like what lesson did you learn that you took away from that? No matter how good things are, you can make them better. This plant had been in operation for fifty years they thought they'd wrung out every opportunity for improvement in the world. But was it your education, your different way of thinking, just believing you could get it better? Like when when our people that are listening, like what did they learn? Like is it lean? Did you like, hey, apply lean because that's what you're educated? Like how'd you do it? I to be honest, ⁓ yeah that's a great question I've never thought of before. I think what made it possible is that I collaborated with everybody Because I had to work with everybody across the whole production cycle. Engineering, manufacturing, procurement, sourcing, legal, everything, right? How do we shrink the cycle time? And the other thing was, ⁓ and this is ⁓ I'm I'm in my mid-30s, I had an aptitude for it. Here I am, I'm mid-career, early career, whatever you want to call, and I finally figured out what I was good at. I have a superpower, and it took me a while to figure out what a superpower is. My superpower is just the way my brain thinks, when people describe a situation to me, just mentally I can see how it connects. And also because that seem kind of cause and effect. Okay, we're doing this in serial. What if we did this in parallel? This is a bottleneck. What causes the bottleneck? And so I started to figure out who I was professionally and what I'm good at. So I left GE. ⁓ needed, I grew up in Utah, I needed to come back to Utah for family reasons. And ran the process improvement line of business for a small consulting firm. And that small consulting firm, sometime months later, acquired or that was acquired by the old Franklin Planner Company, Franklin Quest. So Franklin acquired this consulting company for two of the four lines of business, but not mine. So they shut mine down. And so then I'm an internal consultant at Franklin. And so I'm doing the same thing I did before. Okay, let's map out the process. Let's see where the bottlenecks are. Why does it take so long? How much does it cost? What can we do to optimize? And so I became an internal consultant. And then I ended up in a relatively short period of time. I never asked for this role. I never positioned for it. I never politic it, but they came to me after a few months and said, We'd like you to be the VP of operations. So I owned all of manufacturing and distribution. And at this point I thought my career path was I'm gonna be a manufacturing guy. So I own manufacturing and distribution. And if anybody's old enough like me to remember the Franklin planner, you remember that what you did every day during planning in solitude is you wrote down everything you thought you needed to get done. Then we went back and you prioritized them: A1, A2, B1, B2, B three, C one, C two, C three. And my A1 every day, I'm being a little facetious, but it literally was to just complain about how bad their IT was. Just terrible. Abysmal. The CIO was a great guy, but you know, the technology kind of grown past him. His team wasn't that I I used to joke with them. You count uptime by whether or not there's power to a desktop or laptop, not whether the systems are working. If it's if if there's power to it, it must be up. No, we were had serious downtime problems. And so I complained a lot. And I was I was I was younger, Mike. I was a little more brash. I was a little less patient. Maybe it's not possible for me to be less patient, but I thought I was. And so I was in this running battle with IT all the time. I wanted to make process changes to the way we did manufacturing and distribution, and I kept running into. Our software won't support it. Well, of course it won't. Because you built all the software yourselves. We didn't buy anything, it was all build, nothing. We we built our own accounting system. So I want to make changes to the way we do like inventory values. I want to shift to more of a lean approach. ⁓ sorry, Neil, we can't do that. I just it was can't, can't, can't all the time. And after a particularly bad deploy that shut us down. And required an awful lot of workarounds to get us back up and running. I went in the CEO's office and I said, John, I actually had a job offer to go to be the president of a foresight manufacturing company that was based in Chicago. I had the j the offer letter in hand. I was the only person on my wife that knew I had this offer. ⁓ This was just gonna be me throwing IT under the bus on my way out the door. I went in with the CEO, I said, John, five minutes from now. If you've not fired the CIO and his entire staff, I'm quitting. I'm done. I can't live like this anymore. Well, five minutes later, I was the new CIO, which is something I hadn't anticipated, hadn't planned on, hadn't even dreamed of. Here I am. The last time I did anything with IT was a Fortran class I took in college. That shows how old I am, Mike. I took Fortran in college. I don't even know what that is. Exactly. It was it was an early programming language, and I tell people, they say, Fortran, what's that? I said, Don't just remember. Fortran is the computer programming language that's got us to the moon and back. You'll note that once we stopped using Fortran, we haven't been to the Moon and Back. It was the English. Anyway, so I became the CIO of Franklin Covey and just had ⁓ knew nothing. Inherited a team of about 120 I a team of about 120 IT professionals that knew I hated them, they hated me, and I just got thrown into the deep end. And so that's actually when I started networking, because I gotta find out I gotta find out how to do this job. I don't wanna be a failure. And so we did, I we kind of reviewed the bill versus buy decisions, put in an ERP system, and I learned just incredible lessons in leadership and about technology. about bill versus buy, about the value case, how do you realize value in a project instead of just do a project? I just learned a ton. And what are some of those early leadership lessons you would say was like stuck out through this? Especially in my case, sometimes I think leaders struggle because they're a subject matter expert that gets asked to become the leader of that area. I never suffered from that because I didn't know anything. I wasn't a subject matter expert. So I had to rely on everyone around me. I had to collaborate. I was good at process improvement. I was good at systems thinking. Turned out I was good at architecture, because that's kind of a system. But I couldn't help with anything technology related necessarily. ⁓ and so what I learned is that leadership is a role. But it doesn't mean I'm the expert at anything. So it it helped me realize I take my role seriously. But if I'm relying on my expertise, on my subject matter expertise, I'm probably shortchanging everyone else's expertise. And so even when as as I've as I've gone through my career, one of the things I've always had to remind myself is. They asked you to lead because of what you're good at. Instead of being proud of and kind of flaunting my expertise, my job is to make everybody else on my team as expert as I am at that. Because otherwise, every time they rely on that expertise, they're relying on me, and I become a bottleneck. So would you say as you've looked through like your beginning and you're really Your skill in like systems thinking and all of that, that that's translated mostly to where your strengths lie and where you've seen IT needing that skill, and as you've trained others, that that's really helped them. Like, and is that something they're really good at the technology part, but need to learn systems thinking or need to learn leadership? Like what what are some of the gaps that you've seen or that you've helped fill? Because I think it's part strategy, it's part business, but What do you what really is it? U I think and the thing again, I was thrown into this so I didn't I didn't have to work my way up through the technology ranks. I just approached it differently. I was a customer. I want my customers to be happy. That doesn't mean I do what they ask. I want them, my customers, to be successful. It's more important to have successful customers than happy customers. What's it gonna take to be successful? And so one thing, you know, I've just learned a lot of lessons about I need to understand what matters to them. I need to understand their lives. I need to spend time with them. I've worked in a retail store when I work for when I'm the CEO of a specialty retailer. I've worked in distribution centers. I've gone on sales calls. I've participated in the financial monthly close. I have made myself available. One of the best things I do when I, you know, I've I've had a number of CIO slash CTO roles because I've spent my career ever since then doing these turnarounds. A series of turnarounds or transformations. Turnaround sounds kind of negative. Transformation. The technology group is operating at this level, it needs to operate at this level. Okay, in order to get from here to there, we gotta do things differently. So they bring me in and we do things differently and hopefully better. but but along that way, it's I've got to understand. How to go from A to B. And this is where my system thinking helps because I say, okay, what are the things that are stopping us from going from A to B? From a cause analysis perspective, what capabilities do we need that we don't have? What technology capabilities do we need that we don't have? What process capabilities do we need that we don't have? And then bigger, I found over time. What cultural capabilities do we need that we don't have? Because the thing that's evolved the most for me is a recognition and a understanding and respect for culture. If I build and and then the other thing is, the other the important thing to me is if I'm gonna take my team and also the entire organization on this journey from where we are to where we need to be, they have to trust me. So I always ask myself. What does it take to build relationships of trust with everyone in my life? Everyone. My staff, my extended team. I'm on the executive team. What does it take to get the executive team members to trust me? What does it take for the CEO to trust me? What does it take for the board of directors to trust me? Because I'm going to be asking them to do big things and ask their approval. And then what does it take to get the the teams of my executive team peers to trust me? And so to me, it's ⁓ I the most important lesson I've learned is since I've had kind of these transformational roles, and honestly, I think any tech leader today, it's a transformation role. Which means I've got to get people willingly to follow me. I'm gonna say, here's where we're going. I need you to come with me. They're only gonna come with me if they trust me. What does it take to have build relationships of trust? I they have I have to be competent, I have to be credible. I have to be a decent human being. People don't trust people who abuse them. They they have to they have to no believe that I understand their lives. And they have to believe the vision I've painted for them of where we're going and why we need to get there. And so the I I've the thing I've learned is my lack of technology expertise hasn't hurt me. Because I've always had I've always inherited great teams. They might have been underperforming, underappreciated teams, but they've always been great teams. What I've got to do, I I use this example. I grew up in this small farming community in northern Utah, so I'm a real, you know, really steeped in the arts, right? I'm being facetious. But there's a difference between there are two important roles in any symphony. There's the conductor who's got the baton. And there's the concertmeister. The concertmeister is the lead violinist. Anytime you look at a symphony, the first person that's sitting furthest to the left on the front row is the concertmeister. The rest of the symphony follows the concertmeister. It's the conductor that knows who to bring in, who to take out. When they need more volume, when they need less. And so the analogy I have is when I'm asked to be a technology leader, to a certain extent I have to put my concertmeister violin down, trust my people that they'll know what to do, they'll know how to play, and my job becomes organization and direction. Have you gone into teams super technical, super smart, super effective technologically, but have struggled making that human connection and or figuring out the leadership relationship side and what did you do to to help with that? I would say in probably every one of my roles, and I've done these turnaround things nine times. Shortest one was a year, longest n seven and a half years. ⁓ what I found find is a a team who might be technically really good, but they have they don't have a relationship of trust with the rest of your organization. And part of that is you know, I say, okay, here's some here are the levers I pull when I do these transformations. One is we've got to get really good at delivery, because that's my that's the base of trust is credibility. If if the Team hasn't done well just in system performance, system reliability, system uptime, ⁓ project delivery, project performance. It's gonna be hard for the organization to trust them. They're gonna have low credibility. And once I hired a team, and the reason they hired me is said IT is a black hole. Projects go in and never come out. And I see that a lot. And then part of it is also just helping them understand. Our roles, even down to the service desk, our relationship roles. I've trained my teams on quality customer management down to the service desk. What does it mean to have a great service experience with somebody from IT? Whether you're the CIO, the CTO, the CISO, the database administrator, the storage administrator, or the PC technician? What does it mean? That's when somebody has a great experience because I'm gonna interact with, let's say, one company, we had sixteen hundred employees. I interacted regularly outside of IT with probably 40 of those sixteen hundred people. What forms their opinion of tech the technology department? Not me. I never interact with them that clo closely. It's the rest of my team. even down to the service desk. And so that matters to me 'cause our that relationship of trust can't just be with me. It's gotta be with the whole team. Any tools you found effective to get them customer service oriented, like any books or any or did you just go say, yeah, these are our customers, we gotta deliver well. Like how do you do that practically? Like what what does that look like? I th that's a really good question. I think in some cases I've had the luxury Of inheriting teams that the company didn't trust, the organization didn't completely trust. And so they they kind of recognized that they were in a bit of a relationship hole, a trust hole, a credibility hole. And and so and and I've always treated everybody the same. What I mean by that is ⁓ I I'll give you a quick example. One place the president, when he hired me, I inherited a team of six people. And he said, Neil. None of them are any good. You have my pre-permission to fire all six of them. And I said, thanks. Let's kind of see how it plays out. six amazing people. Three of them are CIOs today. So rather than fire them, it was just a matter of here's let's be honest with ourselves. Let's be honest. If you want, I've sometimes used some customer satisfaction surveys. Because sometimes I've had teams doubt. I don't think it's that bad. Let's ask our customers. Let's see what they think of us. You know, when you do a a an IT department net promoter score and you're at 20%, you got some room to grow. It's okay to recognize. But but the whole thing is wherever we are, we're gonna get better. That's the goal. This is just a baseline. And we're gonna get better. And here are the ways we're gonna get better. Because It's the same thing when I'm telling telling the organization we're gonna go from where we are to where we need to be. I create that same hopefully vision and credibility and trust with the IT department. Wherever we are, let's look at the what's happening around us. Even if it's not a transformation or turnaround. Technology changes every day. What capabilities do we need in order to guide the organization into a technology driven future? Are they do they like what do they say to say we've had bad leadership in the the past or our CEO won't invest in technology to make it so we can? Like and then how do you overcome those? 'Cause I mean, these people are people we've worked with f and they're great. Like they're running teams, they care about their teams, they care about their customers, which are the employees, they are geniuses. Like we're working with them and and then you What you've seen is you've been able to elevate that. Like what's usually the bottleneck that they're they have a difficult with that they need to that may be able to help? It could be any any of those things, Mike. One team, ⁓ the previous CTO was this tyrannical micromanager and just beat people up all day long. And like ⁓ one of the people I inherited, she said, We were living the Stockholm syndrome. We we didn't know how bad it was, we just kind of accepted that this was l reality. Cause I'm like, How did you stay here? When people would tell me these stories, this is what it was like. I'm like, why did you stay? It's like Stockholm Syndrome. You you love your abuser. I'm like, okay, whatever. And sometimes it's the organization won't invest. So really it doesn't matter where the starting point is. It's let's ask ourselves. And that's why it's important to understand and align to What the goals and priorities are of the organization. The organization needs to go from here to here. In some cases, we're going to inform the organization that we need to go from here to here. Okay, let's talk about what would it take for us to do that? What are we lacking today? What are the areas we need to get better at today? And it's, I can tell you, it's delivery. Like ⁓ this one, ⁓ Serious downtime problems. Serious. Okay. It's hard for people to trust us with their future if we can't keep the current systems up. Let's do some root cause analysis. Let's understand what causes the downtime. We were terrible at production change. I could, you know, you track it for a couple of weeks, you can see every time we made a production change, the system went down. Okay, we we we're terrible at this. Can we just say we're terrible at this? Guess what? We can get better at this. The rest of the world's figured out how to do quality production changes. We're gonna get good at this. We got good at it. And after that, we never had an outage unless it was delivered by a third party. How'd you get good at it? So here we I rely on my process improvement stuff. So I'll let I'm gonna backtrack just a little. So we're gonna get good we're gonna get good at delivery. What does that take? I'm gonna train everybody in the organization on agile, because that improves delivery in uncertain when life's uncertain, iterative methods work better. I'm gonna train everybody on lean. Lean is the study of waste. Where's waste? What causes waste? The primary form of waste in IT is rework. If I do a failed production deploy, I have to redo it. That's rework. Okay, how do I avoid rework? There's there are four primary tools in lean to improve processes. So I train everybody on the forms of waste. Here are the primary four tools, and we're gonna get good at them. And then there are the what I call the ITL foundation. We're gonna get good at production change. We're gonna get good at service management, service definition of management. And we're going to get good at incident response and improvement. If we're good at those three things, over time, we're going to get better and better. A quick example. ⁓ one of the so I've got some very pragmatic tools. I was thinking about this because we're going to do this kind of the CIO university thing. I was thinking I'm putting the content for that together. I was thinking about one of the first the first session or the second session after the introduction is on improved delivery. And we talk about agile, lean and ITAL. And an example of this, bringing those together, is I call it proactive service improvement. So let's make sure we're capturing all of the incidents that are happening as reported to the service desk or our bug catcher or whatever we're doing. We once a month we get the entire group together, the whole team. Software engineering, system administration, service desk, everybody. Okay, let's look at, let's do a Pareto analysis of those incidents that have been. Let's pick one of the top two or three and ask ourselves, how do we stop this from ever happening again? I want to stop it. Okay, who needs to work on stopping this? Well, I need somebody from software engineering because it seems to be a software bug we can't find, we got a memory leak somewhere, whatever it is. I need storage administration, I need the database administration. Whatever the problem is, we try and figure out. Okay, how do I stop this from happening ever again? And I tell people, if you do that for six months. And knock down the top one or two every month for six months. Six months later, you're dealing with issues that no one cared about six months before. You know what I mean? You've just improved quality and delivery so significantly that one day the rest of the organization wakes up and says, our system hasn't been down in months. And then they blame me. They say that Nat Neil guy's a genius. No. All I did was get the team together and say, let's figure out how to solve this. That's ⁓ it's I hate to say it, it's an easy job 'cause I don't have to do anything. I'm that agile, is that lean or is that all those together? That's all those together. Yep. Okay. And then when you go into an organization, do they already have understanding of Agile and and lean and you're teaching them? And then how do you teach them? 'Cause 'cause People know of it, but I'm trying to think of our organization. Do we are we experts in lean? No. Should I go get everyone trained in lean? Maybe. Is is that I mean, we're is this official training or were you like, hey, we're just gonna I'm gonna train you on lean methodology, ⁓ lean thinking. Like how'd you do it over the years I've developed the content myself. Happy to share with everybody. I always do. Here's here are agile principles. When I go to an organization, like I inherited a large software engineering team once, they use agile. No, they were using agile methods, not principles. Meaning we have a stand up, we do sprints. Okay, that's a method. What are the underlying principles? Let's focus on the principles. Same with lean. ⁓ most organizations, especially IT organizations, I found lack a good understanding of lean. And so I developed years ago a training program in lean. It's short, it's easy, lean for IT. Same with the ITL, I call it the ITIL Foundation. It's okay, here are the things we want to get good at. So when I combine all three, it's okay, I've got an understanding of waste and continuous improvement, how to reduce waste and improve processes. I've got an understanding of agile because that improves delivery. And I've got an understanding of ITIL so I know what the goal is. What's the goal? I never have a failed deployment. I always find and resolve the root cause. You know what I mean? So the the the combination's been very helpful. But but that's been my approach. So we talked about improved delivery, and then you've also got to understand the engine that drives the business. Because I need to align to that. I need to make really good decisions about where we invest in technology and where we don't. I only want to invest in technology that advances the cause. What's the organization trying to improve? And what are the levers I can pull to achieve those from a technology perspective, to achieve those goals? And so I've got to do that. And at the same time, the other one is I've typically got to improve the culture. The culture oftentimes, no matter how good it is, and and I've become very non-judgmental, meaning Yeah, the previous CTO was a tyrannical micromanager, but that was more situational than personal. The president of the of the organization's a train wreck to work with. Okay, how are we gonna change that relationship? So I don't blame people, I just say, here's where we're going. Do you want to come along for the ride? And I build relationships of trust outside of IT. I'll give you this quick example. One time I'm sitting in the CEO's office. We got a board meeting coming up. And this is one early on in the organization. I've only been there for a couple of months. I'm still trying to help people understand who I am and how I operate. So I'm just finishing up a one-on-one with the CEO, and the and the CRO walks in. And she says, ⁓ Neil, I didn't know you were here. I said, It's fine. Interrupt. It's okay. And she said, she talked to the CEO. She said, Dave, I'm really having a hard time figuring out how to articulate this in my board report. And said, Well, show me. So she goes to the whiteboard and I said, I got an idea. What's that? I said, what if you did it this way? She looked at me, she said, That's perfect. Because in her mind, I was the IT guy. I wasn't the business guy that knows technology. So I've got to change that perception that whoever the CIO, CTO, VP of IT, CISO is, that they're a technologist. I'm a business or organizational leader that understands what it takes to deliver results for the organization. I am completely, I don't want to say clueless. Technology is a means to the end. It's not the end. Any examples of where you saw a very technology focused up and coming leader, a director or IT professional, making that transformation into leadership, into understanding the business. How did they do it? I'll give an example. ⁓ someone who's near and dear to my heart. So I find I'm pretty biased. Because I look at my career where I wasn't really a technologist, an IT tech and I an information technologist, and I think I've had a reasonably successful career as one. and I did that because I understood the business. My first big project at Franklin Covey was to replace all the homegrown software with it with one of those massive ERP systems, which forced me to learn business processes. I don't know how many times, I don't know how many ways. I can look at the accounts receivable process and say, this is just broken. I'm sorry, your process is broken, not the technology, your process is broken. Because I learned everything doing ERP. And so a really good IT ops guy. He owns the network team, the sysadmin team, the storage team, the cloud team. He's a technologist. And he came to one day and he said, Neil, because I always I always do career development conversations with my team. And I think that's important for anybody to do with their team. Find out what their goals and aspirations are from a career. Because my job is to build my team and build their capabilities and build their future. And so he's you know, and I kind of challenged him, okay, what do you want to do? What do you want to be in three to five years? Because let's chart that path for you. So he came to me, he you know, I've been thinking about that. I want your job. And I said, first of all. You're too smart to want this job. If you're really as bright as I think you are, you don't want this job. It's a nightmare, it's a train wreck. This is I look at me, I'm only 35 years old. You can see what it's down to me from a health perspective. I said, okay. I said, it's gonna be a challenge for you because you've grown up in IT ops. You know system administration, storage administration, network administration, database administration. You know that's your life. This is gonna be different. Are you ready to make that change? He said yes. I said, okay, then here's the path forward. What I'm going to do, and again, this is my own bias. Next time there's a large scale, I call it put the business at risk project that isn't a technology project, but an application, a business system, some type of project, I'm going to ask you to run it. It's outside your wheelhouse. You're gonna learn a lot. So, but I'm gonna be there to help you, don't worry. And I said, between now and then, there we've got a project like that's coming probably next year. It's probably nine, twelve months away. Between now and then, I need you to get comfortable with the executive team, the teams of the executive team, and the board of directors. Because if you're gonna run this large-scale, put the business at risk project, You're gonna be the one at a quarterly board report giving the report on it, not me. So let's talk about, let's collaborate. What could we do that would help you with that exposure? So we kind of charted out a path. How do you build that relationship? And so, okay, I spend a lot of time with the members of the executive team and their teams. What are some areas where you could spend time with the executive team and members of their teams? And I'll make I'll get that going, but then you've you'll run with it after. And so you've got to be very intentional about that. So what is he doing today? He's the CIO of a company. It worked because he wanted it to work. And then my part of the agreement was we're gonna create opportunities for you to develop those skills and get confidence in those skills. So it works. Any examples of how you got I mean, I think people know they need a relationship with the executive team, but it's just not their top priority. And like how to do that, right? Like you sketched out a plan of how to do that. How any things that worked one or two ways that that actually looks in practice? Is it like, hey, go say hi to them? I mean, well in this case, in this case, we were doing a massive modernization. Now, the rest of the organization knew a little bit about the or ⁓ the modernization, but it's very technical, right? We're gonna migrate off of this legacy database technology onto this other one. We're gonna migrate off this legacy operating system, this proprietary operating system, to an open one. And so we had these projects that the organization was aware of. And I said, okay, he's running this modernization. He's really leading the point on this modernization. We are migrating workloads to the cloud as another example. Okay, ⁓ let's just raise the level of transparency and reporting. We can invent a reason how modernization is going to affect and benefit the finance and accounting organization. Hey, let's go talk to, let's ask the CFO if we can spend some time with him and his team talking about what they should expect to see from this modernization. Hey, let's go make some time. Let's make an appointment and meet with the marketing, the director, the VP of marketing and her team and talk about here here's what we're doing, and here's what you should expect to see. And I'd like to come back once a month and just give you a quick 15-minute update at the at your monthly staff meeting on where we are with the modernization. First you make it important to them. Here's how you're going to benefit from the modernization. And then I just want to come back and give you an update every f every month. So you know we're on track or off track. And if we're off track, what we're doing to recover. Because ultimately that's what my communications are. And then once you've once you've made that introduction, then when he's talking to the finance and accounting team. They say, well, what about this? ⁓ that's a good question. Let me come back within to you next month and talk about what we there's a that sounds like an issue for you. Let me come back next month and let's talk about how what we might be able to do about it. So they're shifting from reporting to solution definition of management. And it's just, you just have to be intentional about it, which I think, and again, this is the other thing I've learned in my career. I cannot be the heroic leader. Instead of being the hero, I have to be the figurehead. On my business card, it should say CIO slash figurehead. Because my team is highly capable. I can let them, I just I tell people: once we've figured out what the right things are to get done and the right way to get things done, you should never need to ask permission. Just go. Are we doing the right things? Are we doing them the right way? Once you've got that. I want to get rid of the permission culture in my life. No one should ever need to ask permission. They might ask for advice, they might ask for input, but you should never have to ask for permission. One of the best books I've ever read is Turn the Ship Around by David McKett, where he takes over the worst submarine in the Pacific Fleet and he gets rid of the permission culture. Instead of Captain May I, it's Captain I'm going to, unless you tell me not to. And he turns the whole culture around because the other the last one we we haven't touched on much is I want this culture where I want to lead th I think of it this way. Think of the capability and the capacity. If I've got a team of twelve people What is our capacity? What are our capabilities if I'm the only one getting capable of getting anything to done? As opposed to thirteen people that can get stuff done. You want to turn around the attitude and the credibility for an organization? One of the best experiences in my life, the the place that hired me and when they hired me, he said, y you got six people, fire them all if you want. And IT's a black hole, project's going to never come out. I started in August. It was about February when the the executive team came to me and said, Neil, you gotta slow IT down. We can't absorb all the stuff you're getting done. I thought this might be the crowning achievement of my career, where we went from nothing ever gets done and you've got six idiots as your team to you gotta slow down. We can't do it. We can't deal with what you're getting done. Now from a from a com purely selfish perspective, At that point, I owned the organization. I could do whatever I wanted. Yep. Now I didn't. I still wanted to do good stuff and serve serve the organization. But I from that point on, it was almost impossible to do wrong. Because that we had changed the outcomes. And we did the same way we've talked about. Let's get really good at delivery, let's get really good at relationship management, let's get really good at trust. Let's let's do the right things and do them the right way. And let's be honest with ourselves. And one of the things that the most frustrating part of my career is sometimes encounter people on the team who are change averse. Well, Neil, no, we really can't do that. Or no, we've been it's been successful for the last eight years doing it this way. I don't know why you want to change it. I'm like, of all the professions in the world. Who's seen more change in the last thirty years than IT professionals? No one. No one. We should be the most change embracing group of people in the world. We should. And it's anyway, so that's always been And I I think you are. And as I've observed, the best learners, and really I have so much respect for all the IT professionals and CIOs in this. And and which is really why we want to create this. this podcast, these conversations and we really appreciate everyone joining CIO and Scripted. We're gonna continue this conversation and talk ⁓ another time, but we're going to continue and I I jotted down some notes. I wanna talk about kind of your career development philosophy. I think that's something that we'll wanna talk about. Culture, like really how I wanna dig deep, like how do you establish the culture? How do you determine it? Is this is this vision boards and putting up quotes or is this like just Talking to the team and like how you really do that. Sure. But I love I love your story and what you've you've taught us