The People Analyst Guide to Nine Lies About Work. Format: what the book argues → what the research actually says → how you run it → the analysis you can run → the AI-era turn → what to do Monday. No reproduction of the book's text; the substance is ours. Research anchors verified on read.
What the book argues
The third lie is "the best companies cascade goals." The book's counter is that mechanically cascading goals down the org chart — the CEO's objectives split into VP objectives split into team objectives — is slow, brittle, and quietly disengaging, and that what high-performing companies actually do is cascade meaning: share the why and the context richly, and trust people to set the right goals locally. Meaning flows down; goals form where the work is.
What the research actually says
Both halves are evidence-backed, and the chapter is really about not confusing them. Goals work: Locke & Latham's goal-setting theory is one of the most robust findings in all of organizational psychology — specific, challenging goals reliably lift performance. So "goals are bad" would be wrong, and the book doesn't quite say that.
What fails is the cascade mechanism, not goals. Rigid top-down cascades produce goal displacement and gaming (people optimize the assigned number, not the intent — the same failure mode behind bad OKR rollouts), they go stale between cycles, and they strip the local judgment that makes a goal fit the work. What aligns an organization isn't cascade compliance; it's shared priorities — and shared priorities come from shared meaning and context, which let people set locally-correct goals that still point the same direction. So the honest version: cascade the meaning and the context; let the goals form locally; and measure alignment — whether priorities actually agree across the org — rather than whether the cascade was completed. Alignment is the real target, and it's measurable.
How you run it
Stop measuring cascade completion and start measuring alignment. Communicate meaning and context deliberately; let teams author their own goals against it; then measure the dispersion of priorities across leaders and teams — tight agreement is alignment, wide scatter is a meaning problem upstream, not a cascade-discipline problem.
The analysis you can run
An alignment analysis — the leadership-quality alignment instrument with survey-orchestrator —
that measures shared-priority dispersion across leaders and teams (do priorities actually agree?),
scoring CAMS-Alignment. It tells you where the org is genuinely pointed the same way and where it only
looks aligned because the cascade was filled in. (This is the alignment dimension of the Measuring
Leadership battery, and it pairs with executive prioritization.)
The AI-era turn
Cascading rigid goals was always partly a communication-bandwidth hack — you couldn't give everyone the full context, so you handed them a number. AI removes that constraint: it can propagate meaning and context consistently to everyone, and continuously measure whether priorities are actually converging. The move is from a once-a-year cascade of targets to a living read of alignment — meaning out, alignment measured back.
What to do Monday
- Stop reporting cascade/OKR completion as if it were alignment; it isn't.
- Cascade the why and the context; let teams set their own goals against it.
- Measure priority dispersion across leaders/teams — agreement is alignment; scatter is an upstream meaning gap.
- Keep goals (Locke & Latham holds) — fix the mechanism, not the use of goals.