Purpose: This guide is a practical filter for formulating and evaluating P3-compatible strategy. It is designed to be used as a lens — either by an AI system or a practitioner — to bring strategic thinking into alignment with P3 theory. It does not require any existing P3 infrastructure and is particularly useful when extracting strategic intent from market research, leadership communications, or planning documents, or when evaluating whether a stated strategy is genuinely strategic.

Who this is for: Organisations at early maturity who need to distinguish their strategy from their principles and their products. Strategy answers why we are moving and where. Principles answer what constraints govern how we move. Products answer what value we are delivering. This guide addresses the first question only.

Strategy is not a plan. It is not a list of goals. It is not a product roadmap or a set of governing principles. Strategy is a directional force — the intentional vector that determines where an organisation is pointed and at what pace it is moving.

The most important word in that definition is directional. Strategy does not specify every decision. It orients the mechanism. When strategy is well-formulated, each part of the organisation can interpret it independently and still move in a coherent direction — the way a ship's crew, given a heading, can each perform their role without being told the exact path of every wave.

A strategy that names a destination ("become the leading provider of X") is not yet a strategy in the P3 sense. It is an aspiration. Aspirations tell you where you want to arrive but not how fast you are moving, what you are sacrificing to get there, or whether your current capability can sustain the journey.

A P3-compatible strategy takes the form of a desired slope: a direction of travel combined with a sustainable rate of advance. The difference is significant:

The slope acknowledges that the destination may shift, that the rate is constrained by real capacity, and that the direction is subject to recalibration as the environment changes. Destinations invite disappointment when circumstances change. Slopes invite intelligent adjustment.

Planning asks: what steps will we take? Navigation asks: where are we, where are we going, and are we still on course?

Planning is operational — it belongs in the product and pattern layers. Strategy is navigational — it belongs at the level of intent and direction. An organisation that confuses strategic direction with operational planning produces one of two failure modes: either the strategy becomes a micromanagement exercise (the Admiral enters the engine room to direct the stokers), or the operational plan floats free of any genuine direction (the engine room runs at perfect efficiency toward nowhere in particular).

What strategy is not: a list of principles, a product brief, a feature roadmap, an operational procedure, or a mission statement. When any of these appear in a document labelled "strategy," flag them for reclassification. Conflating them with strategy is one of the most common causes of strategic decoupling — where leadership believes the organisation is executing a strategy that the operational layer has never actually received.

Strategy is the primary communication vehicle between executive intent and operational execution. But the two levels speak different languages. When an executive says "we need to move faster," they mean: accelerate time-to-market, compress the feedback loop. When an engineering team hears "move faster," they hear: cut testing, skip reviews, ship what isn't ready. Neither interpretation is wrong in its own frame. The breakdown is linguistic before it is organisational.

A well-formulated strategy bridges this gap by stating intent at a level of abstraction that is interpretable at every organisational level without being re-invented at every level. It tells the organisation what it is optimising for, at what pace, and in exchange for what trade-offs — and from that, each level can make locally coherent decisions that remain globally aligned.

Apply the following filter sequentially to any statement presented as strategy in client materials — strategic plans, leadership communications, board presentations, OKRs, or vision documents.

Ask: does this statement identify a direction of travel, or does it name a destination, a task, or a principle?

Ask: does the statement specify both direction and sustainable velocity?

Does it acknowledge what the organisation is currently capable of, and calibrate the rate of advance accordingly? A statement that demands more than current capability can sustain is not a strategy — it is a command issued to an engine room that cannot hear it.

Rewrite any aspiration as: "We are moving toward [direction] at a pace [capability constraint], by [specific means this epoch]."

Ask: if this strategy were stated to an executive, a team leader, and a product owner, would each find something meaningful and actionable in it — without it meaning the same thing to all three?

Good strategy is robust enough to maintain identity as it crosses organisational boundaries, but flexible enough to be interpreted locally. Too abstract and no one can act — it is a slogan. Too specific and it can only be read one way — it is a plan masquerading as strategy.

Ask: is this direction moving toward uncontested value space, or is it competing on the same terms as existing players?

