A designer working alone inside a product team may have plenty of collaboration but little contact with other designers. A cross-team guild creates that second connection. People keep their ordinary delivery responsibilities while meeting peers to compare methods, share resources, and work on problems that recur across teams.
In Spotify's 2012 organizational design, guilds connected people across teams as voluntary communities of interest. This gave people a second network alongside the teams responsible for delivery.
A second network inside the organization
Designers in a public-service organization could use a guild to compare accessibility testing, develop reusable examples, and introduce new colleagues to experienced peers. A problem solved in one team would no longer need to be rediscovered in every other team.
Participation takes time that delivery managers may prefer to spend on immediate deadlines. A guild can therefore become an evening hobby unless the organization recognizes its work. Its authority also needs clarity: a discussion group proposing standards is different from a body empowered to require them.
The guild's advantage is connection without full reorganization. It helps a craft develop across project boundaries while leaving the teams responsible for their outcomes. That becomes harder if the guild quietly turns into another approval committee through which every team must pass.