Statement of Purpose
Teams that cannot articulate why they exist in one sentence are teams that cannot say no. A statement of purpose gives a team the language to focus.
Overview
A statement of purpose is a team’s elevator pitch: one sentence that captures why the team exists and what it is working toward. It follows the template “Our team exists to [what we do] so that [why it matters].” The statement anchors every other decision in a team’s frame; objectives, success measures, and working agreements all flow from a shared understanding of purpose. Without it, teams default to defining themselves by their backlog rather than by their impact.
The statement doesn’t need to be permanent. In Framing, the statement of purpose lives inside a time-boxed frame and evolves as the team’s mission shifts. A product team’s purpose might change from “reduce onboarding friction for new analysts” to “expand self-service reporting for enterprise accounts” when the frame expires and a new one begins. What matters is that at any given moment, every team member can state the purpose from memory and use it to evaluate whether incoming work belongs on their plate.
The Message Map Exercise
The Message Map is a technique from Carmine Gallo for distilling a team’s purpose into a clear, spoken message. It works well as a facilitated exercise during frame creation.
Step 1: Headline Message. Draft a single sentence that captures the team’s purpose. Use the template: “Our team exists to [X] so that [Y].” Aim for something a new team member could repeat after hearing it once.
Step 2: Supporting Messages. Identify three pillars that support the headline. These are the key areas of work or value the team delivers. Each pillar should be a short phrase, not a paragraph. For example: “reliable CI/CD infrastructure,” “developer onboarding tooling,” “production observability.”
Step 3: Proof Points. Under each pillar, list 1-2 concrete examples or evidence. These ground the purpose in reality: specific projects, metrics, or user outcomes that demonstrate the pillar in action.
Step 4: Audience Alignment. Test the message against your stakeholders. Would your users, leadership, and dependent teams recognize this as what you do? If not, refine.
Step 5: Final Message. Synthesize everything into a 60-second spoken version. The full message should be: headline, three pillars with proof points, then restate the headline. If you can say it aloud in under a minute and it feels true, you have a working statement of purpose.
Resources
- Framing — statement of purpose is a required frame component
- Frame Creation Workshop — the workshop where this exercise is typically facilitated
- Carmine Gallo, “The Storyteller’s Secret” (St. Martin’s Press, 2016) — the Message Map technique originates from Gallo’s work on communication
Knowledge