Today’s digital products require cross-functional teams that include product managers, designers, and developers combining their unique strengths to achieve common objectives. As organizations grow, so does the complexity involved in keeping track of who’s working on what, and which objectives you have the capacity to tackle.
In this article:
How teams work
In Productboard you can now clarify which teams are working toward which objectives to provide alignment and accountability.
But that’s not all teams are for.
Teams also make it easy to share a saved view (on the Features board) or a roadmap with just those on a specific team. It means you could easily share a tentative roadmap with the leadership team without inviting the individual members one at a time.
And by @mentioning a team by name (e.g. @sales, @prodmktg, @design) you can notify all its members about a discussion taking place on a note, feature, release, objective, or any other entity that supports comments.
As you can see, teams can be defined around functional areas (marketing, design, leadership) in addition to being conceived as cross-functional product teams, Scrum teams, or squads. Since the same workspace member can belong to multiple teams, you’re free to use both types of teams for different purposes. We’ll discuss how that works below.
In workspace settings, under Teams, makers can group members of a Productboard workspace together:
- Click + Create team and give it a name, description, avatar, and specify what handle can be used in a comment to notify all members of that team.
- Search workspace members to add them to the team.
Assigning a member to a team
You can assign a member to a team from the team’s settings (above), from the member’s account info page, or when first inviting a new member into the workspace.
Keep in mind the same member can be added to multiple teams. So a designer could belong to one or more product teams as well as a design functional team.
Note: If you have SAML SSO configured, you’ll still need to assign members to teams from within the application.
Assigning objectives to teams
Objectives are often assigned to cross-functional product teams. For example, you might be working toward driving the adoption of your product by a certain user segment.
Other objectives may be assigned to functional teams, such as an objective related to miscellaneous usability improvements being assigned to the design team.
You can also check out a full discussion on the importance of objectives in effective product management. But the gist is we want to identify product objectives representing valuable outcomes for our users or important goals for our business (or both!). And we’ll use those objectives to guide our prioritization process and organize our roadmap.
For product leaders, associating teams with objectives helps keep track of who’s working on what and plan what objectives you have the capacity to tackle over various time horizons.
And for the teams who will be working toward these objectives, this system provides clarity and accountability — the good, empowering kind that comes when teammates feel ownership over a problem and are equipped to hurl their curiosity, creativity, and intellect into finding the optimal way to solve it. (This is also why an objective can only be assigned to one team!)
Assigning an objective to a team:
- On the Features board, open the objectives side pane and select an objective.
- From an objective’s details, assign it to a team.
Once assigned to an objective, the team’s avatar will then appear beside it in the objectives list among other places in the application.
When visualizing your Roadmap by objective, you will have the option of displaying each team’s avatar beside their objectives.
You can also filter the Features board and Roadmap by one or more teams to see just those features that belong to their objectives.