Enabling Team
A team whose output is other teams' increased capability, working alongside them temporarily and deliberately removing itself.
An enabling team exists to raise capability, not to deliver a service. It embeds with a stream-aligned team for a bounded period, helps them adopt a practice or a technology, and leaves. Its success measure is that the team no longer needs it.
The distinction from a platform team is sharp and often blurred. A platform team provides something consumed as a service, indefinitely, with a contract. An enabling team provides help, temporarily, and its interaction mode with any given team is supposed to end. Blending the two produces the worst of both: a group that is a permanent dependency for work it does not own, which is the classic shape of a central architecture or DevOps function that everyone must go through and nobody can plan around.
The failure mode is not leaving. An enabling engagement that becomes permanent has quietly turned into either an outsourced capability or a bottleneck, and either way the receiving team has not become more capable, which was the entire point.