Transformation Every Day
00:16:16 · Alexander Greb, Johannes Langguth
[00:16:16] S3: incredibly grateful if you could leave us a five star review and share it with your friends and colleagues. Your support means the world to us. Thanks so much, and happy listening. [00:16:36] S1: I fully agree with that because although when you look at, and I've seen in the past very, very, very commonly, you have some set coding somewhere. You have a modification somewhere and so on, or some some add on where you deviate from standard going to the add on. And quite often, nobody can tell you why or can remember why. They they just say, yeah, probably there is a reason because it exists. So the pure existence of something is the reason to clinch on that and to keep on that. And to break this kind of, let's say, circle, yeah, open, that that has always been one of the biggest challenges. And with the capability you bring into that and to unlock this kind of knowledge of what is happening there, why do you use it, do you use it at all and so on. It it can bring a lot of transparency with... Which is missing. And I think from my background, the lack of transparency in exactly what you meant about this context, which is not even known to the user themselves anymore. Why did anybody do that? It's one of the biggest problems in transformation at all. Because if you do not understand yourself, [00:17:44] S3: how can you transform? [00:17:45] S1: How can you unlock any strengths? It's just not possible. I fully agree with you. Let me
00:17:45 · Johannes Langguth, JP Haas
[00:17:45] S1: How can you unlock any strengths? It's just not possible. I fully agree with you. Let me [00:17:49] S0: give you one example that I thought was really, really beautiful. There was some custom code in one of our customers that said something along the lines of if the truck that is delivering something for your production line is over two meters in height, then it needs to go to gate b and not to gate a. Now if you read that in the custom code, how do you know whether you should... Whether you need to keep that and whether that exception should remain in place in in a cleaned up environment going forward? Because there could be a 100 different reasons why you have that exception. Right? It could be because The gate is too low, [00:18:32] S1: something like this. Yeah. [00:18:33] S0: Exactly. Or it could be because on a on a... In the next downstream step of that, you can't deal with a with a truck that's that's that's over two meters high. Or it could be because they found out that if you only fill a truck to a certain to a certain degree, that actually leads to higher throughput in your production line, and they've optimized the the flow of the of the production line in some way. Now all of these are the the why and the business intent behind that custom code, which ultimately just encapsulates and encodes your operational learnings and your operational identity as a company. And that needs to be that needs to be figured out. And that needs to be captured in order to accelerate transformations.
00:18:33 · JP Haas, Johannes Langguth
[00:18:33] S0: Exactly. Or it could be because on a on a... In the next downstream step of that, you can't deal with a with a truck that's that's that's over two meters high. Or it could be because they found out that if you only fill a truck to a certain to a certain degree, that actually leads to higher throughput in your production line, and they've optimized the the flow of the of the production line in some way. Now all of these are the the why and the business intent behind that custom code, which ultimately just encapsulates and encodes your operational learnings and your operational identity as a company. And that needs to be that needs to be figured out. And that needs to be captured in order to accelerate transformations. [00:19:20] S1: So so how do you guide users to these kinds of new knowledge? Is it something like an you list everything and then you then you you go through this? Or how does this kind of logic works? Does it find out that there's something extremely strange? Let's go deeper into that. Or does it go through the okay, let's step one, take step two, take step three approach in that way?
00:19:20 · Johannes Langguth, JP Haas
[00:19:20] S1: So so how do you guide users to these kinds of new knowledge? Is it something like an you list everything and then you then you you go through this? Or how does this kind of logic works? Does it find out that there's something extremely strange? Let's go deeper into that. Or does it go through the okay, let's step one, take step two, take step three approach in that way? [00:19:41] S0: Let's talk a bit about how we how we approach and how we think about this this wider problem of of fit gap analysis, we we kind of bucket it under that, right, which is in order to figure out how the new system should be set up, the best indicator is you need to understand how you're how you're running today and which of these operating steps are actually business critical for you and which of them are not. And most companies today don't have that visibility. And so the way they they approach that is by speaking to the end users and mapping out all of the different steps in the applications they're using today in a in a qualitative way. Right? They they just have user interviews, and then they build up these manual lists, and then they go through each of the steps in order to try and figure out what's going on. We do it the other way around. We we can generate a list of all of the business capabilities of your system by just reading out the custom coding configuration of the system. And we then give the IT and business teams a list of all of these requirements that they can then work through almost in a checkbox kind [00:20:53] S1: of way.
00:20:55 · JP Haas
[00:20:55] S0: And importantly, we then also add additional context to this, wherever you have documentation, comments in the code, whatever that is. Right? But often even that is not enough. Because often the two meter the two meter truck rule is not... It's not documented anywhere. It's just in the heads of the business that was requesting it or the the consultant that that implemented it back in the day. And so whenever we come across these types of situations, we actually ask the user for input. Right? We basically flag that something is a bit of an exception, and it looks... That it's unclear why that that rule exists. We can we can then start capturing that knowledge from the user. And that I think is really important. Right? Because at that point, you're you're building you're building this living and breathing and ever growing intelligence layer that that keeps the knowledge about how and why your system and your company operates the way it does. You keep that in a platform that you always have access to and that doesn't leave the organization. And that's really, really important, we think. So that... That's how we that's how we approach it. And what we what we're seeing as a dynamic is that teams are starting to work differently because the having that that foundation to to argue about, right, and to discuss between teams in a much more transparent way, it flips the dynamic. It flips the dynamic from we're flying blind and we we need to we need to try and ensure that that every capability is captured to I know all of the capabilities are captured. Now let's talk about how we can get better as a company.
00:22:36 · Johannes Langguth, JP Haas
[00:22:36] S1: One sentence I read about you, I'm not really sure if you were stating it or if it was said about you, so you can comment about this, but I really liked it because I think it describes very well what you are what you are doing is AI operating system for enterprise IT. How should somebody who has not crossed roads with Conduct AI already, how should somebody like that who said, I really need that. And what I heard about this kind of, okay, I learned to understand my system based on the custom code. What are the first steps with Conduct AI? [00:23:09] S0: The first steps are thankfully very, very quick. And that's one thing that our our customers are always so amazed by and frankly surprised by because in the past and in the enterprise IT space, just because the stakes are so high, everything used to take a long time. The platform we've built works completely out of the box and is set up in a very rapid and hands off way. And that means you only have to have to install a small a small ABAP program on your SAP system. And the rest is happens, know, completely completely hands off. We can we can onboard and give you that level of transparency and insight into how your system operates within twenty four hours. And we've done this with, you know, some of the biggest Fortune five hundred and one hundred customers in the world, and it's always worked like that out of the box to to the incredible, you know, amazement.