Cascading does not mean dictating objectives from the top and pushing them downward. That approach merely repackages command-and-control management in new terminology. True cascading is a two-way process in which company-level objectives inform team-level priorities while team-level insights shape what the organisation believes is achievable.
Starting at the Top
Effective cascading begins with a small set of company-level OKRs. Most successful organisations limit themselves to three to five objectives at the highest level. These should represent the most critical priorities for the coming quarter, not an exhaustive list of everything the company does.
The wording of these top-level objectives matters enormously. They need to be specific enough to provide genuine direction but broad enough to allow teams to find their own path to contribution. An objective like 'become the leading provider in the mid-market segment' gives clear direction without prescribing exactly how each department should contribute.
The Alignment Conversation
Once company-level OKRs are published, the most important step in the cascading process begins: the alignment conversation. This is not a presentation where leaders explain what they have decided. It is a structured dialogue in which teams discuss how their work connects to the broader objectives and propose their own team-level OKRs in response.
These conversations frequently reveal misunderstandings, competing priorities, and hidden dependencies. The marketing team might assume that the 'mid-market expansion' objective means increasing lead volume, while the sales team interprets it as improving conversion rates on existing leads. Without the alignment conversation, both teams charge ahead in different directions, each confident they are working toward the company objective.
Avoiding the Waterfall Trap
The most common cascading mistake is creating a strict hierarchy where each team's key results become the next level's objectives. While this creates a neat visual tree, it produces several problems. First, it takes weeks for objectives to cascade through multiple management layers, creating the same delay that OKRs are supposed to eliminate. Second, it strips lower-level teams of the autonomy to define their own objectives.
A more effective approach is directional alignment. Teams review the company-level OKRs and craft their own objectives that clearly contribute to the broader goals without being mechanically derived from them. The engineering team might see the company objective around market expansion and create their own objective focused on platform reliability, reasoning that enterprise customers in the mid-market demand higher uptime guarantees.
Organisations that manage cascading well often use OKR alignment and tracking software such as Profit.co to visualise how team objectives connect to company goals. This visibility helps leaders spot gaps where no team has picked up responsibility for a company-level priority, as well as overlaps where multiple teams are pursuing the same outcome.
Cross-Functional Dependencies
Cascading inevitably exposes cross-functional dependencies. The product team's key result around launching a new feature depends on engineering capacity. The sales team's pipeline target depends on marketing generating qualified leads. These dependencies need to be surfaced and negotiated during the alignment process, not discovered mid-quarter when deadlines are at risk.
One practical technique is to hold a brief dependency mapping session after teams have drafted their OKRs. Each team identifies which of their key results depends on another team's output. These dependencies are then discussed and, where necessary, reflected in shared OKRs or explicit commitments between teams.
Keeping It Manageable
The simplest way to prevent cascading from becoming an administrative nightmare is to limit the number of levels. For most organisations, three levels are sufficient: company, department, and team. Individual OKRs add a fourth level that can be valuable for senior contributors but is unnecessary for everyone. The goal is alignment, not bureaucracy.
Revisit the cascade at the midpoint of each quarter. A brief check-in to confirm that team objectives still align with company priorities, especially if external conditions have changed, prevents the common scenario where teams complete their OKRs successfully but the outcomes no longer serve the organisation's most pressing needs.
Comments
Post a Comment