>>From the Bellagio hotel in Las Vegas, it's the cube covering UI path forward for brought to you by UI path. >>Welcome back to Las Vegas. Lisa Martin, with Dave Vellante at UI path forward for, we have had it all today. Lots of great guests. We've had weather, we've had rain. We are outside and lots of great conversations going on. Next up, we're going to be talking about automation at healthcare giant. Merck. Joining us from merch is Dan Boyd automation leader, and from CGI partner of UI paths, bill angles, senior automation architect, guys, welcome to the program. >>Thanks for having us. >>So Dan, we'll go ahead and start with you. Let's talk about Merck and the implement and the adoption of automation, such a history company. >>Yeah. Thank you. Um, our journey started about two years ago and started with the small team and has evolved ever since we started just the handful of folks we've evolved, uh, from the size of our team, matured, operationally and expanded our capabilities along that journey to where we are today. And it continues to evolve as the technology changes. And it's been exciting to see the adoption at Merck over, you know, across the enterprise. Um, it's been an educational process, but it's been exciting just to see that understanding of the power that automation can deliver to them. And they see the value in making it real to them has been key. Um, then once it's real and they get excited and the word spreads and they appreciate the value right before their eyes and bill, are you, >>Uh, industry specialized or more automation specialist? >>Yeah. Yeah. So I'm more, uh, automation specialized, but uh, you know, CGI, we partner with our industry experts to identify use cases for automation and I help kind of, you know, solution the best approach to automation. Uh, and you know, so I actually started, you know, with, with Merck a little bit earlier before it was really formalized and, uh, just CGI is a large partner of merch and embedded within various areas of business. And, you know, I, I ended up educating, uh, CGI on automation and here's what to look for, you know, in a, in a, in a great use case for automation and, you know, really, we started to drum up some internal excitement and then came up with some actual real use cases within Merck, proved it out early. And then we began to partner with, uh, Dan and his team. >>Can you share a little bit about some of those use cases? Yes. >>So, you know, the ones that, uh, we've worked on are really specific within, uh, various areas, uh, within the division. So Dan, you want to talk about some of the >>You're working on yeah, I'll share one use case within a specific market of merch, and it's a commercial area where they were embarking on a revision in their customer engaged engagement approach in this market and where the, they had a problem. They, they needed to get the invoices out of SAP for customers. So that was on the one side of the process on the other was a customer portal where the customers needed access near real time to those invoices. So when they came to us, they had the invoices kind of set up to be emailed out of SAP. So they had that process set up. The problem is how do they get them over here into this customer portal? Say the backup plan was to have a temporary workers come on and do that manually handle the open emails with the invoices attachments and get them loaded. >>So we came in, uh, they called us in, in the 11th hour and we were able to, fortunately that the process was straightforward, uh, whereas invoices were coming through, uh, an email attachment and that was set up. So basically we automated the reading of the emails, the processing of the PDF attachments and saved them into a shared drive where there was another process to load them into SAP. So the volume was really large on a daily basis. Initially it was estimated at approximately 2,500 emails per day with these invoices. Um, so that would estimate it would take about 125 hours of people time to do that manually. Um, so that's what we automated. And in the end it was the averages it's over 3000 a day. So, um, the solution really came in and, and we were able to deliver that. And it's been a really, they were, they were static with what they could do, and then they saw the art of the possible with, with this automation. So it's a good success story. And, um, it's exciting to see, and they were thrilled >>And it's not an uncommon story, right. Where you're automating mundane tasks that was pushing a lot of paper, a lot of copy and pasting. Um, do you see how far away, and maybe we're there already? You think about mark it's it's uh, in a, in a unique industry, we've got, got highly skilled scientists too in serious R and D high risk trials. You got partners, you do some organic, some inorganic, you've got the manufacturing components. So a lot of different parts to the business. And when you think about saving time, as you think about some of the, the scientists that are working on various pipeline products, highly paid, if you can save more of their time, wow. That even drops more to the bottom line. Are we at that point yet? We heard the stats this morning. It was 2% or some single digit percentage of our processes are automated. How far away are we from attacking those types of automations? Are we there today? >>Uh, we do automations for all the, all the functions across Merck. Um, in some places adoption is farther along than others in their journey, but yeah, um, from the shop floor and the manufacturing sites, we found opportunities to, to introduce automation there. And even in the, in the labs in various capacities, see the use cases continue to grow and the adoption continue. We see that growing as well. >>Do you find that the, the highly skilled, uh, automations targeted at highly skilled folks are, are harder to sort of get your hands around, but they give you bigger ROI? Or is it not the case? Is it all sort of earn and burn? >>Yeah, from my perspective, I think it's, you know, use case by use case. Like if it's a, a complex use case, it requires, you know, more advanced capabilities, uh, you know, machine learning models, you know, leveraging, uh, you know, AI center within UI path, uh, you know, those they can, you know, provide, you know, fairly sizeable ROI, but I think is for those highly skilled workers, I'll give one example is, you know, out in, out in the labs, we, we helped, you know, automate some things that, you know, just made their life easier, right. Uh, you know, tests running overnight, if something failed, uh, with, with a test that was happening, then, you know, they, they wouldn't know about it and they lose critical data for, for these early tests that they're doing in, in the, in the preclinical cycle. So we actually put in a UI path robots to, to monitor and send alerts and provide recovery to make their lives a lot easier. Uh, so they don't have to worry about things, you know, failing in the middle of the night, you have a UI path robot, you know, supporting them in that map, that aspect, >>What's an automation, architecture look like we, where do we start architecting automation? >>Well, I think the journey, uh, so where do you start with an automation? Right. It's really understanding the use case. It comes down to what is the, the end to end process, and then where, where can we automate, uh, within that process and what is the right set of automation capabilities? So, you know, RPA is great for, you know, um, where we get, where we need to interact with user interfaces. But if we can, uh, you know, interact with API APIs, we would do that. You know, preferably over a UI is, is to keep, keep it more of a seamless integration. But I think it's about understanding the process, laying out the right solution, uh, if there's an opportunity to improve the process prior to automating it, you know, if there's, if there is that ability, then we'll look to do that. And we've done that. We may change that process, uh, up a little bit, just to make automation more efficient, more effective. Uh, and so, and then it just, we built it and we deploy it and they start to realize the value >>Hard. Is it dental prove the, on the versus just automating what's, what's known. In other words, you've got dependencies and there are complexities there w what's your experience in terms of how you approached it >>From my experience and what we found to be best practice and bill touched on it. But every use case is of course different than the, the corresponding process. Very, very varied, but really what's key, I think, is to right upfront, understand the end to end process. And a lot of cases, my team it's new to us, right. But the process owners, they live it every day. So understanding, partnering with them to really understand the end to end solution in the form of like a process map. So you can kind of echo back your understanding of their process and get that nod of the head from them and say, yes, you understand that this is an accurate representation. Then we can with the spirit of trying to get it right the first time. And, but it really, I think is incumbent upon us to really get that in-depth understanding upfront. And a lot of cases, if there's time sensitivity in the end, it's just more efficient and saves a lot of rework. So, >>So working backwards, sorry, at least working backwards from the known existing process and then implementing an automation is probably the best starting point, as opposed to trying to work backwards from some kind of the outcome that you envision. But, but I would think there's attractiveness in the, in the ladder. Right. So that you're not just repeating a process that may be outdated. >>Yeah. So your, uh, it comes down to a couple of things. So when you're initially looking at a process, you know, should we automate this or not? And how complex is it? You need to understand what is the potential benefit. So, you know, how much, uh, you know, how much time am I able to, uh, you know, have those workers reinvest into other areas of work, right. Or what other, what are some other benefits? Uh, you know, there, there may be some, uh, you know, compliance fines that were experienced through automation, we're able to, you know, to make sure we're meeting SLS and so on. Uh, so you is a lot to, you know, defining the benefits, the automation, putting a value to that. And then the process of going through the actual process, understand the complexity, right? And then you can come up with, you know, here's, here's what it's gonna take to build this thing. Here's the potential value. And then we have ways where we track, you know, what's, how has that ROI trending once it's in production? Uh, so we'll be, that gives us more insight. >>Dan, I've got a question for you. One of the conversations that Dave and I had earlier on the program was about automation as a boardroom topic. I'd love to get your perspectives. Merck is a history organization, been around for a long time. Cultural change is incredibly challenging, but I'd love to get your perspective on where is automation at Merck's board. Is that something that is really key to transformation? >>I'd say automation falls under our strategic initiative, just around digital digital transformation, right? So it's a sub pillar of that. So that is a strategic imperative and very important. And just being a more efficient and, and leveraging technology effectively, um, just to make merch more efficient and, and, and optimized and RPA and automation plays a part in that. I mean, >>That's what I suspected Lisa this morning when we have in that conversation, it seems to me that you wouldn't necessarily create an automation stove pipe at the board meeting. You might want to report on how these automations have affected, whether it's the income statement or the health of the company, et cetera. But it seems to me to be a fundamental part of the digital transformation, um, which involves a lot of different things, data and cloud and strategy and it et cetera. So is that pretty >>Common bill? Yeah, I, yes, it is. I mean, when, when an organization is looking to automate there's, you know, various angles are coming out, they're coming from the top-down approach where, you know, management saying, Hey, we need to, we need to automate what's, let's look across all the divisions and, and figure out where, where we should go. But then it's also, you know, bottom up where, you know, folks out in, out within the various lines of business know, they, they know the problems. They know, they know the business processes. So there's a couple of different angles where, you know, you you're able to discover new opportunities to automate. Uh, but those also those smaller ones opened the door to understanding, you know, much larger processes where we can look, you know, automate more of the upstream or downstream in that process. Are there variations of the process? So >>Was, was merch more bottom-up or top-down or middle out? I wouldn't say it's >>Started bottoms up. That's really out there. It came from the top-down. So as bill touched on, I think it's really key that we do have, uh, from, from this coming from the top, from our leadership is endorsing it and advocating it, but also we're on the, on the ground floor and educating. So the people with the hands-on doing the process, they understand it and the word is spreading. They see we've, we've made it real for them. Now it's real for them, and they can appreciate the value. And they're happy to be able to do more, to be freed up from the tedious tasks and do more interesting work. >>So we did start in the department, there was a champion with a budget who said, Hey, I'm going to try this and then look what I got. Yeah, >>Yeah. You definitely need the champion. So part of that is creating champions out in the different business lines to truly own the pipeline and understand the opportunities are out there and say, yeah, this is a good opportunity. This, this one let's look at it later. So you definitely have to have those folks out there that, that understand the technology, but also understand the business. >>How has that changed in the last 18 months with healthcare care undergoing such? I mean, my goodness, the things that have happened in a healthcare organization, how has that accelerated the need for things like automation, Christian, for both of you and for mark as well? Yeah. >>Yeah. So mark initiated, uh, like most companies that digital transformation, three, three plus years ago, and this just became an extension of that. And, and it's, it's a, it's a must, right? Just to stay up with the, the digital transformation and everything that's happening in this world. And, and obviously, uh, COVID accelerated, helped accelerate it in certain areas and made it real for a lot of people and appreciate the value and the need for it. >>Yeah. W within CGI, just across all of our clients, it's automation is really towards the top of the list of strategic priorities. So it's, so we've seen this massive just acceleration of, of needing to automate more and more and more, you know, which is, which is great. >>What's it like inside a merch these days, you guys must be really excited with all that. I mean, I know it's early days and nothing has been fully blessed yet, but I mean, you know, some of the big has got a lot of headlines and obviously, you know, we've been taking jabs, et cetera, but, but now here's Merck in the headlines. It's, it's gotta be an exciting time for you guys. >>Yeah. It's, it's great to be part of a company whose mission is to save and improve lives and right. It's um, with today, it's, it's really becoming real and more relevant, uh, of that mission and vision. So it's exciting. >>There were any gotchas when you go into this, I'm sure there are into this automation journey. What kinds of things would you advise people, Hey, make sure that you deal with these, whether it's an audit scope, consideration or things that you definitely don't want to do, or do you want to do? >>Yeah. It just comes down to the, you know, choosing the right use case to start with. Right. Making sure that you, if you're just starting out in your automation journey, you know, start with those use cases that you can quickly prove value for and then tackle the more complex ones. That's good >>For folks to know where to start, especially when there's still such a tumultuous environment that we're living in. Dan and bill. Thank you for joining Dave and Manet, talking about automation, the innovation that you're doing at Merck partnering with CGI really appreciate >>Your time. Thanks for having us >>For Dave Volante. I'm Lisa Martin, coming to you from windy, chilly Las Vegas. We are at UI path forward for stick around Dave and I will be right back with our next guest.

