Vision Core · Mission Statement · Module

Keeping it current

What happens when the organisation changes and the mission does not — because drift into inaccuracy is silent and revision should be an event.

The idea

How it works

Missions go out of date faster than purposes and slower than plans. The usual failure is not that the statement is wrong but that nobody noticed when it became wrong, which is a review problem rather than a writing problem.

Revision should be triggered by events rather than by the calendar. A new market, a discontinued product line, an acquisition and a material shift in where revenue comes from are all reasons the sentence may no longer describe the organisation.

Working with it

In practice

  1. 01

    Set event triggers, not an annual slot

    The events that make a mission inaccurate are the ones worth reviewing against.

  2. 02

    Revise as an event with a record

    A statement quietly reworded between versions of a deck has not been revised; it has drifted.

  3. 03

    Say what changed and why

    People notice when the mission changes. Being unable to explain it is worse than the change.

  4. 04

    Keep the superseded versions

    The sequence tells you how often the organisation has redefined itself, which is worth knowing.

One level in

The components of keeping it current

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

  1. The triggers

    The events that require the mission to be checked against the organisation.

    Learn
  2. The version record

    Each version with its dates and what prompted the change.

    Learn
  3. The explanation

    What changed and why, in a form that can be given to anyone who asks.

    Learn

A statement quietly reworded between two versions of a deck has not been revised. It has drifted.