>>Hello, everyone, and welcome to track three off beyond. My name is being in Yemen and I am an account executive here at Thought spot based out of our London office. If the accents throwing you off I don't quite sound is British is you're expecting it because the backgrounds Australian so you can look forward to seeing my face. As we go through these next few sessions, I'm gonna be introducing the guests as well as facilitating some of the Q and A. So make sure you come and say hi in the chat with any comments, questions, thoughts that you have eso with that I mean, this whole track, as the title somewhat gives away, is really about everything that you need to know and all the tips and tricks when it comes to adoption and making sure that your thoughts what deployment is really, really successful. We're gonna be taking off everything from user training on boarding new use cases and picking the right use cases, as well as hearing from our customers who have been really successful in during this before. So with that, though, I'm really excited to introduce our first guest, Kathleen Maley. She is a senior analytics executive with over 15 years of experience in the space. And she's going to be talking to us about all her tips and tricks when it comes to making the most out of your center of excellence from obviously an analytics perspective. So with that, I'm going to pass the mic to her. But look forward to continuing the chat with you all in the chat. Come say hi. >>Thank you so much, Bina. And it is really exciting to be here today, thanks to everyone for joining. Um, I'll jump right into it. The topic of evolving your analytics center of excellence is a particular passion of mine on I'm looking forward to sharing some of my best practices with you. I started my career, is a member of an analytic sioe at Bank of America was actually ah, model developer. Um, in my most recent role at a regional bank in the Midwest, I ran an entire analytics center of excellence. Um, but I've also been on the business side running my own P and l. So I think through this combination of experiences, I really developed a unique perspective on how to most effectively establish and work with an analytic CEO. Um, this thing opportunity is really a two sided opportunity creating value from analytics. Uh, and it really requires the analytics group and the line of business Thio come together. Each has a very specific role to play in making that happen. So that's a lot of what I'll talk about today. Um, I started out just like most analysts do formally trained in statistics eso whether your data analyst or a business leader who taps into analytical talent. I want you to leave this talk today, knowing the modern definition of analytics, the purpose of a modern sioe, some best practices for a modern sioe and and then the role that each of you plays in bringing this Kuito life. So with that said, let me start by level, setting on the definition of analytics that aligns with where the discipline is headed. Um, versus where it's been historically, analytics is the discovery, interpretation and communication of meaningful patterns in data, the connective tissue between data and effective decision making within an organization. And this is a definition that I've been working under for the last, you know, 7 to 10 years of my career notice there is nothing in there about getting the data. We're at this amazing intersection of statistics and technology that effectively eliminates getting the data as a competitive advantage on this is just It's true for analysts who are thinking in terms of career progression as it is for business leaders who have to deliver results for clients and shareholders. So the definition is action oriented. It's purposeful. It's not about getting the data. It's about influencing and enabling effective decision making. Now, if you're an analyst, this can be scary because it's likely what you spend a huge amount of your time doing, so much so that it probably feels like getting the data is your job. If that's the case, then the emergence of these new automated tools might feel like your job is at risk of becoming obsolete. If you're a business leader, this should be scary because it means that other companies air shooting out in front of you not because they have better ideas, necessarily, but because they can move so much faster. According to new research from Harvard Business Review, nearly 90% of businesses say the more successful when they equipped those at the front lines with the ability to make decisions in the moment and organizations who are leading their industries and embracing these decision makers are delivering substantial business value nearly 50% reporting increased customer satisfaction, employee engagement, improve product and service quality. So, you know, there there is no doubt that speed matters on it matters more and more. Um, but if you're feeling a little bit nervous, I want you to think of it. I want you think of it a little differently. Um, you think about the movie Hidden figures. The job of the women in hidden figures was to calculate orbital trajectories, uh, to get men into space and then get them home again. And at the start of the movie, they did all the required mathematical calculations by hand. At the end of the movie, when technology eliminated the need to do those calculations by hand, the hidden figures faced essentially the same decision many of you are facing now. Do I become obsolete, or do I develop a new set of, in their case, computer science skills required to keep doing the job of getting them into space and getting them home again. The hidden figures embraced the latter. They stayed relevant on They increase their value because they were able to doom or of what really mattered. So what we're talking about here is how do we embrace the new technology that UN burdens us? And how do we up skill and change our ways of working to create a step function increase in data enabled value and the first step, really In evolving your analytics? Dewey is redefining the role of analytics from getting the data to influencing and enabling effective decision making. So if this is the role of the modern analyst, a strategic thought partner who harnesses the power of data and directs it toward achieving specific business outcomes, then let's talk about how the series in which they operate needs change to support this new purpose. Um, first, historical CEOs have primarily been about fulfilling data requests. In this scenario, C always were often formed primarily as an efficiency measure. This efficiency might have come in the form of consistency funds, ability of resource is breaking down silos, creating and building multipurpose data assets. Um, and under the getting the data scenario that's actually made a lot of sense for modern Sealy's, however, the objective is to create an organization that supports strategic business decision ing for individuals and for the enterprises the whole. So let's talk about how we do that while maintaining the progress made by historical seaweeds. It's about really extending its extending what, what we've already done the progress we've already made. So here I'll cover six primary best practices. None is a silver bullet. Each needs to fit within your own company culture. But these air major areas to consider as you evolve your analytics capabilities first and foremost always agree on the purpose and approach of your Coe. Successfully evolving yourself starts with developing strategic partnerships with the business leaders that your organization will support that the analytics see we will support. Both parties need to explicitly blocked by in to the objective and agree on a set of operating principles on bond. I think the only way to do that is just bringing people to the table, having an open and honest conversation about where you are today, where you wanna be and then agree on how you will move forward together. It's not about your organization or my organization. How do we help the business solve problems that, you know, go beyond what what we've been able to do today? So moving on While there's no single organizational model that works for everyone, I generally favor a hybrid model that includes some level of fully dedicated support. This is where I distinguish between to whom the analyst reports and for whom the analyst works. It's another concept that is important to embrace in spirit because all of the work the analyst does actually comes from the business partner. Not from at least it shouldn't come from the head of the analytic Center of excellence. Andan analysts who are fully dedicated to a line of business, have the time in the practice to develop stronger partnerships to develop domain knowledge and history on those air key ingredients to effectively solving business problems. You, you know, how can you solve a problem when you don't really understand what it is? So is the head of an analytic sioe. I'm responsible for making sure that I hire the right mix of skills that I can effectively manage the quality of my team's work product. I've got a specialized skill set that allows me to do that, Um, that there's career path that matters to analysts on all of the other things that go along with Tele management. But when it comes to doing the work, three analysts who report to me actually work for the business and creating some consistency and stability there will make them much more productive. Um, okay, so getting a bit more, more tactical, um, engagement model answers the question. Who do I go to When? And this is often a question that business partners ask of a centralized analytics function or even the hybrid model. Who do I go to win? Um, my recommendation. Make it easy for them. Create a single primary point of contact whose job is to build relationships with a specific partner set of partners to become deeply embedded in their business and strategies. So they know why the businesses solving the problems they need to solve manage the portfolio of analytical work that's being done on behalf of the partner, Onda Geun. Make it make it easy for the partner to access the entire analytics ecosystem. Think about the growing complexity of of the current analytics ecosystem. We've got automated insights Business Analytics, Predictive modeling machine learning. Um, you Sometimes the AI is emerging. Um, you also then have the functional business questions to contend with. Eso This was a big one for me and my experience in retail banking. Uh, you know, if if I'm if I'm a deposits pricing executive, which was the line of business role that I ran on, I had a question about acquisitions through the digital channel. Do I talk Thio the checking analyst, Or do I talk to the digital analyst? Um, who owns that question? Who do I go to? Eso having dedicated POC s on the flip side also helps the head of the center of excellence actually manage. The team holistically reduces the number of entry points in the complexity coming in so that there is some efficiency. So it really is a It's a win win. It helps on both sides. Significantly. Um, there are several specific operating rhythms. I recommend each acting as a as a different gear in an integrated system, and this is important. It's an integrated decision system. All of these for operating rhythms, serves a specific purpose and work together. So I recommend a business strategy session. First, UM, a portfolio management routine, an internal portfolio review and periodic leadership updates, and I'll say a little bit more about each of those. So the business strategy session is used to set top level priorities on an annual or semiannual basis. I've typically done this by running half day sessions that would include a business led deep dive on their strategy and current priorities. Again, always remembering that if I'm going to try and solve all the business problem, I need to know what the business is trying to achieve. Sometimes new requester added through this process often time, uh, previous requests or de prioritized or dropped from the list entirely. Um, one thing I wanna point out, however, is that it's the partner who decides priorities. The analyst or I can guide and make recommendations, but at the end of the day, it's up to the business leader to decide what his or her short term and long term needs and priorities are. The portfolio management routine Eyes is run by the POC, generally on a biweekly or possibly monthly basis. This is where new requests or prioritize, So it's great if we come together. It's critical if we come together once or twice a year to really think about the big rocks. But then we all go back to work, and every day a new requests are coming up. That pipeline has to be managed in an intelligent way. So this is where the key people, both the analyst and the business partners come together. Thio sort of manage what's coming in, decking it against top priorities, our priorities changing. Um, it's important, uh, Thio recognize that this routine is not a report out. This routine is really for the POC who uses it to clarify questions. Raised risks facilitate decisions, um, from his partners with his or her partner so that the work continues. So, um, it should be exactly as long as it needs to be on. Do you know it's as soon as the POC has the information he or she needs to get back to work? That's what happens. An internal portfolio review Eyes is a little bit different. This this review is internal to the analytics team and has two main functions. First, it's where the analytics team can continue to break down silos for themselves and for their partners by talking to each other about the questions they're getting in the work that they're doing. But it's also the form in which I start to challenge my team to develop a new approach of asking why the request was made. So we're evolving. We're evolving from getting the data thio enabling effective business decision ing. Um, and that's new. That's new for a lot of analysts. So, um, the internal portfolio review is a safe space toe asks toe. Ask the people who work for May who report to May why the partner made this request. What is the partner trying to solve? Okay, senior leadership updates the last of these four routines, um, less important for the day to day, but significantly important for maintaining the overall health of the SIOE. I've usually done this through some combination of email summaries, but also standing agenda items on a leadership routine. Um, for for me, it is always a shared update that my partner and I present together. We both have our names on it. I typically talk about what we learned in the data. Briefly, my partner will talk about what she is going to do with it, and very, very importantly, what it is worth. Okay, a couple more here. Prioritization happens at several levels on Dive. Alluded to this. It happens within a business unit in the Internal Portfolio review. It has to happen at times across business units. It also can and should happen enterprise wide on some frequency. So within business units, that is the easiest. Happens most frequently across business units usually comes up as a need when one leader business leader has a significant opportunity but no available baseline analytical support. For whatever reason. In that case, we might jointly approach another business leader, Havenaar Oi, based discussion about maybe borrowing a resource for some period of time. Again, It's not my decision. I don't in isolation say, Oh, good project is worth more than project. Be so owner of Project Be sorry you lose. I'm taking those. Resource is that's It's not good practice. It's not a good way of building partnerships. Um, you know that that collaboration, what is really best for the business? What is best for the enterprise, um, is an enterprise decision. It's not a me decision. Lastly, enterprise level part ization is the probably the least frequent is aided significantly by the semi annual business strategy sessions. Uh, this is the time to look enterprise wide. It all of the business opportunities that play potential R a y of each and jointly decide where to align. Resource is on a more, uh, permanent basis, if you will, to make sure that the most important, um, initiatives are properly staffed with analytical support. Oxygen funding briefly, Um, I favor a hybrid model, which I don't hear talked about in a lot of other places. So first, I think it's really critical to provide each business unit with some baseline level of analytical support that is centrally funded as part of a shared service center of excellence. And if a business leader needs additional support that can't otherwise be provided, that leader can absolutely choose to fund an incremental resource from her own budget that is fully dedicated to the initiative that is important to her business. Um, there are times when that privatization happens at an enterprise level, and the collective decision is we are not going to staff this potentially worthwhile initiative. Um, even though we know it's worthwhile and a business leader might say, You know what? I get it. I want to do it anyway. And I'm gonna find budget to make that happen, and we create that position, uh, still reporting to the center of excellence for all of the other reasons. The right higher managing the work product. But that resource is, as all resource is, works for the business leader. Um, so, uh, it is very common thinking about again. What's the value of having these resource is reports centrally but work for the business leader. It's very common Thio here. I can't get from a business leader. I can't get what I need from the analytics team. They're too busy. My work falls by the wayside. So I have to hire my own people on. My first response is have we tried putting some of these routines into place on my second is you might be right. So fund a resource that's 100% dedicated to you. But let me use my expertise to help you find the right person and manage that person successfully. Um, so at this point, I I hope you see or starting to see how these routines really work together and how these principles work together to create a higher level of operational partnership. We collectively know the purpose of a centralized Chloe. Everyone knows his or her role in doing the work, managing the work, prioritizing the use of this very valuable analytical talent. And we know where higher ordered trade offs need to be made across the enterprise, and we make sure that those decisions have and those decision makers have the information and connectivity to the work and to each other to make those trade offs. All right, now that we've established the purpose of the modern analyst and the functional framework in which they operate, I want to talk a little bit about the hard part of getting from where many individual analysts and business leaders are today, uh, to where we have the opportunity to grow in order to maintain pain and or regain that competitive advantage. There's no judgment here. It's simply an artifact. How we operate today is simply an artifact of our historical training, the technology constraints we've been under and the overall newness of Applied analytics as a distinct discipline. But now is the time to start breaking away from some of that and and really upping our game. It is hard not because any of these new skills is particularly difficult in and of themselves. But because any time you do something, um, for the first time, it's uncomfortable, and you're probably not gonna be great at it the first time or the second time you try. Keep practicing on again. This is for the analyst and for the business leader to think differently. Um, it gets easier, you know. So as a business leader when you're tempted to say, Hey, so and so I just need this data real quick and you shoot off that email pause. You know it's going to help them, and I'll get the answer quicker if I give him a little context and we have a 10 minute conversation. So if you start practicing these things, I promise you will not look back. It makes a huge difference. Um, for the analyst, become a consultant. This is the new set of skills. Uh, it isn't as simple as using layman's terms. You have to have a different conversation. You have to be willing to meet your business partner as an equal at the table. So when they say, Hey, so and so can you get me this data You're not allowed to say yes. You're definitely not is not to say no. Your reply has to be helped me understand what you're trying to achieve, so I can better meet your needs. Andi, if you don't know what the business is trying to achieve, you will never be able to help them get there. This is a must have developed project management skills. All of a sudden, you're a POC. You're in charge of keeping track of everything that's coming in. You're in charge of understanding why it's happening. You're responsible for making sure that your partner is connected across the rest of the analytics. Um, team and ecosystem that takes some project management skills. Um, be business focused, not data focused. Nobody cares what your algorithm is. I hate to break it to you. We love that stuff on. We love talking about Oh, my gosh. Look, I did this analysis, and I didn't think this is the way I was gonna approach it, and I did. I found this thing. Isn't it amazing? Those are the things you talk about internally with your team because when you're doing that, what you're doing is justifying and sort of proving the the rightness of your answer. It's not valuable to your business partner. They're not going to know what you're talking about anyway. Your job is to tell them what you found. Drawing conclusions. Historically, Analyst spent so much of their time just getting data into a power 0.50 pages of summarized data. Now the job is to study that summarized data and draw a conclusion. Summarized data doesn't explain what's happening. They're just clues to what's happening. And it's your job as the analyst to puzzle out that mystery. If a partner asked you a question stated in words, your answer should be stated in words, not summarized data. That is a new skill for some again takes practice, but it changes your ability to create value. So think about that. Your job is to put the answer on page with supporting evidence. Everything else falls in the cutting room floor, everything. Everything. Everything has to be tied to our oi. Um, you're a cost center and you know, once you become integrated with your business partner, once you're working on business initiatives, all of a sudden, this actually becomes very easy to do because you will know, uh, the business case that was put forth for that business initiative. You're part of that business case. So it becomes actually again with these routines in place with this new way of working with this new way of thinking, it's actually pretty easy to justify and to demonstrate the value that analytic springs to an organization. Andi, I think that's important. Whether or not the organization is is asking for it through formalized reporting routine Now for the business partner, understand that this is a transformation and be prepared to support it. It's ultimately about providing a higher level of support to you, but the analysts can't do it unless you agree to this new way of working. So include your partner as a member of your team. Talk to them about the problems you're trying to sell to solve. Go beyond asking for the data. Be willing and able to tie every request to an overarching business initiative on be poised for action before solution is commissioned. This is about preserving. The precious resource is you have at your disposal and you know often an extra exploratory and let it rip. Often, an exploratory analysis is required to determine the value of a solution, but the solution itself should only be built if there's a plan, staffing and funding in place to implement it. So in closing, transformation is hard. It requires learning new things. It also requires overriding deeply embedded muscle memory. The more you can approach these changes is a team knowing you won't always get it right and that you'll have to hold each other accountable for growth, the better off you'll be and the faster you will make progress together. Thanks. >>Thank you so much, Kathleen, for that great content and thank you all for joining us. Let's take a quick stretch on. Get ready for the next session. Starting in a few minutes, you'll be hearing from thought spots. David Coby, director of Business Value Consulting, and Blake Daniel, customer success manager. As they discuss putting use cases toe work for your business