The last of the timing facets is the due date, and it’s the one people misuse most, so it needs a clear rule on how to use it correctly. Back in Part 1, due date inflation was a whole failure mode: you slap deadlines on things to force them up your list, and eventually your list is a wall of overdue tasks where none of the dates mean anything. This is where we make sure that never happens again.

A due date needs a cause that lives outside your own desires. Something real has to happen if the date passes. Sometimes the impact is very real. Here in the USA, your taxes are due April 15th because the government will penalize you, that’s a structural due date with a real tangible consequence. Sometimes the impact is more subtle. Your manager asked for a report but never gave you a due date. You still set one for Friday because a report like this shouldn’t take more than a week, and letting it drag longer would look bad. That’s also a due date, even though nothing formally “breaks”, looking unreliable to your manager is a real consequence, just a social one. The line isn’t “hard external deadline versus nothing.” It’s “a real consequence exists” versus “I made this up to make myself feel the pressure.”

So, “read this book by Friday” is not a due date, if the only reason is that you’d like to read it by then. Nothing happens Saturday. That’s not a deadline, and if you record it as a due date you’ve just started inflating again. What you actually mean is “this matters to me”, and that’s what impact is for. Wanting something done soon is a ranking fact, not a timing fact. Keep them separate and your due dates stay trustworthy.

Interestingly, when I started to separate the two, I noticed something: a lot of what has a real due date isn’t what you’d call important, and a lot of what’s genuinely important has no due date at all. Renewing your car registration has a hard deadline, miss it and you’ll pay for it, but it’s maintenance; nobody puts it on their list of goals for the year. Figuring out where your career is headed belongs on that list, and it isn’t due any particular day, which is exactly why it’s so easy to let it slide forever. Deadlines and importance are different axes, and conflating them is how the obligatory-but-uninspiring tasks keep crowding out the important-but-dateless. Keep them separate and your due dates stay trustworthy: when something’s due, it’s really due.

Yes, there’s judgment in the gray zone. Sometimes I put a due date on a task because I know my team is expecting it, or frankly because I don’t want to look bad. That’s fine. The consequence is real even if it’s soft. The test isn’t “is this consequence severe,” it’s “is there a consequence at all, or did I invent the date to motivate myself.” If the only person you’d be letting down is yourself, it’s a priority, not a due date.