Adding OKRs in Tability when you have multiple teams
This guide will show you the best way to structure your plans in Tability if you have multiple teams with different sets of OKRs.
📌 Watch the video
📌 The model
Here we'll use a fictitious company called Acme Inc that is organized as such:
They signed up for Tability, and they now need to add OKRs for each team.
📌 Naming convention
In order to keep track of each quarter separately, it is recommended to prefix each plan name with the corresponding quarter.
For instance, if we're in 2022 Q1, then each plan will be named 2022 Q1 <team> OKRs.
📌 How to organize your workspace
Step 1. Create a top-level plan for the Leadership team
First, they create a plan in Tability for the leadership team that they name 2022 Q1 Acme OKRs. They name it after the company since it is the top-level plan.
Step 2. Create sub-plans for the other teams.
Now that the top-level plan is live, they can create sub-plans underneath for the other teams.
- 2022 Q1 Product OKRs for the Product team
- 2022 Q1 Marketing OKRs for the Marketing team
- 2022 Q1 Support OKRs for the Support team
They end up with a workspace structure looking like the picture below.
📌 Benefits of that approach
Scan OKRs with the Strategy Map
Once the plans are created, users can simply open the Strategy Map to compare the different OKRs and keep track of progress across the org.
No extra configuration is required, this map will automatically show you active plans in your workspace.
OKRs grouped by quarter
By prefixing the plan names with the quarter, you can keep your workspace organized when the next quarter comes. Create a new top-level plan for the leadership goals named 2022 Q2 OKRs and then add all the sub-plans underneath.
📌 Need help?
Our team will be happy to get on a call with you and show you how to best set things up for your org.
Just schedule an onboarding call with us!