
Standard goal advice says put a date on it. A goal without a deadline isn't a goal, it's a wish, and so on.
For a lot of work that's right. But plenty of people set a date because they've been told to, on something that has no natural one, and the invented deadline does two things: it fails to create urgency, and it hands them a specific day on which to feel like they've failed.
What a real deadline does, and what an invented one does
The reason deadlines work, when they work, is that something happens on the day.
A client is expecting the report. The exam is sat. The venue is booked and the guests are coming. That external event is doing all the work — it can't be renegotiated privately at eleven at night, and the consequences of missing it belong to somebody else as well as you.
An invented deadline has none of that. Finish the novel by December is a date you chose, which you can move by deciding to, and which nobody else will notice. It looks the same on the page as the real kind and behaves completely differently.
What people usually mean by set a deadline is create urgency, and urgency is a property of consequences rather than dates. A date with no consequence attached doesn't produce it, and no amount of committing to the date changes that.
Three things go wrong with dates you made up.
They produce a failure event where there wasn't one. On the 31st of December the novel isn't finished, and now there's a discrete moment of having failed — attached to a goal that was, in every other respect, going fine at fifteen hundred words a week. That moment does real harm, because a goal that has failed is much easier to abandon than one that is merely unfinished.
They distort the work near the end. Deadlines encourage finishing over finishing well, which is correct when something has to ship and wrong when the date was invented. People cut the last edit, skip the difficult chapter, submit the version they know is weaker, in service of a date that means nothing.
And they make the wrong thing the measure. Once there's a date, the question every week becomes am I on track, which is unanswerable for anything creative and demoralising when the answer is no. The useful question — did I work on it this week — gets displaced by one you can't answer honestly.
Which goals do better open-ended
Three types.
Practices, where the point is the doing rather than a finish. Learning an instrument, fitness, a language, a creative habit. These have no completion state, so a date is arbitrary by definition, and the only meaningful measure is whether it's still happening.
Work of unknown size. Anything where you can't know the scope until you're inside it — a first novel, a research problem, a business you haven't validated. A date set at the start is a guess made at the point of least information, and holding yourself to it means holding yourself to the least informed decision you'll make on the project.
And work where quality dominates timing. If nothing bad happens by taking another month, and the extra month makes it better, the deadline is costing you something and buying nothing.
What to use instead
Not nothing, because the objection is fair: goals with no date and no structure do drift.
Use a rhythm rather than a date. Two evenings a week is a commitment you can keep or break weekly, with no distant day to fail at, and it produces the thing a deadline was supposed to produce — regular contact — without the failure event.
Use the gap as the measure. How long since you last touched this is a question with an honest answer every single day, unlike are you on track, and it catches drift at eight days rather than at the end of a quarter.
And use a review point rather than a delivery date. Look at this again in March and decide whether it's still worth doing is a date with a decision attached rather than an obligation. It creates a moment of honesty without creating a moment of failure.
Where deadlines are genuinely needed
The counter-argument, and it's stronger than the open-ended camp usually admits.
Some work expands indefinitely without one. Anything with a satisfying middle and an unpleasant ending — a piece of software that could always be refined, a manuscript that could always be edited — will absorb any amount of time offered, and a date is what forces the transition from the comfortable part to the exposed part. Plenty of open-ended projects are open-ended because finishing means being judged, and it's ready when it's ready is a phrase that has protected an enormous amount of unfinished work.
Deadlines are also what let other people plan around you. The moment anyone else is involved, an open-ended goal quietly transfers your uncertainty onto them, and the fact that you find dates uncomfortable isn't their problem.
The test worth applying: is the absence of a date protecting the quality of the work, or protecting you from finishing it? Those feel identical from the inside. The way to tell is whether the last three months moved it towards completion or around inside it.
The novel and the deck
Two projects, one person, same autumn.
Rebuild the deck. There's a date, because the family are coming in June and the deck has to be safe by then. That's a real deadline — external, consequential, not privately renegotiable — and it does exactly what deadlines do: the work gets scheduled backwards from June and the awkward bits get done.
Finish the novel by December. This date was invented in January because a book said to. By October he's at sixty thousand words and going well, roughly fifteen hundred a week, and every week he is also failing, because fifteen hundred a week does not reach the end by December. The date has converted an entirely healthy project into a losing one.
In November he changes it. The goal becomes two evenings a week on the novel, with a note: review in March — is this still the book I want to write? The word rate doesn't change at all. What changes is that there's no longer a day on which he fails, and the weekly question has an answer.
December arrives and nothing happens, which is the improvement. In March he reads it back and decides to keep going, which is a decision he makes rather than a deadline he misses.
What gets counted instead
goaldrift has no deadline field, which surprises people.
Days-since is what it counts, and for open-ended work that's the honest measure: not whether you're on schedule against a guess, but whether you're still in contact with it. A novel at four days quiet is alive. The same novel at ninety is in trouble, and that's true whether or not December was ever mentioned.
If a goal has a real external deadline, put it in the description, because that's a fact about the world and worth having in front of you. What the app won't do is invent one, or measure you against it, or tell you on the 31st of December that you've failed at something you were doing perfectly well.
Related: Outcome goals vs process goals · Write the goal so tomorrow-you knows what to do · Why the goals you care about most go quiet first
Share: