Best Practice: Creating and Managing Teams
  • 01 Mar 2023
  • 1 Minute to read
  • Contributors

Best Practice: Creating and Managing Teams

Article Summary

Managing teams

Once your teammates have been invited to the workspace, you can organize them into teams. Teams can be assigned to plans, and they'll get their own team page that can hold their mission, vision, values and any updates they share.

Find the instructions for creating teams here!

After the team is created, you'll be brought to the team's page. From here, you can add the team's mission, vision, and values, add a team description, and even create new plans for that team.

Team members will also be able to create team updates that they can publish for the whole workspace to see. This is an incredible way to increase visibility and collaboration around your strategy!

Now that the team is created, you can also assign the team to an existing plan by opening up the plan, and selecting the '+Assign to team'. From there, you can assign that existing plan to any team in the workspace.

Best practices for teams!

The best way to organize your teams is to create one team per plan. This can depend on how you organize your plans - we recommend having about eight collaborators per plan, which would then translate to having about eight team members per team!

A team can also own multiple plans, if they are owning multiple workstreams.

If necessary, one person can be in multiple teams. If someone is collaborating or contributing on work in multiple plans, they can be a part of the team owning that plan as well. This will allow everyone working on this plan to publish team updates connected to that work!

So to summarize:

  • Each plan in your workspace should be linked to a team.
  • A team should include around eight team members - that's our recommended number of collaborators per team!
  • Anyone collaborating or working on the goals in a plan should be in the associated team, so that they can create and share team updates to promote collaboration and visibility across the organization!

Was this article helpful?