>>Mhm Hello and welcome to today's session of the 2021 aws Global Public Sector partner awards. I'm Natalie early, your host for the cube and I'm delighted to present our guests. They are Jose Montero, ceo logitech the central America and Rafael Ramirez Product manager. Costa rica Ministry of Education. Welcome gentlemen to today's session. >>Think in Italy >>religion and belief. Well, let's start with Rafael. Please tell us about some of the key challenges that are affecting the Ministry of Education in Post A Rekha. >>One of the main challenges was to be able to have a product that is always available to schools that is easy to use for schools and at the same time that the product should be user friendly. That is you don't need so much training for schools to use it more. A few things that we thought of was to consider our client because schools have a very limited connectivity so we could not use very highly tech technologies because that required very huge. Both advanced and our clients, the schools would be subject to a service that was not available to them. One of the main things was to consider the client and how to reach them. Thanks to Ed attack, the ministry made an alliance with a company that thought about the innovation and they recommended different services that we can provide with a cloud through the cloud so that we are able to get to take the service to deliver the service to our clients and then they can use the platform that we are building in an easy way and at the same time to take care of the quality they need. Something important about schools was that while they were using the product, they were getting benefit that made schools to be willing to participate. >>Terrific. Well Jose I'd love it if you could give us some insight on some of the services that you are providing to the ministry. >>Sure. Um, so when, when the ministry approaches and um, and we had the opportunity to work with them um, of course, as an AWS partner, we thought, well, this is couldn't be better, right? And um, so we um, we we started to think on all of the different services that AWS offers in the cloud to provide to the ministry to be able to reach this gap. That has been for a long time where you see still, you know, people using Excel, using access Microsoft access as databases, um, instead of using all of the energy and all of the, the power that the cloud has. So when we approach to them and um, and we were able to um um, to show all of these different services that AWS could um, could provide to the Minister of Education. It was it was a perfect marriage. So, um, we we started to work with uh, with them and I think it's been awesome. This is only the first part of of a project of eight stages, We are currently working on stage two and stage Three, which will come in August and in January of 2020, And, um, but we're we're super happy to to see just in this first face, everything that has come and all of the data that has come to help the Ministry of Education in order to take action in the student's lives. >>Yeah, that's really terrific to hear. Um, you know, I'd love to hear from Rafael further about why he thinks it was so important to have cloud data at the Ministry of Education level. >>Okay, I >>will give you an important example for us in our country. We would rather gather the, collect data in paper and take that to the central office and this would enter into an Excel file. This take around two months to process all this later and make decisions. Mm When we started with the first service, which was to record the number of enrollees of the students, we could pay teachers on time, we could get the number of students and know where we had the biggest needs. So this would make a very innovative solution. And when the pandemic started, we had the first active service. This allowed us to react very quickly and we realized that in the first quarter, 19,000 students were not in in our schools because we were from a face to face service to a virtual service. So we could react very quickly. We plant a strategy with the Ministry of Education that was to come back. That is the idea goes to locate where students were. And in the next four months we could reduce the dropout From 90 students to 18,000 students. After that, we initiated a Another stage to retrieve those 18,000 students back to school. This was thanks to having the information online in some countries that may not have this problem. This might be very little. But for us, this was very, very important because we were able to reach the poll a wrist households so as to bring those students back to the school. >>Terrific. Well, that's really fantastic. Um, you know, in a non covid world, how do you think this technology will really help you, uh, to enhance education within Costa rica? See I can't. The important thing. >>This is important in the idea of this innovative product for us has a strategy of having a single file of the student. This allows us to do a follow up of what the student has done during the different school years and we can identify their lacks the weaknesses and we can see which are the programs that are more appropriate. Was to replicate this in the rest of the country without a centralized file. Like we have now, we are looking to have this traceability of students so as to have strengthened our witnesses and replicate our strength in the rest of the educational system. one of the most important things when you is that this technological unit, this implementation not only reached primary school students, but also preschool kindergarten, primary school, secondary school higher education, technical Education. So we reached every single sector where the Ministry of Education was able to detect where there was a need in the country. >>Yeah, Terrific. Well, I'd love to hear more from our other guest Jose monteiro Ceo of ecotech to central America. Uh, you know, if you could give us a, you know, more insight, more depth on the services that you provide. You, you talked about like an eight step plan. If you could just highlight those eight steps. >>Sure. Um, so part of this aid stages that we're going to be developing and um, and we hope that we'll be working with the Ministry of Education and every single one of them. Um, It causes where it brings a lot of technologies. For example, there's one that were planning on using, which is recognition from AWS. Um, the fact of um, there was, there's a lot of students that come to the country that have no documentation. There's no passports, There's no um, document I. D. There's nothing, right? So it's really hard for a um within the same school system to be able to track these students, right? Because they can they can go, they can come and they can, if they want, they can change their name. They can they can do a lot of things that are maybe are not correct. And um and sometimes it's not even because they want to do something incorrect. It's just that the uh the system or the yeah the the way of doing things manually, it allows us to do these types of changes. So for example, with with the service like recognition have been able to recognize their face or or recognize their um their idea with their with their fingerprints um and and being able to a um to interact and give give an actual recognition as the word says to this student. It's amazing. It's amazing technology that allows the Ministry of Education and the students to have a voice to have a presence even though they don't have their actual documentation because of whatever reason. Um There is something behind this that helps them um b be valuable and the b at the same time, a present in the in the system. Right? And so and and with with not only that, but with the grading with um with the attendance, with with the behavior with um with a lot of things that we're creating within these stages. Uh It's gonna be, for example, let me give you a quick example. Um There's, for example, the system that we've created for the dropouts. Um The student doesn't come one day, two days, three days and automatically. Now it'll, it'll become an alert and it will start to shot emails and alerts to the different people involved in order to see, hey listen, this student has not come for the last week, two classes. Um, we need you to go and see what's going on, Right? So this is maybe it is something very small, but it can, it can change people's life and they can change students lives and um, and, and the fact of, of knowing where they are, how they are, how are they doing, how their grades are, where we can help them and activate these different types of alerts that, um, that the system allows them to, um, to do that. It helps incredibly, the life of the student in the future, of this, of this student. And uh, in that exact, that is exactly what we're trying to do here. At the end. It's not only, um, it's okay, all of the technological and all of the different efforts that we're doing, but at the end, that's what it matters. It's, it's the student, right? It's it's the fact that, um, that he can come and he can finish his school, he can graduate, he can go to college, he can, he can become an, uh, an entrepreneur and, and be some, some day here and I at AWS conference and give him give a conference, and, and and that is exactly what the Ministry of Education is looking at, what we are looking at the project per se. >>Yeah, I mean, that's a really excellent point that you're making. I mean, this technology is helping real people on the ground and actually shaping their lives for the better. So, I mean, it's really incredible, you know, I'd love to hear more now from Rafael, just a bit what insight he can provide to other ministries, who, you know, also, you know, ministers of Education, who also would consider implementing this kind of technology and also his own experience um with this project in the AWS. >>Well, the connectivity for us is really important, not only with within the institutions of the Ministry of Education, but we also have connections with the Ministry of Health, we also have connections with the software called Sienna Julia, which allows the identification of people within the country and the benefits provided by the stage. So the country where all by little is incorporating the pieces and these cloud services, we have found that before we developed everything AWS has a set of services that allow us to focus on the problem and instead of on the solution of the technology, because services are already available. So at the country level, other ministries are incorporating these services nowadays, for covid management, the Minister of Health has a set of applications that allowed to set links between people that has positive. So this has allowed us to associate the situation with that particular student in our classrooms. So little by little services are converting education and other services into a need that allows us to focus on the problem instead of on technological solutions because services are already there for us to consume >>terrific. You know, I'd love to now shift to our other guest um Jose could you give us some insight what is the next phase for your business when you look at 2021? You know, it's gonna be, I mean, we hope it's going to be a wonderful year. Uh post Covid. Uh you know, what's your vision? >>It's it's interesting that you're saying that Natalie um education has changed Covid has um has put an acceleration to um has accelerated the the whole shift of the technological change in in education. It will not, well I hope it will not go back to the same before Covid. Um it's all of these technologies that are being created that are being organized, that are being it developed um for education specifically um an area where everything has been done the same for a long time. Um we need it, it's crazy to say this, but we needed a Covid time in order to accelerate this type of of organizations right in and now like ministry, the ministries of Education, like like the Minister of Education of Costa rica, they've had this for a long time and they've they've been thinking of the importance of making changes and everything, but until now it became a priority. Why? Because they realized that without these technologies with another pandemic, oh boy, we're going to see the effects of this and, and, and it's going to affect a lot of countries and a lot of students. Um, but it's gonna help to accelerate and understand that for example, internet, it has to be a worldwide access, just like water or electricity is in some, in our countries right now. You know, the fact of a student not having internet, um, we're taking away lot of development for this student. So I believe that after this post covid time education is going to continue to do a lot of changes and you and you'll see this and you'll see this in all of the areas in elementary, in preschool, in university, in high school. Um, you're going to see the changes that this is, um, is starting to do and we've seen it and we've seen it, but now it's going to be at a 23 or four X. So we're pretty excited. We're pretty excited what what the world it's gonna what the world's gonna bring to this table and to this specific area which is education. >>Yeah. That's really terrific to hear a silver lining in this pandemic. And just real quick uh final thoughts from rafael, are you looking to ramp up further? Uh you know, in light of what Jose has said, you know, to ramp up the digital transformation process? >>Yes, I believe this is an opportunity. The country is facing the opportunity, the resistance that we had in the sector of education, the current emergency situation. And they need to use virtual tools Have flattened these curves and narratives. Since 2000 and 20, Costa Rica started a very strong uh teach that trainer process that every four years ago it was very difficult to set to involve all teachers. But nowadays all teachers want to get trained. So we are getting there with virtual trainings with new tools, with the implementation and the use of technology in the classroom. So these kinds of emergencies somehow we have to uh, we know the pain but we know that also the gain of this whole idea of this whole situation. So this opportunity for change is something that we have to take advantage of. Thanks to these cloud services, I believe this is nowadays available and the country realized that these things are closer than what we thought of. An innovation is here to stay and I believe we have to exploit this a little by little >>terrific. Well gentlemen, thank you so much for your insights, loved hearing about the innovations taking place in the classroom, especially overseas in Costa rica. And that of course was Rafael Ramirez, the Product Manager, Costa rica, Ministry of Education, as well as Jose monteiro, the ceo of Ecotech D central America. And of course, I'm Natalie ehrlich, your host for the cube for today's session for the 2021 AWS Global Public Sector Partner Awards. Thanks very much for watching. >>Mhm.

