This article is designed to help you understand how to structure and/or define the teams and divisions within your organization in Kindor. We will explain clearly and concisely how each grouping works so that you can make the most of all the features the platform offers.
Kindor allows clients to define two types of groupings:
Vertical Groupings: These could be squads, tribes, or any other vertical organization oriented towards a product or business objective that includes collaborators with different roles.
Horizontal Groupings: These could be functional areas or chapters such as security, data, frontend engineering, etc. This type of grouping generally includes collaborators with the same role but different seniority levels, for example, Jr. & Sr. Backend Engineers.
During the onboarding process to Kindor or when adding a new collaborator, it is important to provide information about the groupings to which the collaborators belong.
Usage of Groupings or Teams in Kindor
Kindor allows the user to see metrics, insights, or relevant information at both individual and team levels.
By default, when a new organization is onboarded to KINDOR, at least one grouping called “All” is created, which includes all the collaborators being monitored in the organization.
It is important to note that in multiple dashboards, KPIs are displayed as Weekly Average per Team Member, meaning that the total activity is divided by the number of collaborators. For example, if a grouping has 20 collaborators and 100 commits were created in one week, the metric would show 5 commits per team member. This is important to mention because, in the “All” grouping, all monitored collaborators are considered, which can include roles like Product Managers or QAs who might not perform code release activities, thereby affecting the weekly activity metric per team member. This is where the relevance of other defined groupings comes into play.
Vertical Groupings or Teams
Vertical groupings are known as “Teams” in Kindor and generally align with a product or business objective. For example, Acquisition Team or Platform Team.
In Kindor, this type of grouping is only used to consolidate information from multiple collaborators in one space or dashboard.
A collaborator may not belong to any vertical grouping (e.g., a CTO) or to one or more vertical groupings, as Kindor supports a person belonging to more than one vertical team.
Comparisons or Benchmarks in Vertical Teams
Currently, Kindor does not support comparisons or calculations like averages or medians between members of the same vertical team. This is because it is understood that a vertical team can have collaborators with very different roles, and it would not make sense to compare a Software Engineer with a Product Manager, for example.
Horizontal or Functional Groupings (Divisions)
Horizontal or functional groupings are known as “Divisions” in Kindor.
Divisions typically group collaborators who perform the same type of tasks or have the same function. For example, Frontend, Backend, Product, Data, DevOps divisions, etc.
This type of grouping is not always fully defined in organizations, but in Kindor, they play a very important role and it is highly recommended to define them.
Comparisons or Benchmarks in Divisions
Kindor provides multiple metrics and indicators focused on measuring the activity of individuals and teams and how they compare to other collaborators with the same function.
Kindor currently calculates averages and medians of activity at the organization, division, and role levels. Therefore, it is extremely important to correctly define the division to which a collaborator belongs, allowing you to properly evaluate the activity of individuals according to their function.
For the product to function correctly and deliver better results, it is important that each collaborator belongs to a division. Currently, the product does not support a collaborator belonging to two or more divisions.
For collaborators with executive or management roles, it is recommended to define a management division, as their function is generally very different from that of an individual contributor.
Re-organizations, Team Changes, and Adding or Removing Members
In Kindor, it is possible to make changes to both the divisions or teams to which each collaborator belongs, as well as create new groupings or delete existing ones. It is important to consider the following:
• It is important to notify the Kindor team as soon as possible about any changes.
• Movements of a collaborator to a different team (vertical grouping) will be reflected immediately after notifying Kindor.
• Movements of a collaborator to a different division, although they will be reflected immediately in the structure, will not immediately affect the calculated metrics of that division.
• If a new team or division is created, the metrics for that team will start reflecting from the moment it is notified to Kindor. There will be no historical data for that team, as it is assumed that the team is entirely new.
Conclusions:
To make the most of KINDOR, it is highly recommended to specify to which team (vertical grouping) and division (horizontal or functional grouping) each collaborator belongs.
• A collaborator may or may not belong to one or more teams, and it is highly recommended that they belong to a division. They cannot belong to more than one division.
• Changes to team organizations can be made after the initial setup.
Comments