Purpose & Objectives: what it is and how to measure it

Try this at your next team meeting. Give everyone a sticky note and ask them to write down the team's three most important goals right now, without conferring. Then put the notes on the wall. In teams that score high on Purpose & Objectives the notes say nearly the same thing. In teams that score low you get eight notes and fifteen different goals, and a quiet realisation that people have been pulling in different directions for months.

That exercise is the whole KPI in miniature. Purpose & Objectives asks whether the team knows why it exists and what it is working towards right now, and whether that knowledge is shared rather than held by one or two people.

Two layers: purpose and objectives

The KPI has two layers that fail in different ways. Purpose is the standing answer to "why does this team exist and for whom". It changes rarely. Objectives are the current answer to "what are we trying to achieve this quarter", and they change often. A team can have a clear purpose and fuzzy objectives (everyone knows the mission, nobody knows what to do on Monday), or sharp objectives and no purpose (everyone knows the sprint goal, nobody can say why it matters). Both show up as lower scores, and both drag on the rest of the survey, because objectives are what the process KPIs are supposed to be in service of.

In the PEAKTEAMS model this is an Input KPI, one of five conditions the team needs before any process can be judged. Clear direction sits first in that list for a reason: without it, the team cannot tell good coordination from busy coordination.

Why clear goals matter so much

The best-known finding is from Edwin Locke and Gary Latham, who spent thirty-five years studying goal setting and summarised it in 2002: specific, challenging goals lead to higher performance than vague or "do your best" goals, provided the person has accepted the goal and gets feedback on progress. The effect held across the tasks, settings and countries they reviewed. Vague goals do not simply fail to motivate; they leave people free to define success in whatever way is most comfortable.

Richard Hackman put direction first among the conditions for team effectiveness in Leading Teams (2002). His argument is that a compelling direction has to be clear about the ends while leaving the means to the team: tell people what the outcome is and why it matters, and let them work out how. Teams given detailed instructions but no clear purpose tend to comply rather than commit.

The input-process-output tradition that PEAKTEAMS is built on (Ilgen, Hollenbeck, Johnson and Jundt, 2005) treats goals as an input that shapes everything downstream. The model is a reminder that a low Purpose & Objectives score is rarely a problem on its own. It is usually the first link in a chain that ends in missed deadlines and a feeling that the team works hard without getting anywhere.

What it looks like at five, and at two

Low scores often come with a particular tone in the free-text answers: "we are busy but I am not sure it matters" or "priorities change every week". Both are worth taking literally.

How PEAKTEAMS measures it

The Snapshot survey, which takes each team member about 12 minutes and covers all 18 KPIs, asks two statements for Purpose & Objectives. Each is answered on a five-point agreement scale and the KPI score is the average across the team.

The Deep-Dive survey adds twelve more, covering mission statements, measurable objectives, stakeholder expectations, constraints and whether the purpose actually motivates, plus one reverse-keyed check ("It is often unclear what we are ultimately trying to achieve") that is flipped before scoring so that agreeing with it lowers the KPI.

Because this KPI is about shared understanding, the spread matters as much as the average. The Consensus Matrix in the report plots each survey item's average against how closely members agreed on it, so read this KPI's items together. A Purpose & Objectives item at 3.6 made of 5s from the lead and 2s from everyone else is a different problem from a uniform 3.6, and the matrix shows which one you have. Results appear only once at least five team members have answered; the owner's own answer does not count, so the lead cannot pull the score up alone.

How to improve it

• Write the purpose in one sentence and test it on a newcomer. If they cannot repeat it back, it is not clear enough to guide decisions.
• Limit current objectives to three or four and make them outcomes, not activities. Locke and Latham's finding depends on goals being specific enough that progress can be seen.
• Start every planning session by reading the objectives aloud. Thirty seconds of repetition does more for shared understanding than a beautifully formatted document nobody reopens.
• Connect each piece of work to an objective when it enters the backlog. Work that connects to nothing is either a hidden objective or waste; both are worth knowing.
• Name the stakeholders and what each one expects, in writing. Most "the goal changed" complaints are really "we never knew what they wanted".
• Re-run the sticky-note test every quarter. It is free, takes five minutes and tells you whether the survey score is moving for the right reason.

Related KPIs

Purpose & Objectives is closest to Values & Vision, which covers the longer horizon: where the team is heading and the principles it will not trade away. Whether the goals are actually pursued day to day shows up under Motivation & Focus, and whether the structure lets people act on them is Team Organization. A team with high purpose and low focus knows exactly where it wants to go and keeps getting interrupted.