>>Good day. And thanks for joining us as we continue our series here on the Coupa, the AWS startup showcase featuring today, big ID and what this is, will Murphy was the vice president of business development and alliances at big idea. Well, good day to you. How are you going today? Thanks John. I'm doing well. I'm glad to be here. That's great. And acute belong to, I might add, so it's nice to have you back. Um, let's first off, let's share the big ID story. Uh, you've been around for just a handful of years accolades coming from every which direction. So obviously, uh, what you're doing, you're doing very well, but for our viewers who might not be too familiar with big ID, just give us a 30,000 foot level of your core competence. Yeah, absolutely. So actually we just had our five-year anniversary for big ID, uh, which we're quite excited about. >>Um, and that five-year comes with some pretty big red marks. We've raised over $200 million for a unicorn now. Um, but where that comes to and how that came about was that, um, we're dealing with, um, longstanding problems with modern data landscape security governance, privacy initiatives, um, and starting in 2016 with the, uh, authorship of GDPR, the European privacy law organizations, how to treat data differently than they did before they couldn't afford to just sit on all this data that was collected for a couple of reasons, right? Uh, one of them being that it's expensive. So you're constantly storing data, whether that's on-prem or in the cloud is we're going to talk about there's expense that you have to pay to secure the data and keep it from being leaked. You have to pay for access control. It's paid for a lot of different things and you're not getting any value out of that. >>And then there's the idea of like the customer trust piece, which is like, if anything happens to that data, um, your reputational, uh, your reputation as a company and the trust you have between your customers and your organization is broken. So big ID. What we did is we decided that there was a foundation that needed to be built. The foundation was data discovery. If you even an organization knows where its data is, whose data it is, where it is, um, and what it is, and also who has access to it, they can start to make actionable decisions based on the data and based on this new data intelligence. So we're trying to help organizations keep up with modern data initiatives and we're empowering organizations to handle their data sensitive, personal regulated. And what's actually quite interesting is we allow organizations to define what's sensitive to them because like people, organizations are all different. >>And so what's sensitive to one organization might not be to another, it goes beyond the wall. And so we're giving organizations that new power and flexibility, and this is what I still find striking is that obviously with this exponential growth of data and machine learning, just bringing billions of inputs, it seems like right. All of a sudden you have this fast reservoir data, is that the companies in large part, um, don't know a lot about the data that they're harvest state and where it is. And so it's not actionable, it's kind of dark data, right. Just out there reciting. >>Um, and so as I understand it, this, this is your focus basically is tell people, Hey, here's your landscape. Uh, here's how you can better put it to action, why it's valuable and we're going to help them protect it. Um, and they're not aware of these things, which I still find a little striking in this day and age, >>And it goes even further. So, you know, when you start to, when you start to reveal the truth and what's going on with data, there's a couple things that some organizations do. Uh, and I think human instincts, some organizations want to bury their head in the sand. I'm like, everything's fine. Uh, which is, as we know, and we've seen the news frequently, not a sustainable approach. Uh, there's the, there's the, like, let's be a, we're overwhelmed. We don't, we don't even know. We don't even know where to start. Then there's the natural reaction, which is okay. We have to centralize and control everything which defeats the purpose of having, um, shared drives and collaboration and, um, geographically disparate workforces, which we've seen particularly over the last year, how important that resiliency within organizations is to be able to work in different areas. And so, um, it really restricts the value that, um, organizations can get from their data, which is important. And it's important in a ton of ways. Um, and for customers that have allowed their, their data to be, to be stored and harvested by these organizations, they're not getting value out of it either. It's just risk. And we've got to move data from the liability side of the balance sheet, um, to the assets out of the balance sheet. And that comes first and foremost with knowledge. >>So everybody's vote cloud, right? Everybody was on prem and also we build a bigger house and build a bigger house, better security, right in front of us, got it, got to grow. And that's where I assume AWS has come in with you. And, and this was a two year partnership that you've been engaged with in AWS. So maybe shine a little light on that, about the partnership that you've created with AWS, and then how you then in turn transition that, to leverage that for the betterment of your >>Customer base. Yeah. So AWS has been a great partner. Um, they are very forward-looking for an organization, as large as they are very forward looking that they can't do everything that their customers need. And it's better for the ecosystem as a whole to enable small companies like us. And we were very small when we started our relationship with them, uh, to, to join their partner organization. So we're an advanced partner. Now we're part of ISV accelerate. So it's a slightly more lead partner organization. Um, and we're there because our customers are there and AWS like us, but we both have a customer obsessed culture. Um, but organizations are embracing the cloud and there's fear of the cloud. There's there really shouldn't be in the, in the way that we thought of it, maybe five or 10 years ago. And that, um, companies like AWS are spending a lot more money on security than most organizations can. >>So like they have huge security teams, they're building massive infrastructure. And then on top of that, companies themselves can do, can use, uh, products like big ID and other products to make themselves more secure, um, from outside threats and from, from inside threats as well. So, um, we are trying to with them approach modern data challenge as well. So even within AWS, if you put all the information in, like, let's say S3 buckets, that doesn't really tell you anything. It's like, you know, I, I make this analogy. Sometimes I live in Manhattan. If I were to collect all the keys of everybody that lived in a 10 block radius around me and put it into a dumpster, uh, and keep doing that, I would theoretically know where all the keys were there in the dumpster. Now, if somebody asked me, I'd like my keys back, uh, I'd have a really hard time giving them that because I've got to sort through, you know, 10,000 people's keys. >>And I don't really know a lot about it, but those key sale a lot, you know, it says, are you in an old building, are you in a new building? You have a bike, do you have a car? Do you have a gym locker? There's all sorts of information. And I think this analogy holds up for data because of the way you store your data is important, but, um, you can gain a lot of theoretically innocuous, but valuable information from the data that's there while not compromising the sensitive data. And as an AWS has been a fabulous partner in this, they've helped us build a AWS security, have integration out of the box. Um, we now work with over 12 different AWS native, uh, applications from anything like S3 Redshift and Sienna, uh, Kinesis, as well as, um, apps built on AWS like snowflake and Databricks that we, that we connect to. >>And AWS, the technical team of department teams have been an enormous part of our success there. We're very proud of joining the marketplace to be where our customers want to buy enterprise software more and more. Um, and that's another area that we're collaborating, uh, in, in, in joint accounts now to bring more value in simplicity to our joint customers. What's your process in terms of your customer and, uh, evaluating their needs because you just talked about earlier, you had different approaches to security. Some people put their head in the sand, right? Some people admit that there's a problem. Some people fully engaged. So I assume there's also different levels of sophistication in terms of whatever you have in place and then what their needs are. So if you would shine a little light on that, you know, where they are in terms of their data landscape and AWS and its tools, but you just touched them on multiple tools you have in your service. >>Now, all that comes together to develop what would be, I guess, a unique program for a company's specific needs. It is. We started talking to the largest enterprise accounts when we were founded and we still have a real proclivity and expertise in that area. So the issues with the large enterprise accounts and the uniqueness there is scale. They have a tremendous amount of data, HR data, financial data, customer data, you name it, right? Like, we'll go. We can, we can go dry mouth talking about how many you're saying data. So many times with, with these large customers, um, freight Ws scale, wasn't an issue. They can store it, they can analyze it. They can do tons. It where we were helping is that we could make that safer. So if you want to perform data analytics, you want to ensure that sensitive data is not being, or that you want to make sure you're not violating local, not national or industry specific regulations. >>Financial services is a great example. There's dozens of regulations at the federal level in the United States and each state has their own regulations. This becomes increasingly complex. So AWS handles this by, by allowing an amazing amount of customization for their customers. They have data centers in the right places. They have experts on, on, uh, vertical, specific issues. Big ID handles this similarly in some ways, but we handle it through ostensive ability. So one of our big things is we have to be able to connect to every everywhere where our customers have data. So we want to build a foundation of like, let's say first let's understand the goals is the goal compliance with the law, which it should be for everybody that should just be like, we need to, we need to comply with the law. Like that's, that's easy. Yeah. Then as the next piece, like, are we dealing with something legacy? >>Was there a breach? Do we need to understand what happened? Are we trying to be forward-looking and understanding? We want to make sure we can lock down our most sensitive data, tier our storage tier, our security tier are our analytics efforts, which also is cost-effective. So you don't have to do, uh, everything everywhere, um, or is the goal a little bit like we needed to get a return on investment faster, and we can't do that without de-risking some of that. So we've taken those lessons from the enterprise where it's exceedingly difficult, uh, to work because of the strict requirements, because the customers expect more. And I think like AWS, we're bringing a down market. Uh, we have some, a new product coming out. Uh, it's exclusive for, uh, AWS now called small ID, which is a cloud native, a smaller version, lighter weight version of our product for customers in the more commercial space in the SMB space where they can start to build a foundation of understanding their data or, um, protection for security for, for, for privacy. >>And, and before I let you go here, what I'd like to hear about is practical application. You know, somebody that, that you've, you know, that you were able to help and assist you evaluated. Cause you've talked about the format here. You've talked about your process and talk about some future, I guess, challenges, opportunities, but, but just to give our viewers an idea of maybe the kind of success you've already had to, uh, give them a perspective on that, this share a couple stories. If you wouldn't mind with some work that you guys did and rolled up your sleeves and, and, uh, created that additional value >>For your customers. Yeah, absolutely. So I'll give a couple examples. I'm going to, I'm going to keep everyone anonymized, uh, as a privacy based company, in many ways, what we, we try to respect colors. Um, but let's talk about different types of sensitive data. So we have customers that, um, intellectual property is their biggest concern. So they, they do care about compliance. They want to comply with all local and national laws where they, where they, their company resides all their offices are, but they were very concerned about sensitive data sprawl around intellectual property. They have a lot of patents. They have a lot of sensitive data that way. So one of the things we did is we were able to provide custom tags and classifications for their sensitive data based on intellectual property. And they could see across their cloud environment, across their on-premise environment across shared drives, et cetera. >>We're sensitive data had sprawl where it had moved, who's having access to it. And they were able to start realigning their storage strategy and their content management strategy, data governance strategy, based on that, and start to, uh, move sensitive data back to certain locations, lock that down on a higher level could create more access control there, um, but also proliferate and, uh, share data that more teams needed access to. Um, and so that's an example of a use case that I don't think we imagined necessarily in 2016 when we were focused on privacy, but we've seen that the value can come from it. Um, so yeah, no, I mean, the other piece is, so we've worked with some of the largest AWS customers in the world. Their concern is how do we even start to scan the Tedder, terabytes and petabytes of data in any reasonable fashion? >>Uh, without it being out of date, if we create this data map, if we prayed this data inventory, uh, it's going to be out of date day one, as soon as we say, it's complete, we've already added more. That's where our scalability fit Sam. We were able to do a full scan of their entire AWS environment and, uh, months, and then keep up with the new data that was going into their AWS environment. This is a, this is huge. This was groundbreaking for them. So our hyper scan capability, uh, that we've wrote, brought out that we rolled out to AWS first, um, was a game changer for them to understand what data they had and where it is who's it is et cetera at a way that they never thought they could keep up with. You know, I I'm, I brought back to the beginning of code when the British government was keeping track of all the COVID cases on spreadsheets and spreadsheet broke. >>Um, it was also out of date, as soon as they entered something else. It was already out of date. They couldn't keep up with them. Like there's better ways to do that. Uh, luckily they think they've moved on from, from that, uh, manual system, but automation using the correct human inputs when necessary, then let, let machine learning, let, uh, big data take care of things that it can, uh, don't waste human hours that are precious and expensive unnecessarily and make better decisions based on that data. You know, you raised a great point too, which I hadn't thought of about the fact is you do your snapshot today and you start evaluating all their needs for today. And by the time you're going to get that done, their needs have now exponentially grown. It's like painting the golden gate bridge, right. You get that year and now you've got to pay it again. I said it got bigger, but anyway, they will. Thanks for the time. We certainly appreciate it. Thanks for joining us here on the sort of showcase and just remind me that if you ever asked for my keys, keep them out of that dumpster to be here.

