00:08:56
So let me take a step back here. So I would like to dive a bit into an experience that I had, beforehand, at Volkswagen Group and Volkswagen Financial Service, as a global head of data analytics and AI I was, I was charged to really build up digital transformation across the group when it comes to data, I was part of a larger unit that was driving digital transformation.
And my task was to bring in data strategy and a platform strategy to drive that, across all pillars across globally to bring in more, more advanced analytics into p lay. And I can tell you from that experience, when you start off with something like that, usually you have most companies, all companies that I know have BI teams.
So business intelligence teams out there. So when you start to scale this, you want to do two things. You wanted to reach more people. So you start the self service analytics play, you could say. And then the other thing is you want to also build really like killer ML products, like things that really bring you a lot of value.
And then scale that across different markets, across different business units to adopt those ML models. So you start usually with, when you start something new, you start usually quite from the center. You build, what I've done at financial, Volkswagen financial services was I built a data analytics and AI unit at the heart of the company.
And then we only slowly created teams in the US and in China to have a global footprint, but we were driven a lot, driving a lot from quite central teams, you could say, and then there would be some hubs, a few fighters here and there that would do data science or analytics somewhere in the markets, around the world.
We operating globally. But that thing doesn't scale. It's very good to start off like that in the beginning but over time you want to put people closer to the business, so you want to have people in the markets, in each market doing data science running their own models that are more specific to that market or on each business unit, running very business unit oriented stuff.
During that journey, it was not a problem because the area of opportunities were endless and we just focused on the most important things and we grew the central unit, but at some point that doesn't scale, you have to put things into close to the business to make it scale. And at Zalando when I joined, it was a very different picture because that journey happened that I described at Volkswagen Financial Service has happened already the years before.
There was a very central data team, end to end, very large. And at some point it became the bottleneck. So what was done, those teams were put really into the business units. And from one day to the other, the whole pendulum swifted from the very centralized org to very decentralized org.
Where all business units would create dashboards would create a report, would create a model, like there would be no, basically it was like a party, like a data party or like a tech party. Everyone was building, started to build stuff. You can imagine that at first this created tremendous amount of value because you were very close to the business.
You knew what your people wanted and you built what they wanted. Now, that's great and you really increase the speed of value until you don't, because at some point it swings back because what happens is that you end up with a lot of teams building products every day, very decentrally finding some data here and there.
And putting it, in the data lake. Yeah, but still from here and there copied from here and there, they do something, they put it back into somebody else takes it, they create something new out of that. Another person takes it, they create something new out of that and becomes quite of a maze, and you create complexity.
You, you create complexity that. It's very costly, not only infrastructure wise, but very costly because you don't know what to use. There's a lot of tribal knowledge, but as you grow, and we were growing quite a lot during the last years, that tribal knowledge is, doesn't scale as well anymore. So you have to create a new system, another system of how we work with data.
And this is where I came in, and I was asked, can you find a balance between to create a little bit more structure towards how we work together with data and together with my colleague, we thought through how can we do that? And we worked for the first time in the history of Zalando on a data strategy and published it last year.
And that is a strategy was really more of a ways of working around data. That's very different to the data strategies I created. Volkswagen group or earlier on when I was working at Gartner and IBM as a strategy consultant, I was doing, a lot of these data studies, it was always about how much money is in there.
Where should we put our, dollars on or euros on? While at at Zalando, that was not the point. Everyone saw every day how much value there is in data because there were so many products built. The problem was if I wanted to change something, if you wanted to change the technology, you wanted to build something new, which required stuff from other people.
It was incredibly costly, difficult and you had to often you had to create quality controls at the point of consumption and not the point of creation. And this is where we made that change where we said, okay, the central data teams are not just providing infrastructure where people were all data's loaded into that infrastructure.
And we just use whatever makes sense for individual people. Now we said, let's build now out of that, a real data platform and a real operating model. Where everyone can build whatever they want in the same speed. So the decisions what to build are still close to the business, but how we build it and how we share, that would be something like a contract between each other.
So we brought the whole company together to discuss how can we do that best. And, and during that journey, that started two and a half years ago, we really found that data mesh and data as a product is a paradigm shift that actually helps in there because it can, we were already a lot of people that think of data mesh.
They are thinking of decentralization, they are thinking we want to put people everywhere and do data. We were at that point already. What we needed is more structure, more governance without centralizing everything again, because that would create massive bottlenecks that wouldn't work and you couldn't put the genie back into the bottle.
So that's why we came to data mesh, because we wanted to use the ways of working and the governance mechanism of data mesh. And that led us, a few years back, we, to become one of the first companies that started to experiment with these concepts and quite early on. And I think it was when also the Mark started writing about it and we actually worked, it was before my time, but we worked with ThoughtWorks back then as well, closely.
So it's quite intertwined.