A Delay With a Timestamp

By Martin Bergmann | AI Project Lab | August 2026

A line in the Decisions section of a RAID log said “Target: Friday.” That was three Fridays ago. No one took the date out, and no one changed it either. It just remains there, in a technical sense past its due date, and in practical terms exactly the same as if no date had been given at all.

The date was never the hard part.

Setting a target date is simple, and most project managers already do so. That isn't where the problem lies. The gap appears as soon as the date arrives, and the solution is still not available. What typically occurs, then, is that the item remains open, the date stays outdated, and everyone simply agrees in silence to keep waiting without ever making a decision.

That is not a decision plan. That is a delay with a timestamp on it. As early as 1927, the psychologist Bluma Zeigarnik noted that unfinished tasks remain active in memory and continually intrude on attention, whereas completed ones do not.

It wasn't until another eight decades had passed that the resolution of that tension was established. In 2011, E.J. Masicampo and Roy Baumeister discovered that merely drawing up a concrete plan for a task that had not yet been completed was sufficient to eliminate intrusive thoughts almost completely. The task need not be carried out; all that was necessary was a plan.

The open question is what counts as a plan strong enough to do that. Peter Gollwitzer’s decades of research on implementation intentions gives the answer: a conditional, if this happens, then I do that, works where a vague intention doesn’t.

The target date only covers the "if" aspect; most entries in the RAID log end there. The "then" part is almost never recorded, so when the date has passed, there is no trigger left, and the loop simply continues running in the background.

What actually closes it?

The fix isn’t dropping the date. It’s pairing every date with the answer to one question: what happens if we get here and still have no response? Escalate to the sponsor. Extend two weeks and say so out loud. Raise it at Monday’s steering meeting. Any of these works, as long as it’s decided before the date arrives, not improvised after.

“Target: Friday” is half a plan. “Target: Friday. If no response, escalate to the sponsor” is the whole thing, and it takes one extra sentence to write.

Where AI actually helps.

Point it at your RAID log and ask it to flag two things: items whose target date has already passed, and items with a date but no defined next step for when that date is missed.

The first check is easy for anyone to do by hand once. The second one is the one nobody keeps doing every week across every item, which is exactly why it’s worth handing to something that doesn’t get tired of checking.

The date was never the plan. The plan is what happens when the date doesn’t hold.

---

Martin Bergmann is the Director of an IT PMO and founder of the AI Project Lab. He writes about AI, project management, and the future of intelligent work.