Week-11 | AI Agent Project Elimination Strategy | Enterprise AI Architect | Realtime Best Practices

Hello friends, how are you doing today? We have seen so many videos about the A architectures and enterprise A architectures and also I provided tips and tricks for tracking your A architect interviews etc. You can go and explore that in our uh architect IT cloud channel and you can uh enjoy watching this video and put your comments in the comments box. Right? So that way we can easily interact well and if you want to ask a particular question to me and I can help uh arranging the calls with you and you can talk about it more right so in this video I just wanted to bring one more important topic that you must need to understand as enterprise a what exactly it is. So you have been doing lot of a agent projects and you would be delivering some types of critical business um objectives for your organization by using the A agent architectures and also you might be building gen architectures etc. Right? So one critical part of this particular process is how to pick the business uh objective or business use case for executing the AI agent project. That is very critical and if you are dealing with the business architects in your organization you definitely know the importance of picking the right project for the agent architecture or a agent implementation. You cannot just go and adopt a agent um architectures for all the existing projects or just like that if you have small use case adopting a agent architecture is costly. Why? Because you have to use LLM in the behind and uh every call that you make to LLM is cost right. So token cost is very important. So you have to keep that in mind before picking a business use case for adopting a agent. So how to pick a project and adopt with a agent architecture that is the main thing that we are going to see in this video. So normally when it comes to picking a project you may go in the right direction of listing out all 100 projects in your organization and classifying it whether it needs a agent architecture whether it needs gen architecture etc. That is one of the approaches that you may need follow or some other uh folks in your organization may follow. My strategy here is do not just categorize all the projects and look for the areas to adopt a agent or generic implementation rather first start with an elimination. So how you can do that? Normally if you are writing a competitive exam or certification exam what you would do once after reading the question you go through all the options like four choices given for that particular question to pick and you remove the wrong answers first. Right? That is the elimination process. You look for the first option and check whether this is relevant for this question and you will come to a uh conclusion that it is not relevant and you remove it and go for the second and you may think that it is right you keep it as uh the right answer and third one you go and analyze and if it is wrong you remove it and fourth one you go to the uh answer and you analyze it and remove it if it is not required and finally the second one of the right option for that particular question. So this is the elimination process that you follow when you write an exam, competitive exam or certification exam, right? So follow the similar approach for picking a project in your organization to adopt with a agent or ja architecture. So what you must need to do first list out all the 100 projects or 100 uh use cases that you got from the business team and remove the use case or the project which are not required to be implemented with the AA. For example, you may have a project or use case that can work as is without touching anything. One of the project is like internal application that may uh get the user inputs in this case like your employee input as a feedback mechanism and just lists out all the answers provided by the employer and then logs into the system. You don't need to have a for this particular use case. Just remove this particular use case or project from your list and go for the second uh project or second use case. Similarly, we keep eliminating the projects or use cases which are not required to be implemented with the AI agent or gena architecture. And finally, you may have three or four projects that may really need to implement with the AA

agent or gen architecture. So, pick those four or five projects and then start um creating the A agent architecture for those projects. Okay? So this way you can critically land on a area where those projects really need a agent implementation. That way you can save cost for your organization. As an enterprise architect, you must keep in mind that when you get into a real-time project, you will be dumped with lot of tasks to uh sort it out and work with your business team and you will be asked to work with the CTOs and leadership and finally you have to prove yourself that which one will be the best for your organization. So keep this elimination strategy in mind. This is not a revolution or anything. You must need to just adopt this elimination strategy when you start working for your uh organization as an enterprise architect. So what are all the key benefits of this elimination process? First, it'll help you to understand the existing projects and leave the existing project as is uh because it doesn't require a agent implementation over there. And second thing, some projects may have the automation existing. For example, one of the projects that might be using robotic process automation already it has the implementation in place for the automation. You don't need the intelligent automation there. It will work as is. Some of the projects will be like this. So leave those project as is because those projects already has that implementation of uh automation there. You don't need to further waste your time and energy and money on further automating with the AE. And third category is the one that will bring you to think in the A angle perspective. For example, your uh organizations may have some projects which are helping your end customer answering the right query and solving the customer satisfaction problems and solving the written and refund problems. So these activities would be done by the customer satisfaction representative. But um if you don't adopt AA there will be a problem here because your customer satisfaction representative or customer support representative might be spending too much time on resolving a particular query by referring lot of documentation and talking to different systems and inventory etc. So here you really need AI architecture or a agent architecture or gener architecture and look at this particular area and pick these projects and implement the A agent architecture here. And this way your uh customer support representatives can focus more on providing the support to your customers rather than spending time on researching the data, pulling the data from different systems, summarizing it, all those steps. So pick these type of projects for your organization and bring in the AI agent architecture and provide the solution for your organization. So this is the best way to do the a agent implementation for your organization that will bring the high return on investment and reduced the TCO. Um so this is called elimination strategy. I have followed this elimination strategy with multiple customers so that I was able to pick the right project for those customers and adopt with the agent architecture. Um so when it comes to adopting a agent architecture do not think always a agent architecture is the best some cases your gen architecture would be enough for addressing a business problem. So do not bring in the tool calling API calling uh unless otherwise is really required for your organization. In that case if it is not required just stick with the gen architecture for example summarization of the lengthiest documentation and Q& A all those steps you can achieve with the gen architecture. Okay. And if it is really required for the intelligent task automation then think about a agent architecture. Do not just go with a aent architecture for all the project that you identified as the project that needs a implementation. So I hope this video is helpful for thinking in the right direction while choosing a project for your organization and implement with ja or a agent architecture. If you like

this video, give a thumbs up and share it to your friends so that they will also get benefit out of it. Take care. But