Ep.2 Architecting Lead to Opportunity Transformation - Introducing Archimate

Thanks everyone for joining in. So welcome, welcome, welcome. So welcome everyone, thanks for joining in. So if you are joining from any part of the world, thank you, thank you for joining in. Welcome back, welcome back. So welcome to our second episode of our architectural track. So talking about, uh, the Revenue Tuesday. So we have a dedicated session for every week. So every Tuesday we talk about the customer experience segment, and that we call it as a Revenue Tuesday. Okay, so in this entire primetime series, we have Sunday is dedicated for Source Sunday, Identity Leaders of Transformation Monday, we have Workforce Transformation Tuesday, we have Revenue Transformation Finance For Wednesday, procurement Thursday, supply chain Friday, so business transformation Saturday. So you're full pack of almost every aspect of what a core business does, and also the entire, you know, end-to-end learning will be having. So with that note, so welcome to the second episode of our learning journey in this customer experience and revenue transformation. And also we call it the core business journey that lead to opportunity and to work, and entire CRM sales marketing This is, we are the ideal audience for it, and we're not specifically technology product. We talk about technology agnostic, the best part of it. So we can transfer that knowledge into any other product or, you know, industries like that. Okay. So we will start with that. In case you have not watched the previous session, those are already in our YouTube channel and also in our platform. Okay. And those are already available. You can subscribe and you can Okay, go through those. Okay, so with that note, let's start with the Revenue Tuesday. This is our segment, and so it's all about sales transformation, CRM consulting, and customer success roles, people who are actually into those kind of a career. Okay, but today we'll be going to a particular aspect of it as we see that architecting, right? So without our particular framework or particular technology, particular, you know, we cannot have this kind of, uh, content, right? So for that, we have to have a proper segment. So we will be discussing that today. And today in second episode, we will be focusing on a particular tool called Archimate. How many of you have heard about something called Archimate? Especially people who are coming from technology background, or if you have already TOGAF certified, similar to that, right? You might have heard about it, but people already coming in SAP LeanIX or similar kind of a product, right? You will be having something you might have heard about it. Okay, so Archibed. People who are already TOGAF certified, no need to say, you already might be knowing something about it. Okay, and also there are people I know who are already Archibed certified also. They also have Archibed certified. Okay, so how does it actually— Archibed will be applicable for a customer experience journey point of that we will talk about today. Okay, this entire framework we will try to understand today. And from a, from an aspect of a business point of view, from an applications point of view. And for that, you need to go to, there's a, it's open source tool. You can simply go to ArchimateTool.com. Okay. And from there, you can download the tool. The tool is pretty much free, open source tool. Okay. Go there and you can go select Archi, you can download it. And there are also pretty much resources like user guide and all everything we are having. So we will focus on this part of it. This is an example of an insurance industry, but something we will try to draw this kind of a detail— strategy, business, application, technology, motivation, all of these things. And also we'll try to understand how it is connected to your typical TOGAF standard, and that we will talk about today. Okay, so with that note, let's then get started. And as we discussed that it is the— for Unified, for the whatever today's topic is Okay, so today's topic is we'll do the Archimedes modeling for a unified revenue operations across marketing, sales, and customer success. Okay, so this is today's topic. Today we don't have any presentation as such, so we will be going through the hands-on activities like this only, and we'll try to understand as much as possible through the example, a real case study. Okay, so why actually this is— there is a crisis, like we also try to understand the marketing, sales, why those are actually— even if everything is hyperconnected, right, so why there is issues in the handoffs, okay? So what are the possible reasons, right? And we'll try to understand those things. And today's session is very much fundamental session. We'll try to understand there are different layers, okay, of it. So we have a business layer, we have application layer. So all those things we'll try to understand so that we can model it a better way. Okay, so in that context, we'll try to understand the entire unified flow. If you're using SAP or similar kind of ERP, we will also try to understand. Okay, so we are focusing today on a consumer staples industry. Okay, so there are so many industry as per the 11 GICS sectors we, we have identified, means as per the standard. Okay, so we will following one particular industry or sector, basically consumer staples sector. Okay, and how it is applicable, okay, for, uh, how we can utilize it for using Archimedes. How you can model that entire company, especially using the Archimedes. There are so many other tools available, but thing is, this is one of the most reliable tool I have seen, open source tool, I will say, okay. We will be see what are the things area, okay. So now with that note, we will, uh, go through this and we will try to see those things in detail. Okay, consumer staples sector. So people who do not know, so we have— we are following a standard here also called GICS industry classifications. We are following, and out of that, today we'll be focusing on one of the sector. I mean, I will be giving you homework. It could be a boot camp for you. Okay, so ultimate boot camp. And today we're focusing on consumer staples, a particular sector out of 11 sectors what we have. Otherwise, we have 25 industry groups, 74 industries, 163 sub-industries we are having it. But out of that, we'll be focusing on today only one, that is the Kanjima Staples. And based on that, we will try to capture it, we'll try to understand it in a detailed way. Okay, so today we'll be talking about the, as I said, Kanjima Staples. So first of all, before we go there, there are certain terminologies also we need to understand in the Archimate. Okay, so in Archimate, what happens? The entire language, okay, of the Archimate comprises two main elements. They call it layers and aspects. So what are the things layers? So the strategy, business, application, technology— these are all physical implementation, migration— these are all typical layers we call it. These are like all the horizontal lines, whatever you are seeing, these are the layers. And aspect means active structure, passive structure, behavior, and motivation. These are the 4 aspects you will be having here. Okay, so we'll try to understand in a more detailed way. So let's say from our context, okay? So we'll try to understand layers and, uh, aspects in detail, okay? So let's say I will go through this, and this entire thing I will take to my notes, and we'll try to understand this first. Then we will go to the system, okay? And from that we will try to understand how exactly it can be done, okay? So now with that, okay, we would go to our Notion And we will try to understand. So this is what exactly definition of it. So we'll try to capture here the notes. Huh. So we'll try to understand first the aspects. Okay, so aspects is little tricky to understand, but the thing is not so difficult. So we have active structure and passive structure. Okay, so what exactly they mean? Aspect means they represent different perspective or a view, how, from what angle you are looking at. Okay, view of the enterprise architecture. They provide specialized viewpoint from which angle you are looking at. Okay, and what is the focus on that? And ArchiMate defines this as primary aspects. Okay, what are those? So you'll be finding those as active structure, behavior, passive structure, and motivation. Okay, so we'll try to understand again further the active aspect. Okay, we'll focus on the subjects that can perform behavior representing the organization structure, components, and properties. So just to say, listen to carefully and also try to understand. It's a little complex whenever you try to, you know, understand in that way. Okay, it includes concepts such as the actors, business roles. Okay, these are the key thing which is actually they are actively involved, right? Actors, business roles, the users. Application components and infrastructure elements. These are your typical— we call it active structure because these are actively involved. Okay, that is why they actually called as a— they perform the behavior and they're part of the original structure component, the properties like that. Okay, but when it comes to behavior, behavioral aspect captures the dynamic aspects of the architecture. That means your behavior interactions of the architectural elements over time. It includes concepts such as Processes, functions, services, and interfaces. Just remember what are the concepts, okay, which comes under behavior, okay? So we try to understand that under behavior we have 4 things: processes, functions, services, and interfaces, okay? So now we'll also understand the passive structure. So we'll try to understand from this context. Let's say, uh, we'll try to do this in a table here, okay? Active structure, behavior, passive structure, and motivation, right? So here, out of this, uh, active structure, behavior, and passive structure, they are core framework. And motivation is the fourth one, which is actually part of full framework. Okay, passive structure, as I suggested, so it is actually representative of data within architecture. There are elements on, elements on which behavior is performed. Okay, so behavior means your processes, functions, services, interfaces. Those are actually on top of it which is performed. So what are the examples in the passive structure? The examples are data objects, business object, and artifact. Any kind of data objects you're working on, any kind of business object you're working upon, right? Or any kind of artifact you're working upon, right? Those are the different examples of a passive structure, okay? So this is an example of it, or a understanding of passive. So we will have the example. We can give an example, you'll understand much better, right? Then motivation. So motivation is actually nothing but it's, uh, focus on the modeling the drivers, goals, principles, requirements, and stakeholders that influence the shape of the architecture. That is a motivation, we call it. Okay, so now let's try to draw a table, okay, which is actually understanding this. So we'll try to understand based, uh, create a Notion table, create a Notion table, uh, explaining each elements of aspects, aspects, aspects, uh, then like your all the each element and sub-elements, I will say, and sub-elements of aspects with examples from consumer. Uh, we're talking about the— here, the example which we'll be taking today is the typically consumer staples, okay? So consumer staples sector focusing on CX, customer experience. Okay, so this is the codex or the AI prompt which will be doing it. Let's see what is bringing in. You can also try it outside. So I will go to my other AI tool, AI PS Star, and here I will also try the same thing. Let's see what exactly it is bringing in today. So I will be using this, and I will go there. Meanwhile, it will be updating here. You will see that this concept is very, very important because that is the fundamental of your typical— any of the architecture point of view to understand, especially the Archimedes if you're following, okay? And these are called your aspects or views or perspective, we call it, okay? In whatever the views here, what are the perspectives you're looking at? Active structure, passive structure. Behavior, motivation. So ABPM— active structure, behavior, passive structure, motivation, right? So we try to now understand. So now it will much easy once we give this example, okay? So we'll see this example, okay? And we will try to understand much better way, okay, to see that. So let's expand this particular table and we will try to understand who— what is your element, sub-element and what it is, and what is the consumer staples example in that case, and what is the relationship among those. Okay, so we'll try to understand, so then we will go further. So here what we see, active structure, so active structure, passive structure, motivation, and we have seen the behavior, right? So business actor, so who does the thing, okay? So that's actor, your consumer, retailer, customer service team, there's a branding team, right? Those are the different, different business actors, okay? So that is the example of an active structure, okay? And actor is assigned to a role, okay? So definitely, so whenever any organization, you'll be having different, different role. And actor is assigned to role, role is assigned to process. So this is the way you'll be understanding. So in active structure we have 3 things as we discussed: business role, application component, and device. So business role is all about responsibility and a person, or a person or an organization is playing, right? So this is what it could be, your CS agent, customer support agent, store associate, loyalty program manager. There could be any more, anything else similar to that. Okay, there's some of the few examples. So business roles is all about who is actually, as this is a typical standard English term, so you have like customer support agent. That means they are actually playing, supporting the customer, right? Whatever is required. And those roles are assigned to process. In the typical diagram you might have seen, okay, those process diagrams and all. Okay, now third one is application component. That is software building block. Okay, so it could be your customer contact, CRM, loyalty engine, e-commerce platform. Those are different, different application components, and those components realizes the application service. So whatever the application service you are doing it, it will be realizing that. Then fourth one is a device or node. Okay, that is another active, uh, I will structure, I will say any kind of mobile application, cloud node, a POS terminal in a store, right? And those node actually host that application. Okay, it could be any of the applications, okay, CRM application, any of this, right? So that is the understanding of— I hope now it must be a little bit clear, right? So active structure has 3, uh, means 3 sub-elements. So main element is business actor, and under that we have again business role. So you have business actor, business role, we have application component and device role. Similarly, behavior. So behavior will be all about— you'll be finding the business process. So business process example could be Handling the entire consumer complaint, managing return, running the royalty redemption— those are the different, different business process in the customer experience sector or consumer circle sector, right? So processing, what are the example? Like process will be triggering process, another process will be also accessing a business object. That is a relationship. We'll all come to relationship at a point of time. Behavior. Behavior means you're having another behavior is a business service that is externally visible value of— what are the value are added, right? So that is your customer support service, order tracking service. Those are different, different examples of business service. So I'm not going through everything, but I've just shared with you all of this material anyway. Application service, that is means case management service, recommendation service, referral processing service. Those are the different, different application service, okay? So from an application's point of view, okay? And application service serves the business process, right? But business service serve the actor. So you understand the difference. So maybe you will be trying to understand here business service and application service, okay, how those are interrelated. So you try to— let's try to understand more in detail. We'll do an activities here also. So we'll check, uh, this for the difference between the business service and your application service and technology. So there are 3 different service, right? So we'll try to deep dive into this. So let's say I will do an exercise here, AI core. Business, uh, service versus your application service versus technology service differences. With examples in Notion table. Okay, so we try to understand in this context. Okay, this is a little, uh, easy to understand. Technology service means all kind of API gateway service, queuing service, identity and access service, messaging service, WhatsApp, whatever you're using it, right? Which is about actually supporting your application component. Okay, so that is your— in this particular example We have 3 types of behavior we like to understand. Inside this, we have business service, application service, technology service, okay? And out of that, which is serving business process? Application service is serving the business process, okay? Business service will be serving the actor. Technology service will be supporting the application component. So that is the way we will try to understand this 3 thing, okay? So this is what we have to understand. If customer can describe it that is a business service. If system provides it, that's an application service. If the platform, platform provides it, then that's a technology service. That is the rule of thumb here. We'll try to understand here. Okay, so these are the different examples, as I say. Okay, so already we've already understood what service does the business provide, that's a business service. What capability does the software provide, that is application service. What capability does the platform provide? That means a technology service. Okay, so that is how we will try to understand this 3 things. Okay, so that's all. After understanding active structure, we understood the behavior. Okay, so active structure, active structure we understood, then instead of the behavior. Okay, now we'll try to understand the passive structure. Okay, so what is the meaning of a passive structure? So the passive structure here, the example will be your business object, data object, and artifact. Okay, so business object, as I say, this is your any kind of a complaint you are doing, consumer profile, written request. Okay, so those are the different, different example of a business object. So processes will be accessing the business object here. Okay, similarly we have a data object, data represented by the different, different applications. Okay. Customer 360 record, order event stream. Those are different, different data objects here. An artifact is physical or deployable. It could be mobile app, personalized model file, knowledge-based articles, KBA. Those are the artifacts we call it, okay? And these are used by the application components. So that is a passive structure. We now understood application, we understood active structure, behavior, passive structure. Now the motivation part. So motivation part is all about Your stakeholder— who are the stakeholders? We understood consumer, retailer, regulator, brand leader. So those stakeholders actually we are having here, the party who are having the interest, who are having the interest in that particular object, particular, okay, entity. Okay, so driver means pressure or reason for change. Okay, so suppose there are any, uh, low net promoter score there is repetitive complaints, the social sentiment is high, going risk area, you need some transparency, right? So those are the actual driver we have. So that is the motivation. Goals is your, your target outcome. What is your target outcome, right? So like improving the fast contact solution, increase the repeating purchase, those are the different, different goals you have. Then the requirement. Requirement means what are the things must you must have, okay? Omnichannel care history, single customer identity, refund within 48 hours. These are different examples of requirement. Okay, that also comes under the motivation side of it. Principles— what is actually your guiding rule, okay, which is actually you are following every time, okay, irrespective of whatever happens, right? So customer data, once captured and reused, so privacy by design, explainable, of course, those are the things which are the example of motivation. Okay, so now what we will do, we now understood this part of it. Okay, now, uh, this is your— typically we call it a Upper side, if you have seen the layers, okay, strategy, business— sorry, the aspects part of it we have understood, okay. Now we'll try to understand the layers. Layers is a little easy, okay. Aspects is little— I will not say difficult, but if you are seeing for the first time, maybe you might be wondering why they have made it so complicated, right? Initially, that was the initial reactions you will be having, but it is not so difficult once you practice familiar, okay. You will be perfect. Okay, so now coming to the layers part. So layer is easy: strategy, business, application, technology, physical, and implementation, migration layer. So there are 6 layers we're talking about here. Okay, so in this diagram also you'll be seeing there are 6 layers: strategy, business, application, technology, physical, implementation, migration. These are the 6 layers we do have. Okay, so we'll try to also understand with an example here. So all these layers So strategy is all about the highest level of layer in the Archimate framework. It could be like mostly the capabilities, business goals, driver, principles, and policies. Okay, so what are the elements of the strategy layer? We'll try to understand. So first of all, we'll see— I will show you first, then it will be easy for you. Okay, so the aspects part of it I'll show you later, but strategy I can show you now. Okay, the strategy layer, if I go to the Archimate tool event, so I've already installed the tool. You can see that. So this is the tool we are having, and at present we have named it as a customer experience. Okay, and let's say I will give a proper, you know, purpose of this customer experience, you know, project. Okay, of the file. Okay, so customer experience adds some description, purpose, scope, and okay, focus of the model. So I will be using my AI Pista to fill it up. Okay, so it has already fill it up. So other things, but for now I will fill it up like this. Okay, so let's say I will say customer experience for it, write an explanation, short explanation Short explanation: customer experience, uh, covering what? Covering— describing purpose, scope, and focus. Describing purpose, scope, and focus. Describing Purpose, scope, and focus of the model in Archimate. So let's see what is the explanation it is giving, and we will try to add that. This is a— from a customer experience point of view. So why this— what the model is You know, explaining all those things we will talk about here. The purpose is to share the architectural understanding. Why the organization is investing in CX like a driver, marketplace, a competitive differentiation? Who participate in the CX ecosystem? It could be all of the stakeholders. How can CX processes, that means services interaction, orchestrate across the channel, right? E2C, retail, omnichannel. What data system capabilities enables this thing, right? So that is what exactly they are talking about. I think it has given a lot. So what I will do, I will put it in our Notion and we will be having a short description of it in our Archimate tool. Okay? So meanwhile it is updating, I will be showing you the elements first. What are the different elements? Then we will go to the other part of it. So in this model you can see that we talked about your strategy, business, application, technology, and physical motivation, implementation, and migration. These are the different, different layers. So 6 layers we're talking about, right? Start— starting with the strategy to all of this thing, right? So now we'll try to understand this. So let's go to the tool first and we— okay, I think it's almost done. So what I will do, I will just capture it in our notes and what are the different success criteria, next step they're talking about. So I will use it. Use it in our Notion. So first of all, we will try to capture it in our Notion first, then we will go to the system. Okay, so I will capture these things in this example. Oh, let's say so while doing the hands-on, we're capturing it. Also, I can give you homework for the same thing in a later point of time. So now we'll try to understand customer experience model, Archimate overview, So Archimate overview, actually what is having, the describes the consumer staples enterprise designs, deliver, optimizes the end-to-end interactions between organization and consumer from product discovery to post-purchase, all of this thing, right? This is already we have understood, okay? This is okay. So what is in the scope of business? What is the application scope? What is the technology scope? All the details are here. And what's the focus also, right? Increasing the trust, high LOI, loyalty factor, repeat purchase, faster problem resolution, competitive differentiation, data-driven insights. Okay, so that is a typical structure they are having. Okay, so now what you have to do is write a short description of it. So this is a guide for a centerless consumer staples customer access governing aspect layer relations of viewpoints and practical starting model structure in Archi. Okay, so we are doing the Archi. Archi means your, uh, the Archimate structure, Archimate Primer. Okay, so now I will update it here in our tool. I will go here and, uh, structured Archimedes Primer and Build Guide centered on consumer staples. So we are actually now talking about a model for customer experience in consumer staples sector. So we are talking about customer experience and, uh, consumer staples sector. Now what I will do, I will go to the start with the strategy, okay? So because already we have the elements, okay, we will do a hands-on, then only be easy for us to understand this point, okay? So how to do that? Let's start with one by one, layer by layer, okay? So first of the— first of all, creating— whenever creating the first in our key we have to first of all set up these things. Okay, keep the standard document folder but use them like this— motivation, like your drivers, goals, principles, right? So maybe that I will start with here. So I will keep it here like this. So this is the consumer staple sector and motivation. So motivation, I will start with here. So what is the motivation? So that means it is having the driver, goal, principle, and requirement, right? So if I go here, whenever I click new, right, you can see all of these options are coming in, okay? Driver, you know, goal, right? And principle, requirement, constraint, meaning, value. And all of this thing, right? So we can see 3, 3, 6, 3, 9, 10 things are coming up, okay? Stakeholder, driver, assessment, goals, outcome, principle, requirement, constraint, meaning, value, okay? Everything has its own meaning of it, okay? So from a motivation element, if I go there, we will not be doing everything. We will— today we'll be doing only 4 things, and the remaining thing we'll be doing in our boot camps, okay? So driver, goals, principle, requirement only we will do today. Okay, so let's say I will be doing for it. Before that, we have to fill it up, by the way. So for consumer sector, what are the different content? First of all, we'll capture here. Okay, so, um, before we go there, okay, we will be first of all fill it up. Okay, so let's go to that section where it will be— this is the motivation layer. So suggested motivation layer we will be having here. So we will fill it up here. Okay, so from a consumer sector point of view, what are the different motivation layer? As I say, driver, goal, requirement— these three things we will fill it up. Okay, so we'll try to fill it up now. So let's say driver, goals, principles, and requirements. Okay, driver, goals, principle, requirement. Driver, goals. So we have here driver's goal, driver goals, business requirement, driver goals with requirement. So where is that? Just a minute. Driver goals, this is the suggested motivation layer which you'll be practically using it, okay? Requirements, driver goals, requirements. So actually we will follow the model, then it will be easy for us. So we will capture the screens, okay? So screenshot we will capture. People who are attending for the first time, you can just take a snapshot of it, and anyway you will be getting recordings as well to follow up, but It'll be easy for us to understand them first, then we will go for the further steps. Okay, so let's try to understand in the way we'll try to capture these things in our system, then we will go further. Okay, so first of all, we'll try to capture the drivers. Okay, so what are the different drivers for us? Consumer demand for transparency, definitely. So we will capture here new Driver. Once I say driver, so I have to simply capture here what is that driver, okay? So I will be updating here driver as maybe one of the driver is consumer demand for transparency. Consumer demand for the transparency, okay? So that is one of the driver. Okay, so this is the properties analysis. You— these things we will doing later point of time, but for now I will be capturing this. Okay, so there is no— there is no specialization now, but we will do now like this only. So this is one of our driver. Okay, so now once it is done, driver is— we understood. Okay, so this is our driver. Driver is there. This is the consumer demand for transparency, right? So now, uh, if we are having here, this is the driver we are having, okay? One of the driver, okay? So now what I will do After driver is— so we'll take one, one example today, so I will not be going too much, okay? So it will be overwhelming people who are doing for the first time this modeling. So consumer demand for transparency is one of the driver, okay? So this is the— I will say here, I will put it here itself, okay? So driver name, so let's say consumer demand for the transparency, that's one of the driver. And now the next one is, uh, another thing which I can do. I can have multiple drivers. Okay, so definitely food safety risk. Okay, so that is also a driver, right? So this is a food drive— food safety risk. That is another driver. So if you go here, I can always see whenever I'm selecting it, right? You can see the top, you can— the bracket itself is writing as a driver. I have not mentioned it. Only the name I'm giving here, okay? Consumer demands, automatically it captures the driver only. The system understands that. Now we have supply chain disruption, that is another driver for this particular thing, okay? So let me go through that motivation layer. I will be capturing another driver as this one, supply chain disruption. So that is another motivation, right? So now the next one is, uh, sustainability pressure. Every company nowadays, they're having sustainability pressure. So they have to— even in a technical paper, on paper, they will be writing as a sustainable organization, minimum. So this one is the second, another driver I will mention here. So this is another driver, sustainability pressure, right? So these are all your Regulatory compliance, margin pressure, brand loyalty, Amazon, right? You are typically drivers. So now let's do that. This is also a driver, regulatory compliance, right? Then we have, uh, margin pressure. You should be having good margin, right? So why these are also driver, if you try to understand, you can do that, okay? So we will see that if you do not understand why these are driver. So I put another driver here, margin pressure, right? Then another one we have, brand loyalty erosion. Okay, so there are 8, 7 driver we have kept it here. Drivers, goals, and requirements. Okay, so we will go here to our system. This is another motivations. Under motivation we have a driver And our driver is here, this one, brand loyalty. That is also very important to my customer experience sector, customer experience segment, right? And on a typical consumer staple sector we're talking about, okay? So these are the 7 things from a motivations point of view, from a driver point of view, okay? So people who do not understand why these are called driver, I think people have— somebody have asked it. You can make, make sure, okay. Uh, explain why above 7 are key drivers for consumer staples sector, okay. Consumer staples sector with an example, with an example from India and global, global. Let's say I will take example from US or KSA in a tabular format. In table KSA or any European countries. Country. So I'm putting this here, uh, as the codex which you will be utilizing directly when you do this exercise. This is very interesting, and you will be finding all these things, okay. Okay, so let's see what it is bringing in. Hmm. So we'll insert it, and what we see here in our observation— so this is not in a proper format. I will ask to put it in a proper format. Let's see. Put above table in proper format. So meanwhile, this is the example, but we understood the driver, and we have next is your goals, then requirements. Okay, and what we can also see that here, after the motivations part of it, then also we do have, uh, in the screen you will be seeing that model One is a driver, then we have goals, outcome, principles, all these things. So we're focusing on today one part of it only. Okay, so other part definitely I will be giving you an exercise. We'll do it in the next session, maybe next, uh, uh, Tuesday. And this entire week we will be talking about this part mostly. And today we talked about customer experience. Similar, we're doing a similar activity for finance and Wednesday. And Thursday we'll be doing the for procurement. Friday we will be doing the supply chain. And Monday we'll be doing for the workforce, that's your HR. And we will continue with this exercise because this is also a very one of the topic, very few people know it. And those who know it, actually they realize part of the benefit of using it, right? So we will talk about this. Okay, so now with that note, okay, I think this table is updated. Okay, so this table is updated. We can see that driver and why it is a key driver. Okay, so you can see what I will take one of the example. Let's say, uh, one of the thing is, uh, consumer demand for transparency. So for one, proof of ingredients, origin, nutrition, and claims, right? So what is in it, where it came from, right? Especially in India, we have seen FSSAI levels, right? What is the ingredient, we'll check it. Clean level cues, keyword-driven product pages. Okay, those are the key examples how we need typically transparency. Many, you know, social media also might have seen that how it is varying, especially some of the, you know, influencers, they have actually talked about it and how much the ingredient, especially the Bonvita Horlicks, in those ingredients of tea, coffee, whatever you're taking it, right, the ingredients how they are diluted, or if you talk any oil also, right, in India, how, how, how the percent is, and how in European countries and US, other those variation. Okay, so you can see that in this example, right, how these things are taken care. Okay, similarly, sustainability also, you can talk about plastic waste and all of this in case they are having Vision 2030 to responsible packaging through supply chain efficiencies and all. So it is a good read, you can go through that point of time. But this is exactly the meaning of a driver. Okay, so after driver, we'll try to understand the goals. Okay, so goals, then the requirements will come after. So goal is that is really improve the product traceability. Okay, so product traceability is also one of the key factor we'll try to understand in this session. So goals are— so there are 6 goals, and in this example we will try to capture those also. In our motivational layer. Okay, so what we have here, I will go to— this is a driver, this is the goal, and goal will be— this is one of the goal, improve product traceability. Okay, then we have typically reduce recall time, so that is what also we have Reduce recall time is also one of the goal here. Okay, so I'll put it as a goal. This is one of the goal. Reduce recall time. Improve self-availability. So we'll go here. Motivation is goal self- Availability, improve self-availability. Then what we have? Improve, reduce waste and packaging impact. So this is another goal we have. The next one is increase consumer trust, which is very, very important in a customer experience segment in any of the sector. Winning the trust is the new currency these days, okay? So it has to be also there. So I will mention it here as well in terms of a goal. Increasing consumer trust. The next one is, uh, improve forecast accuracy. This is another goal which we have. Okay, so these are different goals we have here in this particular sector. Okay, so now what I will do, meanwhile I will also try to save all of this thing. Okay, so these are all saved in my, uh, segment, my design file. I will design, I'll put in my archive folder, Archimac Design folder, then inside that I will put it like a CX, customer experience, in consumer staples sector. Okay, so in this way I will just save this. Okay, so now what I will do Meanwhile, I'm extending the time, so because it will take some more time than expected, because let me go and check the webinar lead to opportunity transfer. I will extend by 30 minutes. And back to our workshop. Okay, so this is back to workshops. We will continue another Few minutes. Okay, so improving the forecast accuracy, that's the different goals we now captured here, right? So improve forecast accuracy. Okay, so again, same things we'll be asking here why these are goals are important. So always ask why whenever you're doing all of this exercise. Why These goals are relevant for your sector, for consumer staples sector. Explain with examples from India and Global in Motion table. So this kind of prompt file, if you're using it while doing it, right, it much easy when you discuss with the customer also, right? So that is why we are doing a little bit detail. Otherwise, uh, anyone can do all of these things. Only thing is you have to think like a, like an architect here. Okay, so we are designing everything from scratch and how we can capture all of this thing. Okay. So these are different options they have given to us, okay? And we can basically go about it, okay, after we have some of those elements, right? So essential elements whenever you're doing it, right? Okay, so then we will go here, okay? So now actually we have seen this thing, so let me capture it while Okay, so now this is actually— I'm not going to read out, but, uh, this is something as a task. At least you can understand why we do what we do, right? So drivers and goals are clear, right? Now we will go to the requirements. Requirements are what you will be finding: the end-to-end visibility, real-time inventory update, quality incident tracking, sustainable packaging, And these are possible requirements you can have in a consumer staple sector, right? So those things also we can have here. Okay, so 6 goals we have defined, 4 2 6, we understood that. Then we will be going to the another thing here. Yes, next is your requirements. Okay, so before that, I'm just putting a prompt here. So this is a prompt we can utilize whenever we're doing this exercise. To call out here, so same thing, you will be capturing— this is the goals, and this is a sector. So you can choose any of the sector at a point of time. Then examples from XYZ country, if you want, or global, you can do that. Okay, so this is a prompt for you, AI prompt, or the Codex, which you can try, I call it. So you can vary whatever your interest area of your sector, right? And you can do the same thing for everywhere. So I'll just put it here. Why these goals are important, I will capture it here. Then I will go here, Ctrl+C. This is the goals. This is the drivers. Drivers also, we have created one section. So this is the callout, okay. Relevant for your sector. So this is the drivers, actually, from India and global. So we will see all these examples very often. So pretty much, so try to understand them carefully. So this is your drivers and goals. We try to understand Then comes your requirements. Okay, so same similar prompts we can utilize for there as well. So here I'll just highlight whatever I'm highlighting. You can change it in your— whenever you're trying with some other elements, okay, or other industry sectors, you can expand this up one. Okay, so I will mention here the next one is the requirements. So multiple thing we have. So we will be not going everywhere, we will be focusing on one, one each. Just I explained to you how do you create all of these things. But, uh, whenever we're doing all of these things, you have to be very careful what exactly you need it, okay? And what are your— what are the view you want it, right? That is very, very important here. So now almost is coming up. So now this is the requirements also, why these requirements are very important for us. 4, 5 major requirements we are having, and we'll try to understand here. Okay, so now I will make it as a call out. So you can utilize this AI prompt later, later point of time. So this is your requirements sector, right? So now these are the 3 things we have done. So in our system also— no, system we have not done the requirement part of it. So requirement will be this one, uh, this is end-to-end Batch visibility. Have we done that? No, we have not done the requirement segment only. We have done the drivers and goals. Okay, and let's do the requirement part of it. Requirement— we will do 5 requirements. We'll capture there. New requirements, I will capture it here. Advent visibility. What is real-time inventory updates? Is also essential, right? And Real-time inventory updates, that is another requirements. Third one is quality incident tracking. So quality incident tracking, new requirement. This is my Quality incident tracking. Then we have sustainable packaging data capture. This is the fourth requirements, motivations, requirements. This is the one, sustainable packaging data capture. Consumer complaint management is the fifth thing which we have in this series. This is the requirements. Okay, so now this is done. Okay, so now what we can do here, these are the drivers, goals, and requirement we understood. So what else we have in this motivations? You will be finding You can note it down. Okay, so what else we have? So we also have principles. Okay, principle, constraint, meaning, value. So I'm also noting it down. Parallelly, you can also check it out. So we have, first of all, uh, we will be doing a mind map, by the way, for this. It will be easy for us to do. So we will go to a mind map and then it'll be much easy for you to understand these things. I will do that. So what we have now understood— drivers, we have— these are all under motivation, by the way, motivation layer. Uh, we have a stakeholder assessment. Stakeholder assessment. Then we have, under motivation, we have what? Stakeholder driver assessment. Goal outcome principle. Goal outcome principle. Then we have, under motivations, we have requirement, constraint, meaning, value. Constraint, meaning, value. So we have out of that part which are the things we have already done. So we have already done for goals, uh, we have done for drivers, driver schools, and requirement we have done. So the drivers, this is— I will highlight drivers, we have done goals, we have done. Then we have also done for the requirements. Other things were yet to do, okay. But before that, 336, 3910, all this comes under the motivation, okay. So this comes under motivation. And what is the motivation? As we already understood from the top Here, this is motivation, okay? This, this is— we have— this is an aspect, by the way, okay? So there are different aspects like active structure, behavior, passive structure, motivation. Inside the motivation, we have seen those other things, okay? So, uh, now what we will be doing it— so here I've given more few examples, but in the system we have more actually, okay? So I have not given every examples here. So motivation under motivations, these are different, different model folders. Okay, keep the standard accurate folder, but I use them like this. Under motivations we have like this. Okay, and okay, they're saying to keep a folder out of it. Okay, this is better. We can do it together. So what we can do, we set up a folder. So inside that will be easy, easy for us to do that, right? So let's try to create a folder, and inside that we will be capturing everything. Okay, so stakeholder, all the stakeholder will be going here. Stakeholder, let me try that. So first of all, we already having the— what are we already having it? We will put that here. Let's say I will be creating a driver goals. Most of you done this, right? Driver goals and requirements. So driver, and inside that I will be keeping because otherwise it's very difficult to manage it. Okay, so this is one, this is a driver, right? So I will put it inside the driver. Okay, you can see now it will be easy for you to navigate. Okay, so in this way you can put it here. So all the drivers together. Regulatory, supply chain. We have a sustainability pressure, right? So these are my driver. I will understand easily. Okay, so that becomes so easy now. Okay, so I could have done it initially, but now, yeah, this is good. So driver, we have a— if you can also see the folder, so these are my drivers, 437 drivers. Okay, so now we are also capturing, uh, other things. Okay, so what are the other things we have? So quickly we will do that activity. Okay, first of all, it is better to create a folder and to be— it will be easy for you to manage it. Okay, otherwise it will be little tricky. First of all, we will see that list. Where is that list? Okay. So we already done the drivers, we have done goals, we have done requirements, we have done, okay. Then we will try to understand constraint, meaning, value, okay. The stake— anyway, motivations has all of this thing, okay. Under motivations we have, uh, and we will see again, 1, 2, 3. 4, 5, 6, 7, 8, 9, 10, right? So under that we have stakeholder. We have seen stakeholder. So 1, 2, 3, 3, 3, 6, 10. Okay, we already have a 10, right? So driver, goals, requirements already we have done. So now we will be repeating it for the others. Okay, so we will go in the same sequence. So driver we are done, and I will go here. This thing, but we will be utilizing that codex, you remember, which you have done. So driver stick is done. So stakeholder assessment, all these things I will do. So I will take it after driver. So I will Ctrl+X. So wherever we are having the drivers, below that only I will do. Okay, it will be easy for me to track. This is my drivers. Now here I will Put it here, stakeholder. Okay, so now after understanding the stakeholder, I will go to the assessment. Ctrl+X, assessment, stakeholder assessment. Then I will go for the next one. Now goals is already there, so I don't have to worry much. So both already there. After goals, what I will be having outcome, principle, then we will be having requirements. So this is what we have: outcome and principle, outcome and principle. We have requirements already. Now we'll understand these 3 things: constraint, meaning, and value. Okay, so this is something we'll talk about it. Okay, so now let's do these activities little quick, and we'll be utilizing the Codex directly, and we will, uh, do that activity together. So now, so let's, uh, outcome. What is the Codex for the outcome? So we will utilize this. Give an examples of Uh, all of these things, okay, we'll try to understand those. So driver, goals, already we have done it. Requirements also we have done it. I will not ask out of this what are the other examples. We constrain meaning, value, outcome, principle, outcome, principle. Then we have, uh, stakeholder assessment. Stakeholder assessment, 2, 2, 4, 5 to 7. Okay, 7 are there. Okay, so this 7 I will be asked for. Give examples of each. Uh, maybe I'll be using AI Fiesta for better quality outcome, so I will use it. Give 6 examples of each, of each, for consumer stakeholder sector, GICS sectors. Okay, so we'll try to briefly— so these are motivational elements, as I said, that you will be having stakeholders and all of this thing, right? So motivation layer elements. So motivation, by the way, this is, uh, in terms of the Archimate language, we have, as we have seen, these are the different part. If you go to the top, we talked about it. It is an aspects. There are different, different aspects, okay? Not a layer, okay? So layer is not a right word. Layer means your different thing— business layer, application layer— those are different layers. Okay, so now we'll try to understand it and we will see a couple of examples, relevant examples. Stakeholder assessment, okay, then constraint, okay, we have meaning, okay, and, uh, circular economy model, trust badge, personalization, KR— these are different for meaning. Meaning means the conceptual construct, symbolic representation of use to communicate ideas, values, and principles. Within the architecture context. That's the meaning of meaning. Okay, we have a constraint. This is a limitation, restriction. What are the boundary conditions you will be having it, right? That is a different— this is called as a constraint, right? Similarly, assessment, also very similar thing. Okay, and actually it has given a good quality examples, okay, which is primarily directly we can utilize it in our modeling. Value: consumer trust, operational efficiency, revenue uplift, brand equity. This is a value. Outcome: omnichannel loyalty program, unified customer data platform, AI-powered personal engine, personalization engine. Principles— principle is actually overarching rule, guideline, or foundational belief that governs decision-making and architecture design. Okay, everything is actually based on that. Data privacy by design, omnichannel consistency, consumer-centricity, radical transparency, sustainability integration, failsafe recall automation. right? So these are different examples, and also they have given very good quick reference table for all the 6 elements. Okay, this is a very good example. Okay, so now we will document it, we will capture it here in our Notion, and we will model it. Okay, so now here we go. If I try to capture it here So let's do it. So first of all, we will capture this one stakeholder, okay? So stakeholder who is having that interest in all of this thing, right? So we will see that. So the stakeholder, we will put it here. Then assessment, we will go further. Stakeholder, we do never do an assessment at a point of time. So this is what we will be having in the stakeholder map. This is the definitions and this is the table. So this table I got here— brand manager, sustainability officer— these are different, different stakeholder, we will say that. So I will put it here after driver stakeholders. Yeah, this is the one, and this is a stakeholder thing. Now I will make it as a heading so that we do not forget this. Okay, this is an aspect, okay, not a layer. So we'll be very careful while using this. Motivation aspect. This aspect, this is the aspect. Aspect means all the columnar things, whatever you are seeing, right? So now this is the drivers, we understood. These are stakeholders, we understood. Then your assessment, what kind of an assessment you will be having? Your assessment, you will be evaluation of analysis, outcome, identity, strength, weakness, all of this thing. Right, so I will see, I will capture it here. Ctrl+C, assessment in, and assessment is here. Assessment, assessment, where is the assessment? So you will go through the assessment section and we will update here. Yes, this is the assessment. So this is assessment. Now we'll try to capture it, turn into heading. This is our assessment. Okay, so now, uh, this one we understood. So in the same way, after assessment is done, next part is your what? Assessment constraint. Constraint, it could be retail partner lock-in, budget constraints. Those are possible examples. So constraint, I will put it here. It is under here. Okay, after stakeholder assessment is done, so we have now— this is the requirements. I'll put the Constraint. See, okay, so now this is my constraint. So I will make it header, header 2. Constraint we understood now, okay. So now stakeholder assessment also we understood clearly what is stakeholder, what is assessment, which in the below, above we have already seen it, right? So this is your drivers, okay? So all this thing, now we would be understanding technically constraint. All this thing understood. Assessment constraint, we understood. Meaning, meaning, as I say, it's a conceptual construct or symbolic representation, how you communicate your ideas, values, or principles. Within the architecture context. Okay, so this is something I will be giving to you. Meaning, meaning, meaning, meaning here. Okay, so meaning is coming after— here, here, here. Driver, assessment, goals, outcome, principles. We have constrained meaning here. Here is the meaning. People say doing a meaningful work, right? So here, farm-to-table narrative, it's a story, right, that connects consumer to origin, the farmer sustainability journey. It's a branding point of view, is very, very important, right? Similarly, circular economy, personalization as a care, right? These are real meaning of it. So You have to put it here. This is the meaning of it, and we'll try to understand how these are relevant, okay? What it represents, and from a customer experience point of view, what is the significance of it, okay? So this is the meaning of it. So meaning is not equal to value. Value is different, okay? So meaning is here, means, uh, conceptual construct, as I said, right? So this is the meaning of it. So, uh, I will put it here. The definition of a meaning, meaning of meaning. Okay, so this is what it is. Okay, and after understanding the meaning, we have the next one is we have value. So value, what we see here is this one: consumer trust, revenue uplift, brand equity. These are the different, different examples of a value. So value, if I go here I will go and update here, okay? And value here means turn into a heading 2. This is my value, okay? So there are different values. You can see that income, revenue, equity, brand equity, data asset, right? These are typical values we do have, okay? So we understood the values as well. Now the outcome, what exactly the business impact, okay? The end state, right? The observable, tangible results, okay, or end state achieved after implementing the architecture, right? So that should be the outcome, okay? It could be sustainability impact dashboard, automated recall orchestration, unified customer data platform, right? What are the possible outcomes? So I will go here. Outcome. Okay, so this is my outcome. So now I will turn into heading. This is my outcome. Now we'll try to understand the principles. So principles, this is the overarching rule, guideline, or foundational belief. Okay, so which is actually any kind of decision making, even in your life also, this is very, very important. Any All depends upon your values and principles, right? So whenever taking decision, you would ask yourself, is it aligned with my value? Is it aligned with my principles? Okay, so the same principle, same way we are doing it here. Ctrl+C the principle. So I will go to the principle layer, principle aspect here. Okay, so principle is this one. Okay, this is your principle. Okay, so this is what I will do, heading and we'll try to understand the application in customer experience segment. So principle, we are done. Okay, so I think almost we are done with everything. So these are the 6, uh, 7 elements, so which you are having it. Okay, and, uh, I think in the same sequence, let me check we are having it or not, right? Motivation. So under that we do have stakeholder driver assessment. Stakeholder driver assessment. This driver, not drivers, right? Driver. Yeah, there's no plural here. Stakeholder driver. Because we are— after we do this for the first time, then it will be easy for you to next time whenever you do it, right? For other sectors and all, it's much easy. So stakeholder, driver, we have driver, SDAG, SDAG, stakeholder, driver, assessment, goal. Stakeholder, driver, assessment, goal. We are in the same sequence. This is correct. Now we will go to the next part. What exactly is Outcome, principle, requirement. Outcome, principle, requirement. They're all same sequence: 4, 3, 7. Then we have constraint, meaning, value. Constraint, meaning, value. Okay, 1, 2, 3, 4, 7. So we today will try to complete the motivation, you know, that particular aspect. Okay. These are 10 aspects we'll try to understand, we try to apply. It's not only we try to understand but also try to apply for a sector, consumer staples sector. And this is comes under motivation aspect, okay, under mostly motivation aspect. These are the 10 things we try to understand, okay. So this is the summary part of it and I will make it as a note. This is the main thing, okay? And it is heading. Under that we have, these are the 10 things we have understood today, and we will try to capture it as, uh, header. Let me check if I can do that. Yes, I can do that. Header 2. Okay, so this is the header 2 we have, and what I will try to do Uh, keep motivation aspect as— motivation aspect as top, and under that, all 10 can be foldable, and under each element allow to again fold where I can put all examples. Let's see whether it is able to do this by folding. In this— so in the target architecture, we'll try to build it up on how does it look like. We will see this. Okay, so now we have a motivation aspect, and I think it is done. It— they have done it. Let me check. So they are still doing it. Yeah, I can see that motivation aspect. They have wrapped up the edits here, and I can see that one, the motivation aspect, as I say, in the same sequence: stakeholder, driver, assessment, goals. 4, 3, 3, 10. Okay, in the stakeholder, we have examples. Okay, like this. So here we can build a list like this. Okay, so this is— we will publish it in our platform. And, uh, setting— they are following the same principle. Driver examples list, assessment examples list. Okay, this is good. Yeah, so this is a task I'll be giving to you also, which you can do it for your sector. Okay, so this is the one of the aspect which you try to understand. And anyway, the examples, uh, you can folder— create a folder also same way. So we have understood the stakeholder here. So stakeholder is the first one we've understood. I think here I can sequence also, right? Let me know. I think properties, if I go, uh, let me check. Link to view visible folders. Yeah, all of these are visible. Stakeholder. Okay, but anyway, drivers we have done. So driver, 7 things we have done. Then stakeholder. So I will be creating a folder for that, all of these things. We have a driver, stakeholder, uh, then we have assessment, goal, outcome. Okay, assessment, goal, outcome. Assessment, goal, outcome. Assessment, goal, goal, outcome. Goal outcome. Then we have your principal requirement constraint. Principal requirement constraint. Principal— we have requirement constraint. Principle, requirement, constraint, constraint. Principle, requirement, constraint. Then we have meaning, value, requirement, constraint, meaning, value. Meaning value. Okay, so now this is done. So now it becomes super easy for you to navigate through, and you'll be creating the respective things only when you go to the respective sections. Okay, so the consumer complaint segment management, this is a requirement, so I will be moving into the requirement folder. Like this. It's easy. And current batch visibility, this is also requirement. Quality incident tracking, this is a requirement. Real-time inventory updates, this is a requirement. Then we have sustainable packaging and data capture, this is a requirement. Okay, so now requirement folders we have done. Next is your goals. Okay, these are different goals. Improving forecast accuracy, This is your goal, right? So improving product traceability in consumer sector, right? These are different, different goals we have, right? So increasing consumer trust, okay? So this is also a goal. Reducing recall time, this is your goal. Reducing waste and packaging impact, these are your goals, right? So this is the series of goals which we have. Okay, so now we will be capturing the remaining things quickly, and then we will proceed. We will, uh, go to the next step and the next session. Okay, so we have just covered only one aspect today in detail. Okay, and we will try to speed up, and this is a very easy task. Only thing is to understand, okay, there's no rocket science here. Okay. And just we need to understand these things carefully. So what we have done, I have done, right, rather, driver goal requirements we have done. So we'll go to the assessment side of it, okay? So now let's go to the assessment. What kind of assessment we have? Product transparency gap. So this is an assessment, assessment here. So I will put an assessment here. So it'll be easy for me to now frame. Okay, so product transparency gap is an assessment here. Okay, so next one is your omnichannel fragmentation assessment. Omnichannel fragmentation. Okay, next one is recall response weakness. This is an assessment we will be doing. And here we go. Recall response weakness, this is an assessment. Then Royal loyalty program ineffectiveness, that is our assessment, right? Then Another assessment is this one: loyalty program ineffectiveness. Okay, customer data fragmentations. If your consumer profiles are split in 5 different systems— same thing happens in the employee profile also, by the way, in different organizations, they're in 5 different systems, 4 different systems. Okay, so this is another assessment. All right, now next one is, uh, Sustainability Communication Deficit. Okay, so this is another assessment we have. Sustainability Communication Deficit. Okay, so this is another one which you try to understand this model. And, uh, yeah, I think there are 6 assessment we have done. Added in our, our R key. Then let's go to the— after assessment is done, the next part is we have constraints. What are the possible constraints we can have? All right, so let's go to the constraint sections and we will see that the constraint section says 6 constraints. Legacy ERP system, so still you are in old— if you're using SAP on-premise, SAP HCM. That is your answer. Okay, it's a constraint. That is your constraint. New constraint is that constraint. You see the symbol, this is a symbol of a constraint. Okay, so you have to maintain that legacy ERP system is one of the constraint. Data privacy regulations, GDPR or CCPA or whatever you're having in local data privacy, you know, that is a constraint for you, right? So this is another constraint. I will say here, go and put it here. This is your constraint, right? Data privacy. Then we have retail partner lock-in. That is your constraint, right? So I will go here and I will update here. Retail partner constraint, right? So this is your constraint number 3, okay? In a consumer retail sector, consumer staple sector. Then we have a cold chain requirements, okay? Because for perishable goods, perishable products, you require temperature-controlled logistics, okay? Otherwise you will lose them, okay? It will be loss for the organization, right? So I will be putting that as well in the constraint sections, okay? So cold chain requirements, that is also a constraint here. So two more are there, then we will close here. Others are for homework. Okay, packaging material sourcing, right? So if I go here, another constraint is your packaging material sourcing. Okay, so that is your constraint. Then your budget constraints, this is also a constraint. Okay, so I think this is really helpful. So all the 6 we have drawn, uh, or 5, then another 5 motivation. This is for your homework, like already have given the thing. You can just simply create so that your motivation aspects will be complete. Okay, so I will save this. Okay, and I think we will be checking it out in the next session. Okay, so this 5 things 7 things we have done, and hope it was helpful. And but actually, this is actually a tedious task initially, but when you see the results and all, you will be finding much interesting. Okay, you can see those once you see the outcome, right? Okay, so you'll not be seeing the outcome immediately, okay, but over a period of time once you build this entire thing, right? So with that note, signing off here and see you in the next sessions. And if you're not a part of any of the members, you just subscribe to membership. So it is very much this academy.com, and, uh, they say we are discovering by learning all of these things, right? So we're offering called Architect with AI, okay? Go there, and we are architecting with AI, by the way. So everything, each and everything, whether it's a learning technology tools or such a kind of an element, right? So go there and you will be finding, uh, your It's called Discover, Learn, Apply, and Build Architect with AI. And you can simply go for— if you want to continue with the journey and, uh, with more depth to— with handholding and all, you can choose your membership. You can start with Selma, okay? And, uh, from there you can proceed further. So you can— this is a lifetime membership at present we're offering for limited time, and over a period of time it will be a yearly basis. Okay, so bronze, silver, at this moment it's lifetime, but gold and diamond, this is actually yearly subscription we have, right? So this will be more details, more in-depth. We will go and go and worry about— diamond is more about accountability and precision, right? So it's not about more courses, but in this sequence, sort of sequence, people can directly also opt for a diamond if they want to have a higher accountability and higher no, speed up that. So with that, we will stop here. Thank you very much. See you there in the upcoming sessions. Okay, take care. Bye-bye.