Purpose and shared goals: why activity isn’t the same as alignment

A team can be busy, capable and full of good intentions and still not be aligned. Everyone is working hard. Nobody is idle. And yet the work pulls in slightly different directions, because the team agreed on why it exists but never translated that agreement into anything specific enough to actually guide a decision. From the outside it looks like momentum. From the inside it feels like everyone quietly doing their own version of the job.

This is not a commitment problem, and it is not usually a talent problem either. It is a translation problem, and it is a lot more common, and a lot more fixable, than most leaders assume. The teams that stay coordinated under pressure do one particular thing that others don’t: they don’t stop at agreeing on purpose. They convert it into a small number of shared, specific goals, and they keep checking that those goals still hold. That is a specific, learnable team practice, not a personality trait some teams happen to have.

What this actually buys you as a leader of your team

Leaders whose teams lack this are used to a particular kind of friction. Two capable people solve the same problem in incompatible ways because each was working from their own private sense of what mattered most. Decisions get argued over again every meeting because there is no shared reference point to settle them. Effort duplicates or, just as often, drops through the gap between two people who each assumed the other had it. None of this looks like a purpose problem when it’s happening. It looks like poor communication, or a personality clash, or someone not pulling their weight. Usually it is none of those things. It is a team navigating without a shared map.

Leaders whose teams have done this work get something specific in return: a fast way to settle disagreement. When a genuine shared goal exists, a trade-off that would otherwise take a long meeting to resolve can often be settled by asking which option serves the goal better. This is the practical payoff of purpose and shared goals: not motivation in the abstract sense, but faster, more consistent decision-making under exactly the conditions, time pressure, ambiguity, competing demands, where teams most need it and are least likely to have it.

Why it matters

Before the research, it helps to see the shape of the idea in miniature. Purpose is rarely a single statement. It is a cascade, narrowing from broad intent down to the specific things people do on an ordinary Tuesday (The Open University, 2011).

A team’s purpose narrows as it moves from broad intent to daily action. The exercises in this chapter work mainly on the middle layers, translating vision and mission into a small number of shared goals, but the same logic extends further down, into the objectives and targets that make up an ordinary working week.

The rest of this section, and Exercise 2 in particular, is really an attempt to do the middle part of that cascade properly: turning vision, mission and values into aims or goals specific enough to coordinate around. That is where Hackman’s, Katzenbach and Smith’s, and Locke and Latham’s research becomes directly useful.

J. Richard Hackman, whose research underpins much of what is known about what makes teams effective, placed a compelling direction as one of the small number of conditions a team cannot succeed without. Not a vague sense of mission, a direction specific enough to energise the team and clear enough to let members make their own judgement calls without checking in constantly (Hackman, 2002). Direction that is too vague does the opposite of what leaders often intend: rather than giving people freedom, it forces them to guess, and different people guess differently.

Katzenbach and Smith’s long-running research on team performance drew a distinction that has held up well since: the difference between a working group and a real team is not effort or talent, it is whether members share specific performance goals they hold themselves mutually accountable for, rather than simply working under a common manager toward a common mission (Katzenbach and Smith, 1993). A working group can have an excellent mission statement on the wall and still not be a team, in their sense, if that mission was never broken down into anything specific enough to coordinate around.

Locke and Latham’s goal-setting research, built up over more than three decades and among the most replicated findings in organisational psychology, found a consistent pattern: specific, appropriately difficult goals produce better performance than vague or easy ones, and “do your best” is reliably one of the weakest instructions a leader can give, precisely because it sets no clear bar against which effort can be judged (Locke and Latham, 2002). Applied to a team rather than an individual, this means a purpose statement alone is doing very little work. The performance gain shows up once purpose has been broken into goals specific enough that two different people would make the same call.

Shared mental models research adds the mechanism for why this matters more in teams than in individual work. Mathieu, Heffner, Goodwin, Salas and Cannon-Bowers found that teams whose members hold congruent mental models of the task and of each other coordinate more effectively and perform better, particularly under time pressure or when facing something novel, precisely the conditions where there is no time to stop and ask (Mathieu et al., 2000). A shared goal is one of the fastest ways to build a congruent mental model, because it gives everyone the same answer to “what matters most right now” without requiring a conversation every time the question comes up.