>>Yeah, yeah. >>Welcome back to our final session in cultivating a data fluent culture track earlier today, we heard from experts like Valerie from the Data Lodge who shared best practices that you can apply to build that data flew into culture in your organization and tips on how to become the next analyst of the future from Yasmin at Comcast and Steve at all Terex. Then we heard from a captivating session with Cindy Hausen and Ruhollah Benjamin, professor at Princeton, on how now is our chance to change the patterns of injustice that we see have been woven into the fabric of society. If you do not have a chance to see today's content, I highly recommend that you check it out on demand. There's a lot of great information that you could start applying today. Now I'm excited to introduce our next session, which will take a look at how the democratization of data is powering digital transformation in the insurance industry. We have two prestigious guests joining us today. First Jim Bramblett, managing director of North America insurance practice, lead at its center. Throughout Jim's career, he's been focused on large scale transformation from large to midsize insurance carriers. His direct experience with clients has traditionally been in the intersection of technology, platform transformation and operating remodel redesign. We also have Michael cast Onus, executive VP and chief operating officer at DNA. He's responsible for all information technology, analytics and operating functions across the organization. Michael has led major initiatives to launch digital programs and incorporating modern AP I architectures ER, which was primarily deployed in the cloud. Jim, please take it away. >>Great. Thanks, Paula E thought we'd cover a few things today around around data. This is some of the trends we see in data within the insurance sector. And then I'll hand it over to Michael Teoh, take you through his story. You know, I think at the macro level, as we think about data and we think about data in the context of the insurance sector, it's interesting because the entire history of the insurance sector has been built on data and yet, at the same time, the entire future of it relies on that same data or similar similar themes for data. But but different. Right? So we think about the history, what has existed in an insurance companies. Four walls was often very enough, very enough to compete, right? So if you think about your customer data, claims, data, CRM, data, digital data, all all the data that was yeah, contained within the four walls of your company was enough to compete on. And you're able to do that for hundreds of years. But as we we think about now as we think about the future and the ability to kind of compete on data, this data comes from many more places just than inside your four walls. It comes from every device, every human, every vehicle, every property, every every digital interaction. Um in upon this data is what we believe insurers need to pivot to. To compete right. They need to be able to consume this data at scale. They need to be able to turn through this data to drive analytics, and they serve up insights based on those analytics really at the desktop of insurance professionals. And by the way, that has to be in the natural transition of national transaction. Of that employees work day. So an underwriter at a desktop claim him on the desktop, the sales associate of desktop. Those insights need to be served up at that point in time when most relevant. And you know. So if we think about how insurance companies are leveraging data, we see this really on kind of three horizons and starting from the left hand side of the page here, this is really brilliant basics. So how my leveraging core core data and core applied intelligence to monetize your existing strategy? And I think this brilliant based, brilliant basics concept is where most of most of my clients, at least within insurance are are today. You know, how are we leveraging data in the most effective way and putting it in the hands of business decision makers to make decisions largely through reporting and some applied intelligence? Um, Horizon two. We see, you know, definitely other industries blazing a trail here, and this is really about How do we integrate ecosystems and partners Now? I think within insurance, you know, we've had data providers forever, right? Whether it's NPR data, credit data risk data, you know, data aggregators and data providers have been a critical part of the insurance sector for for decades. I think what's different about this this ecosystem and partnership model is that it's much more Oneto one and it's much more, you know, kind of. How do we integrate more tightly and how do we become more embedded in each other's transactions? I think that we see some emergence of this, um, in insurance with automotive manufacturers with building management systems. But I think in the grand scheme of things, this is really very, very nascent for us as a sector. And I think the third horizon is is, you know, how do we fundamentally think about data differently to drive new business models? And I, you know, I don't know that we haven't ensure here in North America that's really doing this at any sort of scale. We certainly see pilots and proofs of concepts. We see some carriers in Europe farther down this path, but it's really it's really very new for us. A Z Think about these three horizons for insurance. So you know what's what's behind all this and what's behind. You know, the next powering of digital transformation and and we think at the end of the exercise, its data data will be the next engine that powers digital transformation. So in this exhibit, you know we see the three horizons across the top. You know, data is activated and activating digital transformation. And this, you know, this purple 3rd, 3rd road here is we think some of the foundational building blocks required to kind of get this right. But I think what's most important about about this this purple third bar here is the far right box, which is business adoption. Because you can build this infrastructure, you can have. You know, this great scalable cloud capability. Um, you can create a bunch of applications and intelligence, but unless it's adopted by the business, unless it's democratized, unless those insights and decisions air served up in the natural course of business, you're gonna have trouble really driving value. So that way, I think this is a really interesting time for data. We think this is kind of the next horizon to power the next age of digital transformation for insurance companies. With that brief prelude, I am, I'm honored. Thio, turn it over to Michael Stone Is the Cielo at CNN Insurance? >>Thanks, Jim, for that intro and very exciting Thio be here is part of part of beyond when I think a digital transformation within the context of insurance, actually look at it through the lens of competing in an era of near perfect information. So in order to be able to deliver all of the potential value that we talked about with regard to data and changing ecosystem and changing demands, the question becomes, How do you actually harness the information that's available to everybody to fundamentally change the business? So if you'll indulge me a bit here, let me tell you just a little bit more for those that don't know about insurance, what it really is. And I use a very long run on sentence to do that. It's a business model where capital is placed against risk in the form of products and associated services sold the customers through channels two companies to generate a return. Now, this sounds like a lot of other businesses in across multiple industries that were there watching today. But the difference within insurance is that every major word in that long run on sentence is changing sources of capital that we could draw on to be able to underwrite risk of going away. The nature of risk itself is changing from the perspective of policies that live six months to a year, the policies that could last six minutes. The products that we're creating are changing every day for our ability to actually put a satellite up in the air or ensure against the next pandemic. Our customers are not just companies or individuals, but they could be governments completely different entities than we would have been in sharing in the past and channels were changing. We sell direct, we sell through brokers and products are actually being embedded in other products. So you may buy something and not even know that insurance is a part of it. And what's most interesting here is the last word which is around return In the old world. Insurance was a cash flow business in which we could bring the premium in and get a level of interest income and being able to use that money to be able thio buffer the underwriting results that we would have. But those returns or dramatically reduced because of the interest income scenario, So we have to generate a higher rate of return. So what do we need to do? Is an insurance company in through this digital transformation to be able to get there? Well, fundamentally, we need to rethink how we're using information, and this is where thought spot and the cloud coming for us. We have two basic problems that we're looking to solve with information. The first one is information veracity. Do we believe it? When we get it? Can we actually trust it? Do we know what it means when we say that this is a policy in force or this is a new customer where this is the amount of attention or rate that we're going to get? Do we actually believe in that piece of data? The second is information velocity. Can we get it fast enough to be able to capitalize upon it? So in other words, we're We're working in a situation where the feedback loop is closing quickly and it's operating at a speed that we've never worked in before. So if we can't solve veracity and velocity, then we're never going to be able to get to where we need to go. So when we think of something like hot spot, what do we use it for? We use it to be able to put it in the hands of our business years so that they could ask the key questions about how the business is running. How much profit of my generating this month? What brokers do I need to talk? Thio. What is my rate retention? Look like what? The trends that I'm seeing. And we're using that mechanism not just to present nice visualizations, but to enable that really quick, dynamic question and answer and social, socially enabled search, which completely puts us in a different position of being able to respond to the market conditions. In addition, we're using it for pattern recognition. Were using it for artificial intelligence. We're gonna be capitalizing on the social aspect of of search that's that's enabled through thought spot and also connecting it into our advanced machine learning models and other capabilities that we currently have. But without it solving the two fundamental problems of veracity and velocity, we would be handicapped. So let me give you some advice about if I were in your position and you don't need to be in sleepy old industry like insurance to be able to do this, I'll leave you with three things. The first one is picking water holes so What are the things that you really want to be good at? What are the pieces of information that you really need to know more about? I mean, in insurance, its customers, it's businesses, locations, it's behavior. There are only a few water also really understand and pick those water holes that you're going to be really good at. The second is stand on the shoulders of giants. You know, in the world of technology, there's often a philosophy that says, Well, I can build it something better than somebody else create if I have it in house. But I'm happy to stand on the shoulders of giants like Thought Spot and Google and others to be able to create this capability because guess what? They're gonna out innovate any of the internal shops all day and every day. So don't be afraid. Thio. Stand side by side on the shoulders of giants as part of your journey. Unless you've got to build these organizations not just the technology for rapid experimentation and learning, because guess what? The moment you deliver insight, it begs another question, which also could change the business process, which could change the business model and If your organization the broader organization of business technology, analytics, customer service operations, etcetera is not built in a way that could be dynamic and flexible based on where the market is or is going, then you're gonna miss out on the opportunity. So again, I'm proud to be part of the fast black community. Really love the technology. And if if you look too, have the same kind of issues with your given industry about how you can actually speed up decision making, deliver insights and deliver this kind of search and recommended to use it. And with that, let's go to some questions. >>Awesome. Thank you so much, Michael and Jim for that in depth perspective and those tangible takeaways for our audience. We have a few minutes left and would love to ask a few questions. So here's the first one for Michael Michael. What are some of the most important things that you know now that you didn't know before you started this process? I think one of >>the things that's a great question. I think one of the things that really struck me is that, you know, traditional thinking would be very use case centric or pain point centric Show me, uh, this particular model or a particular question you want me to answer that can build your own analytics to do that or show me a deficiency in the system and I can go and develop a quick head that will do well, then you know, wallpaper over that particular issue. But what we've really learned is the foundation matters. So when we think about building things is building the things that are below the waterline, the pipes and plumbing about how you move data around how the engines work and how it all connects together gives you the above the waterline features that you could deliver to. You know, your employees into your customers much faster chasing use cases across the top above the waterline and ignoring what's below the water line to me. Is it really, uh, easy recipe too quick? Get your way to nothing. So again, focus on the foundation bill below the water line and then iterated above the water line that z what the lessons we've learned. It has been very effective for us. >>I think that's a very great advice for all those watching today on. But Here's one for Jim. Jim. What skills would you say are required for teams to truly adopt this digital transformation process? >>Yeah, well, I think that's a really good question, and I think I'd start with it's It's never one. Well, our experience has shown us number a one person show, right? So So we think to kind of drive some of the value that that that Michael spoke about. We really looked across disciplinary teams, which is a an amalgamation of skills and and team members, right? So if you think about the data science skills required, just kinda under under understand how toe toe work with data and drive insights, Sometimes that's high end analytic skills. Um, where you gonna find value? So some value architectural skills Thio really articulate, you know, Is this gonna move the needle for my business? I think there's a couple of critical critical components of this team. One is, you know, the operation. Whatever. That operation maybe has to be embedded, right, because they designed this is gonna look at a piece of data that seems interesting in the business Leader is going to say that that actually means nothing to me in my operation. So and then I think the last the last type of skill would be would be a data translator. Um, sitting between sometimes the technology in the business so that this amalgamation of skills is important. You know, something that Michael talked about briefly that I think is critical is You know, once you deliver insight, it leads to 10 more questions. So just in a intellectual curiosity and an understanding of, you know, if I find something here, here, the implications downstream from my business are really important. So in an environment of experimenting and learning thes thes cross discipline teams, we have found to be most effective. And I think we thought spot, you know, the platform is wired to support that type of analysis and wired to support that type of teaming. >>Definitely. I think that's though there's some really great skills. That's for people to keep in mind while they are going through this process. Okay, Michael, we have another question for you. What are some of the key changes you've had to make in your environment to make this digital transformation happen? >>That's a great question. I think if you look at our environment. We've got a mixture of, you know, space agent Stone age. We've got old legacy systems. We have all sorts of different storage. We have, you know, smatterings of things that were in cloud. The first thing that we needed to do was make a strong commitment to the cloud. So Google is our partner for for the cloud platform on unabashedly. The second thing that we needed to dio was really rethink the interplay between analytics systems in operational systems. So traditionally, you've got a large data warehouses that sit out over here that, you know, we've got some kind of extract and low that occurs, and we've got transactional operational systems that run the business, and we're thinking about them very differently from the perspective of bringing them together. How Doe I actually take advantage of data emotion that's in the cloud. So then I can actually serve up analytics, and I can also change business process as it's happening for the people that are transacting business. And in the meantime, I can also serve the multiple masters of total cost and consumption. So again, I didn't applications are two ships that pass in the night and never be in the world of Sienna. When you look at them is very much interrelated, especially as we want to get our analytics right. We want to get our A i m all right, and we want to get operational systems right By capturing that dated motion force across that architecture er that was an important point. Commit to the cloud, rethink the way we think analytics systems, work and operational systems work and then move them in tandem, as opposed to doing one without the other one in the vacuum. >>That's that's great advice, Michael. I think it's very important those key elements you just hit one question that we have final question we have for Jim. Jim, how do you see your client sustain the benefits that they've gained through this process? >>Yeah, it's a really good question. Um, you know, I think about some of the major themes around around beyond right, data fluency is one of them, right? And as I think about fluency, you only attain fluency through using the language every single day. They were day, week, over week, month over month. So you know, I think that applies to this. This problem too. You know, we see a lot of clients have to change probably two things at the same time. Number one is mindset, and number two is is structure. So if you want to turn these data projects from projects into processes, right, so so move away from spinning up teams, getting getting results and winding down. You wanna move away from that Teoh process, which is this is just the way working for these teams. Um, you have to change the mindset and often times you have to marry that with orb structure change. So So I'm gonna spin up these teams, but this team is going to deliver a set of insights on day. Then we're gonna be continuous improvement teams that that persist over time. So I think this shifting from project teams to persistent teams coupled with mindset coupled with with or structure changed, you know, a lot of times has to be in place for a period of time to get to get the fluency and achieve the fluency that that most organizations need. >>Thanks, Jim, for that well thought out answer. It really goes to show that the transformation process really varies when it comes to organizations, but I think this is a great way to close out today's track. I like to think Jim, Michael, as well as all the experts that you heard earlier today for sharing. There's best practice as to how you all can start transforming your organization's by building a data fluent culture, Um, and really empowering your employees to understand what data means and how to take actions with it. As we wrap up and get ready for the next session, I'd like to leave you all with just a couple of things. Number one if you miss anything or would like to watch any of the other tracks. Don't worry. We have everything available after this event on demand number two. If you want to ask more questions from the experts that you heard earlier today, you have a chance to do so. At the Meet The Experts Roundtable, make sure to attend the one for track four in cultivating a data fluent culture. Now, as we get ready for the product roadmap, go take a sip of water. This is something you do not want to miss. If you love what you heard yesterday, you're gonna like what you hear today. I hear there's some type of Indiana Jones theme to it all, so I won't say anything else, but I'll see you there.

