Ad Finum

There was no eureka moment.

No whiteboard or notebook in a coffee shop. No up at 3:00AM. No single conversation that cracked it open. Just a problem I kept running into, and a growing irritation that no one had solved it yet.

In 30 years, I have watched the tools change — from paper schedules on boards with red thread across the cards to Gantt software, from email chains to Slack, from handwritten notes to AI transcription. Each wave brought more capability and, quietly, more noise. We got better at capturing everything. We got worse at knowing what mattered.

The last wave — Plaud, Copilot, Teams transcription, all of it — finally pushed me past the edge. Everyone was recording everything. Every meeting left behind a document. By the end of a complicated week I was drowning in words, all of them mine or a colleague’s, all of them theoretically important, none of them telling me what I actually needed to know: had anything changed from what we agreed?

That is the question I have been trying to answer for three decades. Not “what happened in the meeting.” What changed from what we said we would do.

Leaders have always wanted the same thing. They call it different things — predictability, certainty, a reliable forecast — but what they want is determinism. Tell me when. Tell me how much. Tell me it will be exactly as planned.

Software has never been able to give them that. Not honestly. Especially not in the complicated, legacy-heavy, politically fraught world of enterprise modernization, where the sinkholes hide beneath the surface of every project — unplanned features no one remembered were there, dependencies that were assumed and never stated, decisions that were made in hallways and never written down.

Scope and schedule and budget look like constants. They are not. They bleed. Slowly, quietly, through hundreds of small decisions about details that no one flagged as significant in the moment. And then one day you look up and realize you have crossed a line you cannot see on any document, into a territory where the original agreement no longer describes the reality you are living in.

The problem was never information. It was the gap between what was agreed and what was actually happening. And I never had a tool that watched that gap for me.

There was a program manager once — I will not name him, or the project, or the client — who decided he did not like the answers I was giving him. So he stopped asking me and started doing. He was the kind of person who needed to be in charge, and in his mind, needing to be in charge was the same as being in charge.

I felt the shift before I could name it. Someone on the team was filling a role that was not theirs. Another person was operating in the space between responsibilities. The boundaries of who was doing what had quietly dissolved, and the dissolution was invisible because it had happened through a hundred small acts of accommodation, none of which anyone had decided to make.

One-on-one conversations did nothing. Stepping back made it worse. The only thing I could do was call it out as a risk — which felt, in the moment, like pointing at smoke and being told there was no fire.

What I needed was documentation. Not of what I thought. Of what I had actually observed, in sequence, across time. Evidence that a pattern existed before it became a crisis. A place where I could say: here is the shift, and here is when it started, and here is what I said about it, and here is what happened next.

That is what I built.

I called it Ad Finum. Latin for “to the end.”

As a musician, I know Ad Infinitum — to infinity, forever, without end. I was struck by the opposite. Projects end. They are supposed to end. The whole discipline of project management is a discipline of endings — of shipping, closing, completing, releasing something into the world and then letting it go.

To the end felt right. Honest. A little austere.

I want to say something about why I am writing this here, on The Rope, which is not a publication about software or project management or anything that comes with a license key.

The Rope is about the examined life. About paying attention to the interior. About what happens when you stop performing and start noticing.

Here is what I noticed: I had been carrying a limitation for thirty years and calling it the nature of the work. The information was always too much. The patterns were always too subtle. The evidence of a slow drift was always arriving faster than I could process it, so I managed from intuition — which is real, which is earned, but which leaves you alone with a feeling you cannot prove.

The tool I built helps me not lose the thread. It reads what happened in a meeting and compares it to what we said we would do, and surfaces the gap. It does not replace my judgment. It frees up enough of my attention that I can actually use my judgment — on the things that require it. On the conversations. On the people. On the quiet coaching that an experienced project manager spends most of their time doing, whether or not anyone names it that.

I have always had ideas. I have not always had the means to build them. That changed too.

Within a couple of days of starting — working alongside AI tools in a way I had never worked before — I had built something I did not believe I could build. Not a prototype exactly. A working thing. It surprised me in the way that anything surprises you when the gap between imagining and making turns out to be smaller than you thought.

What do I hope for it?

I hope it helps project managers — real ones, the ones doing complicated work in complicated organizations, the ones who feel the shift before they can prove it — have one less thing to carry alone.

I hope it protects people. From the passive drift. From the program manager who does not like the answer. From the meeting that changed everything and left no trace.

I hope, in some small way, it makes more room for the human parts of the work. The parts that cannot be automated, summarized, or extracted from a transcript. The part where you sit across from someone who is struggling and you have something useful to say, because you were not spending your whole afternoon rebuilding the record of what happened last Tuesday.

That is enough. That is what I hoped for when I started.

If you know a project manager who manages complicated things and feels the weight of it — you might send this to them. The product is at adfinum.us. The beta is open, by invitation. There is a request access form.

And if you are just here for The Rope — that is enough too. This is the examined life, applied to the tools we build to help us live it.

adfinum.us