A goal creates momentum when it has been worked backwards into weekly activity you control. The method is arithmetic: take the outcome you want, use your own conversion rates to find the number of conversations, proposals or jobs behind it, divide by the working weeks, and put that figure in the diary as recurring time. "Grow revenue 25 per cent" changes nothing. "Six conversations and two proposals a week" changes Tuesday.
Business owners are not short of goals. January produces them, so does every strategy day and every quiet Sunday with a notebook. What is usually missing is the architecture between the target and the behaviour. 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. Here is how to build the architecture.
Why do most goals stop mattering by March?
The usual explanations are lack of clarity or insufficient ambition. Both matter, but neither is the main problem. Goals fail because they are disconnected from the decisions that actually determine the outcome. You can have a well-worded target on the office wall and still make choices every week that move the business away from it, because the target was never translated into behaviour.
A goal that does not tell you what to do on a Tuesday morning is a wish with a number attached. The translation step is the whole job.
What is the difference between 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, quotes returned inside two days.
You can only influence outcomes. You can control processes. So every outcome goal needs a process goal attached, and the process goal is the one that goes in the diary. Owners who track only outcomes oscillate between motivation and guilt, because the number moves for reasons they cannot act on directly.
How do you turn a revenue target into a Tuesday?
An invented illustration of the shape — not a client, and not a claimed result. A business turns over £600,000 from 80 clients at an average of £7,500 a year, and the owner wants £750,000. The gap is £150,000, which at £7,500 average value is 20 net new clients. Client losses run at about one in ten a year, so roughly 8 will leave: the real requirement is 28 wins, not 20. If the historic close rate on proposals is one in four, 28 wins needs about 112 proposals in the year, which is a little over 2 a week allowing for holidays. If one in three qualified conversations becomes 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 — something you can diarise, 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. Better to find that out in January than in October. Run the same arithmetic on your own numbers; if you do not know your close rate, that is the first project, and it is a fortnight's work at most.
Why ninety days rather than 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 is just three months of activity. Our guide to 90-day planning sets out that cycle in detail.
Which numbers should you actually track?
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 inside 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 doing the work. Owners who watch only lag measures spend six months believing the plan is working and then discover it never started. Keep the numbers visible — a figure you walk past daily will outperform a beautifully structured plan in a folder, because measurement works by making the gap impossible to ignore.
Why does accountability change the outcome?
Owners who make consistent progress almost always have somebody 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 structural rather than moral. A commitment made to another person, with a date attached and a scheduled point at which it will be discussed, behaves differently from one made privately to yourself. It is most of what makes personal coaching work, and our post on building real accountability into your business covers how to create the same effect with your team.
When should you change a goal?
Changing a goal because it has become uncomfortable is how goals die. Changing it 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 changed in the facts. If the close rate is one in eight rather than one in four, the activity requirement has doubled and the goal needs rebuilding on the real number. If nothing changed except your appetite, keep the goal and fix the execution. The Rubber Band model is a useful way to think about the tension a real goal creates and why the instinct is to release it.
The checklist
- Write the outcome as one number with one date.
- Work backwards to weekly activity using your own conversion rates.
- Sense-check capacity. If the business cannot deliver the extra work, the delivery constraint is the real goal.
- Cut to three goals for the quarter. If you have ten, you have written a task list.
- Put the activity in the diary as recurring time — not "find time for sales" but Tuesday and Thursday, 9 to 11.
- Pick one lead measure and one lag measure per goal, and look at both weekly.
- Book the ten-minute weekly review now: did I do what I said, and what changes next week?
- Name who holds you to it, and tell them, with the dates.
Get the next one in your inbox
One practical, plain-English guide for business owners each week. No spam, unsubscribe any time.
Frequently asked questions
How ambitious should a goal be?
Ambitious enough that your current way of working will not deliver it. If you can hit the number by carrying on exactly as you are, it is a forecast rather than a goal, and it will not change any decision you make. At the other end, if it needs everything to go right at once, it is a fantasy and the team will read it as one within a fortnight. The practical test is the arithmetic: work the target back to weekly activity and look at the figure honestly. If the activity is somewhere between uncomfortable and just about possible with the capacity you have, the ambition is about right.
What should I do if I miss the quarter?
Review it properly rather than quietly replacing it with a fresh goal, which is the most common response and the least useful. A missed quarter almost always tells you one of three specific things: the activity never actually happened, the conversion assumption was wrong, or capacity ran out somewhere in delivery. Each has a completely different fix, and you only find out which by looking at the weekly numbers you tracked. If you did not track any, that is the finding. Rebuild the goal on whatever the real numbers turned out to be, keep the same rhythm, and start the new quarter with the correction already made.
Should the team have the same goals as me?
They should have their own, derived from yours and expressed as things they control. A delivery manager cannot control revenue; they can control on-time completion and rework, both of which feed it. Giving somebody a goal they cannot influence produces either anxiety or indifference, and usually both in turn. Two or three goals each is plenty, on the same quarterly cycle as yours so the reviews line up. Make the connection explicit when you set them, so people can see how their on-time completion figure connects to the revenue number on the wall. Otherwise it reads as arbitrary target-setting.
Do I really need to write goals down?
Yes, and not for ceremony. An unwritten goal quietly edits itself to match whatever happened, and it does so without you noticing, which is why owners often finish a quarter feeling it went reasonably well with no evidence either way. Written down with a number and a date, the goal stops moving and the gap becomes visible. Keep it short: one page for the quarter, the outcome, the weekly activity, the two measures and the review dates. Then keep it somewhere you see it without opening anything. A number on the wall gets read by accident, which is the point.
What if I do not know my conversion rates? The whole method depends on numbers I have never tracked.
Then estimate them this week rather than waiting a year for clean data. Go back through the last twelve months of sent proposals or quotes, count how many were issued and how many were won, and you have a close rate accurate enough to plan with. That is an afternoon in the sent folder for most businesses. Where the record genuinely does not exist, assume a deliberately pessimistic rate, write next to it that it is an assumption, and correct it at the first quarterly review. Then start recording properly from Monday: five columns, being date, source, proposal sent, value and outcome. One quarter of that gives you real numbers, and the plan you built on the estimate has been running the whole time.