![A Framework for Choosing Winning AI Use Cases [Agent Readiness Part 3] - The AI Daily Brief: Artificial Intelligence News and Analysis cover](/_next/image?url=https%3A%2F%2Fd3t3ozftmdmh3i.cloudfront.net%2Fstaging%2Fpodcast_uploaded_nologo%2F41472609%2F41472609-1752234663609-8665756a468e5.jpg&w=1920&q=75)
Transcript
A (0:00)
Welcome back to the AI Daily Brief. Today we have part three of our Agent Readiness series featuring Nuphar Gaspar and we are digging into use cases. The AI Daily Brief is a daily podcast and video about the most important news and discussions in AI. All right, quick announcements before we dive in. First of all, thank you to today's sponsors, Blitzy, kpmg, ROVO and Robots and Pencils. To get an ad free version of the show, go to patreon.com aidailybrief or you can subscribe on Apple Podcasts for information about sponsoring the show. We are rapidly running out of inventory for Q1 now, so if you are interested and want to hear more about what's available, send us a Note@ SponsorsIDailyBrief AI. Lastly, a reminder as always, about our AI ROI benchmarking study. Thanks to all of you who have contributed now hundreds of use cases. If you would be willing to take one or two minutes to do the same, it is at roisurvey AI in the first episode we talked about the cultural dimensions of agent readiness with nufar introducing her change framework. In Part two we talked about data and technical readiness where we have found at Superintelligent that data issues are by far the biggest blocker for agent adoption across all the different challenges that enterprises face. Today we are talking about what makes for a good use case and where to invest your resources and time. With this you're going to get a little bit of an inner working in the way that we do use case recommendations and it should provide once again a nice actionable framework for how you can think about which use cases might benefit your organization most. All right, nufar, welcome back. Part three of three. This is technically we're calling this use cases, but I think this is like the make it practical, like go do interesting things kind of section of the conversation. I'll let you kick it off and.
B (1:41)
Frame it for us, but right, yeah, that's a good take. Like you said, three out of three final part of the Agent Readiness series and we did save the best for last and that is the use case readiness. And we don't just refer to the are there enough use cases in production, but rather we are talking about whether there are enough opportunities in the company. And often these are not opportunities that the company is able to articulate, but rather ones that we're able to identify for them. It can be question on whether the business process in the company could be augmented or replaced by agents and whether they have the right mindset in order to do proper use Case discovery and execution. So that's what agent readiness from a use case perspective is. And in terms of the process and because we are all such big fans of frameworks, I wanted to cover this topic following the following steps. So we will start with identify and then select, manage and track our use cases. And I want to give you enough practical tools not only to identify the next agent use case, but also to manage it, almost like an investment portfolio, such that you can continuously improve your use case readiness. So let's start with the identify phase. And first I want to talk about the sources of ideas for agents. In many cases what I'm hearing is that like a CEO or a company leader will go into a room and they will say we need to build an agent, let's build an agent. And this is probably one of the worst way to source a use case idea because you'll probably build the wrong agent. Good source for you to build these agent use cases will be probably to get it from either bottoms up or mid level up because they often are the ones that know best what is feasible and also they are the one that needs to be bought in in order to execute. The question still remains, what are these good use cases? And what I wanted to do here is to provide you with some hints for what good use cases are and sometimes what good use cases aren't. And I want you to look first for use cases that involves a very complex and highly changing decision making. For example, to resolve a customer issue will require different action each time there is a new customer issue being raised on the flip side, and that's my very aggressive opinion, that in any situation where you can describe a fixed process or a decision tree with limited amount of branches, you shouldn't build an agent. You should just go for the simpler technology because the agent will probably not be worth it. The next thing that I want you to consider are places where humans are in the loop, but they are being the bottlenecks. This is often where you will find the gold mine of ROI for your use case because you need a professional judgment and you just don't have enough professionals. Think for example legal contracts review. Another place where you should look into are places where you need to have 24,7 human response. It can be for employee support, for customer and so on. And also I want you to think about cases where you want to achieve a high level of personalization. Think for example where you want to issue a highly personalized email, not just one where all the text is the same and you say hi nufar this is not the one I'm talking about cases where you will issue a personalized outreach at the right time, with the right offer and with the right text to get me hooked into your product. Next thing that I want you to consider is that I want you to only focus on use cases where you do have some tolerance for errors. For example, with one of the companies that I work with, payroll said we want an agent to replace some of the processes for calculating the employees salaries. And after I stopped catching my breath from how intimidated I was with this notion, I said, guys, you don't do an agent here. You don't even include AI in this process. You do a simple automation because with celery you have to get it 100% or 200% right. So agent will not be the right way to go about this process. And until now we didn't talk about kind of the elephant in the room. But because around agents there is so much discussion and sometimes fear around job loss, a good place to start will be to focus on the use cases that employees want to offload. Those will be the repetitive or the tedious type of works. You should focus there and then you will create a better momentum for more sensitive use cases. And also in cases where the only way to understand how a job is being done is to say, hey Sarah, can you explain how the job is being done? Because Sarah is the only one who knows this is not a good place for an agent. We need to have a process that is well defined and well documented for an agent to be able to interject. And lastly, we want to have a use case that is extremely measurable, not just to measure the roi, but because these agents are goal driven entities. And if you cannot measure whether you are closer or not to your goal, you cannot implement an agent. So if you use all of these hints, one thing that you can do at your company in order to initiate the creation of many, many such ideas is to have an ideation sprint. And this will help you harvest more agent ideas in the company and what you do there. Typically you will teach the employees using slides like that or others what agents are and aren't and what they can and cannot do. Then you harvest many, many, many ideas across the entire company. And then with this very large inventory, you do a very crude prioritization of your use case to keep it simple. And here I want you to be very aggressive and nip in the bud any use case that you can execute in a different manner, automation or otherwise. Right? So that's the first step with so many ideas, the next step will be to select and plan an agent roadmap. The selection should always be driven by the holy tree, the feasibility, the investment and the value. And this means that you will need to score each of our use cases accordingly. And if you've heard the previous episode where we talked about the intentional opportunism, you by now know that I'm very, very much into having low hanging fruits and focusing on them first. And these should be use cases with high feasibility and low investment or ones that are highly critical and start with them and then it will create the momentum of learning and doing in order to benefit future higher stakes use cases. So let's make it even more concrete and talk about the list of use cases that almost all companies should consider. And these are ones that we often find ourselves uncover or recommend companies when we audit them for agent readiness. And I think none of them will surprise you, but the first one will be the FAQ or the policy bots. These are either internal or external and I'm not talking like old fashioned bots that only know to answer from a predefined set of questions, but rather agents that are able to answer complex questions with many nuances in the information sources. The other thing that everyone needs and are asking for will be the company knowledge retrieval. I think this comes across all interviews. Everyone needs good access to their data and even though many companies are already utilizing the Microsoft and the Glean and other solutions, often these are not enough and they need to create either an additional layer or looking for additional ways to get access to their very specific data that is fragmented across systems and so on. The next one will be operational workflow automation. So those will be drag work at the team level like automated status reporting and many other things that people spend unnecessary brain power and time to do and agents can take from their plate. And lastly, I'm calling them like market watchers. These are everything related to keeping a close eye on your competition, on your regulation, or everything that you need to know in order to do your business well and you never have enough time. So these are the top most prevalent use cases, but we do find ourselves recommending many other use cases as part of the readiness audits. And I don't believe that anything on this list will surprise you. And of course it starts with the top two most common use cases and those will be vertical use cases around customer support and software engineering. They come across very often, but we also see in many cases content generation for marketing or other purposes, as well as many sales Related use cases, they come across very, very often in the audits and with many companies that we've been working with. And this is also something that I mentioned in previous session. Agents can often help with things related to contract and regulations and other things and with the process of cleaning your data, which is where there isn't a lot of unlock with the data access issues and many things that we mentioned before. And lastly there are many industry or even company specific, often ones that will create opportunities for growth in the company that come across as highly relevant in some of these audits. So this is a very rich selection of use cases. And what I want to encourage everyone to do is basically to manage the inventory and the choices of which agents and which use cases you want to pursue like you would manage an investment portfolio. As I said at the beginning, and I want first to have you balance between two main elements and those will be the efficiency or the cost focused use cases and also those that are more focused on the growth. And when I talk efficiency use cases, I'm talking about all the do the work with the fuel resources type of use cases. While growth use cases in my book are everything that basically has an impact on the top line. And I want you to balance the two. Often we're seeing companies highly biased towards the first one of efficiency and not thinking enough about the growth opportunities. And often the biggest value is on the right hand side of the growth. So make sure that you pay closer attention to those as well. And then to continue on balancing your agent portfolio, I want you to look at this proposal and here I'm paraphrasing on the 1970s Boston Consulting Group growth share matrix. It's a kind of a classical and I want you to look at the identified use cases in the lens of the complexity versus the value. And of course where there is high complexity and low value and often we see such use cases just don't go there at all. There are of course the low hanging fruits or low hangers. These are an awesome place to start. And over time though those should become the thing that people self serve. So these should be catered by agent building platforms or other capabilities rather than having a company focus on and eventually you should aim to have a handful of what I refer to as moonshots. These are kind of the high risk, high reward use cases. Often by the way, they correspond to either a radical shift in how you do the work or they are a gross use case. So that's often where the moonshot is and they should be led and executed by a professional and centralized AI team rather than just the best effort in the business units. And they require a significant investment and a specialized knowledge. So these are not for the faint of heart. And lastly, most of your area of focus should be in this like high or highish value and decent complexity because this is where there is enough value. But still you will be able to get agents out the door. And by the way, for companies that are getting low readiness scores from us in the audit, we will never offer ideas for stuff that are more on the moonshot. We will always focus them either on the low hangers or the focus areas and over time we'll encourage them to go after bolder bigger things. So there are a few other dimensions that you should probably consider. One is to balance between vertical versus Horizontal agents. Don't just do one or the other and also build versus buy. So keep that in mind as you balance your portfolio and make sure that you have diverse and well balanced portfolio of all the complexity combinations as well as vertical, horizontal and build versus okay, so this portfolio has to be centrally managed and periodically updated in order to support the constant learning and the growth.