An Objective gives a team direction. It describes a meaningful change that matters to the strategy and helps people decide where to put their effort.

The wording matters, but it comes last. First, the team needs to agree on the change it wants to create.

Are we naming the change or prescribing the solution?

“Migrate the legacy platform” may be important work. It is not automatically an Objective.

Ask what problem the migration should solve. What would become possible if it succeeded?

For example:

Enable product teams to deliver customer improvements safely and independently.

The migration might be part of the work. It is not the reason for the work.

A useful question is:

Would this still be our Objective if our preferred solution became impossible tomorrow?

If the answer is no, you are probably describing an initiative.

How certain are we?

Objectives do not all carry the same level of certainty.

  • A committed Objective describes a result the organisation intends to achieve.
  • An aspirational Objective points towards a meaningful state that has not yet been achieved.
  • A learning Objective tests an assumption before the organisation commits further.

This distinction matters. An uncertain hypothesis should not be presented as a delivery promise. Equally, routine delivery should not be dressed up as ambition.

Questions worth asking

Before agreeing on an Objective, test it with the people who will need to make it real.

  • Is it important enough to justify the time and capacity it will require?
  • How does it contribute to the wider strategy?
  • What will we choose not to do because this is more important?
  • Does it describe a change that people can understand and care about?
  • Has it improved because the affected teams and stakeholders challenged it?
  • Does it require a real collective effort, or could one person achieve it alone?
  • What decisions will people make differently because this is the Objective?
  • When will we review whether it remains the right direction?

An Objective needs a clear review point, usually a cycle or a relevant milestone. Without one, it is difficult to distinguish commitment from inertia.

Write the sentence last

Once the direction is clear, make the sentence simple and active.

Instead of:

Develop and implement initiatives to improve the customer experience during initial product use.

Try:

Help new customers reach their first success with confidence.

The second version does not include every detail. It should not. An Objective is not a requirements document. It gives people a shared direction while leaving room to find the best solution.

A good Objective represents a choice: the change that matters now, the trade-offs the team accepts, and the outcome it is trying to create.