Facts, not opinions

I once spent an evening with a lawyer arguing about the difference between a fact and an opinion. Not a courtroom argument, a real one, over dinner. What stayed with me was how often the two get swapped on purpose. An opinion, said with enough confidence and the right vocabulary, starts to pass for a fact. People do it. So does software.

In software the disguise has a particular shape. The opinion gets dressed as a function. A tool decides your work should be ranked a certain way, or scored, or sorted by a formula somebody chose, and then it ships that decision as a feature and spends the rest of its life arguing the decision was right. Every tool in a category claims its approach is the correct one. They can’t all be correct. Most of what they’re selling isn’t a fact about your work. It’s an opinion about how you should do it, wearing the costume of a feature.

I wanted Deadlinewatch to do the opposite, to state facts about your deadlines and stop there. Walk through what it actually asserts and you’ll find there’s almost no opinion in it.

Is this a deadline with a due date? If yes, it goes in the tool. Fact.

Where does it sit? At its due date, soonest first. Not where a formula thinks it belongs. Where the calendar puts it. Fact.

Is it a priority to you? If it is, you mark it, and it rises. The tool doesn’t decide that, because it can’t. It’s your judgment, recorded as a fact about what you decided, not computed as an opinion the tool holds. There’s a whole piece on why it refuses to rank for you.

Is it something you don’t want in front of you right now? Snooze it, and it dims out of the way until the day you chose. Fact. Did the work go stale, the kind of thing you won’t touch for the foreseeable future? Put it on hold and it leaves the dashboard. Fact.

None of those is the tool telling you what matters. Each is the tool recording something true, either about the deadline (its date) or about your own decision (priority, snooze, on hold), and then getting out of the way. Every one of those controls is a yes or a no, which is part of why they stay facts and don’t drift into opinion. A scale would be an opinion. A switch is a fact.

The difference matters more than it sounds. A tool built around an opinion has to keep defending the opinion. It adds a setting to justify the last setting, a score to explain the sort, a reason its way is the right way. A tool built around facts has nothing to defend. It shows you what’s true and lets you decide what to do about it. Keeping the math visible is the whole point.

I’m not claiming there’s no point of view in Deadlinewatch. The point of view is that you don’t need its opinion. You need the facts about your week laid out clearly enough that your own judgment has something to work with. Most software wants to think for you and calls that intelligence. This one wants to show you what’s true and let the thinking stay yours. That isn’t a smaller ambition. It’s an honest one.

Common questions

Doesn’t every tool have an opinion baked in? Some opinion is unavoidable. The question is what kind. Deadlinewatch’s only real opinion is that you don’t need its opinion about your work, so it sticks to facts (the due date, and the choices you make about each deadline) and leaves the judgment to you. That’s different from a tool that decides how to rank your work and then defends the ranking.

Isn’t “just the facts” itself a design stance? Yes, and it’s the one stance the tool will own. The point isn’t that Deadlinewatch has no point of view. It’s that the point of view is restraint. Show what’s true about your deadlines, clearly, and never dress a preference up as a feature you can’t turn off.