Leadership Foundations and Team Direction · Lesson 2

From Purpose to Goals: Priorities and Success Criteria

4 min read

Lesson objectives

  • Distinguish broad purpose from an operational goal and a success criterion.
  • Write a specific goal with a measure, timeframe and context-appropriate quality guardrail.
  • Use priorities to resolve work trade-offs without treating a goal-writing tool as a causal promise of performance.

Purpose Explains Why We Exist; a Goal Specifies What We Will Achieve Now

Purpose describes the value the team exists to serve, such as “make support requests easier and more reliable for customers.” A goal translates part of that purpose into a specific result over a defined period. A success criterion explains how the team will judge whether the result is acceptable. Saying “we want better service” may express broad direction, but it is not enough to prioritize work or evaluate progress.

Goals work better when they are clear, realistically challenging and supported by commitment from those doing the work, but their effects depend on factors such as task capability, feedback, complexity and context. Locke and Latham’s review summarizes decades of goal-setting research. We therefore do not treat a writing template such as SMART as a guarantee. A template may help express a goal; performance still depends on resources, capability, coordination and information.

A Useful Goal Needs a Result, a Time Boundary and a Quality Guardrail

A more useful statement is: “Within six weeks, reduce average first response time for standard tickets from 10 hours to 6 hours or less, while keeping the standard-ticket reopen rate no higher than the current 8% baseline.” These figures are part of a teaching case, not a universal service benchmark. The goal combines speed with a quality guardrail so the team is not rewarded for fast but unhelpful replies.

When setting priorities, distinguish “important” from “highest priority now.” Many activities may matter, but capacity is limited. Ask: Which work contributes to the current goal? Which dependency will block others if delayed? Which risk or quality requirement cannot be traded away? Then state what will not be done now, because a priority list that excludes nothing is not a real ordering.

Lesson summary

Purpose clarifies shared value; a goal translates it into a specific result over a defined period with success criteria. Goals are not magic: they require capability, commitment, feedback and context, and priorities should prevent one metric from improving at the expense of quality.