Setting Realistic
60-Day Goals

Sixty days is a strange unit. It is long enough to ship something real and short enough that ambition collides immediately with reality. Most year-end sprints fail not because of effort but because the goal that was set in early September was never the kind of goal that could finish in sixty days. This page is about how to spot the difference before you commit.

What a 60-day goal is — and isn't

A 60-day goal is a goal whose completion can fit inside the window. The full project may be much larger, but the slice you commit to has a defined finish line that you can reach without inventing new infrastructure or borrowing time from your normal life.

A 60-day goal is not:

• A direction ("get healthier"). Directions are useful, but they do not close.
• A wish ("launch the business"). A wish is a goal that has not yet been sized.
• A list of activities ("write more, exercise more, network more"). Activities run; they do not finish.
• A target whose completion depends on someone else's decision happening on their timeline.

The four selection criteria

Before you write a 60-day goal in your planner, run it through these four filters. If it fails any one of them, rewrite the goal or pick another.

1. Finishability

Can you describe a moment that proves the goal is done? "I will know I'm done when X exists / has shipped / is in the world." If the answer is "when I feel I've done enough," the goal will quietly extend itself for as long as you let it.

2. Sole control

Does completion depend only on actions you control, or does it require a yes from someone else by a specific date? If a venture round, a hiring decision, or a partner's review is on the critical path, the goal is partially out of your hands. That doesn't mean drop it — it means rewrite the goal in terms of the part you control ("submit the application package by November 1") and treat the external decision as a separate event.

3. Sized to four working weekends

Sixty days contains roughly forty-three weekdays and eight weekends. Most people, after subtracting normal life, have somewhere between three and six weekends of real focus time available. If the goal cannot be done in four weekends of concentrated work, it is too big for this window. Cut it down to a slice that fits.

4. Recovery from a bad week

Will the goal survive one bad week — illness, a work crunch, a family obligation? If the plan assumes every week is a normal week, the goal is fragile. The right test is to mentally delete week five and ask: does the rest still finish?

A worked example

Suppose someone arrives at the start of September with a vague goal: "I want to leave my job and start consulting." That is a direction, not a goal. Run it through the four filters.

Finishability. What proves it's done by November 1? A signed first client? An LLC formed? A website live? Each of those is a different goal. Pick one. Say: "By November 1, I will have a signed retainer contract with my first paying client."

Sole control. A signed retainer depends on someone else saying yes. Rewrite: "By November 1, I will have made formal pitches to at least eight target clients and held three discovery calls." Now the bar is action, not external assent.

Size. Eight pitches over eight weeks is one a week. That fits four working weekends of preparation plus normal weekday hours for outreach. It is sized.

Bad-week test. If week five vanishes, can the rest absorb it? Probably yes — drop one pitch, or front-load the early weeks. Sized correctly.

Notice what happened. The goal moved from "start consulting" to "make eight pitches and hold three discovery calls." The latter is the actual ground on which the bigger ambition gets a chance. If the pitches land, you have momentum. If they do not, you have data you couldn't have gotten any other way.

Common mistakes

• Stacking three goals into one sprint. Two is the maximum that most people can hold across sixty days without one of them quietly starving the other.
• Choosing the most exciting goal instead of the highest-leverage one. Excitement is correlated with novelty, not with what would matter most by year end.
• Confusing input goals with output goals. "Write every day" is an input. "Have a 12,000-word draft by November 1" is an output. Inputs are useful inside a sprint but should not be the sprint goal itself.
• Forgetting the second half. Most sprints collapse around day 40, when the initial energy is gone and the deadline still feels far. Build a checkpoint at day 30 to re-evaluate scope.

A two-minute test before you commit

Write the goal in one sentence. Read the sentence aloud. Then answer four questions, out loud, in order:

1. "On November 1, what will exist that does not exist today?"
2. "Who has to say yes for that to happen?"
3. "How many weekends of real focus does this take?"
4. "What happens if week five disappears?"

If any answer is fuzzy, the goal is not ready. Rewrite and run the test again. The whole exercise should take less than five minutes per candidate goal, and it saves you the much larger cost of working hard on a goal that was never going to finish.

For the structure of the sprint itself, see the September Sprint page. For the execution-heavy second half, see October Finish. And for the closing reflection that turns this sprint's data into next sprint's better goal, see How to Run a Year-End Retrospective.