Reporting hierarchy does not make priorities transitive — verify alignment at each level
Before assuming organizational hierarchy makes strategic priorities transitive, verify alignment at each reporting level independently, as 'reports to' relationships do not make 'shares priorities with' transitive.
Why This Is a Rule
Organizations assume that strategic priorities cascade cleanly down the hierarchy: the CEO's priorities become the VP's, which become the director's, which become the manager's, which become the individual contributor's. This assumption treats "reports to" and "shares priorities with" as the same transitive relationship. They're not.
"Reports to" is transitive: if IC reports to Manager and Manager reports to Director, IC is in the Director's organization (safe chain inference). "Shares priorities with" is NOT transitive: the Director's priority might be "increase revenue," which the Manager interprets as "ship more features," which the IC interprets as "write more code faster." Each level's interpretation shifts the priority — by the bottom of the chain, the working priority may contradict the original intent.
This priority drift is invisible because everyone believes they're aligned. Each level thinks they're executing their manager's priorities. But the chain of interpretations has shifted the priority at each link, and the endpoint priority may be orthogonal to the origin priority.
When This Fires
- When assuming your work aligns with organizational strategy because your manager's does
- During strategic planning when cascading priorities down the org chart
- When organizational misalignment produces surprising outcomes despite "clear priorities"
- Any time you're reasoning about priority alignment across multiple reporting levels
Common Failure Mode
Checking alignment only at adjacent levels: "My manager confirmed I'm on the right track." But your manager's interpretation of the director's priority might already have drifted. Verify at each level independently: does your work serve the original strategic priority, not just your manager's interpretation of it?
The Protocol
Before assuming priority alignment through hierarchy: (1) State the original strategic priority from the top of the chain. (2) At each reporting level, ask: "How does [this level's] interpretation of the priority map to the original?" (3) Check: has the interpretation drifted at any level? (4) If drift is found → realign at the point of drift rather than assuming the chain transmits accurately. Priority alignment requires verification at each link, not trust in the chain.