Why Deadlinewatch has no formula chain.

Most deadline tools rank for you. Some use machine learning. Some use weighted scoring. Some, surprisingly often, use a number-soup algorithm someone wrote in a single afternoon and then never revisited. The user opens the tool and sees a list pre-sorted in an order the user didn’t choose.

Deadlinewatch doesn’t do this. The list sorts by date. That is the whole sort. Pin a deadline to lift it above the date order. Snooze it to set it aside. Otherwise: in order by when it is due.

This is deliberate. Four reasons.

One. The math has to be visible

The user has to be able to read why the list looks the way it looks. “Tax filing is at the top because it is due Friday” is a read-and-trust statement. “Tax filing is at the top because a weighted score of 8.3” is not, even if the score is thoughtfully constructed. The user cannot verify the score from the surface. They have to trust the tool, blind.

Trust delivered blindly is fragile. The first time the score is wrong, the user notices. They start second-guessing. They open the tool less often. The tool earns its place in the morning routine by being legible, by letting the user read why it is showing what it is showing, and a hidden formula chain breaks legibility.

I had a version of Deadlinewatch with a formula chain. It computed a final_priority_score per deadline as a product of due-date proximity, importance flag, and (in an early experiment) revenue weighting. Users liked it for a week. Then they stopped trusting it. By the third week the dashboard’s pre-sorted order felt intrusive. The tool was telling them an answer they didn’t agree with, and they started ignoring the sort and re-sorting manually in their heads. I retired the formula chain in the 2026-05-08 simplification pass. The math is now days-until-due. That is all.

Two. An algorithmic rank implies expertise the tool doesn’t have

Deadlinewatch does not know which of your deadlines matter most. It only knows the dates. Anything beyond that is a guess dressed up as a recommendation. When a guess proves wrong, the user blames the tool, and the trust required to use the tool every morning evaporates.

This goes wrong most often in finance-adjacent territory. A tool that scores deadlines and surfaces them in a sorted order looks like it is offering professional advice. It isn’t, but it reads like it is. A user who acts on the recommendation and misses something else can reasonably feel the tool let them down. The legal exposure aside, the product story is bad.

The honest move is to render the shape and let the human decide. The human knows their context. The tool does not. The tool’s job is to make the context legible, not to impose an order on it.

Three. The experienced practitioner doesn’t want a ranking

They want a rendering. They will do the ranking themselves, because that is the part of the work they are actually good at. Pattern recognition is the senior skill that this whole publication keeps coming back to , and that skill produces the ranking automatically as a byproduct of reading the shape. A tool that does the ranking for them removes the part of the work they want to keep doing. It also removes the daily practice that keeps the skill sharp.

My target user, someone who carries many submission dates and feels the cognitive load all day, is almost always a senior practitioner of something. They have a ranking already. They just want help holding the shape that produces it.

Four. The math has to be honest

The math the user sees in Deadlinewatch is days until due. Pinned items appear at the top. Overdue items appear in their own section. Snoozed items appear as ghost rows. That is the entire ordering logic. It fits on a sentence. It can be checked at a glance. It does not require trust.

The negative-space catalog on the methodology page names every thing I deliberately don’t do. The first item on that list is “no directive verbs.” The third is “no formula chain.” They are not the same rule, but they belong to the same family. The family of design choices that keep the user in charge of their own work. (See also the four axes piece for the same principle applied to the mechanics. )

Most of these are easy to add and hard to take back. I chose not to add them.