Goals, Objectives, Strategies, Tactics and KPIs: the planning framework every public affairs team needs

By Paul Shotton, Advocacy Strategy

Across many years of working with public affairs teams in trade associations, in-house functions, and NGOs, one framework has come up more often than any other in our consulting work. We use it for setting priorities, for quantifying the impact of issues on the organisation, and as the spine of an annual public affairs plan. It is the means by which a team translates its ambition for the coming period into a clear cascade — from what we want to bring about, down to who is doing what next week. It is also a thinking tool: it forces people to articulate ambition in language the rest of the organisation can recognise.

Can you state your three most important policy goals, the objectives beneath them, the strategies you have chosen, the tactics you are running, and the indicator at each layer that tells you whether the work is succeeding? That question almost always produces a long pause followed by a list of activities. Activities are not strategy. The challenge is the same whether you sit in an association explaining your work to members, in an in-house team reporting to the board, or in an NGO answering to funders.

Why a framework — the activity trap

Peter Drucker named the failure mode in 1954. He called it the activity trap: the drift in which managers become so absorbed in activities that they lose touch with their purpose. In public affairs work, the activity trap shows up across all three sectors in patterns we see again and again.

There is pressure on resources, because the team has signed up to too many things at once. Objectives proliferate, and many are unclear. Some are broad and directional — they sound like goals. Others are not measurable, because they are not specific enough. Many do not relate back to a clearly defined issue. The cascade has reversed: activities are inferred backwards into objectives, rather than objectives chosen first and tactics designed to deliver them.

Sequencing is the other failure mode. Sometimes the objective comes before the issue. That is the wrong order. You need to know what you want to engage with first — which policy file, which forum, which decision moment — and only then can you formulate the objective for that engagement. And do not let a single objective cover multiple issues; that is the standard route to a vague objective no one can plan against.

Rich Horwath formalised the response as GOST — Goals, Objectives, Strategies, Tactics — in Elevate: The Three Disciplines of Advanced Strategic Thinking (2014). Four layers, no decoration.

The four layers

A Goal is a long-term, directional outcome the organisation seeks to bring about in a defined policy domain. Goals are qualitative, multi-year, and not directly measurable. Their function is to set direction.

An Objective is a specific, time-bound, measurable outcome whose achievement advances the Goal. Objectives convert directional intent into commitments, typically over a nine to twelve-month horizon.

A Strategy is a coherent choice about how the organisation will pursue an Objective. In practice a Strategy works at two levels: an overall statement that names the chosen approach and excludes the alternatives, and a small set of strategic pillars — such as direct engagement, coalitions and partners, trade association leverage, communications and thought leadership, or evidence and intelligence — from which the team draws. Pillars are the unit at which the work is owned.

A Tactic is a specific, owned, scheduled action that implements a Strategy. Tactics name an owner, an action, a deliverable, a deadline, and a target stakeholder or forum.

Two distinctions most often blur in practice: Goal versus Objective, and Strategy versus Tactic. “The European truck industry seeks a regulatory framework supporting a viable transition to zero-emission trucks while preserving manufacturing competitiveness” is a Goal — durable, qualitative. “By Q4 2027, the HDV CO2 Regulation will be amended to introduce a midpoint flexibility mechanism for 2030 to 2035” is an Objective — dated, attached to a named instrument. “Build a coalition with vehicle manufacturers, fleet operators, and infrastructure providers” is a strategic pillar — a chosen lever within a Strategy. “Submit the coalition response to DG CLIMA by 30 September 2026” is a Tactic — a specific scheduled action.

Mission and Vision sit above the framework, not inside it. A public affairs team rarely sets the organisation’s mission. It inherits one and translates it into Goals.

Logical sequencing — and a warning about inflation

The order of GOST is not aesthetic. Each layer is the test of the layer immediately below it. A Tactic is only a good tactic if it serves a chosen Strategy. A Strategy is only a good strategy if it advances a defined Objective. An Objective is only a good objective if it operationalises a Goal. When teams plan top-down, ambiguity at any layer is exposed by the layer above. When they plan bottom-up, the failure mode is Drucker’s activity trap.

A warning before the formulas: do not let your objectives inflate. If they sit on a nine to twelve-month horizon, do not draft too many, and do not stretch any single one much beyond that horizon. A team with twelve objectives has, in practice, none — none can be defended as a real commitment. A team with one or two objectives that secretly span three years has the same problem in reverse: the objective has become a goal in disguise.

A formula for each layer

The point of GOST is to make the language at each layer disciplined. The worked examples below are drawn from a topical European policy question — the competitiveness of the European heavy-duty vehicle industry — and are deliberately generalised.

Goal. In [policy domain], the organisation seeks [directional change] so that [link to mission or business value]. A good Goal names the domain, states a direction of change, and connects to mission or business value. “In EU heavy-duty vehicle policy, the European truck industry seeks a regulatory and infrastructure framework that supports a viable transition to zero-emission trucks while preserving European manufacturing competitiveness.”

Objective. By [date], [which policy] will be changed by [who], to [the specific change]. An objective is a statement about a policy change: which policy, who has the authority, and when. “By Q4 2027, the Heavy-Duty Vehicles CO2 Regulation will be amended by the EU co-legislators to introduce a midpoint flexibility mechanism for the 2030 to 2035 targets, conditional on charging infrastructure deployment milestones.” The how — coalitions, engagement, evidence — sits in the Strategy layer. Compare to “Promote a balanced HDV CO2 framework in 2026.” That is a Goal pretending to be an Objective: no date, no measurable change, no named instrument, no actor.

