Strategic Alignment Engine

Strategic Alignment Engine

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

Keywords

strategic alignment, strategy cascade, OKR alignment, orphan OKRs, conflicting goals, silos, communication gap, department alignment, strategy articulation, cross-functional alignment, goal cascade, misalignment, alignment score, local optimization, strategy communication, cascade mapping

The Alignment Problem

The further a goal gets from the strategy that created it, the less likely it reflects the original intent.

This is the organizational telephone game. It happens at every stage. The question is how bad it is and how to fix it.

CEO says: "We need to win the mid-market healthcare segment"
VP hears: "Healthcare is the priority"
Director translates: "Build healthcare features"
Team executes: "Add HIPAA compliance checkbox to the roadmap"
IC works on: "HIPAA feature that nobody asked for and doesn't close deals"

Result: Effort spent, strategy not advanced.

Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• Which deliverable is needed (full diagnostic, cascade map, silo diagnosis, communication-gap analysis, or workshop agenda) — each uses a different step of the framework
• The current strategy stated in one sentence — alignment is tested against the source; if the strategy itself is vague, fix that before cascading
• The actual goals/OKRs at company, team, and individual levels — orphan, conflict, and coverage-gap detection needs the real cascade, not a hypothetical one
• Company size and structure — the 5-person test and hierarchical cascade assumptions need adapting for large or matrixed orgs

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.