The years before the tool

I carried the shape of my work in my head for two decades before I ever tried to put it on a screen. In those years I tried every tool and system I could find. Mostly I improvised, with notes on scattered pieces of paper, rows of sticky notes framing my screen, and loose digital notes hidden somewhere in my folders. I tried the dedicated software too. All of it lacked more than it offered, and I had little appetite for adding yet another suite to a growing arsenal. Between deadlines, over many years, I tried to name the reasons none of them worked. Those reasons turned out to be more interesting than I expected.

The main finding was that they didn’t work because, despite masquerading as a list, deadlines aren’t one. They constantly shift and morph, mostly due to external factors, sometimes internal. They affect each other. The work runs in a line, but the commitments behind it do not. They form a shape. For years, I was the only one who could see it. I got really good at handling that shape long before I realized what it was. The moment I first saw it as one was the inception of Deadlinewatch.

What the years actually taught me

For a long time I thought I needed a better system, by which I meant a more disciplined version of me. What I actually needed was a different definition of the problem. If you looked at my ‘lists,’ you would soon notice they weren’t really lists. They were diagrams with arrows, cross-outs, exclamation marks, and stars in a myriad of colors. The shape was trying to lift off the page, but it was still called ‘a list.’ Managing the changing priorities was one problem. Not seeing how those changes would affect the weeks ahead was another, and arguably the bigger one.

The load was never the number of items. It was how they sat against each other. A week with eight deadlines spread evenly is lighter than a week with four deadlines stacked on a Thursday. By the time I became a senior professional, I knew this intuitively, and I felt the weight of that shape as the week approached. I reacted by re-allocating resources, calling for extensions, or rolling up my sleeves. There is nothing we can do about the nature of business commitments. They have a life of their own. But I felt I could do something about defining and seeing the shape of the coming weeks, the skill that was learned but never had a name.

The cost was also invisible, which is its own trap. 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.

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. Every mechanic is going to tell you that special jobs require special tools.

So I started treating it as a real problem instead of a private inadequacy. I read the research, which turned out older and better established than I expected. Kahneman and Tversky had named the planning fallacy in 1979. Miller had measured the memory ceiling in 1956. The names were already there. I had just been feeling the things without them. More of that reasoning is 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, and in 2026, with every tool racing to add another feature, the quiet is the part I keep guarding. 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.