Platform teams are the new integration competence center

For two decades, the centralized integration team was the toll bridge of enterprise IT: everything crossed it, everything queued for it, and everyone resented it slightly. The last few years of decentralization were supposed to abolish it. Instead, something more interesting is happening: the competence is coming back, but as a product rather than a gate.

The distinction is not cosmetic. A gate exists to stop things until they are approved; a product exists to help people succeed. The same integration expertise, pointed at those two different goals, produces organizations that feel nothing alike, and understanding why is the key to getting the reinvention right.

Why the old center of excellence failed

The centralized integration team of the 2000s was not staffed by bad engineers, nor was it a bad idea in principle. It failed because it was a queue, and a queue that everything must pass through becomes a bottleneck no matter how competent the people in it are. Every project in the enterprise eventually needed the integration team, and the integration team could only do so many things at once, so the whole organization's pace was capped by one team's throughput.

Worse, being the mandatory gate made the team the enemy of delivery rather than its partner. Product teams experienced integration as the place their work went to wait, and they learned to route around it wherever they could, which produced exactly the ungoverned sprawl the central team existed to prevent. The gate model contained the seeds of its own defeat: the more it slowed people down, the more they bypassed it, and the less it actually governed.

From gate to product

The platform team, in the sense the industry has converged on, does not build integrations for other teams. It builds the paved road on which other teams build their own: the gateway, the templates, the pipelines, the guardrails that make the secure path also the easy one. Product thinking is what distinguishes it from the old center of excellence, its users are customers who could, in principle, go around it, so it must be better than the workaround.

A platform team's success is measured in how rarely other teams need to think about integration, not in how many integrations it ships.

What the paved road carries

• Defaults, not documents: authentication, versioning, and observability arrive pre-wired in the template, so compliance is what happens when nobody does anything special.
• Self-service with guardrails: a team can publish an API without a meeting, and cannot publish one without an owner, a contract, and a policy.
• Visibility as a service: the platform sees the whole estate, so questions about it, for audits, incidents, or architecture, have one place to be answered.

The organizations doing this well report the same, slightly paradoxical outcome: more central platform, more team autonomy. The two were only ever in tension when the center was a queue. Make it a product, staff it like one, and the old toll bridge becomes something rarer in enterprise IT: infrastructure people choose on purpose.