Goals That Create Momentum

Business owners are not short of goals. January produces them, so does every strategy day, every coaching session and every quiet Sunday morning with a notebook. What is usually missing is the architecture that turns a goal into something that changes what happens on a Tuesday.

Most goals fail quietly. Nobody abandons them; they simply stop being referred to, and by March the business is being run by whatever arrived in the inbox that morning.

Why most goals do not stick

The usual explanations are lack of clarity or insufficient ambition. Both matter, but neither is the main problem. Goals mostly fail because they are disconnected from the decisions that actually determine the outcome. You can have an ambitious, well-worded target on the office wall and still make choices every week that move the business away from it, because the target never got translated into behaviour.

A goal of "grow revenue 25 per cent" tells you nothing about what to do on Tuesday morning. That gap — between the outcome and the activity — is where most goal-setting collapses.

Outcome goals and process goals

An outcome goal describes a result: revenue, margin, headcount, a completed project. A process goal describes an activity you control: conversations held, proposals sent, reviews completed.

You can only influence outcomes. You can control processes. Every outcome goal therefore needs a process goal attached to it, and the process goal is the one that goes in the diary. Owners who only track outcomes end up oscillating between motivation and guilt, because the number moves for reasons they cannot directly act on.

A worked example: turning a number into a Tuesday

The figures are illustrative. A business turns over £600,000 from 80 clients at an average of £7,500 a year. The owner wants £750,000 next year.

• The gap is £150,000, which at £7,500 average value is 20 net new clients.
• Client losses run at roughly 10 per cent a year, so about 8 clients will leave. The real requirement is 28 wins, not 20.
• Historic close rate on proposals is about 1 in 4. So 28 wins needs roughly 112 proposals in the year.
• That is a little over 2 proposals a week, every week, allowing for holidays.
• If roughly one in three qualified conversations turns into a proposal, the underlying activity is 6 to 7 conversations a week.

The goal is no longer "grow 25 per cent". It is "six conversations and two proposals a week", which is something you can put in a diary, delegate part of, measure on a Friday and notice missing after seven days rather than seven months.

It also exposes whether the goal is realistic. If the business currently produces two conversations a week and nobody has capacity for more, the plan is not a plan — it is a wish with a number on it. Better to find that out in January than in October.

Ninety days, not twelve months

Annual goals are too distant to create urgency and too big to review usefully. Ninety days is short enough to hold attention and long enough to finish something that matters. A planning session, twelve weeks of execution, then a review and reset.

The discipline that makes it work is the review. A quarter that ends without an honest look at what moved and what did not is just three months of activity.

Make the gap visible

Goals kept in a document you open once a quarter have no effect on behaviour. What matters is not the format but the frequency of contact. A number on a whiteboard that you walk past daily will outperform a beautifully structured plan in a folder.

Measurement works not because it is motivating in itself, but because it makes the gap between where you are and where you said you would be impossible to ignore. When the gap is invisible, it is easy to ignore for months.

Accountability is structural, not moral

Owners who make consistent progress almost always have someone asking the question: did you do what you said you would do? A coach, a peer group, a business partner, a non-executive. The mechanism matters more than who provides it.

This is not about willpower. It is that a commitment made to another person, with a date attached and a scheduled point at which it will be discussed, behaves differently from a commitment made privately to yourself.

Lead measures and lag measures

Revenue, profit and client numbers are lag measures. They tell you what has already happened and they move slowly, which makes them useless for steering week to week. Conversations held, proposals sent, jobs completed on time, quotes turned round within 48 hours — these are lead measures. They move immediately and they cause the lag measures.

Track one of each per goal. The lag measure tells you whether the strategy is right. The lead measure tells you whether anyone is actually doing the work. Owners who only watch lag measures spend six months believing the plan is working, then discover it never started.

When to change the goal

Changing a goal because it is uncomfortable is how goals die. Changing one because the underlying assumption turned out to be wrong is good management, and the two are easy to confuse in the moment.

The test is whether something has changed in the facts. If the close rate is 1 in 8 rather than 1 in 4, the activity requirement has doubled and the goal needs rebuilding on the real number. If nothing has changed except your appetite, keep the goal and fix the execution.

The checklist

• Write the outcome as a number with a date. Revenue, margin, profit, clients, whatever it is — one figure, one deadline.
• Work backwards to the weekly activity. Do the arithmetic above with your own conversion rates. If you do not know your conversion rates, that is the first project.
• Sense-check the capacity. Can the business actually deliver the extra work? If not, the delivery constraint is the real goal.
• Cut to three goals for the quarter. Not ten. If you have written ten, you have written a task list.
• Put the activity in the diary as recurring time. Not "find time for sales" — Tuesday and Thursday, 9 to 11.
• Choose one number per goal to track weekly. Visible, simple, and looked at whether or not it is going well.
• Book the weekly ten-minute review now. Did I do what I said? If not, why not? What changes next week?
• Name who holds you to it — and tell them, with the dates.
• Diarise the 90-day review and reset before the quarter starts.

The questions to sit with

• Is this goal actually yours, or is it what you think you should want, or what someone else said was possible?
• Out of 10, how confident are you that next week will look different because of this goal? If it is below 6, the architecture is missing.
• What would you have to stop doing to make room for the activity this goal requires?
• What is the goal underneath the number — what does hitting it actually change about your life?

Common questions

How ambitious should the goal be? Ambitious enough that the current way of working will not deliver it. If you can hit it by carrying on as you are, it is a forecast, not a goal. If it needs everything to go right, it is a fantasy and the team will read it as one.

What if I miss the quarter? Review it properly rather than replacing it with a fresh one. A missed quarter usually tells you something specific: the activity never happened, the conversion assumption was wrong, or capacity ran out. Each of those has a different fix, and you only find out which by looking.

Should the team have the same goals? They should have their own, derived from yours, expressed as things they control. A delivery manager cannot control revenue. They can control on-time completion and rework, which feed it.

Do I need to write it all down? Yes. Not for ceremony — because an unwritten goal quietly edits itself to match what happened.

Momentum comes from short cycles, visible numbers and someone asking the question. Not from ambition, which every owner already has in sufficient quantity.