>>Yeah. >>Welcome back for our last session of the day how to deliver career making business outcomes with Search and AI. So we're very lucky to be hearing from Canada. Canadian Tire, one of Canada's largest and most successful retailers, have been powered 4.5 1000 employees to maximize the value of data with self service insights. So today we're joining us. We have Yarrow Baturin, who is the manager of Merch analytics and planning to support at Canadian Tire and then also Andrea Frisk, who is the engagement manager manager for thoughts. What s O U R Andrea? Thanks so much for being here. And with >>that, >>I'll pass the mic to you guys. >>Thank you for having us. Um, already, I I think I'll start with an introduction off who I am, what I do. A Canadian entire on what Canadian pair is all about. So, as a manager of Merch analytics at Canadian Tire, I support merchant organization with reporting tools, and then be I platform to enable decision making on a day to day basis. What is? Canadian Tire's Canadian tire is one of the largest retailers in Canada. Um, serving Canadians with a number of lines of business spanning automotive fixing, living, playing and SNG departments. We have a number of banners, including sport check Marks Party City Phl that covers more than 1700 locations. So as an organization, we've got vast variety of different data, whether it's product or loyalty. Now, as the time goes on, the number of asks the number off data points. The complexity of the analysis has been increasing on banned traditional tools. Analytical tools such as Excel Microsoft Access do find job but start hitting their limitations. So we started on the journey of exploring what other B I platforms would be suitable for our needs. And the criteria that we thought about as we started on that journey is to make sure that we enable customization as well as the McCarthy ization of data. What does that mean? That means we wanted to ensure that each one of the end users have ability to create their own versions off the report while having consistency from the data standpoint, we also wanted Thio ensure that they're able to create there at hawks search queries and draw insights based on the desired business needs. As each one of our lines of business as each one of our departments is quite unique in their nature. And this is where thoughts about comes into play. Um, you checked off all the boxes? Um, as current customers, as potential customers, you will discover that this is the tool that allows that at hawks search ability within a matter of seconds and ability to visualize the information and create those curated pin boards for each one of the business units, depending on what the needs are. And now where? I guess well, Andrea will talk a little bit more about how we gained adoption, but the usage was like and how we, uh, implemented the tool successfully in the organization. >>Okay, so I actually used to work for Canadian tire on DSO. During that time, I helped Thio build training and engaging users to sort of really kick start our use cases. Andi, the ongoing process of adopting thought spot through Canadian Tire s 01 of the sort of reasons that we moved into using thought spot was there was a need Thio evolve, um, in order to see the wealth of data that we had coming in. So the existing reporting again. And this is this sort of standard thoughts bought fix is, um, it brings the data toe. Everyone on git makes it more accessible, so you get more out of your data. So we want to provide users with the ability to customize what they could see and personalized three information so that they could get their specific business requirements out of the data rather than relying on the weekly monthly quarterly reporting. That was all usually fairly generic eso without the ability to deep dive in. So this gave the users the agility thio optimize their campaigns, optimize product murder, urgency where products are or where there's maybe supply chain gaps. Andi just really bring this out for trillions of rose to become accessible. Thio the Canadian tire. That's what user base think. That's the slide. >>That's the slight, Um So as Andrea talked about the business use of the particular tool, let's talk a little bit about how we set it up and a wonderful journey of how it's evolved. So we first implemented 5.3 version of that spot on the Falcon server on we've been adding horsepower to it over time. Now mhm. What I want to stress is the importance off the very first, Data said. That goes into the tool toe. Actually engage the users and to gain the adoption and to make sure there is no argument whether the tool is accurate or not. So what we've started with is a key p I marked layer with all the major metrics that we have and all the available permutations and combinations off the dimensions, whether it's a calendar dimension, proud of dimension or, let's say, customer attribute now, as we started with that data set, we wanted to make sure that we're we have the ability to add and the dimensions right. So now, as we're implementing the tool, we're starting to add in more dimension tables to satisfy the needs off our clients if you want to call it that way as they want to evolve their analytics. So we started adding in some of the store attributes we started adding in some of the product attributes on when I refer to a product attributes, let's say, uh, it involves costs and involves prices involved in some of the strategic internal pieces that we're thinking about now as the comprehensive mark contains right now, in our instance, close to five billion records. This is where it becomes the one source of truth for people declaring information against right so as they go in, we also wanted to make sure when they Corey thought spot there, we're really Onley. According one source of data. One source of truth. It became apparent over time, obviously, that more metrics are needed. They might not be all set up in that particular mark. And that's when we went on the journey off implementing some of the new worksheets or some of the new data sets particularly focused on the four looking pieces. And uh, that's where it becomes important to say This is how you gain the interest and keep the interests of the public right. So you're not just implementing a number off data sets all at once and then letting the users be you're implementing pieces and stages. You're keeping the interest thio, the tool relevant. You're keeping, um, the needs of the public in mind. Now, as you can imagine on the Falcon server piece, um, adding in the horsepower capacity might become challenging the mawr. Billions of Rosie erratic eso were actually in the middle of transitioning our environment to azure in snowflake so that we can connect it. Thio embrace capability of thoughts cloud. And that's where I'm looking forward to that in 2021 I truly believe this will enable us Thio increase the speed off adoption Increase the speed of getting insights out of the tool and scale with regards Thio new data sets that we're thinking about implementing as we're continuing our thoughts about journey >>Okay, so how we drove adoption Thio 4500 plus users eso When we first started Thio approach our use case with the merchants within Canadian Tire We had meetings with these users with who are used place is gonna be with and sort of found out. What are they searching for, Where they typically looking at what existing reports are available for them. Andi kind of sought out to like, What are those things where you're pulling this on your own or someone else's pulling this data because it's not accessible yet And we really use that as our foundation to determine one what data we needed to initially bring into the system but also to sort of create those launchpad pin boards that had the base information that the users we're gonna need so that we could twofold, make it easy for them, toe adopt into the tool and also quickly start Thio, deactivate or discontinue those reports. And just like these air now only available in thought spot because with the sort of formatting within thought spot around dates, it's really easy to make this year's report last year report etcetera. Just have everything roll over every month or a recorder s. So that was kind of some of the pre work foundation when we originally did it. But really, it's been a lot of training, a lot of training. So we conducted ah, lot of in person training, obviously pre co vid eso. We've started to train the group that we targeted, which was the merchants and all of the like, surrounding support groups. Eso we had planners going in and training as well, so that everyone who was really closely connected to the merchants I had an idea of what thoughts about what was and how to use it and where the reports were, and so we just sort of rolled it out that way, and then it started to fly like wildfire. Eso the merchants start to engage with supply chain to have conversations, or the merchants were engaging with the vendors to sort of have negotiations about pricing. And they're creating these reports and getting the access to the information so quickly, and they're sharing it out that we had other groups just coming to us asking, How do I get into thoughts about how can I get in on DSO on top of those groups, we also sought out other heavy analytics groups such a supply chain where we felt like they could have the same benefits if they on boarded into thought spot with their data as well on Ben. Just continuing to evolve the training roll out. Um, you know, we continued to engage with the users, >>so >>we had a newsletter briefly Thio, sort of just keep informing users of the new data coming in or when we actually upgraded our system. So the here are the new features that you'll start seeing. We did virtual trainings and maintaining an F A Q document with the incoming questions from the users, and then eventually evolved into a self guided learning so that users that were coming to a group, or maybe we've already done a full rollout could come in and have the opportunity to learn how to use thought spot, have examples that were relevant to the business and really get started. Eso then each use case sort of after our initial started to build into a formula of the things that we needed to have. So you need to understand it. Having SMEs ready and having the database Onda worksheets built out sort of became the step by step path to drive adoption. Um, from an implementation timeline, I think they're saying, Took about two months and about half of that waas Kenny entire figuring out how figuring out our security, how to get the data in on, Do we need the time to set up the environment and get on Falcon? So then, after that initial two months, then each use case that we come through. Generally, we've got users trained and SMEs set up within about 2 to 3 weeks after the data is ingested. It's not obviously, once snowflakes set up on the data starts to get into that and the data feeds in, then you're really just looking at the 2 to 3 weeks because the data is easily connected in, >>um, no. All right, let's talk about some of the use cases. So we started with what data we've implemented. Andrea touched upon what Use a training look like what the back curate that piece wants. Now let's talk a little bit about use cases and how we actually leverage thoughts bought together the insights. So the very first one is ultimately the benefit of the tool to the entire organization. Israel Time insights. To reiterate what Andrea said, we first implemented the tool with our buyers. They're the nucleus of any retail organization as they work with everybody within the company and as the buyer's eyes, Their responsibility to ensure both the procurement and the sales channel, um, stays afloat at the end of the day, right? So they need information on a regular basis. They needed fast. They needed timely, and they needed in a fashion that they choose to digest it. It right? Not every business is the same. Not every individual is the same. They consume digest, analyze information differently. And that's what that's what allows you to dio whether it's the search, whether it's a customized onboard, please now supply chain unexpected things. As Andrea mentioned Irish work a lot of supply chain. What is the goal of supply chain to receive product and to be able to ship that product to the stores Now, as our organization has been growing and is doing extremely well, we've actually published Q three results recently. Um, the aspect off prioritization at D C level becomes very important, And what drives some of that prioritization is the analysis around what the upcoming sales would be for specific products for specific categories. And that's where again thoughts. But is one of the tools that we've utilized recently to set our prioritization logic from both inbound and outbound us. It's right because it gives you most recent results. It gives you most granular results, depending on the business problem that you're trying to tackle. Now let's chat a little bit about covert 19 response, because this one is an extremely interesting case as a pandemic hit back in March. Um, as you can imagine, the everyday life a Canadian entire became as business unusual is our executives referred to it under business unusual. This speed and the intensity of the insights and the analytics has grown exponentially. And the speed and the intensity of the insights is driven by the fact that we were trying Thio ensure that we have the right selection of products for our Canadian customers because that's ultimately bread and butter off all of the retailers is the customers, right? So thoughts bought allowed us to have early trends off both sales and inventory patterns, where, whether we were stalking out of some of the products in specific stories of provinces, whether we saw some of the upload off different lines of business, depending on the region, ality right as pandemic hit, for example, um, gym's closed restaurants closed. So as Canadian pack carries a wide variety of different lines of business, we actually offer a wide selection of exercise equipment and accessories, cycling products as well as the kitchen appliances and kitchen accessories pieces. Right? So all of those items started growing exponentially and in certain areas more than others. And this is where thoughts about comes into play. A typical analysis on what the region ality of the sales has been over the last couple of days, which is lifetime and pandemic terms, um, could have taken days weeks for analysts to ultimately cobbled together an Excel spreadsheet. Meanwhile, it can take a couple of seconds for 12 Korean tosspot set up a PIN board that can be shared through a wide variety of individuals rather than fording that one Excel spreadsheet that gets manipulated every single time. And then you don't get the right inside. So from again merch supply chain covert response aspect of things. That spot has been one of those blessings and one of those amazing tools to utilize and improve the speed off insights, improved the speed of analytics and improve the speed of decision making that's ultimately impacting, then consumer at the store level. So Andrea talked about 4500 users that we have that number of school. But what I owe the recently like to focus on, uh, Andrew and I laughing because I think the last time we've spoken at a larger forum with the fastball community, I think we had only 500 users. That was in the beginning >>of the year in in February, we were aiming to have like 1000 >>exactly. So mission accomplished. So we've got 4500 employees now. Everybody asked me, Yeah, that's a big number, but how many times do people actually log in on a weekly or daily basis? I'm or interested in that statistic? So lately, um, we've had more than 400 users on the weekly basis. What's what's been cool lately is, uh, the exponential growth off ad hoc ways. So throughout October, we've reached a 75,000 ad hoc ways in our system and about 13,000 PIN board views. So why is that's that's significant? We started off, I would say, in January of 2020 when Andrea refers to it, I think we started off with about 40 45,000 ad hoc worries a month. So again, that was cool. But at the end of the day, we were able to thio double that amount as more people migrate to act hawk searches from PIN board views, and that's that's a tremendous phenomena, because that's what that's about is all about. So I touched upon a little bit about exercise and cycling. So these are our quarterly results for Q two, um, that have showed tremendous growth that we did not plan for, that we were able to achieve with, ultimately the individuals who work throughout the organization, whether it's the merch organization or whether it's the supply chain side of the business. But coming together and utilizing a B I platform by tools such a hot spot, we can see triple digit growth results. Eso What's next for us users at Hawks searches? That's fantastic. I would still like to get to more than 1200 people on the weekly basis. The cool number to me is if all of our lifetime users were you were getting into the tool on a weekly basis. That would be cool. And what's proven to be true is ultimately the only way to achieve it is to keep surprising and delighting them and your surprising and delighting them with the functionality of the tool. With more of the relevant content and ultimately data adding in more data, um, is again possible through ET else, and it's possible through pulling that information manually. But it's expensive, expensive not from the sense of monetary value, but it's expensive from the size time, all of those aspects of things So what I'm looking forward to is migrating our platform to azure in snowflake and being able thio scale our insights accordingly. Toe adding more data to Adam or incites more, uh, more individual worksheets and data sets for people to Korea against helps the each one of the individuals learn. Get some of the insights. Helps my team in particular be, well, more well versed in the data that we have existing throughout the organization. Um, and then now Andrea, in touch upon how we scale it further and and how each one of the individuals can become better with this wonderful >>Yeah, soas used a zero mentioned theater hawk searches going up. It's sort of it's a little internal victory because our starting platform had really been thio build the pin boards to replicate what the users were already expecting. So that was sort of how we easily got people in. And then we just cut off the tap Thio, whatever the previous report waas. So it gave them away. Thio get into the tool and understand the information. So now that they're using ad hoc really means they understand the tool. Um, then they they have the data literacy Thio access the information and use it how they need. So that's it's a really cool piece. Um, that worked on for Canadian tire. A very report oriented and heavy organization. So it was a good starting platforms. So seeing those ad hoc searches go up is great. Um, one of the ways that we sort of scaled out of our initial group and I kind of mentioned this earlier I sort of stepped on my own toes here. Um is that once it was a proven success with the merchants and it started to spread through word of mouth and we sought out the analyst teams. Um, we really just kept sort of driving the insights, finding the data and learning more about the pieces of the business. As you would like to think he knows everything about everything. He only knows what he knows. Eso You have to continue to cultivate the internal champions. Um Thio really keep growing the adoption eso find this means that air excited about the possibility of using thought spot and what they can do with it. You need to find those people because they're the ones who are going to be excited to have this rapid access to the information and also to just be able to quickly spend less time telling a user had access it in thought spot. Then they would running the report because euro mentioned we basically hit a curiosity tax, right? You you didn't want to search for things or you didn't want to ask questions of the data because it was so conversed. Um, it was took too much time to get the data. And if you didn't know exactly what you were looking for, it was worse. So, you know, you wouldn't run a query and be like, Oh, that's interesting. Let me let me now run another query of all that information to get more data. Just not. It's not time effective or resource effective. Actually, at the point, eso scaling the adoption is really cultivating those people who are really into it as well. Um, from a personal development perspective, sort of as a user, I mean, one who doesn't like being smartest person in the room on bought spot sort of provides that possibility. Andi, it makes it easier for you to get recognized for delivering results on Dahlia ble insights and sort of driving the business forward. So you know, B b that all star be the Trailblazer with all the answers, and then you can just sort of find out what really like helping the organization realized the power of thought spot on, baby. Make it into a career. >>Amazing. I love love that you've joined us, Andrea. Such a such an amazing create trajectory. No bias that all of my s o heaps of great information there. Thank you both. So much for sharing your story on driving such amazing adoption and the impact that you've been able to make a T organization through. That we've got a couple of minutes remaining. So just enough time for questions. Eso Andrea. Our first questions for you from your experience. What is one thing you would recommend to new thoughts about users? >>Um, yeah, I would say Be curious and creative. Um, there's one phrase that we used a lot in training, which was just mess around in the tool. Um, it's sort of became a catchphrase. It is really true. Just just try and use it. You can't break. It s Oh, just just play around. Try it you're only limitation of what you're gonna find is your own creativity. Um, and the last thing I would say is don't get trapped by trying to replicate things. Is that exactly as they were? B, this is how we've always done it. Isin necessarily The the best move on day isn't necessarily gonna find new insights. Right. So the change forces you thio look at things from a different perspective on defined. Find new value in the data. >>Yeah, absolutely. Sage advice there. Andan another one here for Yaro. So I guess our theme for beyond this year is analytics meets Cloud Open for everyone. So, in your experience, what does What does that mean for you? >>Wonderful question. Yeah. Listen, Angela Okay, so to me, in short, uh, means scale and it means turning Yes. Sorry. No, into a yes. Uh, no, I'm gonna elaborate. Is interest is laughing at me a little bit. That's right. >>I can talk >>Fancy Two. Okay, So scale from the scale perspective Cloud a zai touched upon Throw our conversation on our presentation cloud enables your ability Thio store have more data, have access to more data without necessarily employing a number off PTL developers and going toe a number of security aspect of things in different data sources now turning a no into a yes. What does that mean with more data with more scalability? Um, the analytics possibilities become infinite throughout my career at Canadian Tire. Other organizations, if you don't necessarily have access thio data or you do not have the necessary granularity, you always tell individuals No, it's not possible. I'm not able to deliver that result. And quite often that becomes the norm, saying no becomes the norm. And I think what we're all striving towards here on this call Aziz part the conference is turning that no one say yes on then making a yes a new, uh, standard a new form. Um, as we have more access to the data, more access to the insights. So that would be my answer. >>Love it. Amazing. Well, that kind of brings in into this session. So thank you, everyone for joining us today on did wrap up this dream. Don't miss the upcoming product roadmap eso We'll be sticking around to speak thio some of the speakers you heard earlier today and I'll make the experts round table, and you can absolutely continue the conversation with this life. Q. On Q and A So you've got an opportunity here to ask questions that maybe keep you up at night. Perhaps, but yet stay tuned for the meat. The experts secrets to scaling analytics adoption after the product roadmap session. Thanks everyone. And thank you again for joining us. Guys. Appreciate it. >>Thank you. Thanks. Thanks.