About this conversation
A CIO Talk Network conversation with John Conley (State of Colorado) and Bruce Goodman (Humana), hosted by Sanjog Aul. Recorded August 2008.
How much IT consolidation is enough, and what kind of consolidation delivers the most value to the business?
Consolidating IT infrastructure, applications and data can control costs, but the harder question is how much consolidation is practical. Push it too far and you risk a lethargic, monolithic IT with a lot of inertia and intertwined critical parts that require meticulous synchronization.
This conversation looks at where consolidation pays off and where it starts to hurt: which functions clearly belong under central management, when application engineering should stay close to the business, how to make the case to executives and to staff, and how to keep the organization nimble and compliant while the pieces are being pulled together.
What the conversation established
John Conley of the State of Colorado defined consolidation as logical rather than physical: centralizing oversight, standards and processes rather than relocating people. Bruce Goodman of Humana framed it as centralization under shared services, saying the network, data centers and infrastructure almost always belong under common management, while application engineering can sit in the business when operations are diverse. Goodman argued the primary drivers are business continuity, disaster recovery and security, not cost, and that a shared model can still be agile through a strategic consultancy that engages each business area. Conley described Colorado’s 2007 legislation that pulled 16 departments and 1100 employees under one office after 92 of 100 legislators voted yes, its plan to cut 39 data centers to three or four, and its use of budget ranges, a savings fund and career mobility to sell the change. Both stressed executive sponsorship, a strong PMO, communication and vendor management, and treating people so no jobs are cut. The open problem they named is unpredictable federal and state mandates arriving mid transformation.
Contributors
- John Conley, Deputy CIO, Governor’s Office of Information Technology, State of Colorado
- Bruce Goodman, Senior Vice President and Chief Information Officer, Humana
Moderator: Sanjog Aul, Founder and Host, CIO Talk Network
On this page: Key takeaways · Chapters · Explore more · Transcript
Key takeaways
- Consolidation can be logical, not just physical. John Conley of the State of Colorado defined IT consolidation as centralizing the oversight and management function rather than moving people to one location, so standards and processes stay the same across the organization and every network and database administrator is dancing to the same tune.
- Infrastructure is the clear case to centralize; application engineering is the judgment call. Bruce Goodman of Humana said the network, data centers and infrastructure almost always belong under common management, while whether to put application engineering in shared services or leave it in the business depends on how uniform or diverse the business operations are.
- The primary driver is not cost, it is continuity and security. Bruce Goodman of Humana said that outside the infrastructure, cost cutting is not the main reason to centralize; business continuity, disaster recovery and security matter more, especially in a regulated industry like healthcare where you have to protect members’ information.
- Colorado pulled 16 departments and 1100 employees under one office in an all or nothing move. John Conley of the State of Colorado said the state passed legislation in January 2007 that brought 16 executive branch departments and 1100 employees under Governor Bill Ritter’s Office of Information Technology, with 92 of 100 legislators voting yes, because shadow IT organizations would undermine accountability.
- Sell the change with ranges, a savings fund and career mobility, not a single hard number. John Conley of the State of Colorado said the state gave budget ranges rather than exact figures out of a 250 million dollar budget, set up a fund to reinvest any savings, and used career mobility for IT staff and a cut from 39 data centers to three or four as selling points.
- Win the people by controlling the paychecks and cutting no jobs. Bruce Goodman of Humana compared a gradual rollout to trench warfare and argued for moving everyone under the shared services organization at once while telling staff no job is being cut, and John Conley of the State of Colorado described answering am I going to lose my job 900 times through town halls, a wiki and newsletters.
Chapters
- 0:00 Introduction: how much IT consolidation is enough
- 1:32 Defining IT consolidation and centralization (John Conley, State of Colorado)
- 3:14 Which functions to centralize, and application engineering (Bruce Goodman, Humana)
- 5:13 Colorado’s 2007 consolidation and building maturity (John Conley, State of Colorado)
- 6:32 The real drivers: continuity, security and staying agile (Bruce Goodman, Humana)
- 11:01 COTS solutions and configuration over custom builds (John Conley, State of Colorado)
- 15:36 Big bang or a gradual approach
- 18:12 Trench warfare and moving everyone to shared services (Bruce Goodman, Humana)
- 21:58 The business case: ranges, savings and career mobility (John Conley, State of Colorado)
- 29:35 Communication and keeping the crew’s morale up (John Conley, State of Colorado)
- 32:25 Who owns the risk if consolidation fails (Bruce Goodman, Humana)
- 44:57 A readiness checklist before you consolidate (John Conley, State of Colorado)
Explore more
- IT Modernization: Why now? And how?: Gopal Khanna, Chief Information Officer, State of Minnesota; Peter Gapp, Vice President and CIO, Siemens Canada
- Infrastructures in Flux: Bridging Technical Evolution with Business Ambition: A CIO Talk Network think tank with Michael Roberts (Utica University), Rajiv Rao (Zones) and Raj Polanki (Vacker Chemical Corporation USA)
- Marrying Legacy Systems to Modern Marvels: Helen Norris, Chief Information Officer, Chapman University; Hardik Bhatt, Chief Executive Officer, SDI Presence
- Bimodal IT: Challenges and Lessons Learnt: Sahal Lahar, Executive Vice President and Chief Information Officer, Brooks Brothers
Transcript
Introduction: how much IT consolidation is enough 0:00
Sanjog Aul [00:00:00]:
Good morning and welcome to CIO Talk Radio.
Sanjog Aul [00:00:26]:
And we have Bruce Goodman, who is the Senior Vice President and CIO with Humana.
Sanjog Aul [00:00:46]:
So the topic today is something that is going on. We are going at warp speed to consolidate and do other things with respect to IT so that it delivers more value to the business, and in the first place, how much IT consolidation is enough? We do it with security, we talk about other things, so too much of anything is not supposed to give you the best returns. So to some extent the topic is going to touch different areas pertaining to IT consolidation. What kind of IT consolidation makes the most sense and where can consolidation provide the most bang for the buck? And before we do that, how do you define IT consolidation, because frankly, there are multiple people with multiple definitions of this.
Defining IT consolidation and centralization 1:32
John Conley [00:01:32]:
Thanks, Sanjog. To answer the first part of the question, how does Colorado define IT consolidation, we would define it more as a logical consolidation where you’re centralizing not necessarily the people in a physical location, but rather consolidating and centralizing the oversight and management function, so your standards are the same and your processes are the same throughout the organization. If you have network administrators or database administrators, they all should be dancing to the same tune, so to speak.
Sanjog Aul [00:02:05]:
So, Bruce, what do you think?
Bruce Goodman [00:02:06]:
I would agree with what John just said. I’m more familiar using the term centralization, where it means putting the IT functions, most of them, under a central authority or a shared services environment to better maximize the utilization of both the non personnel and personnel resources. I’ve been around the IT industry for over 35 years and I’ve gone through quite a few centralizations and decentralizations over time, and I think where most people come down today, when you start looking at various IT functions, certainly the network function, the data centers, the infrastructure, there would be very few examples where it wouldn’t make sense to centralize under common management those functions. You don’t want an organization that has those functions becoming redundant and controlled in different fashions,
Which functions to centralize, and application engineering 3:14
Bruce Goodman [00:03:14]:
not only are you exposing yourself to cost issues, but also business continuity, disaster, backup, recovery and security issues. Where you get a little bit more of a trade off is whether you put application engineering, that is program development and maintenance, in that shared services model, or you leave parts of it in the business, and that to some extent depends on the structure of the business. The more uniform the kinds of services and things that the business does, the more it would suggest that you put those resources, the application engineering, in shared services. The more diverse the business operations, you might go to a model where that application engineering is in the business functions or strategic business units. But back to John’s earlier point, you’d have a very strong set of methodologies, processes, controls, so that everybody was dancing to the same tune, so you didn’t wind up with a whole bunch of different technologies that, if you needed to consolidate information in data warehouses, for example, it would become problematic.
Sanjog Aul [00:04:30]:
So would you not think that, Bruce, based on what you said just now, maturity in an organization does take time? And what comes first, a chicken and egg? Would you get maturity in an organization first, or would you get the consolidation exercise going as soon as possible for the maturity to be identified, at least the weak areas to be identified, and then work deliberately to fix those areas so that we don’t have to unconsolidate or consolidate again?
Bruce Goodman [00:04:55]:
I always think, if you’re not already there, you should consolidate as quickly as possible or centralize as quickly as possible. It’s much easier to drive to the various maturity levels when you’re centralized than when you’re decentralized.
Colorado’s 2007 consolidation and building maturity 5:13
John Conley [00:05:13]:
Sanjog, I would concur greatly with Bruce that an organization, if it wasn’t centralized already, would need to take quick steps. In Colorado, when we came on with Mike Locatis, the State CIO, and Governor Ritter in January of 2007, we quickly realized with 16 departments doing their own stovepiped IT, there was no way to move the organization in one direction without a lot of lurching and fits, so we passed legislation immediately to pull that under one office, the Office of Information Technology, under the governor’s leadership. Without that, I don’t think an organization can ever get to a maturity level of any substance.
Sanjog Aul [00:05:57]:
So when we have done this in the past, we have tried to decouple the whole system and make it more plug and play, and get as many systems as you want in a heartbeat, connect them and then go along doing your business, and that was actually very much appreciated because it made the organization nimble and you were able to react to changes fast. Now, basically it could be cost cutting or another form of efficiency that you could derive from consolidation, but unknowingly, are we going and shooting ourselves in the foot to remove that nimbleness that we had, Bruce?
The real drivers: continuity, security and staying agile 6:32
Bruce Goodman [00:06:32]:
I would say this. First of all, I’m not sure cost cutting, except in the area of the infrastructure, is really the primary driver. I think there are more important issues around business continuity and disaster backup, recovery and security, especially in industries where privacy, like in healthcare, is so important. You really need to have those things in the shared service so you know you protect your members’ information adequately. The thing that you can do, again it depends a little bit on what kind of company you’re dealing with, but shared service IT, including application engineering, you can certainly be agile in that mode. You need to set up something that I call a strategic consultancy, which you can think of as a marketing arm or a business liaison arm back to the businesses, so that you go out proactively, engage the different business areas in a company and determine what are their key business objectives, and with your knowledge of IT, understand how IT can be leveraged to achieve those business objectives
Bruce Goodman [00:07:50]:
and in that way you get a couple of benefits. One, you get really good alignment with IT and the business area, just as good and maybe better alignment than if the application engineering was actually in the business unit. And you get sharing of good ideas. In other words, there are generic ideas that go across organizations, so you might pick up some particular self service idea, for example, in one business unit, and by having it in the shared service environment, those representatives of IT can then take it out to the other business units very quickly. In a stovepipe environment, it’s hard to spread that innovation. So you might have some that are way ahead in certain innovations, others that are way behind. This way, by having the application engineering shared and by having this liaison function, it enables you to spread those excellent innovations and initiatives across the entire enterprise.
Sanjog Aul [00:08:55]:
So would you say consolidation becomes a means to an end, that is, to have a much more progressive IT organization which actually comes closer to what the business wants?
Bruce Goodman [00:09:04]:
I believe it does, and what it also does, since IT resources, especially application engineering resources, are sometimes very scarce, it enables an enterprise view of prioritization, and that’s a very important piece of the overall puzzle.
Bruce Goodman [00:09:21]:
So you need a good prioritization scheme when things are shared, but it does enable you to move resources around to the areas of the business that can most benefit. If you stay in a siloed environment, everybody keeps their resources, and in some cases the things that particular business unit is working on might not be as important as what another business unit needs, and being able to have the fungible resources move around and get reallocated easily is a big advantage in terms of leveraging IT.
Sanjog Aul [00:09:55]:
So John, what have you seen? I think there was some major consolidation effort that was undertaken by the state of Colorado.
John Conley [00:10:02]:
Yes. As I alluded to earlier, we passed legislation that brought 16 executive branch departments and 1100 employees under the leadership of Governor Bill Ritter’s Office of Information Technology. We’ve seen, and it’s refreshing to hear the same from the private sector with Bruce, that a large entity in 1980 or 1990, if we were to try, knowing what we knew then, I think you would have got more of a bureaucratic morass out of your IT organization. But we’ve learned those lessons from those years, and now I think a large IT organization can be more flexible and nimble in 2008 than in years past, for all the reasons that Bruce just mentioned. But also, in a state government we have 49 other peers whose business practices are slightly different. Every state issues hunting licenses, every state issues driver’s licenses,
COTS solutions and configuration over custom builds 11:01
John Conley [00:11:01]:
and so we’re seeing a resurgence, in a good way, of COTS and MOTS solutions, commercial off the shelf or modified off the shelf solutions, and what we’re focused on in Colorado is less a hardcore development of applications and more configuration of those systems, and how they can be configured to meet not necessarily wholly different business needs, but just slightly different, and how, with some slight configurations, you can make a technology that was supposed to be working only for hunting licenses five years ago also work for issuing just a regular permit, maybe to a park. That’s what we’re looking at as we move forward, and that does allow us to be more nimble because we don’t need to release an RFP necessarily, or request for proposal. We can use technology we’re already familiar with, just in a different way, and that allows the business to meet their needs much quicker than if we had to custom develop something or go out and procure an entirely new system, not to mention, as I think Bruce was pointing out, the fact that then I have to train them in a new technology.
John Conley [00:12:15]:
If I already know it and I can reapply or reengineer how it’s used, then I already have the staff on hand. I’m much more nimble as an organization.
Sanjog Aul [00:12:27]:
Let’s take a quick break. We’ll be right back after these messages, and let’s see the approach that would work when you take on the centralization, in Bruce’s words, or consolidation related initiative. Would you take a big bang approach, or would this be more of a gradual, behind the scenes, housekeeping kind of task, smaller tasks that you can achieve over time? What particular approach would work better? Let’s stay tuned, we’ll be right back.
Big bang or a gradual approach 15:36
Sanjog Aul [00:15:36]:
Welcome back. So we are talking about IT consolidation and centralization. Which approach would work better, a big bang, major hoo-ha about it where everybody’s getting together in the boardroom and saying we’re going to do this, and then trying to sell it to the top guys, coming up with a huge business case for them to shell out a million dollars or more, or a simple, gradual, piecemeal, behind the scenes housekeeping type of task that is taken out of the petty cash, if you will, of the IT budget? What would work, not only from a financial sponsorship standpoint, but from the very fact that it has to be done? So how much in the limelight should this project be?
Sanjog Aul [00:16:22]:
John, let’s hear from you. What have you guys done?
John Conley [00:16:25]:
We went for the all or nothing approach under our governor. We said, if we’re going to be responsible and accountable for the output, we also need to be responsible and accountable for the input, and we were not in a position where we felt we could allow for shadow IT organizations. Once you go to a consolidated or centralized infrastructure of management, then that’s the focal point, and any success or failure is going to lie at the doorstep of that organization. Knowing that, the only way I feel an IT organization can survive and not be blamed for every little nuance that wasn’t in your control is to have some type of complete control. Now, I think we share that control with the business users and the business aspect of the State of Colorado and the government functions, but what they share is building the requirement. That’s their responsibility, with our help. They’re accountable to ensure that what we’re delivering is appropriate,
John Conley [00:17:20]:
but we have to have complete control over the organization as a whole so we can be accountable and move the ship forward.
Sanjog Aul [00:17:26]:
So you’re saying that the momentum could not have been achieved if you had not taken the big bang approach?
John Conley [00:17:32]:
No, I don’t think it could. There are too many pitfalls and little nuances, and the shadow organizations could create a downfall for you. You need the major push. You need executive sponsorship from your CEO in the private sector, or from your governor or the legislature in the state. Colorado was fortunate to have both. We have 100 legislators and 92 of them voted yes for IT consolidation, and then Governor Ritter of Colorado was a large proponent of this initiative and really helped push us over the top in some stressful times with the executive directors.
Sanjog Aul [00:18:11]:
Bruce, what do you say?
Trench warfare and moving everyone to shared services 18:12
Bruce Goodman [00:18:12]:
I agree with what John did. I don’t know if I’d exactly use the term big bang, because that has some pretty negative connotations in terms of how you go from one system to another, and you think of an atomic bomb going off, so big bang wouldn’t be the way I’d describe it. But what I would say is this: if you’re going to use a warfare analogy, do you like trench warfare? The gradual approach, in my mind, is trench warfare, because to John’s point, you’re going to be carrying on a battle over years, and the quickest way to win a battle and win the hearts and minds of all of the people that have to work together is to get their paychecks. If you control their paychecks, you get their hearts and minds pretty quickly. So I believe that if you are going to centralize, you organizationally do it, and you have the people responsible for various IT functions and parts, different parts of the enterprise, at a certain date all report in to the shared services organization, and then they can work together as a team, and it’s done.
Bruce Goodman [00:19:18]:
If you try to do it gradually, they’re going to continue to battle to try to avoid it, because some people don’t want to, they may think they lose status or position as things are centralized or consolidated, and the easiest way is just once and done, get it over with, have everybody report into that shared service organization, and then identify your key priorities and make it happen.
Sanjog Aul [00:19:46]:
So when you’re trying to sell this to the top management, and if you try to make the business case, all the benefits that you may see there, if you were to itemize them, would you have quantifiable measures for those benefits, or wouldn’t this be more intangible, but you are somehow able to sell it?
Bruce Goodman [00:20:05]:
It depends on the parts. Back to the earlier comments, if you’re talking about the infrastructure, network, data centers, distributed computing, in most organizations, if they’re highly decentralized, you’re going to have very significant cost savings there, because what you’ll find is redundant networks, and once you put them together, there’s a big reduction in cost. You’re going to find multiple small data centers, and once you put them together into several large data centers that can back each other up, there’s another cost saving there, and so on. So in the infrastructure part of IT, it’s pretty easy, when you walk into an enterprise that is highly decentralized, to make a very convincing business case.
Bruce Goodman [00:20:53]:
Then you get into the application engineering. You get the debate of how you align best with the various business functions, which, as I said earlier, may depend somewhat on how diverse those business functions are. But there, in the commonality, the security, the privacy, getting to a highly effective organization, even in that case you get some savings, but more importantly you better leverage IT across the organization, and that’s the key. You’ve got a very critical resource. It tends to have a high cost in terms of the resource.
Bruce Goodman [00:21:33]:
How do you best leverage it? You leverage it by prioritization, alignment, and getting all of the methodologies right.
Sanjog Aul [00:21:47]:
So, John, when you did it and you had to get this all taken care of, how was the business case created? Were you able to give them actual numbers of what you would bring home?
The business case: ranges, savings and career mobility 21:58
John Conley [00:21:58]:
Being a state governmental entity, we didn’t give exacting numbers, for the very fact that once you put a number out there, it’s very likely they’ll just reduce that budget immediately to the amount that you think the cost savings would be. While we have a great relationship with the legislature, if we’re off by a million or even hundreds of thousands out of our 250 million dollar budget, that could be critical. So we gave ranges. We asked them to bear with us in the initial 18 to 24 months, and we set up a separate fund where any savings that were achieved were quantifiable, recordable, and would go into a savings account or a rainy day fund, to be reinvested into the overall IT consolidation efforts in future years. The other thing we used as a selling point was career mobility for the IT employees in the state of Colorado. Before, when you have shops that are set around a five or 20 man team, it’s hard to have upward mobility. Someone has to retire, someone has to have a health issue, someone has to potentially be fired before the lower individuals, the rank and file, can move up into those positions.
John Conley [00:23:18]:
So we looked at it as, look at the career track you’re now creating for IT personnel in the state of Colorado. You’re giving them more upward mobility, you’re giving them more sustainability in their organizations, and you can withstand some of the fluctuations at budget time that everyone’s going to experience in state government, as we come into our income tax in the latter half of the year or the beginning of the next calendar year. So we had cost saving ranges, we had career mobility as a selling point, and then we also had, as was pointed out early in our conversation, business continuity. Now you have a centralized entity, you have people who know what the critical assets are, what the critical systems are, and can prioritize them according to the entire state’s needs, the enterprise needs, as opposed to individual or 16 different department needs. As Bruce pointed out earlier in a different light, sometimes the number one priority for the Department of Agriculture is not the number one priority for the state of Colorado, and we need to recognize that and have an honest conversation so everyone’s on the same page,
John Conley [00:24:28]:
but we couldn’t do that when everybody was controlling their own destiny, so to speak. So those are the three selling points. It didn’t hurt that we had 39 data centers scattered across the state as a number. The legislators, it’s a citizen legislature here, they’re only in session five months, but they were frightened and very concerned that we had that number of data centers, and that was something they were able to latch onto as quantifiable and demand that we see a reduction of those 39 data centers over time to more around three to four data centers in the state of Colorado.
Sanjog Aul [00:25:03]:
Any other tips that you feel, Bruce, the listeners should get in terms of being able to sell it properly to the management?
Bruce Goodman [00:25:11]:
I think we’ve covered practically all of them. John made some good points: the prioritization of the efforts, the cost savings, eliminating the redundancy, making sure security and privacy practices are uniform, so that if you have audit issues, you won’t have audit issues that you might otherwise have. Small shops tend to do things not the best way. You consolidate, you get economies of scale, not only in dollars but in terms of process, and that’s really important.
Sanjog Aul [00:25:46]:
So now that we have sold successfully to the top people and we got the money, now we have to sell it to the crew, the people who will actually make this happen, who will be the ones in the franchise. If they feel, unknowingly, they would not know at this time whether as a result of this consolidation or centralization their own job could be at stake. How do you keep their morale up and how do you keep them moving in the same direction? Bruce, you want to take it?
Bruce Goodman [00:26:11]:
Again, I don’t think your savings come from eliminating people, so that would definitely not be the first thing you’d want to do.
Sanjog Aul [00:26:19]:
But this is a paranoia, is what I’m saying.
Bruce Goodman [00:26:21]:
The way to start out that program is to get everybody in a room, all of the leadership from the various areas, and say we’re not cutting any job. We need all of you as part of the team, and your job may change but you’re going to have a job.
Bruce Goodman [00:26:36]:
That’s the way I’ve done it in the past, and you get those folks involved. Now, the people on the infrastructure side, you’ve got to pick obviously a leader in the various sub areas who knows what he or she is responsible for, so they can drive to, as John pointed out, whether you’re going to have fewer data centers, redundant networks, et cetera.
Sanjog Aul [00:29:22]:
Welcome back. So, John, would you have some suggestions regarding how we could help get the most out of our crew when they are being asked to get involved in an IT consolidation effort?
Communication and keeping the crew’s morale up 29:35
John Conley [00:29:35]:
I do. Once you have the plan established of how you’re going to consolidate and/or centralize and what you’re going to focus on, you need to then immediately launch a PR campaign or a media campaign internal to your organization: constant communication, transparency to a degree with what you’re thinking. Mike and I, Michael Locatis, the state CIO for Colorado, and I, talked very early on. It wasn’t enough just to explain to the individual what was occurring. You also need to take the time with your greatest assets, your employees, and explain why what you’re doing is important to their jobs or to the overall citizenry of Colorado. And then you have to use multimedia. We use a wiki, we have an intranet site, we have newsletters, we do videos, we do a massive amount of town hall presentations, where when we figure out the next logical step that we’re going to take, we try to canvass the entire state and meet with those employees in groups of 25 or larger to discuss with them and get their feedback, incorporate that feedback into the plan, so you’re creating a sense of buy in and a sense that they can affect the plan going forward to a degree,
John Conley [00:30:56]:
and then you have to just repeat that message over and over. I talked to 900 employees in two months around the various geography of the state of Colorado, and I probably answered that question 900 times: what does this mean to me, and am I going to lose my job? It’s easy to get frustrated by the repeat question, because you have all these medias out there that you’re using to assure them they’re not losing their job, but you have to set your frustration aside, quite frankly, and say, at the end of the day, what’s important to the enterprise is that we keep the individual employees happy, because they’re our greatest asset. You have to be willing to answer the same question 900 times or a thousand times over, and find different ways to do it. Some people read it and believe it, some people listen and they need to hear it before they believe it, but communication and transparency are the key, I think, to a successful employee morale increase, or uptick, as you’re going through a consolidation.
Sanjog Aul [00:32:03]:
Now, an IT consolidation or centralization is so pervasive, or should be so pervasive for it to get the most value, but the fact is it is going to touch literally every part of IT and most of the IT business function. Which one should be that one neck to grab if it fails or it succeeds?
Who owns the risk if consolidation fails 32:25
Bruce Goodman [00:32:25]:
It’s going to succeed unless you have some really incompetent organization, but the CIO who’s in charge of it is the one who’s going to lose his or her job if it doesn’t succeed. You’d have to figure out what the measures of success are. Obviously, to John’s point, if you promise some cost reductions, you better get them, or at least pretty close. And the biggest risk, especially if you centralize the application engineering functions, is the business basically saying, see, we can’t get our work done anymore, IT doesn’t understand us, we can’t be successful in the business because we’re not getting the proper support. Sometimes that might be on things more around the infrastructure, systems availability and response time.
Bruce Goodman [00:33:13]:
That would be a shame if the CIO and his or her organization couldn’t make sure those basic service levels, the blocking and tackling, are done correctly. But the trickiest area, and the one that I think the CIO is most exposed to, is what I just mentioned around making sure that the businesses that have launched their application engineering staff are getting proper attention and that you’re delivering on their needs.
Sanjog Aul [00:33:43]:
So you’re the captain of the ship as a CIO and you’re getting paid the big bucks to take that risk. But is it really fair to a CIO to have to assume responsibility for something that has got so many moving parts and so much going on? How should that be further divided, at least? It would seem appropriate that the risk of losing a job, or the responsibility, or accountability, should not be on one neck. What do you call this?
John Conley [00:34:12]:
This is John, Sanjog. Whether it’s fair or not, I think that’s the position we’re in. It’s not fair, from a state government perspective, maybe to blame or assign a degree of accountability for everything that goes wrong within our borders on our CIO, the governor. But that’s the accountability level we ask for when we take on these types of jobs and responsibilities. So is it fair? Probably not. Should the blame be more dispersed?
John Conley [00:34:41]:
Probably. But the fact of the matter is, when you’re leading the ship, it’s the captain who decides at the end of the day to go right or left, and if you choose wrong, he potentially takes the hit.
Sanjog Aul [00:34:53]:
Now, with respect to consolidation being looked at like a pure IT initiative, how much business involvement would you like to have, because that could in a way help, or in some cases jeopardize, because they would keep bringing their own whims about what should happen. How, Bruce?
Bruce Goodman [00:35:09]:
I think you go back to the selling. You have to have senior leadership in the enterprise supporting the initiative in a very strong way, so the CIO has to make it clear that he or she firmly believes that centralizing the IT functions, whatever they may be, and again it’s more touchy if it’s the application engineering ones, is an important corporate objective, and that he expects the various business leaders to do their part, and especially not be lying in the weeds with a bunch of spears to jump out if something goes wrong. In other words, make sure that they’re doing their business requirements, they’re working to make clear to the IT organization what it is they expect. You can work through this. You should certainly have a whole set of service level agreements with the various business areas so that you can publish clear metrics that show success, and that way everybody agrees on what the objectives are. But the CEO says, okay, this is what we’re going to accomplish,
Bruce Goodman [00:36:18]:
and I expect everybody to be working as a team and to resolve things, and I don’t want to hear people coming into my office and backstabbing, saying this isn’t working or that isn’t working. You people are mature and senior leaders of this company and you have to work together to accomplish this important company initiative.
Sanjog Aul [00:36:38]:
John, what have you seen with respect to the business community, in this case the other legislators, who may not be as aware or as IT savvy? Would you welcome their input with respect to this project, or would you say leave us alone?
John Conley [00:36:52]:
We actually are seeking and getting complete business user involvement in the IT consolidation. What’s important for them is important for us, and I think at its foundation, information technology is, to a large degree, a service provider out to the business organizations or the divisions of the department, and we need to ensure that their requirements are being met. What we’ve asked the business users of the divisions and departments, though, is not to bring IT the solution. Please don’t come into a meeting or into a room saying I want X product. What we ask is that they come into the room and ask us, these are the requirements I need, do you have anything in your arsenal that can meet these requirements, and let the technology effort take the solution. But we have to have their involvement, because for them it’s a huge transformation of how a business practices, because now they can’t just go down the hall and say I want you to do this and I want you to do it tomorrow. They can go down the hall and meet with their applications engineer and discuss what their needs are,
John Conley [00:38:10]:
but that application engineer or network administrator is then going to say, okay, I have to put this in a process now, and we’ve all agreed to that process. Agreeing to that process up front is 10 times easier, if not a hundred times easier, than fighting about the process on the back end when the deputy director or the executive director is unhappy.
Sanjog Aul [00:38:29]:
With respect to compliance, most public companies and government all have their own compliance mandate. Should consolidation with respect to IT be a prerequisite to achieving compliance, or should it go hand in hand? Because if it goes hand in hand, then we are really trying to hit a moving target, because you will be breaking things when you’re trying to consolidate and bring things together. Processes and technology both will be ripped apart for it to be brought together and consolidated.
Sanjog Aul [00:39:05]:
So how do you achieve compliance, or keep the company in compliance, while you’re trying to do it, if it has not been done as a prerequisite, Bruce?
Bruce Goodman [00:39:11]:
I’m a little confused on the question, to be honest. Compliance, from our perspective, since we’re a highly regulated industry, is complying with those regulations, whether that happens to be something called HIPAA, which is keeping private various information about our members, their health information, or whether it’s certain reports that we have to give and certain standards that we have to meet for the Centers for Medicare. Those are all compliance issues, and you never go out of compliance. At least you certainly try very hard not to go out of compliance. So I don’t know that consolidating puts you at any greater risk of being out of compliance, from that definition point of view.
Sanjog Aul [00:39:56]:
So would you not be touching systems and processes and people and data, making it even temporarily out of compliance, and even needing immunity during that time?
Bruce Goodman [00:40:04]:
No, you don’t get immunity.
Sanjog Aul [00:40:07]:
So then how do you eat the cake and have it too?
Bruce Goodman [00:40:10]:
You don’t break it. You have to have migration plans, if that’s what’s required, that keep you in compliance. I’m not sure you’re ripping so much apart. I don’t know that it’s as disruptive as the picture you’re painting.
John Conley [00:40:26]:
I guess what I would say is, we always ensure that the process we’re moving to is in place and tested before we retire or decommission an old process, and we’re following the line of service level agreements and performance metrics as well. So we’re having a transition phase in Colorado. As we’re doing our consolidation, we’re going out, we’re getting the performance metrics in place for the added processes and procedures and for uptime, and we’re saying, because we’re not reducing staff, because of the one to one relationship with the business entity, just a different management function, we’ll maintain your performance metrics for 12 months or 18 months. Once we have that performance metric data, we then begin to migrate to the new path, and that’s when the new process takes effect, and they have agreed to those business processes.
Sanjog Aul [00:44:31]:
Welcome back. So we are trying to consolidate our IT, and as a prerequisite we should have some sort of diagnostic that should be carried out for us to see what all is required before we should really kick off this initiative, and whether we are really ready yet. So with respect to that, John, what do you think you would have done? What did you do in your organization, and what could other organizations possibly do?
A readiness checklist before you consolidate 44:57
John Conley [00:44:57]:
First, I’d start off with, as we were talking earlier in the conversation, if you’re existing in a disparate, decentralized IT organization today, you probably need to take the steps necessary to consolidate that type of service. When we came in in January 2007, we essentially made sure we had five things in order. The first and foremost, if you don’t have it, you need to get it, or you’re not ready to move forward, in my opinion, is executive sponsorship or stakeholder involvement. You need to have the CEO, or your CIO, or a division director, in charge, or at least supporting you, not in charge but supporting you, in the direction you’re wanting to take the organization, because there are going to be some tough decisions. I also think you need an analysis of the current situation. Your CEO or your stakeholder is going to ask you, what’s broken, why are we having to do this today? So, return on investment, total cost of ownership, better services delivered to the constituents, or it’s not working that way.
John Conley [00:46:00]:
You need to know what your current situation is, and then the backside of that as well: how is what you’re proposing going to fix that, and what are the goals of the new organization? You need to have a strong leader. Whoever is leading the initiative, whether it be the CIO or a CTO in some organizations, that person needs to be many things to many different people, but the thing they cannot be is a weak leader. So you need strong leadership in the organization. And finally, once you decide to go down the path, have a communication plan. We were talking about it earlier.
John Conley [00:46:34]:
Make sure you’re talking to the stakeholders, you’re providing them updates, and you’re carrying their concerns as well as your own. It’s going to come down, at some point, to relationship building and communication. Having people feel they’re in the know, and knowing they’re in the know, will lead to easier times when you have some of those tough decisions to make. That was our checklist here in Colorado. I’m proud and happy to say we checked it off, and yet we still had some struggles. So it’s not a perfect recipe.
Bruce Goodman [00:47:03]:
I would add, I think John makes some excellent points. I’d add a few other things. One, you need a strong project management office and methodology. Depending on the size of the enterprise you’re dealing with, bringing all of the IT functions together, eliminating redundant networks, reducing the number of data centers, et cetera, is going to take a multi year plan, so you need people that are very skilled at putting that plan together and then tracking it and running it to make sure it stays on target. So, number one, a strong project management office. Another one is communication skills, communicating with everybody. I’ve always believed, in the organizations I’ve run, in having an actual communications expert, somebody skilled in communications, because most of the time, as you know, IT people aren’t exactly great at communicating. So you hire a professional communications director, and they may have to have a couple of people with them, to do both internal and external communication around the business, and potentially outside of the business into the general media.
Bruce Goodman [00:48:12]:
That is an important part of selling the ongoing project and making sure everybody’s comfortable with it. Another key function that I think is helpful to have in place before you go down this path, I call it vendor management, or strategic alliance, because remember, one of the things we believe in is partnering before buying and buying before building. We want our people to be primarily system integrators, which means you have to have a very efficient and well defined process for evaluating vendors who you might use. And back to John’s earlier point, you want the business community to describe what they want and leave the decision of how, for the most part, to the IT organization. So you have this vendor management organization that helps define the requirements with the business, then looks to see what vendors are out there that can supply that particular solution, either totally off the shelf or somewhat customized, brings them in, goes through the process of evaluating them, et cetera, and moves quickly to get all of the legal deals signed and put in place. So you want to centralize all that procurement, because that’s another area of fairly significant savings and leveraging. So I would say those key components, in addition to what John said, are really important.
Sanjog Aul [00:49:41]:
All right, one last question. What are the typical risks you would still have, or the chronic areas you would love to have solved, to make this a smoother ride, Bruce?
Bruce Goodman [00:49:52]:
Again, first of all, you need the cooperation of the business areas. They’re going to be losing control, direct control, of some of the things that they think are very important, so that senior leadership and their buy in to the initiative is critical. You’re going to have to make sure that you do a really good job of assigning people to them who are sensitive to those issues, so that they feel that they haven’t lost that much, and that in dealing over the long run they’ve actually gained expertise and gained leverage.
Sanjog Aul [00:50:25]:
John, what do you think?
John Conley [00:50:26]:
In terms of the risk that I’d like to have removed, and I’m sure Bruce finds this in his entity as well, I never know the future. I don’t know what mandates are going to come down from federal entities or state entities that I’m just quite frankly ill prepared to deal with while executing on a major transformation of how we practice government. So what I wish is that we could have even a three month timeout on federal and state mandates, but that’s not going to be the case, and we have to mitigate those risks, and we have a close relationship with our legislature in order to do that. So that’s what I’d like to have removed. That’s never going to happen. The most important thing is to understand new things are always going to be thrown at you in an IT organization, and you have to have, in my opinion, a centralized organization to be able to deal with that rapidly changing environment quickly and succinctly.
Sanjog Aul [00:51:30]:
On behalf of the show and our listeners, I’d really like to thank you, John and Bruce, for sharing your thoughts about how we can actually make this IT consolidation a smoother ride and eventually help deliver value.
Sanjog Aul [00:51:48]:
In the first place, we have to determine how much IT consolidation is enough for a given organization, and as we discussed, there were points related to the readiness check and the diagnostics that we can perform in terms of where we are and whether we can really get it started. Now, we may also end up overdoing it, and because of that you will relive that old era of monolithic systems that may make it an 800 pound gorilla, which will not have the agility and flexibility that we need so much in today’s world. On the surface it may look great to consolidate to reap benefits, including overall IT efficiency and predictability, and it also gives you high quality levels for IT services, but it could also be a nightmare if it is not planned properly, if the consolidated initiatives are not planned and managed the way they’re supposed to be, with the right type of PMO, which may result in downtime and a high cost of service levels. So what are you doing with respect to IT consolidation in your company? Please send us your story to views@ciotalkradio.com. Thank you again for listening to CIO Talk Radio. This is Sanjog Aul, your talk show host.


