How to write good company goals

A good company goal is one line that everyone in the company can say from memory, with a rough when, a short description of what will be true when it's done, and the evidence you'll watch to know how it's going. It names an outcome rather than an activity, it's ambitious enough to matter, and it has the right people from across the company behind it rather than one department.

That's the short answer. The longer one is below, with how I'd write a goal step by step, a set of real-world examples, the mistakes I see most often, and what to do in the hour after the goal is written, which is where most companies go wrong.

I've spent a lot of time with founders and leadership teams working on their goals, and I've come to believe that most companies don't fail because they set the wrong goal. They fail because they set a goal nobody can remember, or one that's so carefully worded that nobody dares change it when the world moves. Both are writing problems, and both are fixable in an afternoon.

What makes a company goal good?

A good company goal does one job: it gets everyone pulling in the same direction without needing to be explained every week. Everything about how you write it should serve that job. In practice, I'd test any goal against five questions.

1. Can people remember it? If someone in your company can't tell you the goal without looking it up, it isn't really their goal. Aim for a line short enough to say in one breath.
2. Is it an outcome, not an activity? "Launch a partner programme" is a piece of work. "Get a third of new customers through partners by the summer" is a goal. The outcome leaves room for the team to find the best way there.
3. Would it matter if you hit it? A good goal changes something real about the company: its revenue, its survival, its position in the market or what it's able to do next. If hitting it wouldn't change much, it's a task.
4. Does it have a rough when? Without a timeframe there's no urgency, but a goal pinned to an exact date turns every small slip into a crisis. A month, a quarter or a season is usually enough.
5. Could the whole team picture the finish line? If you asked five people what the world looks like once the goal is hit, would they describe the same thing? If not, the goal needs a description, not more precision in its wording.

How to write a good company goal, step by step

This is the order I'd work in, whether you're a founder writing the company's first proper goal or a leadership team resetting for a new year. With the right people in the room, it takes an hour or two, not a quarter.

1. Start from the outcome that would matter most

Ask the question plainly: if we could only achieve one thing in the next year, what would make the biggest difference to this company? Not the most urgent thing, and not the thing the loudest person wants, but the outcome that changes the company's position. For an early-stage startup that might be reaching product-market fit or raising the next round. For a fifty-person company it might be profitability, a new market or doubling revenue.

2. Write it in one line, in plain words

Write the goal the way you'd say it to a new hire on their first day. No acronyms, no stacked percentages, no "leveraging synergies". If you need a comma and three clauses, you've probably got two goals, or a goal and a plan for reaching it. Keep the goal and move the plan underneath it.

3. Add a rough when

Pick a timeframe that's honest about how long the outcome takes. "By the end of next year", "by the summer" and "in Q2" all work. What matters is that the team feels the clock, and that the deadline is far enough away for the outcome to be achievable but close enough that nobody can put it off.

4. Describe what's true when it's done

This is the step most companies skip, and it's the one that does the most for alignment. In two or three sentences, describe the world once you've got there. "We have more than 200 paying customers, most of them came to us without the founder selling, and the sales team runs its own pipeline." Now everyone can picture the same finish line, and the conversation about how to get there gets much shorter.

5. Say how you'll know

This is where the precision belongs. List the evidence you'll watch: the two or three numbers that tell you whether it's working, and the milestones that would show real progress. Keeping the numbers here rather than in the goal's wording means you can refine how you measure without rewriting the goal every time you learn something.

6. Test it on people who weren't in the room

Before you call it done, read the goal to three people who didn't help write it and ask them to say it back an hour later. If they can, and they understand why it matters, you've got a goal. If they can't, shorten it until they can.

Examples of good company goals

Here are some weaker goals beside a stronger version of the same intent. None of the stronger ones is perfect, and yours should fit your own company, but each one passes the five tests above.

And here are examples by situation, each with the description and evidence that would sit underneath it.

An early-stage startup finding its market

Goal: Find 20 customers who'd be genuinely upset if we disappeared, by the end of Q1.
What's true when it's done: We know exactly who our best customers are and why they buy, and they're telling other people about us without being asked.
How we'll know: Paying customers who use the product every week, referrals, and how many say they'd be very disappointed without it.

A startup preparing to raise

Goal: Be ready to raise our seed round by September.
What's true when it's done: We have the traction, the story and the deck to raise on our terms, and we're choosing between investors rather than chasing them.
How we'll know: Monthly revenue growth, retention, a shortlist of warm investor conversations and a finished data room.

A growing company that's hiring

Goal: Build a leadership team that runs the company without the founder in every decision, by the end of the year.
What's true when it's done: Each area has a leader who owns its results, decisions get made without waiting for the founder, and the founder spends most of their week on strategy and customers.
How we'll know: Senior hires made, decisions taken without escalation, and how much of the founder's diary is spent firefighting.

A company pushing for profitability

Goal: Be profitable every month from Q3 onwards.
What's true when it's done: The business pays for itself, we can choose when and whether to raise, and growth isn't paused to get there.
How we'll know: Monthly net profit, gross margin, cash runway and revenue growth staying on track.

A company moving to AI-assisted work

Goal: Every team doing its routine work with AI by the summer.
What's true when it's done: People spend their time on judgement and customers rather than admin, and we've grown without growing headcount at the same rate.
How we'll know: Hours spent on routine tasks, output per person and how many teams have changed how they work, not just which tools they've bought.

A team inside a larger company

