Latest / CIO Unscripted / CIO Unscripted: Jeff Stott on Buy-In and the Replatform That Paid Off
Transcript
- speaker-0: And it was kind of a lesson for me of like you gotta remove the ambiguity and just be very clear about the mission and say, look, for us to realize the synergies of this MA deal, I'll give you the benefit of the doubt that you have an amazing system. And and that there's probably things it does you know it can do that that our system can't. But it doesn't matter. Right now, the only goal we have is to figure out how to get the data out of your system and and move it into our system. Don't try to appease with, okay, we'll look at it. And it was just the right thing to do to just say, this is what we this is what we've got to do. Let's do it. speaker-1: Welcome to CIO Unscripted. the conversation we have with technology leaders a little bit off the cuff, little bit unstructured about their careers and what they feel has made them successful. guest today is Jeff Stott. He's the CIO at Welltower. Prior to that, he was the CIO at Extra Space Storage and has a whole bunch of great technology leadership experience. So let's start, Jeff. If you just kind of give an overview of your career, ⁓ how you got started, where you started, how it evolved, and how did you end up as a CIO for some rather large and significant organizations. speaker-0: Yeah. you know when I first started in technology, I was actually in college and I was a finance major and I was working at a bank and I thought well maybe that'll be my career path. I'll just kind of work my way up at the bank, right? And do finance. And I was kind of bored. I I didn't feel like it was dynamic enough. ⁓ and and I always liked technology, but I wasn't I didn't consider myself somebody who was gonna sit behind a desk and code all day. And so I didn't want to do computer science. My personality was kind of more business oriented. And somebody said to me, Well, have you ever heard of a degree or a career path that's called information systems or some people called it MIS? And I said, no, tell me more. And they're, you know, they're like, well, it's kind of a degree that's the combination of both. And I'm like, that's exactly what I want to do. I want, I want to be at the intersection of helping businesses adopt and use technology to improve their business. And once I figured that out, that that was a thing, ⁓ when I was young, I was like, that's exactly what I want to do. ⁓ so back then this was like late 90s and everybody was trying to figure out the internet. ⁓ and so I I when I was started that degree speaker-1: you don't seem old enough to have been figuring out the internet. speaker-0: Yeah, it was it was fun times because everyone was like, hey, we need to have a website and we need to sell our stuff online. And and every business was trying to do that. It it kind of reminds me of now with AI, how every business is trying to figure out AI. It was kind of felt like that energy then. I was really excited about it and I was reading books constantly and and that's how we learned back then is with with actual real physical books. speaker-1: But you speak. speaker-0: And I was having a lot of fun with that. I was so excited and and I would so I was trying to learn as much as I could and I wanted a job while I was going to school where I could practice what I was learning. And so this tiny little company hired me. They were probably you know, they'd only been in business ⁓ probably five years, and they were a small retailer and ⁓ they were starting to do their consumer products and And they're like, hey, we need a we need a website. We need to sell our stuff online. And so I helped them figure that out and you know, built shopping carts and things like that that was was now now just, you know, you just buy it. ⁓ back then people were building them. And And then they're like, okay, that's great. Now we need to hook it up to our ERP system. And I'm like, well, what's an ERP system? And I would I had to figure out, you know, how their accounting system worked. And and they're like, ⁓ well we're we're gonna need a a newer one because we're getting bigger. We've doubled in size in the last couple of years. So ⁓ and now we need a warehouse management system because we need to be able to connect The e-commerce to the orders to come in and fulfill it in the warehouse, and then we need to account for it properly. And so I had this great education. Where I had all this autonomy, very little direction. I didn't really have a good mentor, but I was kind of like figuring it out by myself. Like And and occasionally I would run into people and they'd say, ⁓ this is what you need to do, or this is how you need to do it. So I I had a very broad kind of baptism by fire of like how to leverage technology. For it was a pretty small business though. So I f I felt like I was adding a lot of value and I was really cheap labor. And I was learning a ton. ⁓ So from there, my career just kind of progressed where each role I took, it it was kind of interesting. It was, I didn't intend it this way, but it was a significantly larger company each role I took, and just kept adding more responsibility. ⁓ and until eventually I ended up at extra space, which was kind of a a very career A bigger career trajectory than what I had had before working kind of for smaller businesses. ⁓ you know, extra space was an SP 500 company and and ⁓ publicly traded, and so had a lot of ⁓ more opportunity there to grow. ⁓ they I think quadrupled in size while I was there. So it felt like this rocket ship. That I was on where they were adding new extra space locations about every business day. And they were at a point where they needed to replatform their technology completely ⁓ to prepare for that growth and that cycle they were on. And there was no way to go buy an off-the-shelf self-storage enterprise platform. We we had to Do it ourselves. And I think if they could write a check and buy it, they would have. But they also considered it ⁓ the proprietary nature of it was important to them because they considered it technology, a bit of a competitive moat when it came to how we would do dynamic pricing or how we would ⁓ acquire customers online. And the whole platform and engine became a way for them to almost s sell it to other. Property owners of self-storage and say let extra space manage this for you because we've got a technology platform and stack that you can't go buy. ⁓ and it it's going to make you a lot more money if if you came on our platform. So that was a really ⁓ career-changing opportunity I had there. speaker-1: Can I ask you a couple of questions about that? So the first one comes up is, how prepared did you feel when you were recruited by Extra Space Storage? I mean, and you talk about this significant jump up. Did you feel intimidated at all? Or did you approach it the same way you did back in your IS degree, meaning I'll read some books and I'll talk to some people and figure it out? speaker-0: You know, when I first came in to that role, I wasn't the CIO, I wasn't the CTO. And they hired me to implement ⁓ an ERP system. Yeah. And and it was just the accounting platform. And and they had it was one that I was familiar with and I'd already implemented it. And so I felt very comfortable coming in and my first year that I was there, I I I got this win under my belt and got to understand the organization and kind of establish trust with everybody that hey I I can help deliver a solution like this. ⁓ so it so I eased my way into it and then came the hey Jeff we want you to take on this really big replatforming and that was a big shift. speaker-1: I would imagine, I'm guessing, and you can tell me that I'm wrong, this re-platform required you to know a lot more about things you hadn't done before. I'm guessing software engineering, software architecture, enterprise architecture, things like that. So how did you get up to speed on something like that that's pretty different from what you've done in the past? speaker-0: Yeah. No, that that's very accurate. There w it required a whole new skill set and knowledge, you know, and DevOps was really coming into this scene and cloud computing. This was this was all like twenty ten early twenty tens. And so technology in general was shifting around that time to be more cloud based, more software engineering, landscape was changing with DevOps. And so I think I I learned a lot and benefited a lot from the the shift that was going on in in just broadly in the industry. And the way I got up to speed on that, ⁓ you know, we we would augment our team with sometimes some outside consultants who who had at least done some of that work before and and they were a few years ahead of us, right? And And so that was our way of of injecting some new thought and some new technical leadership into our team. We made some good outside hires because nobody who was currently on that team had that experience. You know, they they had experience on the current platform and they were excited about the new platform, but we had to inject some new thought into the to the team. speaker-1: Yeah, because it's not that unusual, because you're talking about 2010, how many of us had much experience with cloud services, cloud migration, cloud workload management and orchestration. So that's interesting. OK, so now you're in charge of this big re-platforming that becomes a competitive advantage. also, it sounds like you treat it like a commercial software package. speaker-0: Yeah, in some ways like we didn't directly sell it, but it became part of the product of delivering services to other property owners. And it was part of a kind of a bigger machine and a bigger package we were delivering. And so yeah, it had to be world class in that industry, right? It had to be ⁓ something that we would be willing to market and say speaker-1: You're using it to win property owners. Exactly. Interesting. ⁓ Okay, so I'm guessing the replatforming worked well. So how did that evolve into the CIO role at Extra Space? speaker-0: Yeah, it it was ⁓ I would say the platforming went well, like it it but it took a long time. I think we were naive about how long that would take and I certainly ⁓ thought we could do it faster than it actually happened and ran speaker-1: us, just between us and everybody on the podcast, how long did you think it would take and how long did it take? speaker-0: I'm embarrassed to say this. So but so I was I was being new to the industry, new to the company. I was convinced that we could that we could have an MVP within a year. And I thought, hey, you know, a lot can get done in a year. That MVP took about two, two and a half years. and the full rollout speaker-1: That's the it is. speaker-0: of having a complete mature solution and all stores on it was about five years. speaker-1: I say that's better than me. My biggest transformation, which will be done in three years, seven and a half years later, we're crawling across the finish line. speaker-0: But but one of the valid most validating things about that replatform was ⁓ came a couple years after the five-year stretch where extra space acquired a large competitor. And and it was it grew the company fifty percent overnight. And what was so validating about the work that had been done on that replatform was being able to acquire that company. that was half our size, eleven hundred locations, fold them into our platform in a couple of weeks and not speaker-1: That's crazy. speaker-0: materially change our economic like we didn't I didn't have to buy licenses. I our cloud spin went up, you know, like a little bit, ten percent. But we were we had so much more volume on the platform to where that the scale and just really proved out that it was the right decision to replatform and that the benefits of of that we're now getting the fruit of all that replatforming work. And that was kind of in my mind the the the moment where it was like, Wow, I'm so glad we went through this pain. Those were a tough, you know, three to five years of of slogging through this, but look at where we're at now and that that was really validating. speaker-1: Yeah, look at the capability of because, Bill, because I can't imagine, I've been ⁓ in charge of a number of mergers and acquisitions. The thought of an integration within a few weeks just is amazing to me because it's usually a bit of a struggle to be honest. speaker-0: Yeah, and we have the benefit of look, they all kind of run the same way. It's very homogeneous. And so it's kinda like speaker-1: can say that about anybody. Everybody does accounting, but then somebody digs in their heels and says, well, I'm not going to change the way I do accounting. speaker-0: Yeah, and I kind of learned through that merger too. You know, we got on with their IT team ⁓ you know, in the first few weeks after it was announced, and they wanted to sell me on their platform. And it was kind of a lesson for me of like, you gotta remove the ambiguity and just be very clear about the mission and say, look, for us to realize the synergies of this MA deal. I'll give you the benefit of the doubt that you have an amazing system. And and that there's probably things it does, you know, it can do that that our system can't. But it doesn't matter. Right now, the only goal we have is to figure out how to get the data out of your system and and move it into our system. And because the synergies of this transaction are all about getting us on the same platform so that we can Have an operating platform that's unified and we can drive, you know, revenue and expense reduction and we're not gonna have a bake off. And as soon as I said that, their face dropped a little bit, and then they said, I get it, and I I support it. And they just moved forward with us. And it was it was really a good lesson for me on like, don't Don't try to appease with okay, we'll look at it and it was just the right thing to do to just say this is what we this is what we've gotta do. Let's do it. speaker-1: And you did a good job of articulating why you were taking this approach in a way that they could understand and make sense. Yeah, that's a good point. speaker-0: Then we back later and said, Okay, show me the cool things that we need to build in our Yeah. And they did. speaker-1: Now it's a great feature. We didn't have time to deal with it before, but we can add it to our backlog. speaker-0: Yeah. speaker-1: So as I think about your career, I think about your team making the case for a change of direction, a change of platform, a change of something. How do you convince the organization first of all that it should be done and then it should be done the way you want? You think it should be done. speaker-0: Yeah, you know, I I try to take when it comes to making a case for major transformation, this might sound counterintuitive, but I actually don't try to push or make a strong case. What I try to do is is talk to the all the business stakeholders, executives, and help facilitate a conversation where we collectively understand it and kind of organically that case starts to build versus me saying, hey, I've I've got this master plan and I want to sell you my my vision. I I take a little bit different approach because I've seen that done before and it usually doesn't end well because it becomes Jeff's plan or Jeff's vision. And I find that it's got to be a collective vision that I didn't strong arm or or you know try and push people towards because that you know these are hard and and there's always a point where people will question along the journey are we is this worth the effort is this worth the expense is this more expensive than we thought and and I find that if if they're part of that decision process and they come to that same conclusion there's less of that friction along the wake, right? But it takes longer. It takes a long time to build consensus, but I think it's really important. speaker-1: Okay. So, talking about your career, thinking about your career, what do you think have been some of the reasons that you've been successful in your role, in your various roles? What would you say are your critical success factors? speaker-0: I can tell you times where ⁓ maybe I've learned from some mistakes that I think I've tried to then ⁓ be mindful of so I I can be more successful. So the I guess the way I'll answer that is like where I've gotten into trouble, and this kind of goes back to my earlier statement, is when I think I've got all the answers and I'm trying to convince people that that To get on board with my plan versus being genuinely asking what are the problems, what do you think the solutions are, and acting more like a facilitator than a I'm gonna mastermind this whole thing and I'm gonna come up with a solution. And anytime I've behaved that way, because I think sometimes we Sometimes in technology, that's what we get a lot of satisfaction from is coming up with the solution to everything and and and you know, doing the engineering and and I and I've realized like the higher you get in the organization, if if you don't bring everybody along and bring your team along in the solutioning, you're you're gonna be in trouble. Like there's always And and and I realize too, like, there's always somebody who's gonna know more than me about a particular aspect of like, here's the database we ought to use and here's why we need to use that. And and the tactician like very lower level kind of tactical decisions, the more I can stay out of that and keep keep the team focused on the end goal and why and not try to mastermind the the solution, that's where I think the success comes from. Because people get on board, they want to support me, it's their vision too. I I can stay above some of the the noise of the detail, you like fine-tuned details of every decision. I don't need to to bog get bogged down with some of these things. And that I think has helped me earn more trust and and not be a barrier, right? And not be the bottom. speaker-1: Seems to me your roles represent a decent amount of change. That's what they hire you for, that's what you bring. You inherit a team. How do you get that team to willingly come along with you? And are there certain things you do to develop the skills and capacity and capabilities of the team? Because again, you're trying to do something not only different, but also it seems like in the past, what you've introduced is you've got to the enterprise scale of your solutions as well. So how does that work with your teams to get them to be part of this transformation? speaker-0: Yeah, that's a good question. I think I'm still figuring that out in some ways. Because I I think sometimes I've I'm successful at this and sometimes I think wow I could have done that differently. ⁓ but i in my mind, like if I put myself in other people's shoes and like where where have I wanted to sign up willingly for for something and where where have I resisted, it's always when I'm involved early and I'm part of the solutioning and And if I'm part of that process, then I feel ownership and it's mine. And when when I'm not part of that process, it's like, well, that's you know, the CEO's project or that's somebody else's deal, and I'm just kind of supporting cast and I'm not bought in, I'm not as engaged, I'm I'm I feel like I'm more just alone for the ride, but I don't feel like I own it ⁓ at the same level. And so To me, that that's ideally what I try to do is is maybe articulate the problem, get them involved in what's the s options, the solutions, the how. ⁓ because I think that's what technology people really enjoy is when they get to be part of the solution and I just have to remind myself that the the nothing's more irritating than someone coming and saying maybe not even saying the problem, but they're just saying, we're going to implement X. And you're like, great. why? And how did you decide that? And and I have to remind myself that. The that that that irritates me. It's going to irritate other technology folks if if I come with the same approach, right? And just like I'm an order taker, like just just do this, you know? speaker-1: It's great thought. So as you think through career, what have you enjoyed? Let's start with what have you enjoyed the least? Or the only way to ask it, what have you disliked the most? And then we'll ask what you've enjoyed the most. speaker-0: Ha ha You know, ⁓ that that's a really good question. I think one of the hardest we we've kinda touched on some of the things that are like the harder parts of the role I think are are getting alignment and getting ⁓ enough consensus to be able to execute and I get a lot of satisfaction from doing that. But sometimes it is the difficult part of the job and and especially when you're dealing with maybe one or two individuals who it's like there there's no amount of you know reasoning or ⁓ logic behind this. We're kind of at an impasse. And and maybe that's someone on my team, maybe it's another peer, maybe you know, th it's it's a vendor, and and you just have to do the un like the hard work of saying, hey, we're at an impasse, what are we gonna do about this? And that could ⁓ end up in a variety of options, right? That's not fun. ⁓ but it's necessary, right, to make progress. speaker-1: What have you enjoyed the most? speaker-0: I think some of like what I've really enjoyed is seeing the businesses that I'm involved in win and knowing that I had a a part in it and knowing that we had success together as a team. That is that's why I show up every day. That's what I really care about, is like the kind of impact that we can have. That's why I brought up the merger story because because you know, it was one of the the largest ⁓ and A deals in in in Utah, I think ever. And to know that I had a little piece of of ⁓ the success in that was was really fun. And then knowing that my team really they're the ones who ⁓ delivered on that. And that that's fulfilling. I like that. speaker-1: Any advice for a technology leader or a person who wants to be a technology leader? ⁓ Career advice from Jeff Scott. They look at this and say I want to be like Jeff Scott. That's my goal in life, to be like Jeff Scott. What advice would you give somebody who's kind of mid-career, has some aspirations? What would you say to somebody who came to me and said and asked you speaker-0: Yeah. speaker-1: If I wanted to do things like you do, where should I start? speaker-0: Yeah, I think what I've at least what I think's worked for me or what I've tried when I've had success is when I actually take my technology hat off more and I just try to understand the or if the business lens or perspective and speak the same language and try to show that hey we're connected partners in this and we're not ⁓ Kind of an offshoot technology only focused ⁓ team and and and my leadership is more of hey we're we're all in this together. I want to demonstrate to you and also I need to understand that that what are the business problems that we're dealing with and it's not It's not always just a technology lens and I think this this role requires you to think that way and that's how you gain trust. All right. speaker-1: Thanks, Jeff. I appreciate your time. So here's what I've learned from talking with Jeff today. The importance of articulating why. you know, to the people who had this new system, quote unquote, imposed on them during the acquisition. was okay, here's why we're doing it. And then the why of developing a team, why do we need to make these changes? And then the other thing I've learned is that ⁓ the value and the importance of really understanding what on the business side, and I always hate talking about the business side from the technology side, because it's hard to separate the two, but my peers, my business peers. speaker-0: Mm.