Thematic Goal Workshop: Setting the Rallying Cry

Definition

A Thematic Goal is a single, overarching, non-quantitative priority that a team commits to for a defined period (e.g., a quarter, a year). It is not a permanent objective and does not replace ongoing operational responsibilities — rather, it clarifies where the team places "extra emphasis" when tradeoffs arise. Examples include "Improve customer satisfaction," "Strengthen the team," "Increase market awareness," or "Create a single unified organization" (the latter was the case of a transportation company that had acquired multiple firms). Once a thematic goal is chosen, the team identifies 3–6 supporting objectives — the concrete initiatives or outcomes that would prove the goal has been achieved — and creates a scoreboard around those supporting objectives.

In the Book

Lencioni introduces Thematic Goals (pp. 57–60, 136–138) in the context of Achieving Commitment. The Thematic Goal Exercise asks: "What is the single most important goal that we must achieve during this period if we are to consider ourselves successful?" The book addresses three common objections. First, teams ask: "Don't we always want to improve customer satisfaction? Why single out just one goal?" The answer: a thematic goal doesn't eliminate other responsibilities; it clarifies the tiebreaker. Sales will still sell, Operations will still run operations. But when push comes to shove and resources are constrained, the thematic goal is the north star. Second, the "Specialist's Dilemma": a CFO asks, "What do I have to do with growing market share?" The answer is that team members wear two hats — their functional hat (CFO, VP of Sales, etc.) and a more important one, the "generic team member" hat, where they contribute to collective goals regardless of expertise. Third, the timeframe: it depends on the business cycle and industry — a startup might have 2–3 month cycles, a university might have yearly cycles. The book gives a concrete example: a transportation company post-acquisition chose the thematic goal "Create a single company and work as one unit" with supporting objectives including unifying the executive team, creating consistent business practices, rationalizing computer systems, and establishing one customer service approach. These supporting objectives became part of the team scoreboard.

Why It Matters

Thematic Goals solve the "United Nations Syndrome" where each team member is really a lobbyist for their own department. Without a declared unifying priority, team members make tradeoffs in private — the head of Sales deprioritizes cost control to hit revenue targets; the CFO deprioritizes growth to manage expenses — and the team never coheres. A Thematic Goal makes the tiebreaker public and legitimizes sacrifice: "The head of Engineering just gave up two engineers to bolster Sales for this quarter because we are focused on market share. That is the thematic goal." It also prevents "silo mentality" by forcing the entire team to own a single metric, not just their functional targets. For individuals, knowing the single most important thing the team is pursuing in the next period clarifies which meetings to attend, which projects to champion, and what questions to ask. It transforms commitment from abstract ("we're on the same team") to concrete ("we're unified around this goal").