How to Set Goals That Your Organisation Actually Achieves
13 Jun 2026 · 7 min read
Goal-setting is a ritual in most organisations, and like many rituals it is performed more reliably than it is understood. The annual or quarterly process of setting objectives feels productive because it generates alignment, visible commitment, and a shared vocabulary for what the organisation is trying to do. What it frequently fails to generate is achievement. The gap between stated goals and realised ones is wide in most organisations, and the explanations offered — lack of focus, insufficient accountability, changing circumstances — are usually symptoms rather than causes. The cause is almost always in how the goals were set.
The specificity problem
The most common goal-setting failure is insufficient specificity. Goals stated as directions — improve customer satisfaction, strengthen the team, grow revenue — are not goals in any meaningful sense. They are intentions, and intentions without specification cannot be achieved because there is no shared understanding of what achievement looks like. When the end of the period arrives and the question is asked whether the goal was met, there is no clear answer, which means there is no clear accountability, which means the goal did not change behaviour in the way a goal is supposed to.
Specificity requires three elements: a concrete outcome, a measurable indicator, and a time frame. Not improve customer satisfaction, but achieve a satisfaction score of above eighty-five by the end of September as measured by the post-engagement survey. Not grow revenue, but reach monthly recurring revenue of one crore by December with no more than twenty percent of it from any single client. These formulations are harder to write and they are also harder to escape, which is precisely the point. A goal that cannot be escaped is a goal that changes what people do.
The ownership problem
Organisational goals that are owned by the organisation rather than by a specific person are owned by no one. When a goal is assigned to a team or a function without a named individual who is personally accountable for its achievement, the accountability diffuses. Everyone is responsible and therefore no one is. The goal gets referenced in meetings, included in updates, and largely not driven by anyone specific.
Every goal that matters should have a single named owner — not a team, not a function, one person whose role it is to drive the work, surface the obstacles, and be the accountable party when the review happens. Other people contribute, but ownership is singular. This is uncomfortable to assign and it is what makes goals real.
The connection problem
Organisational goals fail when there is no connection between the stated goal and the daily work of the people who must achieve it. A quarterly objective set at the leadership level remains at the leadership level unless it is translated, explicitly, into what each team and each individual should be doing differently as a result. This translation is rarely done well because it requires more effort than setting the goal itself, and the people responsible for it are usually the same people who set the goal and who have moved on to the next agenda item.
The test for whether this connection has been made is simple: ask someone three levels below the leadership team what they are working on this week and why. If their answer connects clearly to an organisational goal, the connection has been made. If it does not, the goal exists in a layer of the organisation that is not actually driving the work. Goals that do not reach the level of daily activity are aspirations, not strategies.
The review cadence
Goals that are reviewed annually are not goals. They are hopes. Review cadence is the mechanism that converts a stated goal into a performance driver, because it is the cadence that creates the feedback loop between what is happening and what needs to happen. Monthly reviews are the minimum for goals with quarterly time frames. Weekly check-ins on the leading indicators that predict whether the goal will be achieved are what high-performing organisations actually run.
The purpose of the review is not to report on the goal. It is to identify what is blocking progress and remove the block. A review that surfaces an obstacle and takes no action is worse than no review at all — it creates the impression of accountability without the substance. The question that should close every goal review is not how are we doing but what needs to change in the next two weeks to keep us on track, and who is responsible for making that change. That question is what makes goal-setting a driver of organisation performance rather than a calendar obligation.
Where AI changes the picture
AI does not change what makes a good goal, but it changes the information environment in which goals are tracked. When reporting is automated and current rather than manually assembled and periodic, leaders see the state of progress on their goals in near real time rather than at the point someone has compiled a report. Problems surface earlier. Corrections happen sooner. The feedback loop that reviews are designed to create is compressed. This is one of the less-discussed benefits of operational AI — not a direct capability improvement but an improvement in the quality of the information that goal management depends on, which improves the quality of goal management itself.
Ready to put this thinking into practice?
Request a consultation. We will respond within one business day.
Request a Consultation