Strategy. Write the Strategy at two levels. First, an overall statement: To achieve [Objective], the organisation will pursue [chosen approach] across [pillars 1, 2, 3], deliberately not pursuing [excluded option and why]. Then articulate each strategic pillar separately, with its own owner, its own progress indicator, and its own tactics underneath. The test that catches most weak Strategy statements is the explicit exclusion. Good strategy chooses; pillars are where the work lives.

Overall statement, in the HDV example: “To secure the HDV amendments, the industry will pursue a competitiveness-anchored strategy across three pillars — coalition-building, direct institutional engagement, and parliamentary engagement — deliberately not running a high-visibility public campaign that would invite a climate-backsliding framing.”

Pillar 1 — Coalition-building. Build a joint industry submission with vehicle manufacturers, fleet operators, and infrastructure providers. Owner: industry secretariat. Progress indicator: number of signatories on the joint submission.

Pillar 2 — Direct institutional engagement. Engage DG GROW and DG CLIMA at director and unit-head level on the competitiveness case. Owner: Brussels team. Progress indicator: bilaterals held with named units by Q1 2027.

Pillar 3 — Parliamentary engagement. Engage the lead ENVI and TRAN rapporteurs and shadows on the flexibility mechanism. Owner: parliamentary lead. Progress indicator: positioning meetings held; technical input acknowledged in committee discussions.

Tactic. [Owner] will [action verb] [deliverable] by [date], targeting [named stakeholder or forum], in support of [named pillar]. Every tactic should belong to exactly one pillar. Verbs like engage and influence are not tactics; they are aspirations. “The Brussels team will submit the joint industry response to the HDV CO2 Regulation review consultation by 30 September 2026, addressed to DG CLIMA Unit C1, in support of the coalition-building pillar.”

SMART and OKRs

SMART, from George T. Doran’s 1981 article in Management Review, is the discipline most teams already know. It asks whether an Objective is Specific, Measurable, Achievable, Relevant, and Time-bound. In practice the first two letters do most of the work. Specific forces you to name the policy, the change, the actor, and the instrument.

Measurable forces you to state in advance what would count as success. The remaining three are useful as quality control on the articulation, but they rarely rescue an objective that has failed the Specific and Measurable tests.

Objectives and Key Results — OKRs — are the related discipline used in many technology organisations. An OKR pairs an ambitious qualitative Objective with three to five quantitative Key Results that confirm it has been met. Public affairs teams reporting upward into a leadership team that already runs OKRs should adopt the same structure for symmetry. Use whichever vocabulary your organisation already speaks.

The indicator at each layer — qualitative high, quantitative low

The hardest design question in any public affairs scorecard is which kind of indicator belongs at which layer. The simple rule, learned the hard way: indicators at the top of the GOST stack are qualitative and lagging — they capture meaning. Indicators at the bottom are quantitative and leading — they count motion. A scorecard that puts hard numbers at the top, because that is what leadership instinctively asks for, ends up counting tactics and calling them strategy.

At the Goal layer, the right indicator captures whether a policy position has been recognised, whether a piece of legislative text has shifted, whether a stakeholder relationship has been repositioned. These are narrative outcomes — effortful to articulate and to assess, which is precisely why they belong at the top. At the Tactic layer, indicators are quantitative and easy: papers submitted, meetings held, mentions secured. Objective and Strategy sit between — typically one outcome-style indicator on the Objective, plus one progress indicator per strategic pillar.

GOST layer	Indicator type	Character	Examples (HDV competitiveness)
Goal	Outcome indicator	Qualitative, lagging, narrative	Industrial competitiveness named as a primary objective in the Commission’s HDV review; flexibility mechanism for 2030 to 2035 targets recognised as a policy option in the Q3 2026 Commission report
Objective	One outcome + one count	Mixed, mostly lagging	Amendment X adopted in the ENVI Committee report; position paper cited in three named institutional outputs
Strategy (per pillar)	Progress indicator	Mixed, leading	Two of three coalition partners signed onto the joint submission; lead rapporteur bilateral held by Q2 2027
Tactic	Activity count	Quantitative, leading	Joint consultation response submitted by 30 September 2026; eight ENVI member bilaterals held in Q3; three trade-press placements in target outlets

The higher the layer, the more the indicator must capture meaning rather than motion. Qualitative indicators at the top are expensive to draft and slower to assess. That is why they are reserved for the layers where they matter most. A short list of carefully written qualitative indicators at the top will always outperform a long dashboard of vague qualitative indicators at the tactic level — the dominant failure mode I see in public affairs scorecards.

A short word on AI

A team with a clean GOST cascade can use AI tools usefully — to draft objective candidates from a prioritisation list, to propose indicators at each layer, to surface narrative signals at the Goal layer, and to maintain the cascade as the policy environment shifts. A team without a GOST cascade asks AI for generic objective language and gets quantitative indicators that count tactics. The framework is the precondition; the AI is the amplifier.

So the question is the one I started with, in sharper form. Before you add AI, another dashboard, or another quarterly review, can you state the goal, the objective, the strategy, and the tactic — and which indicator lives at which level? If yes, the rest is easier than it looks. If not yet, that is the work.