Cascading OKR: how to align your company, teams, and people

The owner wants to grow revenue. Marketing wants more followers. Sales wants to close the number. Product wants to ship a feature. Everyone working hard — in different directions. If this sounds familiar, the problem isn't effort. It's alignment.

Cascading OKR solves this. The company OKR says where the business is going. The team OKR says how that group contributes. The individual OKR says what each person focuses on. When it works, it's the most powerful way to align an entire company around what truly matters.

How it works in practice:

Level 1: Company OKR (strategic)

Defined by leadership. Usually 1 to 2 objectives per quarter. These are the ones that matter most to the business as a whole.

Example:

• Objective: Make the operation financially sustainable
• KR1: Reach a 20% net margin
• KR2: Achieve 50 recurring customers
• KR3: Reduce fixed costs by 15%

Level 2: Team OKR (tactical)

Each team looks at the company OKR and asks: "What do we do that contributes to this?"

Sales Team:

• Objective: Build a recurring customer base
• KR1: Close 20 new recurring contracts
• KR2: Increase average ticket from $800 to $1,200

Operations Team:

• Objective: Reduce operating costs without losing quality
• KR1: Reduce fixed costs from $25k to $21k
• KR2: Maintain customer satisfaction above 8/10

Level 3: Individual OKR (operational)

Each team member asks: "What do I do that contributes to my team's OKR?"

Sales rep:

• Objective: Close recurring contracts with ideal-fit clients
• KR1: Generate 40 qualified proposals
• KR2: Convert 50% of proposals into contracts

The key: alignment, not copying

Cascading OKR is not about copying the OKR from the level above and pasting it below. It's about translating the strategic direction into tactical and operational actions. Each level speaks the language of its context, but all point toward the same north.

Cautions:

• Don't force cascading in a 3-person company. One level is enough. In my experience, cascading starts to make sense when there are distinct enough functions to justify it — usually from around 8–15 people, but it depends on complexity.
• Don't create circular dependencies. If a team's KR depends on another team that depends on the first, nobody moves forward.
• Review at check-in whether the levels are still aligned. Reality changes — alignment needs to keep up.

Alignment isn't a meeting. It's structure. When everyone sees the same north, the conversation changes.

Create cascading OKRs — company, team, individual in one place. No sign-up required.