Cycle Steering - Execute Phase

What to expect

The Execute Phase monitors engagement and OKR process compliance of all teams during the execution of the OKR cycle. Process compliance of the OKR practice is divided into the health of OKRs and activity of Check-ins. This is monitored by the frequency and distribution of OKR updates as well as regularly and properly performed Check-in meetings.

Why use it

Since the success of the OKR practice is highly dependent on the continuity of its execution it is very important to keep track of the OKR updates and the Check-ins performed. With this section of the report, you will understand which teams are actively working on their OKRs and which are not. Support the overall progress of the teams by helping them with OKR updates and Check-in preparation. This will increase the success of the OKR cycle.

When to use 

The success of the OKR practice is highly dependent on the continuity of its execution. Therefore, as a Program Lead or Coach, you may use this section of the report during the OKR cycle, when your teams are executing the defined OKRs. In order to be up-to-date with your organization’s OKR process, it is recommended to have a look at this section of the report once a week during the cycle. Maintain on average a value of 50% of the OKRs updated regularly to ensure continuous value creation in your organization.

This section can be filtered by cycle, team name, 3 hierarchy levels, labels and/or coaches. You can click on any metric to get a detailed view of the teams or OKRs that do not meet the displayed parameter. The color coding is based on the recommended value the organization should have based on best practices. When you hover over the number, you will see the legend for the color coding of each metric. Once a metric is in the orange or red range, a speech bubble will pop up with a recommendation.

The information button "i" explains in detail how each metric is being calculated:

Execution Score & underneath parameters:

All below metrics are considered in the calculation of Execution Score.

• OKRs updated regularly - From all the active OKRs, total OKRs getting regular updates. Regular update is defined as if an OKR is updated every two weeks, then OKR is considered to be regularly updated. Updates can be in the form of progress, confidence level, or qualitative comment.
• Teams weekly active: From the total teams with at least one member, the total teams active. Team active is defined as if 10% of their members are active on 60% of the days of the cycle.

Further Execution Details:

• OKRs updated at least once: From all the active OKRs, total OKRs updating at least once in the cycle duration.
• OKRs updated in last 1/2/2 Weeks: From all the active OKRs, total OKRs updated in last N (1/2/4) Weeks based on filter selection. (OKRs updates are considered from today if the cycle is current and for previous cycles, cycle end date is being considered).
• Users monthly engaged: From total users, the total number active in the last 30 days. User engaged is defined as if they perform key action in a given timeframe. Key actions can be “updates on progress”, “check in prepared”, “Edit on OKR content”, “Adding feedback”, and “Adding comment”.
• Users owning Initiatives: From the total users, total users owning initiatives. A user is an initiative owner if they own an initiative either in their team which they are part of or in any other team as a stakeholder.
• Users owning OKRs: From the total users, total users owning OKRs. A user is an OKR owner if they own a goal or key result either in their team which they are part of or in any other team as a stakeholder.
• Teams in conversations: From the total teams, the teams that have participated and added at least a talking point in the cycle. If it is greyed out, the conversations feature is not yet enabled. Please reach out to your CSMs to get early access.
• Teams regularly preparing check-ins: From total check-in enabled teams, total teams preparing check-ins. A Team is considered to be regularly preparing check-in if they are conducting check-in at least 60% times of their planned meetings. Teams with only check-in enabled are considered here.

Team Distribution:

This overview shows you a treemap with all teams from the first two hierarchy levels and the corresponding Execution Score. So you can see at a glance which teams need additional support (red or orange). You can also click on a specific team to see the teams below it and their Execution Score.