Contrary to the Teams nomenclature, Figma Teams can actually be a great way to separate out your individual disciplines within your organization.

For example, you might have a structure split into Web, iOS, and Android, all guided by an overarching design system. This is a perfect way to split up your teams into, well…Teams.

By allowing your different disciplines to work independently within their own Figma space, you can operate as transparently as you need. Perhaps the iOS team require the creation of a secret team while the next version of the product is being released? This can be managed independently from the rest of your Figma teams.

This can also be useful for larger teams that encompass separate, more complex projects. We at Figma, for example, have separate teams for each part of our product. This encourages a workflow where our central design system is consumed by disparate product teams that share the central Figma ecosystem.

Or, maybe your Android app requires a more custom approach to design libraries. You can consume your main design system within your Team and add a layer on top for custom or extra functionality, effectively creating a localized team-specific library that references your main design system files.

We've seen teams of all sizes utilizing the benefits of isolated team structures within Figma, and the separation of concerns is something that can immediately ease the “who’s working on what?” question from a management perspective, with the Team settings member list.