Goal: Make onboarding something customers finish in a week, by the end of Q2.
What's true when it's done: New customers are live and using the product within their first week, and support isn't flooded with setup questions.
How we'll know: Time from signup to first real use, onboarding completion and the number of setup tickets.

The most common mistakes

• Too many goals. Every extra goal splits attention and gives the team another place to drift apart. For most growing companies, one goal for the company, or one for each team working on something genuinely distinct, is plenty.
• Activities dressed up as goals. "Launch the new website" or "roll out a CRM" are moves, not goals. Ask what outcome the activity is for, and make that the goal.
• Precision in the wrong place. A goal like "increase MRR by 18.5% quarter on quarter through improved conversion across all funnel stages" is accurate and unforgettable for all the wrong reasons. Keep the line simple and put the 18.5% in the evidence.
• A goal per department. Cascading goals down the org chart sets departments optimising against each other. A few shared goals with the right people behind each one works far better, as I argued in How to set company goals in 2027.
• Treating the goal as fixed. Conditions change. The long-term goal should be stable, but shorter-term goals should change when what you learn says they should, and changing one shouldn't feel like failure.
• Stopping at the goal. This is the big one, and it gets its own section.

Should company goals be SMART?

SMART goals, meaning specific, measurable, achievable, relevant and time-bound, have been taught on management courses for decades, and the intention behind them is good. My view is that they're useful as a checklist for the evidence under a goal, and unhelpful as a formula for the goal itself. Wrestling a goal into SMART wording takes hours, produces a sentence nobody remembers, and makes the goal feel too official to change when the market moves.

OKRs have a similar shape: the objective is the memorable part and the key results are the measures. That split is the right idea. Where OKRs tend to go wrong in growing companies is in the number of them and the cascade around them. If you're weighing up frameworks, I've set out SMART goals vs OKRs side by side, compared the alternatives to OKRs and written about OKRs and Clearahead side by side.

What to do after you've written the goal

Here's where most companies go wrong. They write a good goal, share it at an all-hands, and then everyone goes back to their to-do lists. Three months later the goal is a slide, and the team is busy with work that may or may not have anything to do with it.

A goal tells you where you're going. It doesn't tell you what's in the way. So the next question, before anyone plans a single piece of work, is simply: what's holding us back from this goal? Keep asking until you're past the symptoms and down to the handful of real constraints, put them in order, and then agree the moves that will clear the one at the top, each with one owner. I've written about how to do that in Remove constraints, don't add initiatives.

The last part is keeping it visible. A goal nobody can see progress against slowly stops mattering, so make sure the goal, what's holding it back and who's on what are in one place the whole team can see, updated as the work moves rather than once a quarter. That's what keeps a team aligned between the meetings, which I wrote about in Alignment beats activity.

How Clearahead helps you write and keep a good goal

We built Clearahead around exactly this way of working. When you set a goal, AJ, the AI inside Clearahead, helps you shape it: what you're aiming for in one line, the rough when, what will be true when it's done, why it matters and how you'll know. AJ pushes back when a goal is really an activity, or when it's trying to be three goals at once.

Then AJ asks what's holding the goal back until you're down to the real constraints, and helps you plan the moves under each one. As your team updates their moves in a sentence, AJ keeps the whole picture current, and every Monday it sends everyone a short brief on where the goal stands and what needs a decision. You can see the conversation on the Meet AJ page, or read the full approach in The operating model for the AI era.

Coaches and advisers can use this method in the room with a client’s leadership team. See How to run an annual planning session for a client and the other guides for business coaches.

Questions people ask

What makes a good company goal?

A good company goal is one line that everyone in the company can repeat from memory, with a rough when, a short description of what will be true when it’s done, and the evidence you’ll watch to know whether it’s working. It names an outcome, not an activity, and it has the right people from across the company behind it.

How do you write a company goal?

Start with the outcome that would matter most a year from now. Write it in one line without jargon, add a rough when, then describe in two or three sentences what will be true when it’s done. Add the evidence you’ll watch, test the line by asking a few people to repeat it back, and then ask what’s holding the goal back before you plan any work.

Should company goals be SMART?

Not in the wording. SMART goals take a long time to agree, are hard to change when conditions move and are hard to remember. Keep the goal itself short and memorable, and put the precision into the evidence you track underneath it.

How many goals should a company have?

As few as possible. For most growing companies that means one goal for the company, or one goal for each team working towards something genuinely distinct, and rarely more than a handful in total. Every extra goal splits attention.

What is an example of a good company goal?

“Get to £1m in annual recurring revenue by the end of next year” is a good company goal. It’s one line, it names an outcome rather than an activity, it has a rough when, and anyone in the company can remember it. Underneath it you would describe what’s true when it’s done and the evidence you’ll track, such as monthly new revenue and churn.

What is the difference between a goal and an objective?

In everyday use they mean much the same thing. In the OKR framework, the objective is the qualitative statement of what you want and the key results are the measures. A good company goal combines both ideas: a memorable line for what you want, with the evidence for how it’s going kept underneath it.

The whole approach, in one list

1. Start from the outcome that would matter most a year from now.
2. Write it in one line that anyone in the company could repeat.
3. Add a rough when, not an exact date.
4. Describe what's true when it's done in two or three sentences.
5. Put the precision in the evidence, not the wording.
6. Test it on people who weren't in the room.
7. Ask what's holding it back before you plan any work.
8. Keep it visible to everyone, all the time.