Get In Touch
Ch. du Vernay 14a
Gland 1196 CH-Vaud
me@haideralleg.com
Ph: +‪41 21 561 28 48‬
Back

Every AI Deployment Should Carry an Exit Date Before Anyone Signs It

TLDR: Every deployment memo sets a budget, an owner and a go-live date. Whoever signs the go-live should also sign the exit date, its trigger and the fallback, in the same memo.

The exit belongs in the approval, signed by the same hand

An artificial intelligence (AI) approval memo usually answers three questions: what the system costs, who owns it and when it goes live. The fourth question is the one that decides the most and gets asked the least: on what date does this approval run out, and what has to be true for someone to sign it again?

That question decides who pays when the system stops. Systems do stop. They stop because the numbers turn, because a court rules, or because the people using them stop trusting the output. When the end date stays unwritten, the exit arrives on someone else’s timetable, and the cost lands on the people with the least say over it.

The exit belongs in the approval itself, signed at the same moment and by the same person who signs the go-live. One government has already written it that way. Three well-documented exits show what happens when the memo leaves it out. And a six-line clause, set out below, turns the idea into something a sponsor can attach to the next memo that crosses the desk.

Leave a Reply

Your email address will not be published. Required fields are marked *

Login

Login Form

New here? Become a Member to get started!

Subscribe

Membership

About yourself

Let us know who you are to tailor your experience


Membership

Every month access unique content and earn 1 session of coaching with me


Apply Coupon

We care about your privacy

Please read and consent for your data processing.


Have an account? Sign in to continue.