Skip to main content

Understand Progress Calculation in Lattice

Anna Goryachikova
  • Updated
Understand how OKRs work, how overall %s are calculated with cascading goals, and how to adjust for unequally weighted key results

In Lattice, users can create goals following the OKR format. When creating an OKR:

  • Objectives are considered qualitative goals and will inherit the progress of their quantitative child/supporting goals 
  • Key results are considered quantitative goals and will roll up progress to their objectives.
  • Binary key results are considered quantitative will inherit the progress of their child/supporting goals

Weighing key results equally

In Lattice, each key result is equally weighted. For example, if there are 3 key results, each one will be worth 33% of the total objective.

As shown below, if we create our objective, the 3 different key results roll up to this goal.

  1. Dollar KR 1 with an end goal of $300
  2. Dollar KR 2 with an end goal of $500
  3. Dollar KR 3 with an end goal of $1000

Let's say we update "Dollar KR 1" to be fully achieved. Below, we can see that Dollar KR 2 and Dollar KR 3 are still at 0% completed, and Dollar KR 1 is 100% completed. 

The overall objective is now 33% complete since each Key Result is worth 1/3rd of the total.

Screen_Shot_2022-02-02_at_11.35.13_AM.png

Weighing key results unequally

Sometimes there may be key results or child objectives that should not be weighted equally causing the % calculated for the overall objective may look strange. This can be solved by setting the objective to something other than binary and manually updating it. 

In the example above, we may not want to view the goal as 33.33% complete since the key results should not have equal weight in the overall objective.

To set this up, set custom weighted goals.

Step 1: Select Goals on the discovery navigation.

Step 2: Find and click on the goal you would like to edit to open the context panel.

Step 3: Select Edit weights.

Step 4: The exact editing weights modal shown above will appear. Here, you can make your edits and Save.

Learn more about custom weighting in How to Set Custom Weighted Goals.

Screen_Shot_2022-02-02_at_11.46.15_AM.png

In this example, we have set the Dollar KR1 key result weight to be 0%, while keeping Dollar KR2 and Dollar KR3 at 50% each. When we update our Dollar KR 1 to be 100, the overall objective doesn't progress. This is because the key result is weighted at 0%. 

Screen_Shot_2022-02-02_at_11.48.37_AM.png

Cascading goals

Cascading goals, if enabled, allows users to align child objectives to parent objectives. In these cases, the progress will work as follows:

Example 1: Objective 1 > Objective 2 > Key result 1

Screen_Shot_2022-02-03_at_2.33.29_PM.png

  • Key results automatically add progress to objectives.
  • Key result 1 (Eng KR 1) will flow into Objective 2 (Dept Eng Obj).
  • Objective 2 (Dept Eng Obj) will flow into Objective 1 (Company Obj 1).

Example 2: Objective 1 > Objective 2 > Key result 1 > Key result 2

Screen_Shot_2022-02-03_at_2.37.01_PM.png

  • The parent key result needs to be set to binary to accept the flow of the child key result, therefore, Key result 1 (Eng KR1) will need to be set to binary.
  • Key result 2 (Eng Sub KR)will flow to Key result 1 (Eng KR1) if Key result 1 is binary. 
  • Key results automatically add progress to objectives.
  • Key result 1 (Eng KR1) will flow into Objective 2 (Dept Eng Obj).
  • Objective 2 (Dept Eng Obj) will flow into Objective 1 (Company Obj 1).

Related articles