Skip to content
Apr '266 min read

The years before the tool

I carried the shape in my head for two decades before I tried to put it on a screen. This is what those years taught me, and why the tool looks the way it does.

ConradOn deadlines and the design of working instruments

For most of my working life I tracked deadlines the way everyone does. A list. Then a better list. Then a calendar with the list pinned next to it. Then a wall planner, a desk pad, a notebook ruled into weeks, a spreadsheet that recalculated something every Monday. I tried every aid I could find, and I built a few of my own, and none of them held for long.

They didn’t hold because the thing I was tracking wasn’t a list. It was a shape, and I was the only one who could see it.

What the years actually taught me

The first thing two decades of deadline-heavy work teaches you is that the load is not the number of items. It is how they sit against each other. A week with eight deadlines spread evenly is lighter than a week with four deadlines stacked on a Thursday. Every experienced person knows this in their body, and no list they own shows it. The skill of reading that, fast, is the one nobody names.

The second thing it teaches you is that the cost is invisible. You finish a Wednesday feeling flattened, look at the calendar, and see nothing that should have done it. Four meetings and some email. The energy went somewhere the calendar can’t show. It went into re-shaping the week, over and over, while you weren’t looking.

The third thing, and this took me longest, is that no amount of discipline fixes a representation problem. I kept thinking I needed a better system, by which I meant a more disciplined version of me. What I actually needed was a different picture. The list was a flat drawing of a thing that had weight and depth, and you cannot become disciplined enough to see depth in a flat drawing. You need the drawing to change.

Why I waited so long to build it

I waited because I assumed someone had already solved it. For years I treated my own dissatisfaction as a personal failing rather than a gap in the tools. Surely the calendar was enough, and I just wasn’t using it right. Surely the to-do app would click if I configured it correctly. It took a long time to accept the simpler explanation. The tools were built for a week that arrives one item at a time and stays put, and my weeks had not looked like that in fifteen years.

So I started treating it as a real problem instead of a private inadequacy. I read the research, which turned out to be older and better established than I expected, and which gave names to things I had only felt. The names are on the methodology page. I sketched. I built rough things, used them, threw them out. The sketches kept converging on the same picture: not a list, but a terrain, with the weight drawn where the weight actually was.

What that leaves you with

When you finally render the shape instead of the list, the relief is not what you expect. It isn’t that the tool does your work. The work is the same. It’s that you stop holding the shape against its own weight all day. You glance at a picture someone has already drawn, confirm it still holds, and put it down. The background process that ran for twenty years goes quiet.

That quiet is the whole product. Everything in Deadlinewatch is downstream of wanting it. The thesis, in full, is here. I didn’t set out to build a deadline tool. I set out to stop doing the arithmetic. The tool is what was left when I stopped.