← All thinkings

Tactical thinking

Learning guide and study notes

What exactly happens next? Use it to turn intent into executable steps.

What you will learn

  • Turn a broad intention into an executable next move.
  • Connect a local action to the larger objective.

What is it?

Tactical thinking bridges the gap between high-level intent and immediate execution by translating goals into concrete “if–then” situational triggers, clear owners, and observable completion states.

Implementation intentions link a specific anticipated cue to a specific action: if X happens, then do Y.

Core question
What exactly happens next?
When to use it
Use it to turn intent into executable steps.

Tools and techniques

Key techniques

  • If–then implementation intentionsLink a concrete situational cue directly to an owner and response: if X happens, then do Y.
  • Observable completion criteriaReplace vague intentions with a verifiable next action, time window, and done state.
  • Cue visibility and exception routingEnsure the trigger signal is unmistakable during handovers and define what happens when rules fail.

Procedure: think it through step by step

Work through these steps in order, applying the tools above. Write down the answer to each step before moving on.

  1. Name the outcome

    Replace vague intent with an observable goal and immediate next action. [1] Source: Gollwitzer — Implementation Intentions (1999) (opens in a new tab)

  2. Write an if–then cue

    Specify the situation, owner, time or place and response. [1] Source: Gollwitzer — Implementation Intentions (1999) (opens in a new tab)

  3. Execute and adjust

    Check whether the cue occurred and the action worked; revise the plan if not. [1] Source: Gollwitzer — Implementation Intentions (1999) (opens in a new tab)

Try it now

Turn one postponed task into an if–then action with a cue, owner and observable completion condition.

Visual guide

WorkflowFrom situation through deliberate steps to output
Workflow chart: Tactical thinking
Read the workflow as text
  1. SituationAlerts remain unacknowledged during handover.
  2. Step 1Name the outcome
  3. Step 2Write an if–then cue
  4. Step 3Execute and adjust
  5. OutputTrack acknowledgment and resolution, then refine the handover rule.
Mind mapFour connected questions to keep in view
Mind map: Tactical thinking
Read the mind map as text
Tactical thinking
Desired outcome
Situation cue
Named action
Exception path

Detailed examples

Core scenario

Situation: Alerts remain unacknowledged during handover.

How to apply: If an alert is unowned after the agreed window, assign an on-call owner and invoke the escalation path.

Outcome: Track acknowledgment and resolution, then refine the handover rule.

02 / Turning “improve release coordination” into a cutover checklist

Situation: A post-mortem concludes the team should “communicate better during releases.”

How to apply: Rewrite the vague intent as if–then steps: if T-15 minutes arrives and smoke tests are green, the release lead posts the cutover command; if p95 errors exceed 1% for 3 minutes, trigger rollback.

Outcome: Eliminate hesitation during live cutovers because every trigger and owner is pre-agreed.

03 / Following through on post-incident action items

Situation: Remediation tasks agreed in post-mortems repeatedly slip once normal feature work resumes.

How to apply: Bind each remediation item to sprint planning: if a severity-1 incident review closes, then its top prevention task enters the next sprint with a named owner and test check.

Outcome: Close high-priority prevention work on schedule instead of accumulating an unowned backlog.

Illustrative examples showing how the lens changes decisions; not measured outcomes.

Practice and keep learning

Watch out: ‘Respond better’ is not an if–then plan; a rigid rule also needs an exception path.

Getting better at it

  • 01 · Learn the foundationSpot vague verbs like “monitor closely,” “align with,” or “be careful” and replace them with a concrete cue, actor, and action.
  • 02 · Build daily fluencyEnd every meeting by stating each action item as: “When [trigger/time], [owner] will [action], verified by [observable output].”
  • 03 · Master under pressurePair clear tactical rules with an explicit exception escalation path so operators know when to stop following the script and call for re-orientation.

Combine this lens with others rather than relying on it alone. Browse all thinkings

Review and make it your own

The idea to remember

A tactic turns an objective into a specific move with a trigger, constraints, and observable completion.

An outline for your notes

Use a problem of your own. Write a short answer to each prompt, then return after trying the method.

  • Objective: state the local result and why it supports the wider direction.
  • Move: specify who acts, when, and under which constraints.
  • Completion: define the observable result and exception route.

Check your understanding

Answer from memory before opening the suggested answer.

Why is “improve the rollout” not yet a tactic?

Compare with a suggested answer

It lacks an actor, trigger, concrete move, and success condition. Specify a bounded change such as a canary step with observable acceptance criteria.

Can a successful tactic undermine strategy?

Compare with a suggested answer

Yes. A local win can consume resources or create commitments that conflict with the wider objective. Check fit before optimizing execution.

Sources

These sources support the method; the examples and exercises are original teaching illustrations.

  1. Gollwitzer — Implementation Intentions (1999)Original research on situation–response plans.
  2. Air University — OODA LoopLinking action with feedback under changing conditions.
All thinkings →