There is a caution worth sitting with, though, because it is easy to treat goal-setting as something you can only do too little of. Ordóñez, Schweitzer, Galinsky and Bazerman reviewed decades of goal-setting research and found a consistent set of side effects when goals are applied carelessly: narrowed attention that causes people to miss things outside the goal’s frame, a tendency toward shortcuts or even unethical behaviour when a goal is set just out of reach, and reduced learning in tasks that are novel or complex, because a specific goal can push people toward the fastest path rather than the best one (Ordóñez et al., 2009). For a team, the practical implication is not to avoid specific goals. It is to keep revisiting them. A goal that made sense when it was set can quietly become the wrong goal as the situation shifts, and a team that treats its goals as fixed rather than living is exposed to exactly the failure mode this research describes.

Three states of team purpose

Most teams sit somewhere on a short spectrum between purpose that is merely assumed and purpose that has actually been translated into something specific enough to coordinate around. Each state looks reasonable from the inside, which is part of why teams can sit in the weaker states for a long time without noticing.

Most teams believe they are further along this table than they actually are, largely because a stated purpose feels complete even when it has never been tested against a real decision. The exercises below are built to run that test.

Purpose clarity and goal specificity

The three states above describe a progression, but progression implies a single line, and in practice purpose and goals don’t always move together. A team can have crystal-clear purpose and still lack specific goals. A team can have painfully specific goals and still lack any real clarity about why they matter. Treating the two as one continuum hides this, and hiding it is exactly what lets a team mistake one kind of clarity for the other.

Plotted as two separate axes, purpose clarity and goal specificity produce four recognisable patterns rather than a single line from unclear to clear. Wanderers are low on both: no real direction and nothing specific to point to either, so the team drifts and every decision starts from scratch. Task Mills have specific goals without clear purpose: busy, productive, ticking things off, but pulling in different directions because nobody has agreed what any of it is actually for. Preachers have the opposite problem: purpose that everyone can recite fluently, delivered with real conviction, but never translated into anything specific enough to act on, so people nod along and then quietly do their own thing. Aligned teams have both: a clear why and a small number of specific goals that everyone can point to (See header image for the visual on this)

Most teams assume they know which pattern they’re in. Few have actually checked. The exercises that follow build purpose clarity first, in Exercise 1, and goal specificity second, in Exercise 2, deliberately in that order, because a team that skips straight to specific goals without doing the purpose work first risks becoming a well-organised Task Mill rather than a genuinely aligned one.

Five practices for building purpose and shared goals in your team

Exercise 1: The purpose round

Overview: Teams routinely assume they agree on why they exist because no one has said otherwise, which is a weak basis for agreement. Making each person’s private version visible, before discussing it, is what actually surfaces the gap (Weick, 1995, on how groups construct shared meaning through explicit rather than assumed exchange).

Steps:

1. Give the team a single prompt: in one sentence, why does this team exist right now.
2. Ask everyone to write their own answer silently, without conferring, and put a time limit on it so people write their instinct rather than a polished version.
3. Collect every answer and read them aloud without attributing them to anyone by name.
4. As a group, cluster the answers: which ones are essentially saying the same thing, and which are genuinely different.
5. Where real differences show up, discuss them directly rather than smoothing over them. The disagreement is the useful part.
6. Draft a single shared version together, and check it against the original answers: does it capture what people actually meant, or is it a compromise that satisfies no one fully.

Variations: For a team meeting for the first time, run this before any work is assigned. For an established team, run it as a check rather than an introduction, since the gap that shows up in an established team is often more revealing precisely because members assumed they’d already resolved it. If the team prefers a structured template over blank sticky notes, the Team Canvas in Andi’s canvas collection lays purpose, values, goals and roles out on a single page, and works well as a scaffold for a team running this kind of session for the first time.

Why it matters: This exercise makes the assumed-purpose trap visible in real time. Leaders are often startled by how much variation exists even among people who have worked together for years, because the topic simply hadn’t come up directly before.

Exercise 2: The three-to-five translation

Overview: A shared purpose statement is not yet a shared goal. Locke and Latham’s research is specific about what makes a goal effective: it needs to be concrete enough that two people would recognise the same outcome as success, and difficult enough to require real effort rather than being achieved by default (Locke and Latham, 2002). This exercise works the middle of the purpose pyramid introduced above, turning vision, mission and values into aims or goals. For teams whose work spans several layers of complexity, the same translation logic can be pushed one level further, from goals into objectives and the day-to-day targets a specific piece of work is measured against, but the middle layer is usually where the biggest coordination gains sit, and where most teams should start.

Steps:

