The four axes of attention.

I have used a lot of deadline tools, and built several of my own, and they nearly all make the same quiet mistake. They take different kinds of attention and fold them into one control, and the information you needed disappears into the fold.

Every deadline tool I’ve used collapses the mechanics. They give you a Status (todo / doing / done) and call it complete. Or a priority (high / medium / low) and call it complete. Or both, with the understanding that you’re supposed to manage your attention by toggling between them.

This collapses information that needs to stay separate. More tools ship every year, and in 2026 the typical one still offers exactly those two controls.

A deadline carries one underlying fact, its date. Everything else you do to a deadline is one of four operations on a separate axis. Most tools mush two or three of these into one mechanic. Deadlinewatch keeps them apart.

Status. Am I working on this?

Status is the workflow axis. It answers where this sits in the lifecycle of getting done.

Three states, and each is a real one. Active is what’s in front of you. Completed is the final action, terminal, a deadline met and kept on the record. On hold is the set-aside shelf, a deadline that’s neither on your plate nor finished, kept on its own surface so nothing vanishes. No kanban-of-self. No “in review,” no “blocked,” no “awaiting feedback.” Those are notes about a deadline, not states of attention. Three different answers to three different questions. Am I on this. Did I finish it. Have I set it down.

Snooze. Do I want to see this right now?

Snooze is the temporal visibility axis. It answers whether this deadline should sit at full weight in my attention today, or quieted.

Snooze does not touch the date. The deadline is still due when it’s due. It doesn’t hide the row either. It quiets the row down, dims it to a ghost, while deliberately keeping it in sight. After the wake date the row returns to full weight automatically.

A snoozed deadline stays visible as a faded ghost in its natural section, with a chip reading “Snoozed until Thursday” where the actions row was. An earlier version hid snoozed rows outright, and that turned out to be dangerous. You defer something, forget the wake date, and the deadline is just gone. Hiding is the risk, not the feature. The same instinct is why even shelved work keeps a count in the sidebar. Nothing in this tool is allowed to become a place things vanish into. Quieted, never hidden. Out of mind, but not out of sight.

Priority. Does this matter more than the others today?

Priority is the in-interface attention axis. It answers where this deadline should appear inside the dashboard.

Marking a deadline due in sixty days a priority hauls it to the top of the dashboard. The sixty days don’t change. The user is saying this matters to them beyond what chronology would put it at. Maybe the deadline is small but consequential. Maybe it’s the only thing they care about this week. Maybe it’s an anchor for everything else.

Priority is binary. Either a deadline is a priority or it isn’t. An earlier graded importance field (high / normal / low) got built and tested hard, and cut before it ever shipped. In testing it always collapsed the same way. I flagged a deadline high, or I left it alone. Nothing in between got used. The three-state dropdown was really a two-state field pretending to be three. The binary flag isn’t an experiment. It’s the version the testing settled on.

Email reminder. Should this find me when I’m not looking?

The email reminder is the external attention axis. It answers whether an email should land in my inbox when this deadline is N days away.

On by default, but quiet. A new deadline sends one email a few days out, not a stream of them, and the dashboard stays the main surface. The reminder is a single backstop, easy to turn off on any deadline that doesn’t need it. The restraint is in the default, not in sending nothing. Mass reminders dilute the value of each one, and I learned this the dull way. Back when every deadline could email on every approach, my own inbox turned into wallpaper, and I stopped reading any of it. So one email is the default, not the limit.

A new deadline emails once, three days out. You can leave it there, add more lead times when a date earns them, or switch it off on the ones that don’t need it. The cadence lives on the deadline, not in one global schedule, so a single consequential date can get more notice without raising the noise on everything else. Two dials stay account-wide. A master on or off, and the hour of day the mail sends.

The email is the whole of it. There is no second channel competing for the same job. I did try a browser pop-up alongside it and then took it back out, for reasons I wrote up in a separate piece.

Why four, why these four

The axes are independent. A deadline can be active, not snoozed, a priority, and emailing, or any combination. The combination space is large because the axes carry different information. Collapsing any two of them into one mechanic destroys information.

Priority and Snooze are siblings in opposite directions on the same axis (in-interface visibility). Priority says “louder than chronology dictates.” Snooze says “quieter than chronology dictates.” Same kind of operation, opposite directions. Symmetry is a design tell. When the mechanics rhyme, the user’s mental model holds together. They don’t need to memorize disparate rules.

Priority and the email reminder are siblings on the matters-more axis. Priority = matters more inside the interface (top of the dashboard). The email reminder = matters more outside the interface. Both binary. Priority is off until you reach for it. The email reminder runs by default and stays out of your way until you switch it off. Both are one tap, and both leave the choice with you.

The four-axis frame is the closest thing the product has to a load-bearing design idea. Everything else, the views, the assistant, the streams, exists to render what these four axes describe. The reason they describe it instead of scoring it is the shape thesis. Render the structure, and let the user read it. The reason none of the four feeds a hidden priority score gets its own argument.

The frame is worth carrying even if you never touch this tool. The next time a piece of software asks you to manage your attention with one control, notice what it’s quietly making you give up. Am I working on this. Do I want to see it today. Does it matter more than its date inside the tool. Should it reach me outside the tool by email. Those are four different questions, and a good instrument lets you answer them one at a time.

Common questions

What’s the difference between Priority and Snooze?

They’re the same kind of operation pointed in opposite directions. Priority says a deadline should sit louder than its date would place it, at the top of the dashboard. Snooze says it should sit quieter, dimmed to a ghost row, until a day you choose. One raises a deadline above chronology, the other lowers it. Neither touches the actual due date.

Do email reminders run automatically?

Yes. By default a deadline sends one email a few days before it’s due, then nothing more. The dashboard is still the place you live in, so the email is a single backstop, not a stream. Turn it off on any deadline that doesn’t need it, add more lead times on the ones that warrant it, or switch the whole thing off in settings. An earlier version of the tool kept these off until you asked, and I changed my mind. One quiet email did more good than the empty inbox did, and I wrote up why the default flipped.

Why only three Status states?

Active, completed, on hold. Each is a distinct answer, not a shade of the others. Active is the work in hand. Completed is the terminal move, a deadline met and kept on the record. On hold is the shelf, set aside but still counted, with its own surface so nothing vanishes. Anything finer, “in review,” “blocked,” “awaiting feedback,” is a note about a deadline, not a state of attention.