Recovered next Thursday, filed last year
The Time-Travel Portfolio Dependency
The retrospective occurred before kickoff and identified actions from a meeting no one had attended yet.
The sponsor wanted the project plan delivered before deciding whether to authorize the project. Ordinarily I would have declined. Unfortunately, a future version of me had already accepted and left detailed minutes. They were excellent minutes, which made the situation personally irritating.
Procurement required three competitive bids. The same vendor submitted all three from separate timelines and denied collusion on the grounds that its representatives had never technically met. Legal requested a conflict-of-interest review. The review concluded that the conflict both had and had not occurred, depending on invoice date.
The causality register
I created a register for events that could invalidate their own prerequisites. Every decision recorded who made it, when they believed they made it, and which version of the program remembered it. This reduced paradoxes by twelve percent and increased documentation by four centuries.
Top causal risks
| Risk or dependency | Archive rating | Response |
|---|---|---|
| Team prevents problem that justified project funding | Likely / Existential | Preserve original business case outside editable timeline. |
| Sponsor changes past decision after seeing result | Certain / Executive | Require change control across all affected centuries. |
| Project manager meets future self | Already occurred / Awkward | Do not compare notes in front of the team. |
The final deployment completed forty-two days before its planned start and six months after its cancellation. Finance refused to recognize the savings because they had been spent in an obsolete timeline. The dashboard showed green, amber, and a new status called ‘philosophically pending.’
“We would have finished on time if the deadline had remained where we left it.”
Closing statement, delivered twice
At closeout, I archived one immutable baseline in a room time travel could not enter. It was called Records Management. Future teams regarded this as the project’s most improbable technology. I then received a message from myself advising against the entire engagement. It arrived, as usual, after invoicing.
Recovered lessons learned
What the archive insists we learned
- Never baseline against an event the sponsor can edit retroactively.
- Dependencies need stable owners even when dates are unstable.
- A lessons-learned meeting is less useful when participants can simply go back and deny the lesson.