OKRs & Operating Cadence

What we hit / missed? Add the items we have committed to during this quarter and vote on whether we hit or missed them by reacting with an icon: 🔴 for a miss and 🟢 for a hit.

[Hit = 🟢] [Miss = 🔴]

What decisions did we make that didn’t work out? 🧐 Anything we should revisit regarding how it was made, the criteria behind it, or the overall process? 🔄 (Skip if nothing comes to mind! ⏭️

What patterns, habits, rituals, or actions from this quarter should we keep 🟢 ?

What patterns, habits, rituals, or actions from this quarter should we kill 🔴? Why did certain ones fail, and what exactly didn't work? 🧐

Market, customer, team, product update, etc.

Draft a concise paragraph summarizing the key takeaways from our quarterly goals retro. Please highlight the top four-five points worth sharing, ensuring a balanced view that covers both our major wins and any delays or blockers we encountered.

Review Company Objective 1 and its associated Key Results (KRs).

As a department, identify 3–5 major initiatives, or "Big Rocks," that will directly impact these KRs. These are your critical commitments.

For each initiative, consider its potential impact, required resources, and a clear driver (owner). Ensure each "Big Rock" is actionable and measurable. Add each initiative here, clearly stating the initiative and the assigned driver. Example: "Launch V2 Beta Program - Sarah J."

Now, focus on Company Objective 2 and its Key Results.

Collaborate within your department to select 3–5 key initiatives that will significantly move the needle for this objective. These are your "Big Rocks" for Objective 2. Think about how these initiatives align with your team's strengths and how they contribute to the overall company strategy. Every initiative needs a committed owner. Enter each initiative with its designated driver (owner). Example: "Implement new CRM integration - Mark T."

Move your focus to Company Objective 3 and its Key Results.

Identify another set of 3–5 "Big Rocks"—major initiatives that your department will commit to, ensuring they are directly linked to achieving the KRs for this objective. Prioritize initiatives that are both impactful and feasible within the current quarter. Assign a clear driver for each commitment. Add each initiative and its assigned driver. Example: "Develop Q3 content calendar - Emily R."

Create a 1–2 page document outlining the company objectives and quarterly "rocks" or commitments, including 1–5 major initiatives per department with assigned owners.

Make sure to cover:

An Objective is a high-level statement of what you want to achieve. It should be aspirational, qualitative, and time-bound.

What needs to be true for a good Objective:

How to Write Key Results (The "How")

Key Results (KRs) are the benchmarks that track your progress toward the Objective. They are the "yardstick."

What needs to be true for a good KR:

Example of a KRs for a "Product Excellence" Objective: KR 1: Increase Day-30 user retention from 15% to 25%. 📈

Quarterly Commitments (The "What")

While OKRs are the outcome, Commitments are the specific activities or projects you promise to finish this quarter to move the needle on your KRs. These are the "train rails" we discussed earlier. [ Commitment 1: [Enter your goal here]]

How to list them:

Ex. Project Alpha: Redesign the signup flow landing page. [Owner: Sarah]

When you present this to your team, use this hierarchy:

Pro-Tip: Remember, setting the goal is the easy part. The "real work" is ensuring your budget, leadership, and processes actually allow the team to hit these numbers!

Two primary reasons OKRs fail are when resources and company reality do not support the objectives. When processes, leadership support, and budgets are misaligned, goals are set but teams never discuss the systematic changes needed to achieve them. 🛠️

The "real work" of OKRs isn't setting the goal—that’s the easy part. The challenge lies in deeply understanding our current reality, our strengths, and our procedural weaknesses to build a supportive system. 🏗️

The second biggest mistake is failing to translate high-level goals to the individual level. Without a day-to-day system, teams end up "spinning their wheels," spending more time coordinating and chasing other departments than actually doing the work. This causes a total loss of clarity on priorities and success metrics. 🌪️

It is non-negotiable for leaders to turn company objectives into individual responsibilities. Every team member should know:

"This is my role, and this is exactly how my effort moves us from [Point A] to [Point B]." 🚀

An Objective is a high-level statement of what you want to achieve. It should be aspirational, qualitative, and time-bound.

What needs to be true for a good Objective:

How to Write Key Results (The "How")

Key Results (KRs) are the benchmarks that track your progress toward the Objective. They are the "yardstick."

What needs to be true for a good KR:

Example of a KRs for a "Product Excellence" Objective: KR 1: Increase Day-30 user retention from 15% to 25%. 📈

Quarterly Commitments (The "What")

While OKRs are the outcome, Commitments are the specific activities or projects you promise to finish this quarter to move the needle on your KRs. These are the "train rails" we discussed earlier. [ Commitment 1: [Enter your goal here]]

How to list them:

Ex. Project Alpha: Redesign the signup flow landing page. [Owner: Sarah]

When you present this to your team, use this hierarchy:

Pro-Tip: Remember, setting the goal is the easy part. The "real work" is ensuring your budget, leadership, and processes actually allow the team to hit these numbers!

Define 2 to 4 top objectives and 1 to 2 key results per objective to act as a "GPS" measuring the team's progress.

For each objective, identify a 30-day commitment and a 60-day commitment to serve as focused "rocks."

The "real work" of OKRs isn't setting the goal—that’s the easy part. The challenge lies in deeply understanding our current reality, our strengths, and our procedural weaknesses to build a supportive system. 🏗️

Trade-offs. What are we not doing this quarter? Make this list explicitly. Write it down. The list of what you're not doing is more important than the list of what you are.

How does this get to teams in the next two weeks. Who tells whom. What artifacts go to the all-hands.

It is non-negotiable for leaders to turn company objectives into individual responsibilities. Every team member should know:

"This is my role, and this is exactly how my effort moves us from [Point A] to [Point B]." 🚀

The pre-read rule: Nothing is decided without a pre-read. This is non-negotiable in both models, but it's especially important here because the decision surface is smaller. The pre-read format is simple: here is the decision we need to make, here is the context, here is what we recommend, here is what we need from the group. One page (or use video)

⏲Circulated 24 hours in advance (or sooner)

If the pre-read doesn't arrive on time, the item is pulled from the agenda.

That rule - pull the item if the pre-read is late - will feel aggressive the first time you enforce it. It will be respected by week four.

It teaches the organization that the meeting's time is not available for underprepared thinking.👈

Decisions (40 minutes) - items that need a decision this week, with the decision owner identified before the meeting. Pre-read circulated 24 hours in advance.

The meeting makes the decision - it does not "discuss it further."

What is one team blocked on that another team can unblock. Specific. Named.

One metric or qualitative read from each leader. Not status. Signal. "What changed in your part of the world this week that the rest of us should know."

Create a one-page document detailing the decisions made, the blockers that were resolved (and how), and the key signals mentioned. Include a one-paragraph summary explaining potential consequences and specific items to keep an eye on in the upcoming weeks.

A single document. Not a deck. Each function head writes one page max — the metrics that matter, what the numbers are doing, why, and what they need from the room. No one walks into the room without having read it.

Summarise these pre-reads from step 1 in one page view(pdf). For each department, give its status, its biggest win, and key blockers and what it needs from others. Then list the issues that show up in more than one team.

First fifteen minutes, no one talks. Everyone reads the packet (or re-reads it) and writes their questions and comments directly here and make specific suggestions inside the doc. This is the Bezos move — and it's the single most important change you can make.

Each leader: green / yellow / red on each KR they own. One sentence each. No explanation unless red. Reds drop into the issues list.

Walk the input metrics, not just the outputs. The CFO or CoS leads. Anything off-trend gets two minutes — what it means, what to investigate. Anything that needs a real decision drops to the issues list.

The bulk of the meeting. Take the 2–3 biggest items from the reds and metric drift. For each: identify what's actually happening, discuss, decide. Owner and deadline assigned in the room.

Action items from today, plus a check on action items from last month's review. What got done, what didn't, why.

Each person rates the meeting 1–8. Anything under 6 gets a sentence on what to fix next time.

The CFO compiles into a single packet.

[ Add a quick note here or a 1 page document or video ]

Direct from the front line — what's the team hearing.

Talent issues, hires, departures, dynamics or culture.

A single document. Not a deck. Each function head writes one page max — the metrics that matter, what the numbers are doing, why, and what they need from the room. No one walks into the room without having read it.

Summarise these pre-reads from step 1 in one page view(pdf). For each department, give its status, its biggest win, and key blockers and what it needs from others. Then list the issues that show up in more than one team.

First fifteen minutes, no one talks. Everyone reads the packet (or re-reads it) and writes their questions and comments directly here and make specific suggestions inside the doc. This is the Bezos move — and it's the single most important change you can make.

Each leader: green / yellow / red on each KR they own. One sentence each. No explanation unless red. Reds drop into the issues list.

Walk the input metrics, not just the outputs. The CFO or CoS leads. Anything off-trend gets two minutes — what it means, what to investigate. Anything that needs a real decision drops to the issues list.

The bulk of the meeting. Take the 2–3 biggest items from the reds and metric drift. For each: identify what's actually happening, discuss, decide. Owner and deadline assigned in the room.

Action items from today, plus a check on action items from last month's review. What got done, what didn't, why.

Each person rates the meeting 1–8. Anything under 6 gets a sentence on what to fix next time.

A single document. Not a deck. Each function head writes one page max — the metrics that matter, what the numbers are doing, why, and what they need from the room. No one walks into the room without having read it.

Summarise these pre-reads from step 1 in one page view(pdf). For each department, give its status, its biggest win, and key blockers and what it needs from others. Then list the issues that show up in more than one team.

First fifteen minutes, no one talks. Everyone reads the packet (or re-reads it) and writes their questions and comments directly here and make specific suggestions inside the doc. This is the Bezos move — and it's the single most important change you can make.

Each leader: green / yellow / red on each KR they own. One sentence each. No explanation unless red. Reds drop into the issues list.

Walk the input metrics, not just the outputs. The CFO or CoS leads. Anything off-trend gets two minutes — what it means, what to investigate. Anything that needs a real decision drops to the issues list.

The bulk of the meeting. Take the 2–3 biggest items from the reds and metric drift. For each: identify what's actually happening, discuss, decide. Owner and deadline assigned in the room.

Action items from today, plus a check on action items from last month's review. What got done, what didn't, why.

Each person rates the meeting 1–8. Anything under 6 gets a sentence on what to fix next time.

The CFO compiles into a single packet.

[ Add a quick note here or a 1 page document or video ]

Direct from the front line — what's the team hearing.

Talent issues, hires, departures, dynamics or culture.

Review Company Objective 1 and its associated Key Results (KRs).

As a department, identify 3–5 major initiatives, or "Big Rocks," that will directly impact these KRs. These are your critical commitments.

For each initiative, consider its potential impact, required resources, and a clear driver (owner). Ensure each "Big Rock" is actionable and measurable. Add each initiative here, clearly stating the initiative and the assigned driver. Example: "Launch V2 Beta Program - Sarah J."

Now, focus on Company Objective 2 and its Key Results.

Collaborate within your department to select 3–5 key initiatives that will significantly move the needle for this objective. These are your "Big Rocks" for Objective 2. Think about how these initiatives align with your team's strengths and how they contribute to the overall company strategy. Every initiative needs a committed owner. Enter each initiative with its designated driver (owner). Example: "Implement new CRM integration - Mark T."

Move your focus to Company Objective 3 and its Key Results.

Identify another set of 3–5 "Big Rocks"—major initiatives that your department will commit to, ensuring they are directly linked to achieving the KRs for this objective. Prioritize initiatives that are both impactful and feasible within the current quarter. Assign a clear driver for each commitment. Add each initiative and its assigned driver. Example: "Develop Q3 content calendar - Emily R."

Create a 1–2 page document outlining the company objectives and quarterly "rocks" or commitments, including 1–5 major initiatives per department with assigned owners.

Make sure to cover:

The pre-read rule: Nothing is decided without a pre-read. This is non-negotiable in both models, but it's especially important here because the decision surface is smaller. The pre-read format is simple: here is the decision we need to make, here is the context, here is what we recommend, here is what we need from the group. One page (or use video)

⏲Circulated 24 hours in advance (or sooner)

If the pre-read doesn't arrive on time, the item is pulled from the agenda.

That rule - pull the item if the pre-read is late - will feel aggressive the first time you enforce it. It will be respected by week four.

It teaches the organization that the meeting's time is not available for underprepared thinking.👈

Decisions (40 minutes) - items that need a decision this week, with the decision owner identified before the meeting. Pre-read circulated 24 hours in advance.

The meeting makes the decision - it does not "discuss it further."

What is one team blocked on that another team can unblock. Specific. Named.

One metric or qualitative read from each leader. Not status. Signal. "What changed in your part of the world this week that the rest of us should know."

Create a one-page document detailing the decisions made, the blockers that were resolved (and how), and the key signals mentioned. Include a one-paragraph summary explaining potential consequences and specific items to keep an eye on in the upcoming weeks.

What we hit / missed? Add the items we have committed to during this quarter and vote on whether we hit or missed them by reacting with an icon: 🔴 for a miss and 🟢 for a hit.

[Hit = 🟢] [Miss = 🔴]

What decisions did we make that didn’t work out? 🧐 Anything we should revisit regarding how it was made, the criteria behind it, or the overall process? 🔄 (Skip if nothing comes to mind! ⏭️

What patterns, habits, rituals, or actions from this quarter should we keep 🟢 ?

What patterns, habits, rituals, or actions from this quarter should we kill 🔴? Why did certain ones fail, and what exactly didn't work? 🧐

Market, customer, team, product update, etc.

Draft a concise paragraph summarizing the key takeaways from our quarterly goals retro. Please highlight the top four-five points worth sharing, ensuring a balanced view that covers both our major wins and any delays or blockers we encountered.

The pre-read rule: Nothing is decided without a pre-read. This is non-negotiable in both models, but it's especially important here because the decision surface is smaller. The pre-read format is simple: here is the decision we need to make, here is the context, here is what we recommend, here is what we need from the group. One page (or use video)

⏲Circulated 24 hours in advance (or sooner)

If the pre-read doesn't arrive on time, the item is pulled from the agenda.

That rule - pull the item if the pre-read is late - will feel aggressive the first time you enforce it. It will be respected by week four.

It teaches the organization that the meeting's time is not available for underprepared thinking.👈

Decisions (40 minutes) - items that need a decision this week, with the decision owner identified before the meeting. Pre-read circulated 24 hours in advance.

The meeting makes the decision - it does not "discuss it further."

What is one team blocked on that another team can unblock. Specific. Named.

One metric or qualitative read from each leader. Not status. Signal. "What changed in your part of the world this week that the rest of us should know."

Create a one-page document detailing the decisions made, the blockers that were resolved (and how), and the key signals mentioned. Include a one-paragraph summary explaining potential consequences and specific items to keep an eye on in the upcoming weeks.

Review Company Objective 1 and its associated Key Results (KRs).

As a department, identify 3–5 major initiatives, or "Big Rocks," that will directly impact these KRs. These are your critical commitments.

For each initiative, consider its potential impact, required resources, and a clear driver (owner). Ensure each "Big Rock" is actionable and measurable. Add each initiative here, clearly stating the initiative and the assigned driver. Example: "Launch V2 Beta Program - Sarah J."

Now, focus on Company Objective 2 and its Key Results.

Collaborate within your department to select 3–5 key initiatives that will significantly move the needle for this objective. These are your "Big Rocks" for Objective 2. Think about how these initiatives align with your team's strengths and how they contribute to the overall company strategy. Every initiative needs a committed owner. Enter each initiative with its designated driver (owner). Example: "Implement new CRM integration - Mark T."

Move your focus to Company Objective 3 and its Key Results.

Identify another set of 3–5 "Big Rocks"—major initiatives that your department will commit to, ensuring they are directly linked to achieving the KRs for this objective. Prioritize initiatives that are both impactful and feasible within the current quarter. Assign a clear driver for each commitment. Add each initiative and its assigned driver. Example: "Develop Q3 content calendar - Emily R."

Create a 1–2 page document outlining the company objectives and quarterly "rocks" or commitments, including 1–5 major initiatives per department with assigned owners.

Make sure to cover:

What we hit / missed? Add the items we have committed to during this quarter and vote on whether we hit or missed them by reacting with an icon: 🔴 for a miss and 🟢 for a hit.

[Hit = 🟢] [Miss = 🔴]

What decisions did we make that didn’t work out? 🧐 Anything we should revisit regarding how it was made, the criteria behind it, or the overall process? 🔄 (Skip if nothing comes to mind! ⏭️

What patterns, habits, rituals, or actions from this quarter should we keep 🟢 ?

What patterns, habits, rituals, or actions from this quarter should we kill 🔴? Why did certain ones fail, and what exactly didn't work? 🧐

Market, customer, team, product update, etc.

Draft a concise paragraph summarizing the key takeaways from our quarterly goals retro. Please highlight the top four-five points worth sharing, ensuring a balanced view that covers both our major wins and any delays or blockers we encountered.

The pre-read rule: Nothing is decided without a pre-read. This is non-negotiable in both models, but it's especially important here because the decision surface is smaller. The pre-read format is simple: here is the decision we need to make, here is the context, here is what we recommend, here is what we need from the group. One page (or use video)

⏲Circulated 24 hours in advance (or sooner)

If the pre-read doesn't arrive on time, the item is pulled from the agenda.

That rule - pull the item if the pre-read is late - will feel aggressive the first time you enforce it. It will be respected by week four.

It teaches the organization that the meeting's time is not available for underprepared thinking.👈

Decisions (40 minutes) - items that need a decision this week, with the decision owner identified before the meeting. Pre-read circulated 24 hours in advance.

The meeting makes the decision - it does not "discuss it further."

What is one team blocked on that another team can unblock. Specific. Named.

One metric or qualitative read from each leader. Not status. Signal. "What changed in your part of the world this week that the rest of us should know."

Create a one-page document detailing the decisions made, the blockers that were resolved (and how), and the key signals mentioned. Include a one-paragraph summary explaining potential consequences and specific items to keep an eye on in the upcoming weeks.

What we hit / missed? Add the items we have committed to during this quarter and vote on whether we hit or missed them by reacting with an icon: 🔴 for a miss and 🟢 for a hit.

[Hit = 🟢] [Miss = 🔴]

What decisions did we make that didn’t work out? 🧐 Anything we should revisit regarding how it was made, the criteria behind it, or the overall process? 🔄 (Skip if nothing comes to mind! ⏭️

What patterns, habits, rituals, or actions from this quarter should we keep 🟢 ?

What patterns, habits, rituals, or actions from this quarter should we kill 🔴? Why did certain ones fail, and what exactly didn't work? 🧐

Market, customer, team, product update, etc.

Draft a concise paragraph summarizing the key takeaways from our quarterly goals retro. Please highlight the top four-five points worth sharing, ensuring a balanced view that covers both our major wins and any delays or blockers we encountered.

Review Company Objective 1 and its associated Key Results (KRs).

As a department, identify 3–5 major initiatives, or "Big Rocks," that will directly impact these KRs. These are your critical commitments.

For each initiative, consider its potential impact, required resources, and a clear driver (owner). Ensure each "Big Rock" is actionable and measurable. Add each initiative here, clearly stating the initiative and the assigned driver. Example: "Launch V2 Beta Program - Sarah J."

Now, focus on Company Objective 2 and its Key Results.

Collaborate within your department to select 3–5 key initiatives that will significantly move the needle for this objective. These are your "Big Rocks" for Objective 2. Think about how these initiatives align with your team's strengths and how they contribute to the overall company strategy. Every initiative needs a committed owner. Enter each initiative with its designated driver (owner). Example: "Implement new CRM integration - Mark T."

Move your focus to Company Objective 3 and its Key Results.

Identify another set of 3–5 "Big Rocks"—major initiatives that your department will commit to, ensuring they are directly linked to achieving the KRs for this objective. Prioritize initiatives that are both impactful and feasible within the current quarter. Assign a clear driver for each commitment. Add each initiative and its assigned driver. Example: "Develop Q3 content calendar - Emily R."

Create a 1–2 page document outlining the company objectives and quarterly "rocks" or commitments, including 1–5 major initiatives per department with assigned owners.

Make sure to cover: