Videos
World Economic Forum's Bart Talloen on What It Takes to Scale Digital Transformation
Recorded at the World Economic Forum’s Advanced Manufacturing and Supply Chains Forum 2026, this video was produced in collaboration with the World Economic Forum’s Lighthouse Operating System Academy.
Insights
- J&J built its digital playbook by benchmarking outside healthcare, with "go and see" visits to electronics, automotive, and aviation plants that were years ahead.
- To break out of "pilot purgatory," the team ran test-and-learn: it deployed solutions early and accepted a 30 percent failure rate so the winners could reach full scale.
- Scaling across a decentralized company took an operating model J&J calls "dependency by design," in which central teams set the standards and the businesses funded and deployed them.
Years into Industry 4.0, why do most companies still struggle to transform? Bart Talloen, an Executive Fellow at the World Economic Forum, spent thirty years running manufacturing and supply chain at Johnson & Johnson, and he traces the struggle to the same four fronts: people, process, technology, and strategy. His starting rule is that business and customer needs decide where technology goes, which keeps the effort business-driven from day one. He also argues for over-indexing on workforce training, which J&J did by building digital modules into an existing supply chain academy. The payoff of getting these right showed up in results, such as a collaboration with Intel that put real-time process monitoring into pharma and cut inventory and cycle times by 30 percent. Talloen's throughline is that culture and mindset decided whether the transformation held, as much as any technology.
Bart Talloen:
Every operating system in the past was a single company operating system. It started with the Toyota production system. A lot of companies copy-pasted it. We wanted to really use the opportunity of the Lighthouse network and let a number of interested top leading Lighthouse companies co-create this new operating model. That we make something that is really the best of the best.
Jeff Kavanagh:
I'm Jeff Kavanaugh with the Infosys Knowledge Institute here at the World Economic Forum's Advanced Manufacturing Supply Chain Forum in San Francisco, and I'm here today with Bart. Bart, you're with the Economic Forum as an executive fellow, correct?
Bart Talloen:
Yes, since I retired from Johnson & Johnson and in October '23, I'm an executive fellow with the World Economic Forum, and before that, I was a senior executive in manufacturing and supply chain with Johnson & Johnson.
Jeff Kavanagh:
The transition to the Lighthouse operating system. How did that emerge, and how has that been valuable as well?
Bart Talloen:
In late '23, I think it was, so kind of every year we did a strategic reflection of the Lighthouse program. We've gotten a lot of questions. So by that time, the network was 150, I think, probably plants.
Jeff Kavanagh:
It's more how the operating system came into being.
Bart Talloen:
Yeah, and then we got these reflections from ourselves also, but from also other companies to say, "What makes this community unique? What are they doing different versus others?" Because a lot were still struggling. This was a unique opportunity to build an operating model that was unique. And so we also reflected on previous operating models and what could be better. So one was every operating system in the past was a single company operating system, It started with the Toyota production system. A lot of companies copy-pasted it. But at the end, all the big companies, J&J itself, we had our Johnson & Johnson operating system. You have the Unilever operating system. You have the Danaher system, right? These are some of the famous systems that are used as references. Procter & Gamble, the same. So here, we wanted to really use the opportunity of the Lighthouse network and let a number of interested top leading Lighthouse companies co-create this new operating model. That we make something that is really the best of the best. So that was a first differentiator that we wanted to have. The second thing was it need to be capability-based because at the end, capabilities you can build and change, and that will drive outcome. So that was a second design principle. The third design principle was where in the past, operating systems were a lot focused on process and people, we said in current day and age, '23, it needed to be an operating system that, yes, has people and process, but also technology and data. So it needs to be a holistic operating system that has these four performance levers. And last, it needs to be an operating system, a system that really works together as almost an organic living organism, right? So you have the six capability areas, and each in themselves have their role, a bit like the body, right? The brain thinks, the legs move. The same. Every one of these six elements has a role in the operating system. But the critical thing is how all these six work together and their underlying capabilities. In total, we have six principles. In total, we have about 70 capabilities, underlying capabilities. All of this works together to make the whole system better.
Jeff Kavanagh:
And maybe you can focus on this last maybe nine months or so, where it's kind of coalesced into something more formal and has transitioned to Lumina.
Bart Talloen:
We launched the first version in January '25, of LOS, in a white paper, aligned with the Davos meeting in January '25. There's three modes of implementation. That was another differentiator versus the past. In the past it was, "This is the operating system." You take it, and you need to do everything. Here, we have a menu, and you can select. So in some cases, companies have their operating system, but they have a specific need in a certain capability area, so they want to, I call it the toolbox mode. They want to deep dive in one of the six principles and really adopt best practices in those principle area. Other companies are at the point of a refresh of their current operating system. So that's the upgrade mode. We want to upgrade what we have. The Nestlé example is a good example of that. They wanted to pivot to more end-to-end focus versus functional. And then the third mode is full implementation. So companies that don't have anything can, of course, look at this and adopt it and fit it to their needs. We developed those three approaches, and we did some pilots with companies to refine the approach there. The third element that we worked on in '25 was how can we connect the Lighthouse Operating System with the Global Lighthouse Network? And there came the thinking of each one of the implementation modes starts with a diagnostic in the area that you want to address. Is it a certain principle? Is it a capability? Is it a part of the model, or is it the whole model? And we said it would be great if once you do your diagnostic, you identify or do some maturity assessment so you know, in the capabilities that you want to improve, where you are now, what maturity level you're at, where you want to be and what's your current and future state. And that you then can go somewhere to help you find solutions, how to go from here to there. That's also things that in previous operating systems didn't exist. It was more a guidebook, but how then to make the bridge and implement the actions, that was not articulated. So we wanted to combine this also in one approach. And also from the GLN perspective, we said we have now so many lighthouses, and we wanted to trigger that cross-functional learning. There was a need for how do we share these use cases and best practices in a digital way versus now it was more, like I was saying, peer-to-peer benchmarking. So these two things came together. And Lumina was created in late '25, a digital platform where basically all the use cases and all the GLN information resided. And in the meantime, the platform has expanded to also include the LOS aspect. So it has the assessments, the three types of assessments that I was talking about. In Lumina, there is also that assessment and the maturity evaluation, and then based on the maturity and the gaps, you are guided to specific use cases that can help you to close that gap. For example, I need predictive maintenance. You are guided to use cases from companies, global lighthouses, that were practical examples how other companies have implemented predictive maintenance. I feel really good about the whole LOS journey because, to me, it really ticked the boxes that we set out as the aspiration. As I explained at the beginning. It is a unique framework. It consolidates the best of the best. It is practical. It has optionality, so you can select a mode of implementation. So it gives you a lot of optionality and freedom, and you can fit the approach and use parts of the model or the full model depending on your needs. So it's very customizable while respecting the standardization and the consistency that is embedded in the model.
Jeff Kavanagh:
And you've seen the full arc, both as an executive at your previous company, J&J, as well as a senior fellow with the…
Bart Talloen:
Exactly. That's the other piece. I've been on both sides of the, I wouldn't say of the fence, of the table or the collaboration table. So yes, it also helps me now, the last couple of years, being with the World Economic Forum as an executive fellow, based on my industry experience, to take that experience into what we design and build so that we make it even better for the businesses. Because at the end, these are the customers.
Jeff Kavanagh:
Really appreciate it, Bart. Thanks for your time.
Bart Talloen:
You're welcome Jeff.
