I Called It a Platform Company in 2006

Twenty years ago, a European branding consultant walked into our offices. He had been commissioned to assess whether the company, then in a phase of rapid expansion, should reposition itself. Over several weeks, he met every business unit head. When he finally delivered his report, leadership rejected it. Their stated reason: he had been too influenced by one person's vision. That person was me.

His recommendation had been to reposition the company as a platform. Not a portfolio of services. A platform. A unified, integrated offering where the combined capability would be meaningfully greater than the sum of each part. The consultant had seen something in his conversations with me, and had built a thesis around it.

The report went in a drawer. The company continued on its path as a multi-unit operator. And the subject was closed.

That was not a comfortable moment. But it taught me something I have carried since. When you see a configuration that others do not see, it does not mean you are right. It means the work of making it visible, and credible, is yours to do.

Twenty years later, the platform model is the dominant organizing principle of global enterprise. Technology companies, healthcare groups, logistics operators, financial services firms. The ones that have created disproportionate value are almost always the ones that figured out integration before their competitors did. Not because integration was obvious. Because someone in each of those organizations insisted on asking what the parts could do together, not just what each part could do alone.

I have spent my career asking that question.

It is not a methodology. It is closer to a reflex. When I look at an organization, I do not see departments. I see a set of capabilities, each with its own human capital, each with constraints and outputs. And then I look for the problem in the market that none of those units can solve alone, but that all of them together might.

The human element matters here more than most people acknowledge. You can connect systems. You can build integration layers. But the actual variable that determines whether a platform delivers value is whether the people inside each unit understand what the other units do, and choose to collaborate rather than compete. That is a leadership and culture problem, not a technical one. Technology enables the platform. People determine whether it works.

This is what the consultant had understood. He had sat in the room with me, heard how I was thinking about each unit in relation to the others, and concluded that the whole could be repositioned around that logic. He was not wrong about the idea. He was premature about the organization's readiness for it. Those are different problems, and conflating them is a mistake I have tried not to repeat.

Readiness matters. The best platform strategy delivered to an organization that is not ready to operate as one creates friction, internal politics, and failed integration projects. The work before the work is always organizational. Do the units trust each other enough to share customers, share data, share margin? If the answer is no, the platform is a slide deck, not a business.

What I have learned to do, in the years since that consultant filed his report, is build readiness. Sometimes that takes the form of a shared technology infrastructure that creates dependency before creating value. Sometimes it is a go-to-market motion that requires units to coordinate because the customer demands it. Sometimes it is simply sitting in a room with two business unit heads who have never had a real conversation about what the other one does, and asking the question: what problem could you solve together that you cannot solve separately?

That last one is underrated. The clearest thinking I have done in my career has happened in rooms where people from different functions were genuinely forced to think together. Not in workshops. Not in strategy off-sites with facilitators and sticky notes. In working sessions with a specific problem on the table and real accountability attached to the outcome.

The consultant's report was ahead of its time. That is a polite way of saying it arrived before the organization was capable of acting on it. I do not hold that against the leadership that rejected it. They were running a growing business with real operational demands. The idea required a level of integration that would have been genuinely difficult to execute at that stage.

But the idea was right. And the question it planted, how do you make the whole worth more than the parts, has shaped almost every major decision I have made since.

The executives I find most useful to think with are the ones who ask that question instinctively. Not what does this unit do. What does this unit enable, when it is connected to the right other things. That shift in framing changes everything: which investments you make, which hires matter most, which integrations you prioritize, which customers you should be selling to.

Platform thinking is not a trend. It is a structural reality. The organizations that have not internalized it yet are not behind because they lacked information. They are behind because they lacked someone willing to hold the question long enough to build an answer.

Sometimes that takes two decades.