Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
The hierarchy
On the OKR overview, you can see all of the OKRs in your company in a hierarchy, including KRs of each objective. Thanks to the flexibility of the structure, you can create a multiply nested hierarchy that will reflect the structure of your company’s OKRs, no matter the size.
add screenshot
How to create hierarchical OKRs?
It’s the easiest if you start from the top-level OKRs, but you can rebuild the structure later as well. Go through the example to get a picture of how can you use the hierarchy.
Example:
The company E. has 3 top-level OKRs. The company E. consists of the Tech department, operations department, and business department that have their own goals proposed by the managers. Each of them consists of 2-4 teams that have their goals proposed by team members and team leaders. People in the business department decided to have personal goals as well, while members of tech and operations were skeptical and decided not to introduce them. You can probably already see the structure of OKRs in company E. in your head. So how could you create such a structure in OKRs for Jira?
Create the top-level OKRs. Create KRs for them if there are metrics that are not dependent on the lower goals.
add screenshot
Open each objective’s page. Click on the “Add child objective” button on the top right side of the screen. Create child objectives and add KRs for this level. Repeat the process level by level until you get the hierarchy you need.
add screenshots
| Info |
|---|
If you wish to change the parent objective later, you can do it in each objective’s info area. |
| Info |
|---|
If you want to add an objective later on that fits in the created structure, choose the appropriate parent objective, when creating the new one. It will be nested in the right place. |
Filtering the view
You can filter the OKR overview to look only at specific OKRs. You can search for:
your team’s top-level OKR to see all OKRs in your team
objectives that have a percent of completion less/more than a certain % to identify what’s going well and where are you behind
objectives of a certain status
objectives of a certain owner
and more.
add screenshot
Using the OKR overview in everyday work with OKRs
Meetings
You can clearly see all dependencies between the OKRs on each level, the progress on each objective, as well as which KR is not being worked on. That makes it a perfect view to display or share on a bigger screen during the OKR review meetings on each level and on planning sessions of the individual teams.Planning the work
Start planning your team’s work by looking at the OKRs overview. It will help you choose the right things to do first.
Related articles
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|