Most leadership teams think they have a strategy. What they have is a list of priorities that emerged from last year's politics, this year's budget constraints, and whoever was loudest in the planning offsite.
That's not the same thing.
A strategy is a position. It answers two questions clearly: where will this organization compete, and how will it win there? Not a vision. Not a set of goals. A specific, differentiating choice about where to play and how to outperform on that ground.
The problem isn't that leaders don't understand this. Most do. The problem is sequence.
Organizations hire people, build teams, and establish reporting structures — then ask those structures to execute a strategy. The talent was already in place. The org chart was already drawn. The capabilities that exist are the capabilities that exist.
Strategy becomes whatever the current configuration can credibly claim to pursue.
When structure precedes strategy, you're not making strategic choices — you're rationalizing the choices that were already made for you by headcount, politics, and sunk cost.
The Strategic Anchor is a method for reversing this sequence. It works as a cascade — and it only works if you follow the order.
Start at the top. Fix it before moving down.
Strategic Positioning comes first because it's the only fixed point. Once you know precisely how the organization wins — the specific customer problem it solves better than anyone else, the market position it's defending or building toward — everything else becomes a derivation, not a negotiation.
Capabilities follow from positioning. Given how we've decided to win, what must we be genuinely excellent at? Not competent — excellent. This step forces honest accounting of where current capability actually sits relative to what the strategy requires.
Structure follows from capabilities. How do we need to organize to build and deploy those capabilities at the speed the strategy demands? Structure is in service of capability development — not legacy, not politics, not what's easiest to defend in a reorg.
Talent follows from structure. What does each role actually need to do? What does great performance look like in this specific configuration? Hiring and development criteria become precise rather than generic.
Most leaders encounter the Strategic Anchor when they're diagnosing something that isn't working — a team that can't execute, a function that keeps missing the mark, an organization that's technically competent but somehow not winning.
The diagnostic question is always the same: start at the top of the cascade and ask where it breaks down.
Is the positioning clear and specific enough to make real choices? Most of the time, this is where the problem lives. Not in the talent, not in the structure — in a strategic position that's too vague to cascade into anything coherent. When the anchor is set — when the position is specific and defended — the rest of the cascade becomes derivable. Not easy, but derivable.
You almost certainly have a strategy. Most organizations do, at least on paper.
The question is whether your capabilities, structure, and talent are actually calibrated to execute it — or whether they're calibrated to the strategy you had three years ago, or the one that survived the planning process because it offended the fewest people.
The Strategic Anchor is the diagnostic frame I use at the start of every engagement. It anchors everything else. It's Module 1 in Wired for AI because without it, AI augmentation just optimizes for the wrong things faster.
A strategic anchor is a single, definitive statement that clarifies what an organization is fundamentally optimizing for. It is not a vision statement or a list of priorities — it is the test that every major decision gets run against. When leaders lack a strategic anchor, they tend to approve too many initiatives and make contradictory decisions because they have no single standard to apply.
Most leadership teams mistake a list of priorities for a strategy. Real strategy requires trade-offs — explicit choices about what the organization will not pursue. Without those trade-offs, every initiative gets approved and the organization tries to optimize for too many things simultaneously, which is equivalent to optimizing for none of them.
The test is straightforward: can every person on your leadership team articulate the same answer to the question 'what is our organization fundamentally optimizing for?' If the answers differ, the anchor does not exist — or exists only in someone's head and has not been genuinely shared. The second test is whether the anchor is specific enough to generate real trade-offs when applied to resource allocation decisions.
Sterling Grey argues that a well-formed strategy functions as a filter: it tells you what to say yes to and, more importantly, what to say no to. Organizations that lack this filter end up with an ever-growing initiative backlog because they have no mechanism for pruning. The Strategic Anchor restores that mechanism by providing a single, shared criterion for evaluating whether any given commitment belongs.
The Velocity Gap Assessment takes 8 minutes. It tells you whether your organization is structured to execute the strategy it claims to have — and exactly where the misalignment is.