A strategy that positions the organisation to compete directly against established players on established terms is a Red Ocean strategy — viable, but likely to produce incremental rather than generative value. A strategy that identifies unmet need, underserved beneficiaries, or novel value combinations is moving toward Blue Ocean.

This is not a binary judgement, but it is a useful signal. When evaluating multiple strategic directions, prioritise those that create value rather than merely capture it from competitors.

Ask: what does this strategy explicitly not pursue?

A strategy that attempts to pursue everything is not a strategy — it is a list of wishes. Real strategic direction requires the organisation to concentrate its capacity on a critical path and starve everything else. If a stated strategy does not name what it sacrifices, it has not yet been fully formulated.

Name at least two to three things the organisation will deliberately not pursue during this strategic epoch. The sacrifices are as constitutive of the strategy as the direction itself.

Once a strategic direction has survived the filter in Section 2, the following six-part brief structure provides the minimum information needed to communicate it, evaluate it, and govern its execution.

1. Direction Statement
A one-sentence slope: direction + sustainable velocity.
Formulate as: "We are moving toward [X] at a pace [Y] can sustain." Avoid destinations; state trajectories.

2. Value Rationale
Why does this direction create value that current approaches or competitors do not?
Identify the market void, the unmet need, or the novel value combination that makes this direction worth pursuing. Connect to the Blue Ocean check.

3. Capability Assessment
What can the organisation do now, what does it need to grow, and what is currently out of reach?
Apply the Strategy Sieve (see Section 4) to each major element of the direction. Ambition disconnected from capacity produces damage, not ambition.

4. Sacrifice List
Two to three things the organisation will explicitly not pursue during this strategic epoch.
State these as clearly as the direction itself. The sacrifices are how capacity is concentrated on the critical path.

5. Principle Activation
Which governing commitments does this strategy emphasise?
Every organisation has implicit principles that shape what it builds. Name the two or three that this strategy places in the foreground — and identify which ones require active defence against the pressures the strategy will create.

6. Epoch Definition
What is the time horizon for this configuration, and what signal would prompt recalibration?
Name the horizon and the signal that would warrant re-evaluation — not market noise or a single-sprint failure, but structural evidence that the terrain has changed.

Strategic ambition that exceeds organisational capability does not produce ambitious outcomes — it produces damage. The Strategy Sieve is the mechanism for calibrating ambition to reality. Apply it to each major element of the direction identified in the strategy brief.

Now — The organisation has the capacity, the patterns, and the governance to execute this element immediately. Proceed without modification.

Grow — The capacity gap is real but closeable within the strategic timeframe. Name the investment: what must be built, learned, or acquired, and by when? Accepting a "Grow" state is not failure — it is honest governance.

Recalibrate — The gap between ambition and capability is too large to bridge within a strategically relevant timeframe. This element, as stated, is aspiration rather than strategy. Adjust the direction, extend the timeline, or reduce the scope until the sieve state shifts to "Now" or "Grow."

A strategy composed primarily of "Recalibrate" elements is a fantasy document. The useful zone is a mix of "Now" (executable immediately) and "Grow" (executable with named investment), with any "Recalibrate" elements explicitly acknowledged and either revised or deferred.

A strategy is re-mixed between epochs, not during them. Constant direction changes are as damaging as no direction at all. Apply the sieve test when formulating or renewing strategy at the start of each epoch. During execution, adjust the pace and means in response to operational signals — but protect the direction. Change the how frequently. Change the where only when structural evidence confirms the terrain has fundamentally shifted.

When applied to client materials, this guide should be used as follows:

Statements that do not survive Step 2 are principles, product ideas, operational plans, or identity statements — each valuable, but belonging in a different filter. Route them to the appropriate guide.

A strategy brief that is honest about its "Grow" and "Recalibrate" elements is more useful than one that presents everything as executable. Sieve results are not admissions of weakness — they are the investment plan that makes the strategy real.

This guide is a pre-P3 reference document. It does not assume any P3 governance infrastructure. It is designed to create the conditions in which P3-compatible strategic governance can subsequently be built.