Goal Scope

For what concepts do we create OKRs?
Written by Borut Bolčina
Updated 1 year ago

Organizations are becoming team-oriented and focusing less on each individual. The rationale for how OKRs are created on the Agile Tools platform is based on this observation. This tool can fulfill your needs if you are already in such an organization or want to transition to it.

OKRs for cross-functional teams

In Agile Tools, the Team is a first-class citizen. It is not to be used interchangeably with a group of people working in the same department.

We encourage you to create teams with members of different professions, but you can create teams in a more traditional manner.

Creating goals for long-lasting cross-functional teams can greatly boost the OKR promise of delivering more business value.

OKRs for Value Units (products, services, projects, etc.)

Agile Tools is unique on the market, allowing you to create goals for products and similar concepts. Scrum, one of the Agile practices, is going to great lengths to elevate the need for setting goals for the products we build and services we offer.

OKRs for Organizational Units (company, department, division, branch, plant, etc.)

Creating OKRs for the organization itself and its business units is by far the most common and known method. It can also backfire if alignment and accountability are not done correctly.

You can create your own Value and Organizational Unit types.
Did this answer your question?