Why "grow the business by 20% this year" never turns into a Tuesday task

A big goal and a to-do list live in two different parts of your brain. Here's how to connect them, plus a free calculator that does the math for you.

Set a goal like "grow revenue 20% this year" or "launch the new service line," and something strange happens: you can believe in it completely and still have no idea what to do about it on a Tuesday morning. The goal is real. The next action isn't.

That gap is where most goals quietly die. Not from lack of ambition - from the size of the jump between "here's the year-end target" and "here's what I open my laptop and do today."

The goal is the wrong unit of work

A year-long goal is a fine thing to believe in, but it's a terrible thing to work on directly. Nobody makes progress on "20% growth." They make progress on "send the proposal to the client I met last week," or "publish the landing page for the new service." Those are the actual units of work. The goal just tells you which direction they should point in.

The fix isn't a better goal. It's a middle layer between the goal and the to-do list - something that turns "by December" into "by the 14th of next month, this specific thing needs to be true."

Breaking a goal into checkpoints

The mechanics are simple, even if nobody does them:

1. Pick the deadline. Not "eventually" - an actual date.
2. Pick a rhythm. Weekly checkpoints for anything under three months, monthly for anything longer. Weekly is annoying for a year-long goal; monthly is useless for a six-week one.
3. At each checkpoint, write one sentence: "By this date, ___ needs to be true." Not a task list - a state. "The landing page is live" is a checkpoint. "Work on landing page" is not.
4. Only plan the next checkpoint in detail. The one six months out will be wrong anyway. Keep it directional, not detailed.

Doing this by hand for a 12-month goal means counting weeks, guessing at even spacing, and usually giving up two checkpoints in.

A tool that does the counting for you

That's the whole reason the Goal Breakdown Calculator exists. Give it a goal, a start date, and a deadline, and it lays out the checkpoints for you - weekly or monthly - each with a spot to write what needs to be true by then.

What to do when a checkpoint gets missed

It will happen. The useful move isn't guilt, it's a decision: was the checkpoint wrong, or was the work wrong? If three weeks in a row slip, the checkpoint was probably set too ambitiously - shrink it, don't abandon it. If one week slips because a client emergency ate your time, just move that one checkpoint and keep the rest where they are. A missed checkpoint is data. It's only a failure if you stop looking at the trail entirely.

That's the point of breaking a goal down this way: not to make the goal easier, but to make it impossible to lose track of. A goal you can't see the next step of is a goal you'll quietly stop thinking about by March. A goal with a checkpoint two weeks out is one you'll show up for.

Common questions

How many checkpoints should a goal actually have?

Enough that you're never more than two to four weeks from the next one. For a goal under three months, that means weekly. For anything longer, monthly - more than that and the checkpoints get too far apart to catch a stall early.

What if my goal doesn't have a hard deadline?

Give it one anyway, even an arbitrary one. A goal with no deadline behaves like a goal with no checkpoints - it's easy to believe in and easy to never act on. You can always move the date later; you can't build a trail without one.

What if I miss a checkpoint by a lot, not just a little?

Treat it as a sign the estimate was off, not that the goal is off. Rebuild the remaining checkpoints from today's date instead of the original start - same rhythm, new starting point.

Can I use this for a goal I share with a team, not just a solo one?

Yes, though someone needs to own updating it. The mechanics don't change - the checkpoint still needs to be a state ("the feature is shipped"), not a task list - but with a team, write down who's responsible for that state being true.