Goal Core · Tactical goals · Module

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.

The idea

How it works

An initiative is bounded work. It starts, it ends, and something exists at the end that did not at the beginning. That boundary is what separates it from ongoing operations, which never finish and should not be tracked as though they might.

The most common error is naming an initiative after a desired state rather than a piece of work. “Improve customer satisfaction” cannot be completed; “rebuild the onboarding sequence” can.

Working with it

In practice

  1. 01

    Name the output, not the outcome

    What will exist when this is done? If the answer is a feeling or a number, it is not yet an initiative.

  2. 02

    Check it can be finished

    Anything that would still be running in three years is operations, and belongs in a different list.

  3. 03

    Size it against the quarter

    Initiatives longer than two quarters should be split, or their milestones treated as the real unit.

  4. 04

    Say what it depends on

    The dependency is usually what determines when it can actually start.

One level in

The components of initiatives

A component is something that exists afterwards which did not exist before — a deliverable or a mechanism, not an intention.

  1. The initiative brief

    One page: what it is, what exists at the end, and which goal it serves.

    Learn
  2. The dependency list

    What must be in place first, inside or outside the team.

    Learn
  3. The definition of done

    The agreed test for completion, written before the work starts.

    Learn

An initiative list that only grows is a sign that nothing is being finished, or that operations have been mislabelled as initiatives.