At Swimm, our teams work in squads. This is our workflow using squads in Swimm to keep ourselves organized. 1. After our users hear about Swimm from our Hooks Squad (marketing team), new users typically start playing around and using Swimm. 2. Swimm’s Engagement Squad (engineering team) assists these new users, especially during the first few days. They are responsible for giving Swimm’s first day value to the clients. 3. As an engineering manager, I head a group that’s called ‘The Adoption Squad.’ It’s the team in charge of helping our users adopt Swimm into their daily development routine and culture.  Swimm’s Adoption Squad is an 8-person team made up of one product manager, a UX/UI designer, and developers. 1. After our users hear about Swimm from our Hooks Squad (marketing team), new users typically start playing around and using Swimm. 2. Swimm’s Engagement Squad (engineering team) assists these new users, especially during the first few days. They are responsible for giving Swimm’s first day value to the clients. 3. As an engineering manager, I head a group that’s called ‘The Adoption Squad.’ It’s the team in charge of helping our users adopt Swimm into their daily development routine and culture.  Swimm’s Adoption Squad is an 8-person team made up of one product manager, a UX/UI designer, and developers. The adoption squad Once a company brings Swimm into their organization - that’s where we come in. We’re an 8-person team, including myself, a product manager, a UX/UI designer, and 6 developers. From assisting with CI integrations, through building features to make content consumption from the IDE easier and all the way to developing tools for team collaboration, we’re in charge of everything that has to do with ongoing usage and expansion.