This is an audio conversation from the CIO Talk Network podcast. The timestamps in the chapters and transcript below refer to the audio recording.
About this conversation
A CIO Talk Network conversation with Ying Chan (Texas Health and Human Services Commission), hosted by Sanjog Aul.
What the conversation established
The conversation established that embracing emerging technology is a prioritization problem, not a race to stay current. Ying Chan of the Texas Health and Human Services Commission argued that a new technology is worth adopting only when it adds value, pays back inside the business’s own investment cycle, and is genuinely disruptive rather than a marginal improvement. She separated value-added work from non-value-added work such as ERP, HCM, and general ledger, and said adoption speed should match the product cycle, often 18 to 24 months. Chan treated enterprise architecture as three concurrent horizons and described funneling 10 to 15 candidate technologies, including containerization and hyperconvergence, down to the few that justify five-year enterprise-wide adoption. For a company in the red, she put automation first, citing accounts payable that takes 15 people and 30 days as a target for point tools rather than a full SAP rollout. She also held that automation shifts IT work rather than erasing it, pointing to Texas consolidating data centers while still needing 24/7/365 staffing.
Host Sanjog Aul talks with Ying Chan, CITO – Chief of IT Operations at the Texas Health and Human Services Commission, about how to embrace emerging technologies without chasing every new tool. Chan lays out three questions to ask of any new technology: whether it adds value to the business, when the investment will pay back, and whether it is truly disruptive or just a shiny toy. She describes running three enterprise architectures at once (today, next quarter, and the longer horizon) and funneling 10 to 15 candidate technologies down to the few worth enterprise-wide adoption. Drawing on her semiconductor background and her work in Texas public health, she argues IT should match the speed of the business, separate value-added investment from non-value-added work such as ERP, and lead with automation to pull a company out of the red.
Contributors
- Ying Chan, CITO – Chief of IT Operations, Texas Health and Human Services Commission
Host: Sanjog Aul, Founder and Host, CIO Talk Network
On this page: Key takeaways · Chapters · Explore more · Transcript
Key takeaways
- Ying Chan of the Texas Health and Human Services Commission says any emerging technology should pass three tests before you invest: whether it adds value, when the investment will pay back, and whether it is truly disruptive. She warns that funding a marginal improvement in an expensive technology risks being eclipsed by the next revolution that would have mattered more.
- Ying Chan, CITO at the Texas Health and Human Services Commission, argues that IT should match the speed of the business rather than push technology for its own sake. She says speed for the sake of speed does nothing when distribution channels, seasonality, or a market’s consumption rate cannot absorb what IT accelerates.
- Ying Chan of the Texas Health and Human Services Commission separates value-added investment from non-value-added work such as ERP, HCM, and general ledger. She ties technology adoption to the company’s product cycle, often 18 to 24 months, and keeps short, iterative ROI maps that meet the business cycle.
- Ying Chan of the Texas Health and Human Services Commission treats enterprise architecture as three horizons at once: today’s delivery, next quarter’s promises, and the longer technology outlook. She describes funneling 10 to 15 candidate technologies, such as containerization and hyperconvergence, down to the few worth five-year enterprise-wide adoption.
- Ying Chan of the Texas Health and Human Services Commission says a company in the red should lead with cost control and automation, not distant future markets. She gives the example of accounts payable or receivable that takes 15 people and 30 days, where a point tool beats a full SAP rollout that could cost billions and run two years.
- Ying Chan of the Texas Health and Human Services Commission contends that automation shifts work rather than destroying it, comparing the change to the agricultural and industrial revolutions. She points to Texas moving agencies to consolidated, state-run data centers that still need servers, maintenance, and 24/7/365 staffing.
Chapters
- 0:00 Introduction: embracing emerging technologies with Ying Chan
- 2:20 Three questions before investing in new technology
- 4:54 Why business is more ready to let technology lead
- 8:07 A semiconductor example of IT shaping the business
- 12:45 The pressure to stay current with the stack
- 17:49 Balancing value added and non value added investment
- 20:21 Three enterprise architectures running at once
- 27:33 Matching adoption to the speed of the business
- 36:16 Funneling candidate technologies toward disruption
- 43:43 Why automation shifts work instead of erasing it
- 50:08 Leading a company out of the red with automation
Explore more
- Using Emerging Technologies for Banking Innovation
- Embracing Ignorant Leadership
- Embracing Change with Confidence
- Assistive Technologies: The Business Angle!
- Where Are The Once Overhyped Technologies Today?
- Cloud security, cost, and culture: Technologies Concern
Transcript
Introduction: embracing emerging technologies with Ying Chan 0:00
Sanjog Aul [00:01:01]:
And our topic for today is Embracing Emerging Technologies, and our guest is Ying Chan, who is the CIO/CITO, which is Chief of IT Operations at the Texas Health and Human Services Commission. Hi, Ying. How are you?
Sanjog Aul [00:01:23]:
And, of course, with the topic today where we’re talking about embracing emerging technologies, that makes me excited and also a little nervous with the way people are sometimes tackling it. So the reason we wanted to do this topic is there’s so much going on, and it’s an exciting time for technology and business. However, when it is we are drinking from the fire hose, so much happening, so many new technologies being pitched at us and then in turn pitched to business. No one knows really what to go after or at least you have to find a way to rationalize, to prioritize, and not feel that we are getting left behind. So the first question I have for you, Ying, in this area is are there, say, top 3 questions one must ask, which anyone when somebody is bringing you a new shiny toy, whether I should invest in it or not? What would those be?
Three questions before investing in new technology 2:20
Ying Chan [00:02:20]:
So I think our very first question you have to ask is, is it going to make a difference to the value added side of your business? Right? Every business goal is to make money. Will it help you make money? What will it do to improve your system in order to increase the bottom line? I think that’s question number 1. Question number 2 is, are you able to invest and are you able to reap the benefits of that investment? Or maybe a better question is when will you be able to reap the benefits of that investment? And when will you be able to invest, and yield? And that, of course, brings into, is your organization ready or not ready? And I think the third question is, is it disruptive? Is it an incremental value add and you just like the shiny new toy and is it your passion that’s talking? Or is it truly a disruptive thing that’s gonna take your company to the next level? Because the worst thing you can do is invest in a marginal improvement in an expensive venture into emerging technology only to be eclipsed by a newer, better, or the next revolution of emerging technologies that would have made a greater difference to your organization.
Sanjog Aul [00:03:42]:
You know, comparing to the last decade or earlier times when we used to look at technology, we used to say, okay. Let’s everything be driven by business. And there’s nothing wrong with it if you take from a conceptual standpoint and have a strategy in place and finally see how you can execute that strategy using technology wherever possible. Now when it comes to these emerging technologies and the approaches how people are taking at computing, it seems to be fundamentally disrupting our approach to how we would have even thought of a strategy. We thought of what we can potentially accomplish because it is really taking us into those uncharted waters and which could, in a way, also help drive the strategy. So it looks like, is it tail wagging the dog here or is it actually now letting technology drive it, especially in case of emerging technologies and business taking a back seat for a second and allowing people like you to show them how you can rethink your business and what is possible? Is that the right approach given where we are today?
Why business is more ready to let technology lead 4:54
Ying Chan [00:04:54]:
Absolutely. I think if you go back to the last decade as you mentioned early in this discussion, I think in the last decade, one of the things that we did not do well as an entire IT industry, we did not do customer empathy well. With the advent of d.school, with the advent of 10x moonshots coming out of the valley. These are very strong Stanford and Google concepts, and they’re pretty much one and the same in my view anyhow. We were really driving towards customer empathy from an IT perspective, from any design perspective, actually. And I think in this decade, what we see is a much more partnership, much more of a collaboration, much more of empathy, towards what the customer’s looking for from IT. So this allows IT to take a seat at the table when determining how we do things. And I think the other side is with the advance and the rapid turn in technology uptake from IoT to our handsets or personal, consumer devices. I think technology is taking really a forefront into making a difference in not only just companies and businesses, but in society. So I think business is much more ready to accept technology than they were a decade or two ago. So I think with the event and those two things happening in general, I think it absolutely makes sense that technology drives delivery and disruption into realization of what our customers, our business units want to see.
Sanjog Aul [00:06:44]:
See, but I wanted to take it to the next level. What you’d still again said was it is driving the delivery. So I wanted to take it upstream and say, while we know CEOs are not gonna sit and twiddle their thumbs saying that, okay. Let me see what this technology delivers, and let me see how I’ll move my business. So, yes, there will be some strategic thinking. And, yes, we can say that, okay. We have seat at the table. But if the hat that we are wearing is just plain execution and not essentially saying, you know what? This is what’s coming down the pike. You’re thinking mister CEO in a certain direction, but this could fundamentally be changed if this x y z happens. Like, you talk about artificial intelligence or something totally different, which would replace many people, the kind of way we do things, our processes, everything, but that is not again delivery. We are seeing even what we could potentially offer to the business. So why not have IT actually not just leave that so called delivery hat for a second and say, mister CEO, I’m not saying you chill and relax. We will drive it, but bring us to a level where allow us to give you some ideas on where to go next by first let’s experimenting on these new technologies that are being provided. Do you think we are getting there at all, or is this being even approached in the boardroom?
A semiconductor example of IT shaping the business 8:07
Ying Chan [00:08:07]:
I absolutely believe that we are getting there. I think it’s going to be a small percentage. I’m gonna be honest with you, from what I see. There’s gonna be a smaller percentage. But I’m gonna use a strong background of mine, which is semiconductor for an example. Right? So absolutely, you’re correct. We can speed up delivery. And if we look at, you know, as far as levels go, let’s say that’s kind of in the mid. You know, we at least have a seat at the table. We’re making a difference to the business in terms of delivery and outcomes. But I think to take it to the level you’re at, the example that I have seen that can happen and that is happening in every industry in some way. And I think still a small percentage is, for example, we come and I work in a semiconductor company, and I say, hey, mister CEO, what we’re seeing in the trend in the industry is that we’re going to the cloud. The industry is going to white box, and they’re gonna need this type of performance, this type of capacity in terms of their hardware and their networking gear and their servers and storage and so on and so forth. Hey. We’re a semiconductor company. We should be leveraging this market. We need to build chips to these specs that I’m asking for that I know are not available to be developed. We’re in the emerging market, and that’s a very semiconductor type example. But it’s a good one to say, you know, I have seen the CIO of certain companies affect the business units’ designs and offerings because of the trends in IT.
Sanjog Aul [00:09:54]:
So here, when you mentioned, you spoke about telling them about the markets to opening up the markets. That’s one area. Another is to look at differently what the business we are in. And typically, that there you could pivot based on some of the emerging technologies that are coming out, not from an execution standpoint. In what you will deliver to the customer. So is that type of thinking becoming mainstream as discussions happen within the boardroom or at Watercooler among the top level leaders and the middle people?
Ying Chan [00:10:34]:
I think it’s happening at a higher level. So, you know, I’ve had a change in careers in the last couple of years, and now I’m at HHSC. I’m in health IT instead of semiconductor and manufacturing. I’m in health care, and I’m working in public service. I’m definitely serving and feeling very good about serving the citizens of Texas. And what we talk about here is outcomes, long-term trend outcomes. Making sure we have healthy Texans no matter your socioeconomic situation. We provide that service across a lot. And there’s definitely a lot of talk about predictive analytics. Not only looking past as to what our programs here at HHSC in Texas have provided benefit to Texans, but we also use technology to derive outcomes based on predictive analysis. In some cases, looking at dark data, in some cases, looking at some cognitive algorithms in order to get us to what do we think the best possible outcome, the best way to spend our tax dollars in order to increase those moving forward into the future. So I think technology will drive policies and procedures in government across every level. And I think it’s a completely different topic than semiconductor, but yet you see technology really being at the forefront of making policy, procedures, offerings, if you will, any kind of outcome, to the business. Obviously, public service is very different than private, but same idea. The intelligence, the smarts that we see in IT, the tools that we can bring to the table affect the policy and outcomes of the programs.
Sanjog Aul [00:12:24]:
So when you look at, when you essentially talk to many of the technology leaders, they somehow feel restless if they are not current with the technology they have in their stack, or they almost feel ashamed to tell, okay. This is the stack I’m running. Why is that?
The pressure to stay current with the stack 12:45
Ying Chan [00:12:45]:
I think there’s a certain amount of pride that we want to do good IT versus bad IT. And I think there’s definitely a need to keep moving the needle, keeping pace. You can see the rapid change around us in technology all the time in things that we touch. iPhone is only 10 years old. Nobody can live with an iPhone 4 or an iPhone 5 even at this point. It’s a couple of years old. Technology has moved so quickly that it’s prevalent in our lives. And I think if we’re not moving at that pace, we greatly fear as leaders that we fall behind the curve. We’re not as productive. We’re not bringing technology to the table as best we can to affect the outcome of our business. No matter what it is. So I think there’s a need and a drive to keep current. Now whether we need to do that across the board on everything at once is definitely not. But I think the rationale for wanting to keep current is good. It’s fine. It drives us. If there’s no change, there’s no progress. And you see a lot of technology change all around us every day. You know, the Samsung S8 just came out and people are saying it’s 9, 10 times better than the S6. Still only two generations old. So where are we in our shops moving at that pace?
Sanjog Aul [00:14:14]:
I’d like to stay on this topic about staying current because you can stay current and try to fix your now or prepare for the next or combine the two. So there has to be some balance because if you can keep putting in the investments in technology and saying, okay. This is disruptive, and it’s gonna create value. At some point, business will say, okay. Why are we doing this again? And you’re only looking as a futuristic Star Trek model, or you’re gonna get me the most value from the investment? Because any investment made needs to have some sort of an ROI. So what kind of conversations we need to have with the business in this regard? And internally, as leaders within technology, what kind of balance should we strike between preparing for now versus the next?
Sanjog Aul [00:17:16]:
So we are talking about staying current and even thinking for tomorrow. And all of this, of course, is a continuous tussle for a CXO or an IT CXO to deal with the management. In your case, Ying, or maybe any others that you know of, how are they trying to strike a balance between what they invest for today and tomorrow? And while they do it, how do they manage expectation of the business who typically has all along been saying do more with less or more with nothing?
Balancing value added and non value added investment 17:49
Ying Chan [00:17:49]:
So this is a great question and a very important one, Sanjog. I’m glad you asked it. So the key thing about balancing and leveraging investment is understanding what is value added and not value added in your particular organization or in a particular shop, in any manner. So when I propose something to a business, and it’s an emergent technology, I know that I can adopt it, but I look at out years. And depending on what it is, if it’s value added to my business, and it’s something that’s absolutely necessarily front line, I’ll propose something that’s very rapidly changing. I’ll set up my environment to be very rapidly changed so I can adopt new technologies and make sure that we get return on investment. The cycles that matches the business’s investment. So there’s gotta be, it’s almost like a planting season. We sow the seeds. We reap the harvest. In non value added situations, and I wish that everything that we have in IT shops is value added, but it isn’t. Sometimes you just got to do things in order to enable the business administrative functions for the enterprise, so on and so forth. Make sure that we’re investing appropriately on those investments. So there should be ROI maps that are very short and iterative that meet the business cycle. Our technologies, when we’re able to leverage the value of the emerging technology we’re adopting should meet the investment and reward cycle of the business.
Sanjog Aul [00:19:35]:
What you just said, you said value added versus nonvalue added. How about I added the third one which says, look at the ones which have value adding possibilities. And those are the so called experimentation and the sandboxing type opportunities where when you go back to the business and say, you know what? I cannot really promise you the moon right now, but if the way I look at it and, of course, you give them examples. But you said this is where the value will be added tomorrow, or you would have a competitive advantage tomorrow. And you are being a clairvoyant or a weatherman, if you will, who’s gonna predict the weather, and you want them to be able to buy it, so you do the experimentation today so you have a leap or a potential for a leap tomorrow. What about that part?
Three enterprise architectures running at once 20:21
Ying Chan [00:20:21]:
I think that’s inherently built into the discussion about emerging technologies. So I have never known enterprise architecture to have one flavor. To me, there’s always 3 enterprise architectures. What are we doing today? What are we doing to deal with the business today? What I’m gonna do for you next quarter, the quarter after? What are the technologies I promised you in the last cycle that I need to be delivering on today? And then as I look at the business outlook, I look at technology outlook, and I adopt new technologies, I have to build a ramp to adopt it. If I try to adopt technology interrupting the current revenue stream head on in a collision, that’s what you’re gonna get. So how do I maintain and drive an upward curve on a current revenue stream with the current set of technology promises while experimenting and proving out where I can take you tomorrow? I think that discussion is super important with business as far as adaptation and what the future value add is of things that are not today adding value, but will be in the future. And I think any progressive, forward looking company has this no matter what. And whether it’s in IT or in their own business units, it’s happening in the company. So it’s just a matter of IT relating to the R&D that’s going on and how to map our curves to that curve.
Sanjog Aul [00:21:49]:
And so on one hand, of course, we have to be having that R&D. And frankly, most companies cringe at this whole term R&D because they don’t feel they kind of look at it as an overhead given the fast pace and say, okay, I can keep doing the research and development on what I have in hand, but tomorrow the things change. So all of that I’ve done becomes a throwaway work. So that’s one challenge people are grappling with. And another is to say, okay, on one hand, you look at this cutting edge stuff, but why not take care of what you already have which is working and why mess with it? Because as you mentioned, if there is no value added, I could be working with legacy, and we should feel proud that I got the most value anyone can ever deliver from that initial investment I make 10 years ago. So these are totally two different frontiers on which someone has to tackle. Where’s the balance?
Ying Chan [00:22:39]:
So the balance is, again, really thinking about what it is that we’re doing and when the payoff is going to be. So again, if it’s non value added, I’m gonna go with, you know, maybe a little controversial, but ERP, in essence, is not value added. We do it because we have to. We have to pay the bills. We have to have HCM. We have to have general ledger. We have to have compliance to SOX. We have to have all these things, and the ERP helps us. If we didn’t have to do all that, every company would be investing 100% in their business units and way more higher in R&D. But even if we look and we say, hey, we wanna get an ERP system in. They’re big. They’re monolithic. They’re expensive. My past experience at SAP, PeopleSoft, and Oracle Financials, all are very expensive. Very long term roadmap looking things. But even then, if you don’t keep current at a slower pace, maybe it’s 5 years, maybe it’s 10 years. If I don’t keep pace though, I will fall behind and that will become a disruptor in the wrong direction for a company. On the newer technologies that are gonna move the business units, what we call value added (help the company make money), a non SG&A function. I wanna invest in quicker cycles. Again, I wanna match the product cycles of the company, which typically nowadays, if you’re in technology, it’s probably 18 months to 24 months. A new cycle begins on technology and product development. And you probably have multiple overlapping cycles so that the fall out is pretty quick. So on that, I want my adoption rate to be super quick. So I gear my organization to do that. I not only look at emerging technologies in terms of ability to deliver more, like predictive analysis and so on, but I also look at emerging technology to allow my IT team to deliver quicker. Hyperconvergence, containerization, of all the promises of keeping up to the speed of agile development. Having one part of your organization adopt super fast technology while my hardware side can’t keep up doesn’t help. So I have to make sure that it all can adopt, it moves at a certain pace, and we keep up with it, and then separate that from the longer burns that we wanna get on our ROI, things that don’t need a quick turn, that don’t need the rapid investment. Making sure we keep those both streams going and not ignore the other. The problem is when you focus on one and ignore the other.
Sanjog Aul [00:25:16]:
Here, whatever you mentioned in terms of whether preserving IT investments or going the now and the next, where do you see a typical gap between how you’re thinking versus your business leaders are thinking? Because you could try to be a pied piper, but they may not always follow you.
Ying Chan [00:25:34]:
In the gap, it’s gonna be when IT, when I myself, do not do a good job with the customer empathy. And I’m Pied Piping something that does not make sense to the business. It doesn’t solve their problem. They just see it as a technology for technology’s sake. We see that with PCs. We see that with tablets now in the market. That, hey, I don’t need another one. This one is good enough. This was really cool three, four, five years ago. It doesn’t solve any more problems for me to buy a new one. We see that in our everyday lives, and I think you see it in business. So you have to really be empathetic to what their needs are, what they really see as the next breakthrough when your current breakthrough expires. And really keeping pace in what they’re thinking is gonna be value added to the company, to their business unit, to their needs. Otherwise, it’s just me telling you you need the next iPad or the next whatever else because it is cool technology, but it’s marginal for the business. That make sense?
Sanjog Aul [00:26:42]:
Definitely, it does. And, so when you are looking at the roadblocks, so you know that one is, you know, like you’re talking to the management, getting them to agree to your approach on how you want to build this portfolio, if you will, of technologies which will support the business. Now while all of that is going on, there is some inertia at mid management, at your business unit leader, someone who’s gonna, in one way or the other, influence when this will actually come to fruition. What essentially are the kind of preparatory work you should do before you go and make a big case in front of management, making sure that, okay, when if you get the buy in, then you’re not stuck in execution. Because your success is gonna be not measured that you got them to give you the money, but actually to put that in place.
Matching adoption to the speed of the business 27:33
Ying Chan [00:27:33]:
Absolutely. And I think there’s a follow on measure of that success would be that what you put in place actually did what it is, and that’s a joint ownership between IT and the business unit. But I think the key thing is really making sure that your organization, in my case, my organization, can adopt and move at the speed of business. When I make a promise, it may be 2 cycles out even though the business needed it at one cycle. I am not ready to absorb that technology. It’s one thing to say I’m doing agile. It’s a whole different thing to say that I’m a full on agile DevOps shop that can keep pace at the business. And then secondly is make sure we don’t oversell and over deliver. I’m not sure 100% of the shops out there today need DevOps. I need continuous delivery. I need changes every time a consumer comes on my website. Really, you have to match the speed of your business and what your business needs are and say, hey, maybe just having agile and continuous delivery so our efficiency is the highest is good enough. I don’t need true DevOps where I’m dropping stuff and it’s live the next day on our website or on our application. So map it to the speed of the business. Make sure that your team is culturally, from a software delivery standpoint, from a hardware support standpoint, from a quality and security standpoint can match the speed. Alright. So the last thing you want is you want to check off all those boxes, but we ignored either quality or security, and then pay that price heavily, either in comebacks or poor service or having a breach or some sort of security issue. So there’s so much more to factoring in as technology becomes more than quality and now it’s security. You have to make sure that your team is geared to actually deliver and support and match it to the speed of business. And it could include going a little slower and skipping a cycle to be good rather than fast.
Sanjog Aul [00:29:47]:
I’m gonna pick up on that matching the speed. Now that’s where taking a contrarian view, why should I match to the speed of business today? Because they’re not the ones who either are aware or are as enthusiastic about accelerating. Whereas you know that if you put these disruptive technologies, emerging technologies, as the way to have them rethink the speed they can go at, then that’s when you will pull them along versus trying to push them from behind. What would you do to make this happen where you’re not matching their speed, but let them match to the speed you can take them to?
Sanjog Aul [00:32:39]:
So, here, Ying, the whole idea about matching the speed, it would be almost like well, you know what? There is a saying that if you’re gonna wanna go fast, go alone. But if you wanna go farther, take other people along. In this context though, many people, if you wanna try to pull them or push them to come along, it’s gonna slow down the otherwise better potential that you may have if you were to make them rethink what’s possible. So why match the speed with them? Yes. You have to eventually somehow get them to come to your speed, but it cannot be just us waiting for them to move at their snail pace. So that’s their comfort zone.
Ying Chan [00:33:24]:
Well, I would challenge that. Speed for the sake of speed doesn’t do anything. Again, let’s go back to the goal. The goal is to make money. But I can speed up a business, but the business now has distribution channels. They have marketing channels. You could be in a very cyclical business. You have seasons, all kinds of stuff that are in the way that that’s really the business unit to drive. IT can’t do so much. We can offer to go two or x times faster to money to the business. And I promise you that any business unit that sees a method that are gonna accelerate time to money, they’re gonna take it. But we have to move at the speed they’re able to move in order to realize that money. If we flood a distribution channel and they can’t move it, then they just end up holding the inventory. The market only has a certain amount of consumption rate for your products. So you have to go with that. We all want to be the enviable position of everything we produce is already sold. But that’s typically only one or two or maybe even if you’re really, really lucky, maybe 10% of your portfolio as a company. So I think matching to the speed of business, and we really are empathetic and we are really aligned with the business and the way we think is aligned, we’re like minded with the business. I think that’s where you have to match the speed of business. Now you can have an outlier case where you can obviously see that IT is moving faster than the business. Then I think, again, and the business not responding. I don’t think the way to solve that is to shove it down their throat. There’s more relationship. There’s more understanding of technology that needs to be had with business, and there’s more outreach that we need to do as IT.
Sanjog Aul [00:35:26]:
And then when it comes to organizational readiness, do you think anyone is ever ready to accept what you do, or you essentially piloted an isolated proof of concept, if you will, and then show it to them and then nudge and push them so that it truly gets adopted wherever it’s supposed to. Now while you’re doing it, how much time do you have given the speed at which the emerging technologies even change and become irrelevant? So that you experiment, show it to some people, get it adopted wherever you are before that the technology that you were trying to adopt doesn’t morph itself. What’s the time capsule you’re living in for one emerging technology to the next to its own next iteration?
Funneling candidate technologies toward disruption 36:16
Ying Chan [00:36:16]:
So I would say simply that it’s a funnel. We have great emerging technologies. Maybe there’s 10 or 15 that we’re looking at that can disruptively take our business to the next level. And let’s say our horizon is realistically 5 years for enterprise wide adoption. If I envision 5 years of enterprise wide adoption, I have to keep the business going day to day. So my investment is gonna be, how do I whittle the funnel down to 10 emerging technologies or 10 options within a couple of emerging technologies down to actually making it? And I think you have to look at your road map in that sense of, truly when are we ready to go enterprise wide? Because if it’s not disruptive, it’s not going enterprise wide, then why do it? Back to earlier discussion. Why not milk out the current technology until we hit that truly disruptive technology. R&D, we talked about earlier. Again, that has to happen all the time. It’s a large funnel. So it’s like we do any strategic planning. It’s the typical funnel. So we do quick rounds to design, experiment, and eliminate or look at the potential and say, not ready today, ready in 6 months. Technology is not ready. We’re not ready. Whatever it is, we plot out our road map to when we’re gonna capitalize on those emerging technologies, again, matching the speed of business. So as long as you’re taking an approach that you’re funneling down emerging technologies, you’re willing to winnow, and your goal is to be disruptive. Marginal movements are not worth jumping onto a bandwagon of bleeding and cutting edge technology. I absolutely promise you that a mature, well run implementation, if there’s no big disruptive benefit, is gonna be a better payoff until that disruption hits.
Sanjog Aul [00:38:18]:
Actually, what you mentioned, the response that you gave was very, very articulate when it comes to looking at a portfolio trying to rationalize as you use the word funnel. Right? But with, say, suppose you picked up a candidate, that candidate technology which you want to embrace. But even if you look at, like, you mentioned about Samsung’s S6 versus S8 versus anything else, that one technology that you pick today, and by the time you’re done with sandboxing and trying to get people to adopt a certain that it works in a certain way, that technology itself morphs to something else because they’re evolving too. If you took one candidate, how do you prevent something which becomes a moving target where you’re trying to setting and resetting expectation for the people you want to see adopting that technology. So what essentially say suppose one technology is identified, you go with it, but do you kind of maintain it at the same level till it gets fully adopted and then upgrade, or you essentially say, okay. This technology will keep adopting. Like, if you had Samsung S6 was a corporate standard, would you suddenly say, okay. S8 has come, so let’s go to S8 and then S8 moves to something else because you have to do security testing and everything else. How do you block any subsequent technology evolution of that one technology evolution to try tempting you and other people who start demanding to say, hey. Why are we not using that latest version of the same technology in the initial stages pitched to us?
Ying Chan [00:39:58]:
I do. And I think, again, it’s going back to the disruption that you’re envisioning and when you think you’re gonna really reap the benefit of that technology. So I’ll use an example of containerization and hyperconvergence. Great promise in those technologies. We are going to experiment with those. We’re going to do POCs. We’re going to keep up with how that technology is moving. We’re going to keep moving with the business in order to line up when that actually needs to come to fruition. And we gotta make the promises. We don’t at HHSC or any other company that’s consuming these build them ourselves. These are emerging. So we have to trend. We have to keep track. We have to go along with the promise. If it doesn’t live up, we have to jump off the boat and go to something else. Again, that’s the funneling process. So even with containerization and hyperconvergence, the promise there is that I can spin up any environment that I need within 20 minutes and get going on my project. So just imagine having that promise in any shop. I come out of the boardroom meeting. We wanna build a new product on Java or whatever. I need to set up a whole infrastructure to go do that. I can literally go and get on my computer and configure a complete environment within 20 minutes. That’s a heck of a promise. We’re a ways from that. But it’s happening. Containerization is happening. Hyperconvergence is happening. So we go out, we look at all our vendors that are viable in that space and we engage them. We talk partnership. We don’t talk about commodity type relationships. We wanna drive them to be better. We invest in them during their experiments. They invest in us. We get to a partnership to get where we go in the meantime. We’re monitoring the progress of the technology. We’re monitoring the business needs and keeping cadence. And I think that’s how you do it. You can say, this version’s not ready. There’s not enough benefit to get us to the goal. So here’s the next one. We’re gonna skip it. And the next one comes, we tested it. Hey. It does what we need. Let’s jump. It moves the needle. It moves us towards our goal, which is to reach that disruption.
Sanjog Aul [00:42:33]:
So when you’re talking about the emerging technologies, a natural pushback comes from people because it seems like almost every emerging technology that we are using in some way is automating things and rendering the need for a human intervention to the minimum. And that’s concerning people because we started out as a community, and I’m at shift gear share, to give people jobs to be able to do some meaningful work in the process, feed their families and moving forward. And I’m not saying there’s anything wrong with progress even if it comes to technology. How are you on one hand dealing with that untold fear, which could also be a, you know, could be causing the roadblocks for you someone to embrace the new technologies. But on the other hand, explain to people that it’s gonna help them. Is there a good rationale for us going after all technologies which will move the business forward but take some families down?
Why automation shifts work instead of erasing it 43:43
Ying Chan [00:43:43]:
I think if that is the true model, and I think that’s a true algorithm, then we would have, as a civilization, as a species, run into trouble years ago, starting with the agricultural revolution way before the industrial revolution. I think automation has been happening for a long time. I think that total net unit of work still exists. So, for example, with HHS, I can say we want to get out of running data centers. We want to go to state run data centers. In Texas, that is the Department of Information Resources’ goal to provide centralized infrastructure data centers for the entire state of Texas. As a legacy, we still at HHS have data centers. We’re aggressively trying to move out because there’s no value added for us. But if we look at the state as a net unit, servers still physically exist. Maybe the configuration’s different, maybe the brand’s different, and maybe the architecture’s different, but the need to have serving compute power is still there. The hardware still needs to exist. It still needs to be maintained. My consumption of units of computing power doesn’t change. In fact, it grows. So I’m just merely shifting the work from one bucket to the other. Now when it comes to efficiency, of course, when we consolidate, we can gain efficiency, but I don’t think that automatically necessarily means there’s less jobs. I think the demand continues to grow. The more efficient you are, I think the backlog for compute power is still there. So we just shrink the backlog. In fact, I think having centralized, having moved to that model actually grows the need for more personnel. Requirements that we have to be a 24/7/365 shop now becomes the state’s requirement to be a 24/7/365 shop in the consolidated data centers. So I think the work is shifting, I don’t think this work goes away. And I think if that was true, we never would have survived the agricultural revolution.
Sanjog Aul [00:45:58]:
We should talk about the companies which are in a survival mode. And I’d say that, you know, coming back from the meltdown that we saw, say, almost, like, 9 years ago, we are on that growth path. It looks like there’s an uptick in the marketplace. People, the organizations, are growing, but still, there could be ups and downs in any business. Would you say that emerging technologies definitely, in some cases, have the potential to pull someone out of the red and position them for growth? If those organizations are trying to, are in that position, how can a technology leader make a case for going after those futuristic technologies or some things which provide the potential and could potentially move the needle for that organization, especially when management is scrutinizing every penny spent. Because that would be the job of a CIO to sell or to have the management buy to pull out of already scarce resources. How do we do it?
Sanjog Aul [00:49:20]:
So, when we are looking at this whole idea of using emerging technologies, it may not be the first thing or the top of mind for organizations, their management, and even the CIO in many cases, when they are in the red or they are going through a downturn, and it always happens in all organizations. So when in such cases disruptive technology has the potential to pull them out of the red, what can be done by the technology leader or anyone else involved to make a case for it, especially when you’re watching every penny? And not only stop there, but also see if that could also mean if I could put the emerging technology something specific, then it could prevent going back into such holes. Can we truly make that claim?
Leading a company out of the red with automation 50:08
Ying Chan [00:50:08]:
Absolutely. I think if we look at the situation for a second. When a company is in the red and they are in trouble, what are the levers they’re pulling to get themselves out? Looking at future markets 3 to 5 years down the road is not gonna be what they’re looking at. It’s gonna be cost control. It’s gonna be efficiency of every dollar spent. And probably more than likely, repairing customer relationships. So introduction of technology that’s gonna accelerate that is vital to the survival of a company that is in the red. So let’s look at those one by one. Let’s start with cost control. Automation we know is number one. So if you have an archaic ERP system or whatever it is, it’s time to bring automation in and say, hey, this is how we can help cut the bottom dollar. If it takes 15 people to process accounts payable or accounts receivable and it takes 30 days, if automation can come in and you can bring in a point tool, let’s not force ourselves here. We’re not gonna do a full rollout of SAP to save a company. First of all, that’s, you know, $3,050,000,000 and two years. If you can bring in a point thing to really solve some point issues that really increases the velocity of a process or reduce the cost of a process, I think there’s a huge opportunity to bring in those point solutions. It’s not disruptive in the same view as disrupting future business, but it’s disrupting the inefficiencies of your company. And I think that’s almost universally, if you look at companies who’ve gotten in trouble and come out, they have a very strong footprint in BPI and a very strong footprint in automation. Very few companies hire more people to do back office stuff to uplift them out of a red. No.
Sanjog Aul [00:52:14]:
No. No. Totally. And, you know, to that end, when you’re talking about getting these type of organizations to get out of the red and perhaps stay in black leveraging technologies. Now let’s go back to everyone who’s trying to go in this direction. Anyone who’s trying to go in this direction, how can you make sure that while you are going in this new direction, you do not introduce risk because there’s enough risk already? Security risk, other types of risks are going into uncharted territories.
Ying Chan [00:52:46]:
I think that’s purely how well you execute. Again, factor of previous discussions. Quality, security, all those things are part of what we do today. One of the things that good companies do in downturns is to prepare themselves to come up strong in the upturn. That doesn’t mean going and buying a bunch of stuff because there’s a downturn. There’s not money. Almost every instance of that you see is that companies hold, take their excess capacity at the point of the downturn and fix, streamline, automate their processes. Build its strengths and the processes they need to do to explode out. And that’s no different as we’re executing that with emerging technologies and IT. We can’t be full hearted to bring in things that’s gonna make our system insecure even if it gives us some efficiency or some automation. The automation efficiencies you bring in has to be on some sort of futuristic road map. As CIOs, we have to look out 5 to 10 years. So when we come over the red in 18 or 24 or 12 months, whatever the plan is, you’re left with a cohesive strategy that you springboard off of. If you’re successful and we win, we springboard that energy and we take that momentum and we now move it to disruptive, emerging technologies for the future of the business.


