strategic-alignment

---
name: strategic-alignment
description: Use when teams pull in different directions, OKRs don't connect across levels, departments optimize locally at company expense, or strategy needs to cascade from leadership to individual contributors.
category: C-Level Advisory
version: 1.0.0
tools: []
---

# Strategic Alignment Engine

Strategy fails at the cascade, not the boardroom. Detect misalignment before it becomes dysfunction and build systems that keep strategy connected from CEO to individual contributor.

## Core Framework

The alignment problem: the further a goal gets from the strategy that created it, the less likely it reflects the original intent — the organizational telephone game. It happens at every stage; the question is how bad it is and how to fix it.

### Step 1: Strategy Articulation Test
Before checking cascade, check the source. Ask five people from five different teams: "What is the company's most important strategic priority right now?"

Scoring: all five give the same answer = articulation is clear. 3–4 give similar answers = loose alignment, clarify and communicate. Fewer than 3 agree = strategy isn't clear enough to cascade — fix this first.

Format test: the strategy should be statable in one sentence. "We focus on product-led growth while maintaining enterprise relationships and expanding international presence and investing in platform capabilities" fails; "Win the mid-market healthcare segment in DACH before Series B" passes.

### Step 2: Cascade Mapping
Map company strategy → department OKRs → team OKRs → individual goals/rocks. For each goal at every level: which company-level goal does this support? If achieved 100%, how much does it move the company goal? Is the connection direct or theoretical?

### Step 3: Alignment Detection — three failure patterns
**Orphan goals** — team/individual goals with no connection to any company goal. Symptom: "we've worked on this a quarter and nobody above us seems to care." Root cause: goals set bottom-up without reconciling to current OKRs. Fix: connect or cut — every goal needs a parent.

**Conflicting goals** — two teams' goals that, when both succeed, create a worse outcome. Example: Sales rewarded for volume contracts closes bad-fit customers; CS measured on satisfaction scores tanks. Fix: cross-functional OKR review before the quarter begins; shared metrics where teams interact.

**Coverage gaps** — company has 3 OKRs; 5 teams support OKR-1, 2 support OKR-2, 0 support OKR-3. Symptom: OKR-3 consistently misses, nobody owns it. Fix: explicit ownership assignment — an unowned company OKR won't happen.

### Step 4: Silo Identification
Silos exist when teams optimize local metrics at company expense. Signals: a department consistently hits goals while the company misses; teams don't know what others are working on; "that's not our problem" is common; escalations flow up but never sideways; data isn't shared between dependent teams.

Root causes: incentive misalignment (rewarded for local, not company, metrics); no shared goals (drift without them); no shared language (engineering vs. sales vs. technical debt); geography/time-zone separation.

Measurement: how often do teams request help vs. proceed independently? How long to resolve a cross-functional issue? Can a team member describe an adjacent team's current priorities?

### Step 5: Communication Gap Analysis
What the CEO says ≠ what teams hear; the gap grows with company size. Message decay: CEO communicates at all-hands → managers filter through their lens → teams receive a modified version → individuals interpret further.

Gap sources: ambiguity (strategy stated too high-level lets each team fill in interpretation); frequency (one all-hands per quarter isn't enough repetition to change behavior); medium mismatch (long written doc for visually-oriented teams); trust deficit ("we've heard this before").

Detection: run the Step 1 test across all levels; compare what leadership thinks it communicated vs. what teams say they heard; survey "what changed about how you work since the last strategy update?"

### Step 6: Realignment Protocol
Don't lead with what's wrong — "here's our misalignment" creates defensiveness; lead with "here's where we're heading and I want to make sure we're connected." Re-cascade in a workshop, not a memo — get OKR owners and department leads in a room, map connections, find gaps together. Fix incentives before fixing goals — if department heads are rewarded for metrics that conflict with company goals, goal-setting alone won't fix it. Install a quarterly alignment check to prevent recurrence.

## Alignment Score
Score each area 0–10: strategy clarity (can 5 people from different teams state it consistently?); cascade completeness (do all team goals connect to company goals?); conflict detection (have cross-team OKR conflicts been reviewed?); coverage (does every company OKR have explicit ownership?); communication (do behaviors reflect the strategy, not just stated understanding?).

Total /50: 45–50 excellent, maintain the system. 35–44 good, address weak areas. 20–34 misalignment is costing you, immediate attention. Below 20, strategic drift — treat as crisis.

## Key Questions
Ask your newest team member what the company is most trying to achieve right now. Which company OKR does your team's top priority support — can you trace it? When Team A and Team B both hit their goals, does the company always win, or are there scenarios where it doesn't? What changed in how your team works since the last strategy update? Name a decision made last week influenced by company strategy.

## Red Flags
Teams consistently hit goals while the company misses targets. Cross-functional projects take 3x longer than expected. Strategy updated quarterly but team priorities don't change. "That's a leadership problem, not ours" at the team level. New initiatives announced without connecting to existing OKRs. Department heads optimize for headcount or budget over company outcomes.

## Cross-Functional Coordination
- New strategy set: with the CEO and COO, cascade into quarterly rocks before announcing
- OKR cycle starts: with the COO, run cross-team conflict check before finalizing
- Team consistently misses goals: with the CHRO, diagnose capability gap vs. alignment gap
- Silo identified: with the COO, design shared metrics or cross-functional OKRs
- Post-M&A: with the CEO, detect strategy conflicts between merged entities