A date on your project moves. Not by your choice; a client shifts their launch, a conference moves, a dependency slips. You review the plan, and within minutes the conversation isn’t about the schedule anymore. It’s about what the work was supposed to deliver to begin with.
That second conversation is expensive, and most teams treat it as the unavoidable cost of a moved date. But it’s a sign that the deadline had been standing in for the true goal, and moving the date became a change to the goal as well.
This is a work-design problem, and it’s fixable before the next time this happens.
Why the date becomes the goal
Every project has a date. It’s the one concrete fact everyone knows, written on every calendar, unambiguous and easy to check. You either hit the fifteenth, or you don’t.
The goal is rarely that well-defined. What the work is for, the outcome that makes it worth doing, usually lives in your head, or in all your team’s heads which don’t quite match, or in a kickoff deck nobody has opened since. It’s real, but it isn’t written where the team can recall it easily.
The date masquerades as something it isn’t. It becomes the shared verbal reference the goal should have been. Everyone plans toward the fifteenth because the fifteenth is the thing they can all say, and the outcome rides along underneath, unstated, as long as the date holds.
What a moved date costs
While the date holds, the substitution stays invisible. The work progresses, updates reference the deadline, and nobody says out loud what the finish line produces. The cost comes when the date moves.
Move the fifteenth to the first and there’s nothing steady left to plan against. The team can’t simply compress the schedule, because the schedule was the only way the goal was written. They rebuild the goal from memory, in a meeting, maybe out loud, and find they don’t fully agree on it.
What should be adjusting a plan becomes the team ratifying the goal for the first time, under pressure, at the worst possible moment.
Capable teams do this every time a date moves, because the work design left them no other option. The cost was set when the outcome went unrecorded, and the date was substituted for it.
The goal behind the goal
The fix is to give the goal its own record, written where the date lives now: what this work is for, the outcome you want at the finish line, whenever it comes. One sentence, in the shared record, apart from the calendar. Then a change of date is a plan update rather than throwing out the goal.
Sometimes the date looks inseparable from the goal. The launch must land at the conference; the filing has to meet the regulator’s date. When the deadline seems baked into the goal, look for the goal behind it. The conference is a way to reach the early adopters you came to sign, and there’s more than one way to reach them. The regulator’s date is one route to stay compliant, and compliance is the goal the date was serving. Name the goal underneath, and the deadline turns back into one way to meet it.
A goal you can restate without naming a date is a goal a moved date can’t take from you.
If a deadline on your work has been substituted in for a goal nobody wrote down, the diagnostic is a ten-minute read on where that’s happening and what to record instead. It sorts you toward the individual or the team version on its own. https://amykennedyleadership.com/choose-your-diagnostic/