>>Yeah, yeah. >>Welcome back. I'm so excited to introduce our next session empowerment through inclusion, reimagining society and technology. This is a topic that's personally very near and dear to my heart. Did you know that there's only 2% of Latinas in technology as a Latina? I know that there's so much more we could do collectively to improve these gaps and diversity. I thought spot diversity is considered a critical element across all levels of the organization. The data shows countless times. A diverse and inclusive workforce ultimately drives innovation better performance and keeps your employees happier. That's why we're passionate about contributing to this conversation and also partnering with organizations that share our mission of improving diversity across our communities. Last beyond, we hosted the session during a breakfast and we packed the whole room. This year, we're bringing the conversation to the forefront to emphasize the importance of diversity and data and share the positive ramifications that it has for your organization. Joining us for this session are thought spots Chief Data Strategy Officer Cindy Housing and Ruhollah Benjamin, associate professor of African American Studies at Princeton University. Thank you, Paola. So many >>of you have journeyed with me for years now on our efforts to improve diversity and inclusion in the data and analytic space. And >>I would say >>over time we cautiously started commiserating, eventually sharing best practices to make ourselves and our companies better. And I do consider it a milestone. Last year, as Paola mentioned that half the room was filled with our male allies. But I remember one of our Panelists, Natalie Longhurst from Vodafone, suggesting that we move it from a side hallway conversation, early morning breakfast to the main stage. And I >>think it was >>Bill Zang from a I G in Japan. Who said Yes, please. Everyone else agreed, but more than a main stage topic, I want to ask you to think about inclusion beyond your role beyond your company toe. How Data and analytics can be used to impact inclusion and equity for the society as a whole. Are we using data to reveal patterns or to perpetuate problems leading Tobias at scale? You are the experts, the change agents, the leaders that can prevent this. I am thrilled to introduce you to the leading authority on this topic, Rou Ha Benjamin, associate professor of African studies at Princeton University and author of Multiple Books. The Latest Race After Technology. Rou ha Welcome. >>Thank you. Thank you so much for having me. I'm thrilled to be in conversation with you today, and I thought I would just kick things off with some opening reflections on this really important session theme. And then we could jump into discussion. So I'd like us to as a starting point, um, wrestle with these buzzwords, empowerment and inclusion so that we can have them be more than kind of big platitudes and really have them reflected in our workplace cultures and the things that we design in the technologies that we put out into the world. And so to do that, I think we have to move beyond techno determinism, and I'll explain what that means in just a minute. Techno determinism comes in two forms. The first, on your left is the idea that technology automation, um, all of these emerging trends are going to harm us, are going to necessarily harm humanity. They're going to take all the jobs they're going to remove human agency. This is what we might call the techno dystopian version of the story and this is what Hollywood loves to sell us in the form of movies like The Matrix or Terminator. The other version on your right is the techno utopian story that technologies automation. The robots as a shorthand, are going to save humanity. They're gonna make everything more efficient, more equitable. And in this case, on the surface, he seemed like opposing narratives right there, telling us different stories. At least they have different endpoints. But when you pull back the screen and look a little bit more closely, you see that they share an underlying logic that technology is in the driver's seat and that human beings that social society can just respond to what's happening. But we don't really have a say in what technologies air designed and so to move beyond techno determinism the notion that technology is in the driver's seat. We have to put the human agents and agencies back into the story, the protagonists, and think carefully about what the human desires worldviews, values, assumptions are that animate the production of technology. And so we have to put the humans behind the screen back into view. And so that's a very first step and when we do that, we see, as was already mentioned, that it's a very homogeneous group right now in terms of who gets the power and the resource is to produce the digital and physical infrastructure that everyone else has to live with. And so, as a first step, we need to think about how to create more participation of those who are working behind the scenes to design technology now to dig a little more a deeper into this, I want to offer a kind of low tech example before we get to the more hi tech ones. So what you see in front of you here is a simple park bench public bench. It's located in Berkeley, California, which is where I went to graduate school and on this particular visit I was living in Boston, and so I was back in California. It was February. It was freezing where I was coming from, and so I wanted to take a few minutes in between meetings to just lay out in the sun and soak in some vitamin D, and I quickly realized, actually, I couldn't lay down on this bench because of the way it had been designed with these arm rests at intermittent intervals. And so here I thought. Okay, the the armrest have, ah functional reason why they're there. I mean, you could literally rest your elbows there or, um, you know, it can create a little bit of privacy of someone sitting there that you don't know. When I was nine months pregnant, it could help me get up and down or for the elderly, the same thing. So it has a lot of functional reasons, but I also thought about the fact that it prevents people who are homeless from sleeping on the bench. And this is the Bay area that we were talking about where, in fact, the tech boom has gone hand in hand with a housing crisis. Those things have grown in tandem. So innovation has grown within equity because we haven't thought carefully about how to address the social context in which technology grows and blossoms. And so I thought, Okay, this crisis is growing in this area, and so perhaps this is a deliberate attempt to make sure that people don't sleep on the benches by the way that they're designed and where the where they're implemented and So this is what we might call structural inequity. By the way something is designed. It has certain effects that exclude or harm different people. And so it may not necessarily be the intense, but that's the effect. And I did a little digging, and I found, in fact, it's a global phenomenon, this thing that architects called hostile architecture. Er, I found single occupancy benches in Helsinki, so only one booty at a time no laying down there. I found caged benches in France. And in this particular town. What's interesting here is that the mayor put these benches out in this little shopping plaza, and within 24 hours the people in the town rallied together and had them removed. So we see here that just because we have, uh, discriminatory design in our public space doesn't mean we have to live with it. We can actually work together to ensure that our public space reflects our better values. But I think my favorite example of all is the meter bench. In this case, this bench is designed with spikes in them, and to get the spikes to retreat into the bench, you have to feed the meter you have to put some coins in, and I think it buys you about 15 or 20 minutes. Then the spikes come back up. And so you'll be happy to know that in this case, this was designed by a German artists to get people to think critically about issues of design, not just the design of physical space but the design of all kinds of things, public policies. And so we can think about how our public life in general is metered, that it serves those that can pay the price and others are excluded or harm, whether we're talking about education or health care. And the meter bench also presents something interesting. For those of us who care about technology, it creates a technical fix for a social problem. In fact, it started out his art. But some municipalities in different parts of the world have actually adopted this in their public spaces in their parks in order to deter so called lawyers from using that space. And so, by a technical fix, we mean something that creates a short term effect, right. It gets people who may want to sleep on it out of sight. They're unable to use it, but it doesn't address the underlying problems that create that need to sleep outside in the first place. And so, in addition to techno determinism, we have to think critically about technical fixes that don't address the underlying issues that technology is meant to solve. And so this is part of a broader issue of discriminatory design, and we can apply the bench metaphor to all kinds of things that we work with or that we create. And the question we really have to continuously ask ourselves is, What values are we building in to the physical and digital infrastructures around us? What are the spikes that we may unwittingly put into place? Or perhaps we didn't create the spikes. Perhaps we started a new job or a new position, and someone hands us something. This is the way things have always been done. So we inherit the spike bench. What is our responsibility when we noticed that it's creating these kinds of harms or exclusions or technical fixes that are bypassing the underlying problem? What is our responsibility? All of this came to a head in the context of financial technologies. I don't know how many of you remember these high profile cases of tech insiders and CEOs who applied for Apple, the Apple card and, in one case, a husband and wife applied and the husband, the husband received a much higher limit almost 20 times the limit as his wife, even though they shared bank accounts, they lived in Common Law State. And so the question. There was not only the fact that the husband was receiving a much better interest rate and the limit, but also that there was no mechanism for the individuals involved to dispute what was happening. They didn't even know what the factors were that they were being judged that was creating this form of discrimination. So in terms of financial technologies, it's not simply the outcome that's the issue. Or that could be discriminatory, but the process that black boxes, all of the decision making that makes it so that consumers and the general public have no way to question it. No way to understand how they're being judged adversely, and so it's the process not only the product that we have to care a lot about. And so the case of the apple cart is part of a much broader phenomenon of, um, racist and sexist robots. This is how the headlines framed it a few years ago, and I was so interested in this framing because there was a first wave of stories that seemed to be shocked at the prospect that technology is not neutral. Then there was a second wave of stories that seemed less surprised. Well, of course, technology inherits its creator's biases. And now I think we've entered a phase of attempts to override and address the default settings of so called racist and sexist robots, for better or worse. And here robots is just a kind of shorthand, that the way people are talking about automation and emerging technologies more broadly. And so as I was encountering these headlines, I was thinking about how these air, not problems simply brought on by machine learning or AI. They're not all brand new, and so I wanted to contribute to the conversation, a kind of larger context and a longer history for us to think carefully about the social dimensions of technology. And so I developed a concept called the New Jim Code, which plays on the phrase Jim Crow, which is the way that the regime of white supremacy and inequality in this country was defined in a previous era, and I wanted us to think about how that legacy continues to haunt the present, how we might be coding bias into emerging technologies and the danger being that we imagine those technologies to be objective. And so this gives us a language to be able to name this phenomenon so that we can address it and change it under this larger umbrella of the new Jim Code are four distinct ways that this phenomenon takes shape from the more obvious engineered inequity. Those were the kinds of inequalities tech mediated inequalities that we can generally see coming. They're kind of obvious. But then we go down the line and we see it becomes harder to detect. It's happening in our own backyards. It's happening around us, and we don't really have a view into the black box, and so it becomes more insidious. And so in the remaining couple minutes, I'm just just going to give you a taste of the last three of these, and then a move towards conclusion that we can start chatting. So when it comes to default discrimination. This is the way that social inequalities become embedded in emerging technologies because designers of these technologies aren't thinking carefully about history and sociology. Ah, great example of this came Thio headlines last fall when it was found that widely used healthcare algorithm affecting millions of patients, um, was discriminating against black patients. And so what's especially important to note here is that this algorithm healthcare algorithm does not explicitly take note of race. That is to say, it is race neutral by using cost to predict healthcare needs. This digital triaging system unwittingly reproduces health disparities because, on average, black people have incurred fewer costs for a variety of reasons, including structural inequality. So in my review of this study by Obermeyer and colleagues, I want to draw attention to how indifference to social reality can be even more harmful than malicious intent. It doesn't have to be the intent of the designers to create this effect, and so we have to look carefully at how indifference is operating and how race neutrality can be a deadly force. When we move on to the next iteration of the new Jim code coded exposure, there's attention because on the one hand, you see this image where the darker skin individual is not being detected by the facial recognition system, right on the camera or on the computer. And so coated exposure names this tension between wanting to be seen and included and recognized, whether it's in facial recognition or in recommendation systems or in tailored advertising. But the opposite of that, the tension is with when you're over included. When you're surveiled when you're to centered. And so we should note that it's not simply in being left out, that's the problem. But it's in being included in harmful ways. And so I want us to think carefully about the rhetoric of inclusion and understand that inclusion is not simply an end point. It's a process, and it is possible to include people in harmful processes. And so we want to ensure that the process is not harmful for it to really be effective. The last iteration of the new Jim Code. That means the the most insidious, let's say, is technologies that are touted as helping US address bias, so they're not simply including people, but they're actively working to address bias. And so in this case, There are a lot of different companies that are using AI to hire, create hiring software and hiring algorithms, including this one higher view. And the idea is that there there's a lot that AI can keep track of that human beings might miss. And so so the software can make data driven talent decisions. After all, the problem of employment discrimination is widespread and well documented. So the logic goes, Wouldn't this be even more reason to outsource decisions to AI? Well, let's think about this carefully. And this is the look of the idea of techno benevolence trying to do good without fully reckoning with what? How technology can reproduce inequalities. So some colleagues of mine at Princeton, um, tested a natural learning processing algorithm and was looking to see whether it exhibited the same, um, tendencies that psychologists have documented among humans. E. And what they found was that in fact, the algorithm associating black names with negative words and white names with pleasant sounding words. And so this particular audit builds on a classic study done around 2003, before all of the emerging technologies were on the scene where two University of Chicago economists sent out thousands of resumes to employers in Boston and Chicago, and all they did was change the names on those resumes. All of the other work history education were the same, and then they waited to see who would get called back. And the applicants, the fictional applicants with white sounding names received 50% more callbacks than the black applicants. So if you're presented with that study, you might be tempted to say, Well, let's let technology handle it since humans are so biased. But my colleagues here in computer science found that this natural language processing algorithm actually reproduced those same associations with black and white names. So, too, with gender coded words and names Amazon learned a couple years ago when its own hiring algorithm was found discriminating against women. Nevertheless, it should be clear by now why technical fixes that claim to bypass human biases are so desirable. If Onley there was a way to slay centuries of racist and sexist demons with a social justice box beyond desirable, more like magical, magical for employers, perhaps looking to streamline the grueling work of recruitment but a curse from any jobseekers, as this headline puts it, your next interview could be with a racist spot, bringing us back to that problem space we started with just a few minutes ago. So it's worth noting that job seekers are already developing ways to subvert the system by trading answers to employers test and creating fake applications as informal audits of their own. In terms of a more collective response, there's a federation of European Trade unions call you and I Global that's developed a charter of digital rights for work, others that touches on automated and a I based decisions to be included in bargaining agreements. And so this is one of many efforts to change their ecosystem to change the context in which technology is being deployed to ensure more protections and more rights for everyday people in the US There's the algorithmic accountability bill that's been presented, and it's one effort to create some more protections around this ubiquity of automated decisions, and I think we should all be calling from more public accountability when it comes to the widespread use of automated decisions. Another development that keeps me somewhat hopeful is that tech workers themselves are increasingly speaking out against the most egregious forms of corporate collusion with state sanctioned racism. And to get a taste of that, I encourage you to check out the hashtag Tech won't build it. Among other statements that they have made and walking out and petitioning their companies. Who one group said, as the people who build the technologies that Microsoft profits from, we refuse to be complicit in terms of education, which is my own ground zero. Um, it's a place where we can we can grow a more historically and socially literate approach to tech design. And this is just one, um, resource that you all can download, Um, by developed by some wonderful colleagues at the Data and Society Research Institute in New York and the goal of this interventionist threefold to develop an intellectual understanding of how structural racism operates and algorithms, social media platforms and technologies, not yet developed and emotional intelligence concerning how to resolve racially stressful situations within organizations, and a commitment to take action to reduce harms to communities of color. And so as a final way to think about why these things are so important, I want to offer a couple last provocations. The first is for us to think a new about what actually is deep learning when it comes to computation. I want to suggest that computational depth when it comes to a I systems without historical or social depth, is actually superficial learning. And so we need to have a much more interdisciplinary, integrated approach to knowledge production and to observing and understanding patterns that don't simply rely on one discipline in order to map reality. The last provocation is this. If, as I suggested at the start, inequity is woven into the very fabric of our society, it's built into the design of our. Our policies are physical infrastructures and now even our digital infrastructures. That means that each twist, coil and code is a chance for us toe. We've new patterns, practices and politics. The vastness of the problems that we're up against will be their undoing. Once we accept that we're pattern makers. So what does that look like? It looks like refusing color blindness as an anecdote to tech media discrimination rather than refusing to see difference. Let's take stock of how the training data and the models that we're creating have these built in decisions from the past that have often been discriminatory. It means actually thinking about the underside of inclusion, which can be targeting. And how do we create a more participatory rather than predatory form of inclusion? And ultimately, it also means owning our own power in these systems so that we can change the patterns of the past. If we're if we inherit a spiked bench, that doesn't mean that we need to continue using it. We can work together to design more just and equitable technologies. So with that, I look forward to our conversation. >>Thank you, Ruth. Ha. That was I expected it to be amazing, as I have been devouring your book in the last few weeks. So I knew that would be impactful. I know we will never think about park benches again. How it's art. And you laid down the gauntlet. Oh, my goodness. That tech won't build it. Well, I would say if the thoughts about team has any saying that we absolutely will build it and will continue toe educate ourselves. So you made a few points that it doesn't matter if it was intentional or not. So unintentional has as big an impact. Um, how do we address that does it just start with awareness building or how do we address that? >>Yeah, so it's important. I mean, it's important. I have good intentions. And so, by saying that intentions are not the end, all be all. It doesn't mean that we're throwing intentions out. But it is saying that there's so many things that happened in the world, happened unwittingly without someone sitting down to to make it good or bad. And so this goes on both ends. The analogy that I often use is if I'm parked outside and I see someone, you know breaking into my car, I don't run out there and say Now, do you feel Do you feel in your heart that you're a thief? Do you intend to be a thief? I don't go and grill their identity or their intention. Thio harm me, but I look at the effect of their actions, and so in terms of art, the teams that we work on, I think one of the things that we can do again is to have a range of perspectives around the table that can think ahead like chess, about how things might play out, but also once we've sort of created something and it's, you know, it's entered into, you know, the world. We need to have, ah, regular audits and check ins to see when it's going off track just because we intended to do good and set it out when it goes sideways, we need mechanisms, formal mechanisms that actually are built into the process that can get it back on track or even remove it entirely if we find And we see that with different products, right that get re called. And so we need that to be formalized rather than putting the burden on the people that are using these things toe have to raise the awareness or have to come to us like with the apple card, Right? To say this thing is not fair. Why don't we have that built into the process to begin with? >>Yeah, so a couple things. So my dad used to say the road to hell is paved with good intentions, so that's >>yes on. In fact, in the book, I say the road to hell is paved with technical fixes. So they're me and your dad are on the same page, >>and I I love your point about bringing different perspectives. And I often say this is why diversity is not just about business benefits. It's your best recipe for for identifying the early biases in the data sets in the way we build things. And yet it's such a thorny problem to address bringing new people in from tech. So in the absence of that, what do we do? Is it the outside review boards? Or do you think regulation is the best bet as you mentioned a >>few? Yeah, yeah, we need really need a combination of things. I mean, we need So on the one hand, we need something like a do no harm, um, ethos. So with that we see in medicine so that it becomes part of the fabric and the culture of organizations that that those values, the social values, have equal or more weight than the other kinds of economic imperatives. Right. So we have toe have a reckoning in house, but we can't leave it to people who are designing and have a vested interest in getting things to market to regulate themselves. We also need independent accountability. So we need a combination of this and going back just to your point about just thinking about like, the diversity on teams. One really cautionary example comes to mind from last fall, when Google's New Pixel four phone was about to come out and it had a kind of facial recognition component to it that you could open the phone and they had been following this research that shows that facial recognition systems don't work as well on darker skin individuals, right? And so they wanted Thio get a head start. They wanted to prevent that, right? So they had good intentions. They didn't want their phone toe block out darker skin, you know, users from from using it. And so what they did was they were trying to diversify their training data so that the system would work better and they hired contract workers, and they told these contract workers to engage black people, tell them to use the phone play with, you know, some kind of app, take a selfie so that their faces would populate that the training set, But they didn't. They did not tell the people what their faces were gonna be used for, so they withheld some information. They didn't tell them. It was being used for the spatial recognition system, and the contract workers went to the media and said Something's not right. Why are we being told? Withhold information? And in fact, they told them, going back to the park bench example. To give people who are homeless $5 gift cards to play with the phone and get their images in this. And so this all came to light and Google withdrew this research and this process because it was so in line with a long history of using marginalized, most vulnerable people and populations to make technologies better when those technologies are likely going toe, harm them in terms of surveillance and other things. And so I think I bring this up here to go back to our question of how the composition of teams might help address this. I think often about who is in that room making that decision about sending, creating this process of the contract workers and who the selfies and so on. Perhaps it was a racially homogeneous group where people didn't want really sensitive to how this could be experienced or seen, but maybe it was a diverse, racially diverse group and perhaps the history of harm when it comes to science and technology. Maybe they didn't have that disciplinary knowledge. And so it could also be a function of what people knew in the room, how they could do that chest in their head and think how this is gonna play out. It's not gonna play out very well. And the last thing is that maybe there was disciplinary diversity. Maybe there was racial ethnic diversity, but maybe the workplace culture made it to those people. Didn't feel like they could speak up right so you could have all the diversity in the world. But if you don't create a context in which people who have those insights feel like they can speak up and be respected and heard, then you're basically sitting on a reservoir of resource is and you're not tapping into it to ensure T to do right by your company. And so it's one of those cautionary tales I think that we can all learn from to try to create an environment where we can elicit those insights from our team and our and our coworkers, >>your point about the culture. This is really inclusion very different from just diversity and thought. Eso I like to end on a hopeful note. A prescriptive note. You have some of the most influential data and analytics leaders and experts attending virtually here. So if you imagine the way we use data and housing is a great example, mortgage lending has not been equitable for African Americans in particular. But if you imagine the right way to use data, what is the future hold when we've gotten better at this? More aware >>of this? Thank you for that question on DSO. You know, there's a few things that come to mind for me one. And I think mortgage environment is really the perfect sort of context in which to think through the the both. The problem where the solutions may lie. One of the most powerful ways I see data being used by different organizations and groups is to shine a light on the past and ongoing inequities. And so oftentimes, when people see the bias, let's say when it came to like the the hiring algorithm or the language out, they see the names associated with negative or positive words that tends toe have, ah, bigger impact because they think well, Wow, The technology is reflecting these biases. It really must be true. Never mind that people might have been raising the issues in other ways before. But I think one of the most powerful ways we can use data and technology is as a mirror onto existing forms of inequality That then can motivate us to try to address those things. The caution is that we cannot just address those once we come to grips with the problem, the solution is not simply going to be a technical solution. And so we have to understand both the promise of data and the limits of data. So when it comes to, let's say, a software program, let's say Ah, hiring algorithm that now is trained toe look for diversity as opposed to homogeneity and say I get hired through one of those algorithms in a new workplace. I can get through the door and be hired. But if nothing else about that workplace has changed and on a day to day basis I'm still experiencing microaggressions. I'm still experiencing all kinds of issues. Then that technology just gave me access to ah harmful environment, you see, and so this is the idea that we can't simply expect the technology to solve all of our problems. We have to do the hard work. And so I would encourage everyone listening to both except the promise of these tools, but really crucially, um, Thio, understand that the rial kinds of changes that we need to make are gonna be messy. They're not gonna be quick fixes. If you think about how long it took our society to create the kinds of inequities that that we now it lived with, we should expect to do our part, do the work and pass the baton. We're not going to magically like Fairy does create a wonderful algorithm that's gonna help us bypass these issues. It can expose them. But then it's up to us to actually do the hard work of changing our social relations are changing the culture of not just our workplaces but our schools. Our healthcare systems are neighborhoods so that they reflect our better values. >>Yeah. Ha. So beautifully said I think all of us are willing to do the hard work. And I like your point about using it is a mirror and thought spot. We like to say a fact driven world is a better world. It can give us that transparency. So on behalf of everyone, thank you so much for your passion for your hard work and for talking to us. >>Thank you, Cindy. Thank you so much for inviting me. Hey, I live back to you. >>Thank you, Cindy and rou ha. For this fascinating exploration of our society and technology, we're just about ready to move on to our final session of the day. So make sure to tune in for this customer case study session with executives from Sienna and Accenture on driving digital transformation with certain AI.