The first four weeks of AI governance

Description and use

<p>Ask a company for the list of AI systems it runs and you get a procurement export: licensed tools, seat counts, renewal dates. It is an accurate answer to a question nobody asked. The marketing assistant somebody wired into the CRM through a no-code connector is not on it. Neither is the Python script an analyst wrote in March that calls a model API on a schedule and mails the output to four people. Neither is the AI feature in the helpdesk product bought in 2023, which the vendor switched on in a quarterly update and announced in a changelog.</p> <p>That absence is the whole problem, and i

Problem

<p>Ask a company for the list of AI systems it runs and you get a procurement export: licensed tools, seat counts, renewal dates. It is an accurate answer to a question nobody asked. The marketing assistant somebody wired into the CRM through a no-code connector is not on it. Neither is the Python script an analyst wrote in March that calls a model API on a schedule and mails the output to four people. Neither is the AI feature in the helpdesk product bought in 2023, which the vendor switched on in a quarterly update and announced in a changelog.</p> <p>That absence is the whole problem, and i

Outcome

<p>Ask a company for the list of AI systems it runs and you get a procurement export: licensed tools, seat counts, renewal dates. It is an accurate answer to a question nobody asked. The marketing assistant somebody wired into the CRM through a no-code connector is not on it. Neither is the Python script an analyst wrote in March that calls a model API on a schedule and mails the output to four people. Neither is the AI feature in the helpdesk product bought in 2023, which the vendor switched on in a quarterly update and announced in a changelog.</p> <p>That absence is the whole problem, and i

Evidence

The first four weeks of AI governance

Source