Strategic Intent Framing

Purpose

Frames a clear strategic intent that focuses energy and cuts out noise — a stable point of view about the leadership position an organization wants to reach, distinct from both a vague mission statement and a fully worked-out plan.

Anchored in research

• Hamel & Prahalad (1989), "Strategic Intent," Harvard Business Review — the original source of the term. Strategic intent is deliberately ambitious relative to current resources and capabilities; the resulting "misfit" between ambition and resources is what galvanizes the organization, rather than a comfortable plan sized to what's already available.
• Liedtka (1998) — intent-focused: strategic thinking is intent-driven rather than merely fit-driven — it asks what future the organization is trying to create, not only what current resources allow.

Method

1. State the desired leadership position in one sentence. Not a mission ("we help X do Y") but a specific, contestable claim about where the organization intends to stand relative to competitors or the market in a defined timeframe.
2. Check for productive misfit. Does the intent require the organization to become more capable than it currently is? An intent that's already achievable with today's resources isn't doing its job — it isn't creating the stretch that focuses effort.
3. Define what "winning" concretely looks like. Hamel & Prahalad's point: strategic intent needs an unambiguous win criterion, not an open aspiration — otherwise it can't focus decisions or be tested against reality later.
4. Set interim milestones that build the specific capabilities the intent requires — not just revenue or timeline milestones, but capability milestones ("by Q3 we can do X we currently can't").
5. Pressure-test for focus, not just ambition. A good strategic intent should make some decisions obviously wrong. If the intent doesn't rule anything out, it isn't yet focused enough to be useful.
6. Write it down in a form that travels — short enough to be repeated accurately by someone who wasn't in the room when it was framed.

What this skill does NOT do

• Doesn't make the final decision for you — it produces a structured draft to support a human decision.
• Doesn't confirm figures, market data, or competitor data from memory — it uses the inputs you provide, or marks an assumption clearly ([assumption — verify]).
• Doesn't replace an organization's formal strategy process or board approval.

Refinement notes

Areas to keep deepening with real practice:

• your own rules of thumb and heuristics for this technique
• concrete templates (into ../../references/)
• reference cases / your own examples
• what this skill deliberately does not do (guardrails, common mistakes) — add to the list above

This is an internal working note, not a claim about the skill's current usability. Track depth privately via the maturity field in skills_index.json (see ../../../meta/maturity_levels.md). Don't add new fields to the frontmatter — name and description are the only ones allowed (see ../../../meta/frontmatter_schema.md).

Continue from here

• Next in this pack: ../hypothesis-driven-strategy/SKILL.md — Structures a strategic problem with MECE and an issue tree, then tests the hypotheses against data.
• A ready-made skill chain for this situation: see ../../../playbooks/
• This pack's shared guardrails: ../../CLAUDE.md

References

• ../../references/ — the pack's shared background material
• ../../CLAUDE.md — the pack's shared guardrails