Ask three department heads to write down the company's top priority for the quarter. Do it independently, before they can talk to each other.
In most founder-led companies, you will get three different answers.
Not dramatically different. Nobody will write something that sounds completely unrelated to the business. But the emphasis will shift. The metric will change. One will frame it as a revenue target. One will frame it as a product milestone. One will frame it as a customer count. All three will feel confident that their version is correct, because all three sat in the same planning session and heard the same conversation.
This is the most common and most underestimated problem in company execution. Not that goals are wrong. That goals mean different things to different people, and nobody finds out until the end of the quarter when the results do not add up the way they were supposed to.
The fix is not a longer planning session or a better strategy. It is a more precise way of writing the goal in the first place.
A goal like "grow revenue this quarter" is not a goal. It is a direction. Everyone in the company probably agrees with it. Nobody is aligned on what hitting it actually looks like.
The same is true for goals that sound more specific but still leave room for interpretation. "Improve the customer experience" could mean reducing churn, increasing NPS, shortening onboarding time, or improving support response rates. Each of those is a legitimate interpretation. Each would send a different department in a different direction.
The problem is not that founders write vague goals on purpose. It is that the planning session rewards momentum over precision. When a room full of smart people is aligned and energized, it feels unnecessary to slow down and interrogate whether everyone means exactly the same thing by "grow pipeline" or "ship the new product." The alignment feels real. It is real. But it is alignment on a direction, not on a destination.
By the time the quarter starts and teams begin executing, each department head fills in the gaps with their own judgment. They are not being careless. They are doing what people do when they have a general direction and need to make specific decisions. The problem is that their judgment, applied independently across three or four departments, does not produce a unified outcome. It produces a set of locally reasonable decisions that do not fit together the way the founder expected.
A goal that every department understands the same way has four components. None of them are complicated. All of them are necessary.
An outcome statement. This is what success looks like, written as a completed result rather than an activity or an intention. Not "focus on pipeline growth" but "reach $980k in net new pipeline by end of quarter." The outcome statement describes the finish line, not the direction of travel. If you removed all the context around the goal and handed just the outcome statement to someone who missed the planning session, they should be able to tell you exactly what done looks like.
A single measurable metric. Every goal needs a number. Not a range, not a qualitative descriptor, not a metric that requires judgment to evaluate. One number that either gets hit or does not. The metric is what makes the goal verifiable. Without it, the end-of-quarter conversation becomes a negotiation about whether the goal was achieved rather than a straightforward read of what happened.
The discipline here is in resisting the temptation to add supporting metrics. Supporting metrics are useful for tracking progress, but they should not be part of the goal definition itself. The goal has one number. Everything else is instrumentation.
A single owner. Shared ownership is one of the most reliable ways to ensure a goal does not get hit. When two people own a goal, each assumes the other is more responsible for it. When three departments own a goal, each one executes toward their version of it. A goal needs one person whose name is attached to the outcome, who will be the one in the room answering for progress at every bi-weekly review.
This does not mean one person does all the work. Most meaningful quarterly goals require contribution from multiple departments. But there is a difference between contributing to a goal and owning it. The owner is accountable for the outcome. Contributors are accountable for their piece of the work. Making that distinction explicit prevents the diffusion of responsibility that kills cross-functional goals.
A deadline. "By end of quarter" is a deadline. So is a specific date within the quarter for a milestone that needs to be hit mid-cycle. The deadline is what converts a goal from an aspiration into a commitment. Without it, the urgency is always theoretical.
Put these four elements together and a goal that previously read as "grow pipeline this quarter" becomes: "Hit $980k in net new pipeline by March 31, owned by Candice." That goal means exactly one thing. There is no room for a department head to interpret it differently based on what their team is working on. Either the number is hit by the date or it is not.
Before any goal leaves the planning session, run it through a simple test.
Hand the written goal to someone who was not in the room and ask them: what would you need to do to hit this, and how would you know if you did? If their answer matches what the planning room intended, the goal is clear enough. If it does not, something in the four elements is missing or imprecise.
The most common failure modes are a metric that is too ambiguous ("improve retention" without a baseline or a target), an owner that is too shared ("sales and marketing"), or an outcome statement that describes activity rather than result ("run a pipeline growth campaign").
Each of those failure modes is fixable in five minutes during the planning session. They are much harder to fix in week eight when two departments have been executing toward different interpretations for two months.
The clarity test is also useful mid-quarter. If a goal is drifting or progress is ambiguous, it often traces back to imprecision in how the goal was originally written. Running the clarity test on an underperforming goal sometimes reveals that the problem is not execution at all. It is that nobody was entirely sure what they were executing toward.
Most meaningful quarterly goals are not owned by a single department in isolation. A revenue goal involves sales and marketing. A product launch involves product and engineering and sometimes customer success. A retention goal involves the product, support, and account management teams.
When a goal crosses departments, the four-element structure becomes even more important, because imprecision in the goal definition gets amplified across every team that touches it.
The approach that works is to define the company-level goal with full precision first, then work backward to what each department needs to contribute for the company goal to be achievable. Each department contribution gets its own outcome, metric, owner, and deadline, nested under the company goal it supports.
This is different from assigning each department a piece of the goal and assuming they will coordinate. It is starting from the outcome the company needs and explicitly designing the contributions that produce it. The distinction sounds small. In practice it determines whether cross-functional execution holds together or fragments into parallel workstreams that do not add up.
The most immediate effect of precise goal-writing is that reviews become easier. When a goal has one metric and one owner, the bi-weekly check-in on that goal takes three minutes. The percentage is what it is. The owner either has a blocker to surface or they do not. The conversation moves quickly because there is nothing to negotiate.
The deeper effect is on team behavior between reviews. When the goal is clear, department heads make better daily decisions because they have a precise target to orient toward. They do not need to check in with the founder before deciding whether a particular initiative is worth prioritizing, because the goal tells them. The clarity functions as a decision-making tool at every level of the organization.
That is the real value of a goal that every department understands the same way. Not just that the planning session felt productive. That the clarity from that session holds all the way through the quarter, shaping decisions and surfacing problems without the founder needing to be in every conversation.
FounderMove runs quarterly planning sessions that turn growth goals into precise, owned outcomes your whole leadership team understands the same way.
.jpg)
