Team Purpose & Outcomes

Write down, together with the team, the problem you solve, the few outcomes you owe this year and the work you will say no to, so that priorities stop being renegotiated in every meeting.

Team charters have mixed research support from a thin base (Mathieu & Rapp, 2009). OKRs are practice, not research (Grove, 1983; Doerr, 2018; literature review: Silva & Santos, 2024). SMART is a practitioner mnemonic with weak or contested support (Doran, 1981; critique: Swann et al., 2023). Timings and the review rhythm are rules of thumb.

Use it when:

• You are forming a team, taking over one, or the team has been given new priorities.
• People disagree about what the team is for, or work keeps arriving that nobody chose.
• You lead a project or a small business and need one page that says what you are accountable for.

Skip it when:

• Purpose is clear but nobody knows who decides what: use 4.2 Roles & Responsibilities Map.
• You are setting goals for yourself rather than a team: use 1.10 1-Year Personal OKRs.

Teams drift less when the reason they exist and the outcomes they owe are written down and agreed, rather than assumed. The most direct evidence is team charter research: teams that did chartering work early showed stronger performance trajectories, though the base is thin and the evidence mixed (Mathieu & Rapp, 2009). The goal formats borrowed here are practitioner craft. OKRs come from Grove's (1983) management practice at Intel, popularized by Doerr (2018), and are thinly researched as a method of their own. The measurable, time-bound phrasing echoes SMART, a mnemonic from a practitioner article (Doran, 1981), not a validated method.

So the page spends its space on specifics, not slogans. The problem statement must name who suffers without the team. Objectives turn the mission into a few measurable outcomes with a baseline. The scope list writes down what you do not do, because an unwritten boundary gets renegotiated in every meeting. The limit: the value comes from doing the work together and revisiting it, not from the document.

Name the person who would suffer without your team and what it would cost them. Then write the mission as one sentence another team could not claim.

Strong answer: "Without this team, school principals in the municipality get supplier contracts late and pay list price, which results in budget overruns every spring. Mission: to get schools the goods they need on time at agreed prices, by running joint tenders and a simple ordering catalogue." Not: "To deliver excellence through collaboration."

Problem: "Without this team, experiences , which results in ."

Mission: "To for by ."

Illustrative example: the organization, roles and numbers are made up.

A newly appointed procurement lead in a mid-sized Swedish municipality takes over a five-person team that handles purchasing for schools. Requests arrive from everywhere, and the team cannot say what it is for.

Section 1: "Without this team, school principals get contracts late and pay list price, which results in budget overruns every spring." The beneficiaries are principals (orders arrive before term starts) and the finance department (spend it can forecast).

Section 2: three objectives. The key one: share of school purchases through the catalogue, from about one in three to two in three by December, committed.

Section 3: the team owns joint tenders and the catalogue. It does not handle building maintenance contracts (property department) or IT hardware (central IT). Gray area: urgent one-off purchases, where the team advises within two working days and the school buys.

Section 4: the monthly spend data from finance is the critical dependency; without it no savings can be shown.

Section 5: the team rewrote the mission twice in the session. Two recurring requests moved to other departments within a month.