1. Starting from the team’s agreed purpose, brainstorm every goal that could plausibly sit underneath it, without filtering at this stage.
2. As a group, test each candidate goal against one question: could two different people look at the same piece of work and agree on whether it met this goal. If not, it isn’t specific enough yet. One practical way to run this test is the Wildly Important Goal format from the 4 Disciplines of Execution methodology: from current state to future state by a specific date. A goal that can’t be written in that shape usually isn’t specific enough yet (McChesney, Covey and Huling, 2012).
3. Rank the surviving goals by what would matter most to the team’s purpose over the next quarter.
4. Narrow the list to three to five goals. Resist the pull to keep more; a longer list stops functioning as a shared reference point and starts functioning as a task list.
5. For each goal, agree on what evidence would show progress, not just completion.
6. Write the final goals somewhere the whole team can see, not somewhere they need to search for.

Variations: For teams with genuinely divergent workstreams, it can help to draft goals in smaller subgroups first, then bring them back for the full team to stress-test against the specificity question in step two. For a fuller treatment of turning a goal like this into daily execution, see how can I get my team aligned and more focused?, which develops the full 4DX methodology.

Why it matters: This is the step most teams skip. They stop at a purpose statement because it feels sufficiently agreed, without testing whether it actually tells anyone what to do differently on a Tuesday afternoon. Once the team has settled on its three to five goals, this is also a natural point to fold them into a wider team charter, alongside roles, decision rights and working norms; the Team Charter series is a fuller guide to building that broader document.

Exercise 3: The trade-off test

Overview: Goals that are genuinely shared should produce the same decision from different people faced with the same trade-off. This exercise tests that directly, rather than assuming it, which is where Katzenbach and Smith’s distinction between a working group and a real team becomes something you can actually check (Katzenbach and Smith, 1993).

Steps:

1. Write two or three realistic trade-off scenarios the team is likely to face, drawing on real recent decisions if possible rather than hypothetical ones.
2. Ask each team member to decide, independently and without discussion, what they would choose in each scenario, based only on the team’s stated goals.
3. Collect and compare the answers before any discussion happens.
4. Where the team converges, that’s a working goal. Note it and move on.
5. Where the team diverges, don’t treat it as a personality difference. Go back to the goal itself and ask whether it is actually specific enough to have produced a shared answer.
6. Revise the goal until a repeat of the test produces consistent choices.

Variations: This works well as a recurring quarterly check even after goals feel settled, since goals that were once specific enough can quietly become ambiguous again as the work evolves.

Why it matters: This is the exercise that catches the gap between goals that sound shared and goals that actually function as shared. A team can recite the same words and still make different decisions, and this is the fastest way to find out which is happening.

Exercise 4: The visible progress board

Overview: Locke and Latham’s research treats feedback as a condition for goal-setting to work at all, not an optional extra: goals without a visible way to track progress against them lose their power to guide behaviour over time (Locke and Latham, 2002).

Steps:

1. Build a shared board, physical or digital, listing the team’s three to five goals.
2. Agree on one simple, honest way to show progress against each: a status colour, a short note, a percentage, whatever the team will actually keep updated.
3. Update it together weekly rather than leaving it to one person, so ownership of the goals stays distributed.
4. Open one recurring meeting a week by looking at the board before anything else is discussed.
5. Ask two questions every time: what’s moved, and what’s at risk of not moving.
6. Resist turning this into a status report for the leader. It works because the team owns it, not because it’s being checked.

Variations: For distributed or hybrid teams, an always-visible digital board with a short async weekly update can work as well as a synchronous review, provided the habit of actually looking at it together is preserved.

Why it matters: Goals that live only in a document from a planning session fade from attention within weeks. Visibility is what keeps the goal doing its job as a live reference point rather than becoming background noise. This is a light-touch starting point; for a fuller treatment, including the distinction between lead and lag measures and a weekly cadence of accountability to sit alongside the board, see how can I get my team aligned and more focused?

Exercise 5: The quarterly reset

Overview: Ordóñez and colleagues’ research on the side effects of goal-setting is a direct warning against treating goals as fixed once agreed: goals set for one context can actively mislead a team once that context has moved on (Ordóñez et al., 2009).

Steps:

1. On a set cadence, ideally quarterly, block time specifically to revisit the team’s goals rather than folding this into a regular status meeting.
2. Ask, for each goal, one honest question: does this still reflect what the team’s purpose actually requires right now.
3. Where the answer is yes, keep the goal and move on without labouring the point.
4. Where the answer is no, or uncertain, discuss what’s changed and whether the goal needs to be revised, replaced, or retired outright.
5. Be willing to genuinely retire a goal rather than quietly letting it become background noise nobody tracks any more.
6. Re-run the trade-off test (Exercise 3) on any revised goal before considering it settled again.

