How to build team vision, goals, and playbooks that stick

Executive overview

Teams fail to execute when there's no shared understanding of why they exist. Start with a one-to-two sentence vision — high-level, detached from goals — then layer in goals, KPIs, and playbooks in a single document.

Accountability flows from clarity: vision defines the direction, goals make it measurable, and playbooks make it actionable.

The core insight: bought-in teams outperform assigned ones — build the framework with them, not for them.

Vision: today vs. tomorrow

• Capture team purpose in one to two sentences — high level, not goal-specific
• Use a today/tomorrow table to surface the four to five most important opportunities or shifts
• Example: "Today we rely on paid acquisition; tomorrow organic search is our largest acquisition channel"
• Keep it loose enough to be durable, specific enough to be meaningful

Goals and KPIs

• Each goal needs KPIs — concrete metrics that define success or failure
• Express KPIs as a current state and a target state (e.g. 5,000 → 50,000 monthly organic visits)
• Use tables to make goals legible to both team and leadership
• Number of goals will vary by team scope; break broader objectives into sub-goals as needed

Playbooks

• Every playbook must link to a goal — no orphan projects
• List all playbooks under their parent goal in the same document
• Apply rigorous prioritisation (reference project prioritisation framework separately)
• Get more granular here than in the vision or goals

Building team buy-in

• Walk the team through the full document; invite contribution and challenge
• Ask what would make goals feel achievable: resources, budget, expertise, time
• Adjust involvement by seniority — coach senior contributors, assign and teach juniors
• Once the team is bought in, assign clear ownership for each playbook
• Share the finished document with leadership and cross-functional partners