Teams and team types
Teams model delivery structure and are the main unit used in charts, matrix, and scenario modeling.
Team types classify how teams operate (for example, stream-aligned, platform, enabling).
Team fields in the app
Team create/edit supports:
- name
- parent org unit
- type (optional)
- purpose (optional)
- valid from / valid to dates
You can create team types inline from the team form using search-or-create behavior.
Team types and why they matter
Team types help with:
- matrix column grouping
- filtering and comparison
- communicating operating model patterns
Manage them centrally in:
/settings/team-types
Parent placement and hierarchy
A team belongs in the org tree via its org unit node.
The parent selector enforces valid parent types and scenario context, which prevents accidental cross-context structure bleed.
Team membership is handled by placements
Team pages surface roster and placements with:
- primary/secondary flags
- allocation %
- effective dates
Membership is driven by placements, not by simple team foreign keys.
Team context in scenarios
When you create/edit teams inside a scenario, those rows are scenario-scoped.
That allows you to test reorganizations without touching live baseline.
Practical workflow
- Create team with clear name and parent.
- Assign team type and purpose.
- Add or adjust placements for key contributors.
- Review team in matrix/charts for structure and load balance.
- Validate deltas before promotion.
Common mistakes
- creating teams without meaningful parent placement
- leaving type taxonomy inconsistent across teams
- expecting position creation alone to place actors onto teams