Goal Core · Object

Tactical goals

The layer where strategy becomes somebody’s work. Tactical goals translate a strategic intention into named commitments with owners, resources and a way of telling whether they worked.

The term

What it is

Tactical goals sit between a strategic goal and the work itself. A strategic goal states what the organisation intends to become; a tactical goal states what a particular part of it will do about that, by when, and with what.

The distinction matters because conflating the two is one of the more reliable ways to make a strategy undeliverable. A strategy expressed only as ambition cannot be handed to anyone, and a plan expressed only as tasks cannot be judged for whether it serves the strategy at all.

The translation between the two is not a matter of subdivision. Drucker’s original argument for management by objectives, and the catchball practice in Hoshin Kanri, both treat it as a negotiation: the level that will do the work has information the level that set the goal does not, and the goal should change in light of it.

This object names a level of decision, not a point in time. How it relates to the horizon objects is set out once, on the core page: Two axes, not four boxes

Why it earns a place

What goes wrong without it

01

Strategy that never becomes tactical does not happen

Execution research keeps finding the same gap — not disagreement with the strategy, but no one able to say which part of the business is supposed to change because of it.

02

A goal without an owner is a hope

Assigning a tactical goal to a function assigns it to nobody. It advances only if someone volunteers, which happens often enough to hide the problem and rarely enough to be unreliable.

03

Unresourced goals are worse than no goals

They consume attention, generate reporting, and produce nothing — while occupying the slot a fundable goal could have used.

One level in

The modules within tactical goals

Four working areas. One does the translating, three make the result executable.

  1. Cascade and catchball

    Carrying a strategic goal down into commitments, and letting the answers come back up and change it. The upward half is the part most cascades leave out, and it is the half that surfaces what is actually possible.

    Learn
  2. Initiatives

    The named, finishable pieces of work a tactical goal resolves into. Each with a start, an end, and something that exists afterwards which did not before.

    Learn
  3. Ownership

    One named person accountable for each goal, distinct from the people doing the work and from those merely informed. Shared accountability is the most dependable way to produce an unstarted initiative.

    Learn
  4. Resourcing

    What the goal costs in money, people and attention, agreed before it is committed to. The test is whether the owner could describe the resource without checking.

    Learn

Across the framework

What it touches

  • Business CoreWhere most tactical goals land — systems, people, finance, partners.
  • Time CoreProject management and the year wheel decide sequence and load.
  • Data CoreThe measures that show whether a tactic worked, rather than merely happened.

Beyond the framework

Models worth knowing here

The Omnigoal says where this belongs and what it touches. It does not tell you how to think about it — other people have done that, and done it well. These are theirs.

  1. Hoshin kanri

    Developed in Japanese manufacturing · 1960s

    Translating a few company-level aims down through every level, and negotiating them back up before anyone commits.

    Sometimes called policy deployment. What distinguishes it from cascading targets is the second movement: each level proposes what it can actually do, and the disagreement between that and what was asked for is resolved explicitly rather than absorbed silently.

    Reach for it when
    When strategy is agreed at the top and quietly renegotiated by everyone below it as the year goes on.
    Where it stops
    It is slow, and it assumes a stable enough year that a plan negotiated in January still describes reality in June.

    Yoji Akao (ed.), Hoshin Kanri: Policy Deployment for Successful TQM, Productivity Press, 1991.

  2. Plan–do–check–act

    Walter A. Shewhart, popularised by W. Edwards Deming · 1939

    Also known as PDCA, The Deming cycle, The Shewhart cycle

    A loop that treats every change as a small experiment with a result you are obliged to look at.

    Plan the change and what you expect, make it small, check what actually happened against what you predicted, then either standardise it or start again. The discipline that matters is writing the prediction down first, which is the step most often skipped.

    Reach for it when
    For tactical goals, where the point is a short cycle and a real answer rather than a defended forecast.
    Where it stops
    It improves what exists. A loop of small corrections will refine the wrong thing indefinitely without ever raising the question.

    Walter A. Shewhart, Statistical Method from the Viewpoint of Quality Control, 1939; W. Edwards Deming, Out of the Crisis, MIT Press, 1986.

  3. Management by objectives

    Peter F. Drucker · 1954

    Also known as MBO

    Managers and their people agree objectives together, and performance is judged against those rather than against activity.

    Drucker’s argument was that an organisation only pulls in one direction if each part knows what it is contributing and has agreed to it, rather than been handed it. Nearly every goal system since — including objectives and key results — descends from this, and so do its failure modes, which Drucker himself warned about.

    Reach for it when
    When people are being measured on how busy they look rather than on anything that was agreed in advance.
    Where it stops
    Applied mechanically it becomes a paperwork exercise that rewards easily agreed objectives. Drucker later said the method works only where the strategy behind the objectives is sound, which is the harder half.

    Peter F. Drucker, The Practice of Management, Harper & Row, 1954.

These are other people’s models, named here so you can go to the source and use them properly. The Omnigoal is not affiliated with their authors and is not endorsed by them; nothing of theirs is reproduced here — no canvas, no diagram, no wording. Each is described in our own words, with the originator credited, because the framework is a place to put thinking, not a replacement for the people who did it. Model names and trademarks belong to their respective owners and are used here only to refer to the work itself.

Every model in the framework, and where each one belongs

A tactical goal that cannot be given an owner and a resource is usually not yet specified clearly enough to start. Rewriting it until it can be is quicker than discovering the problem in month three.