Variations: A lighter monthly version, checking only for major shifts, can sit alongside the deeper quarterly reset for teams operating in especially fast-moving conditions.

Why it matters: Purpose and goals are not a one-off exercise from a kickoff meeting. Teams that treat them as permanent are the ones most exposed to the narrowing, misdirected effort that goal-setting research warns against.

Exercise wrap up

These five exercises move through the same progression: surface what’s actually assumed, translate it into something specific, test whether it genuinely produces shared decisions, keep it visible, and revisit it before it goes stale. Running even two or three of these consistently will do more for a team’s coordination than a single, well-produced strategy offsite. Not every week allows for a full exercise, which is where the lighter practices below come in.

Five micro-practices to start today

• At the start of your next team meeting, ask each person to state in one sentence what the team’s top priority is this month. Notice, without commenting yet, where the answers diverge.
• Before assigning a piece of work, ask yourself how it connects to one of the team’s stated goals. If you can’t answer quickly, the connection is probably less clear than you assumed.
• When two team members disagree about an approach, ask which option serves the team’s stated goals better before anything else. If the goals don’t settle it, that’s useful information about the goals, not just the disagreement.
• Once this week, look at whatever the team is currently tracking progress against. Ask whether it’s still telling anyone anything, or whether it’s become background noise nobody actually reads.
• The next time you’re tempted to add a new goal on top of the existing ones, ask what you’d retire to make room for it. A longer list of goals is rarely a stronger one.

Conclusion

Purpose gives a team its reason for being. Goals are what make that reason usable on an ordinary working day, when two good options are in tension and someone has to decide quickly. Teams that stop at purpose alone are not short on commitment. They are short on translation, and translation is a specific, repeatable practice rather than a single conversation to have once and move on from. The teams that keep this current, through explicit goals, regular visibility, and honest quarterly resets, are the ones whose coordination holds up under exactly the pressure that exposes everyone else.

Reflective questions

• If you asked each member of your team, separately, what the team’s top priority is right now, how many different answers would you get?
• Where in your team’s recent work has a decision taken longer than it should have because there was no shared goal to test it against?
• Which of your team’s current goals would survive an honest question about whether it still reflects what the work actually needs?

Explore further

• • How can I get my team aligned and more focused? (4DX Methodology), the fuller operational playbook, wildly important goals, lead measures, scoreboards and a weekly cadence of accountability that several of this article’s exercises draw on.
  • How can I set boundaries with my team that create clarity and improve performance?, on mapping the decision rights and working boundaries that sit alongside shared goals.
  • Team Dynamics Framework, for how purpose and goals sit alongside the other conditions that shape team performance.
  • Managing vision and purpose, on the leader’s own role in keeping purpose alive between sessions, through repetition, consistent action and checking how the message is actually landing downstream.
  • Driving buy-in, on turning nodded agreement into genuine commitment, the difference between a goal the team quietly accepted and one it will actually act on.

Sources

Hackman, J.R., 2002. Leading Teams: Setting the Stage for Great Performances. Boston: Harvard Business School Press.

Katzenbach, J.R. and Smith, D.K., 1993. The Wisdom of Teams: Creating the High-Performance Organization. Boston: Harvard Business School Press.

Locke, E.A. and Latham, G.P., 2002. Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American Psychologist, 57(9), pp.705-717.

Mathieu, J.E., Heffner, T.S., Goodwin, G.F., Salas, E. and Cannon-Bowers, J.A., 2000. The influence of shared mental models on team process and performance. Journal of Applied Psychology, 85(2), pp.273-283.

McChesney, C., Covey, S. and Huling, J., 2012. The 4 Disciplines of Execution: Achieving Your Wildly Important Goals. New York: Free Press.

The Open University, 2011. Understanding Marketing and Financial Information. 3rd ed. Milton Keynes: The Open University.

Ordóñez, L.D., Schweitzer, M.E., Galinsky, A.D. and Bazerman, M.H., 2009. Goals gone wild: The systematic side effects of overprescribing goal setting. Academy of Management Perspectives, 23(1), pp.6-16.

Weick, K.E., 1995. Sensemaking in Organizations. Thousand Oaks: Sage.