COLUMN
Don’t leave generative AI ownership
to IT alone
Account provisioning and the admin center can sit with IT. A quarter later, the task count may not appear in any department’s column. Once the rollout order is set (or alongside it), this is only about where the owner sits. No plan document needed.
Before the steering meeting, write the one line on ownership →We separate what the business unit owns from what IT owns. No plan document, no sales deck after the call
Before the org structure — don’t start with IT alone
What a CEO who doubles as PM hands over is a separate article. So are the three conditions before adding an external PMO. This article is only about one thing: don’t leave generative AI ownership to IT alone.
- NG (ownership sits only in IT)
- Generative AI owner = the IT department. Business units are “users”
Accounts can be issued. The admin center can be checked. A quarter later, which task and how many times may appear in neither IT’s column nor the business unit’s. None of that is a criticism of IT. What you decide first is where one task’s ownership sits.
- OK (the one line that splits ownership)
- Quality Assurance generates 8 defect-report drafts a week (owner: QA; IT keeps the logs)
Write the count in one unit only (e.g. 8 per week — pick one of week / month / quarter). Don’t rely on self-reporting alone. Attach a log or a confirmation from the owner.
The split follows your own org chart. We don’t make that decision on your behalf.
What tends to remain a quarter after leaving it with IT alone
| How it was set up | What tends to remain at the next meeting |
|---|---|
| One part-time person in IT was made the owner | Provisioning and deprovisioning run. The task-name and count columns stay blank |
| Business units were made “users” only | Impressions are collected. No department holds ownership |
| IT hosts the company-wide steering meeting | Attendance is recorded. The department that will write the next count never gets decided |
The first one weighs the most. Provisioning and deprovisioning are IT’s job, and that’s enough. Writing the count is done by the department that owns the task.
Before the steering meeting, write the one line on ownership →We separate what the business unit owns from what IT owns. No plan document, no sales deck after the call
The three ways to split ownership
| Target | What it holds |
|---|---|
| The business unit that owns first | Can state one task and a count on the spot. The owner’s reporting line and the department named in meetings also sit here |
| What IT holds | Accounts, log retention, the bundled admin center. Not the count column |
| Departments not assigned yet | Listed as neither users nor owners. Not mixed into the same person’s remit |
Don’t consolidate company-wide ownership into one person. A single company-wide owner defers the blank at the next meeting.
The order of departments to roll out to is a separate article (who gets accounts). This article comes after that: which business unit holds the count and the owner’s reporting line.
If you bring in an external assessment, “one business unit that owns first” is easier to work with than a single company-wide owner (our Metamon works on the same premise). A first conversation starts from the ownership split. Whether to order an assessment or sign anything can wait until you have seen the split.
The note you can write in-house before the meeting — not a plan document
| Department | Category | The one line on ownership |
|---|---|---|
| Quality Assurance | Owns first | QA generates 8 defect-report drafts a week (owner: QA) |
| IT | IT holds | Accounts and log retention. Not the count column |
| HR | Not assigned yet | — (listed as neither owner nor user) |
The count in the ownership line shouldn’t rest on self-reporting alone. Attach one of: a log, a ledger, or a confirmation from the owner.
You don’t need a plan document to decide the owner. These three columns are what you can write in-house before the meeting. When you contact us, no plan document or internal material is needed either. The form only needs “the ownership line” (e.g. QA | defect reports | 8 per week) or the name of a department not assigned yet (leave it blank if unsure).
No need to hand over the company-wide org chart first. What the meeting wants is the one line from the business unit that owns first.
Before assigning an owner, separate what the business unit holds from what IT holds
We sort it out in line with your own org chart. No plan document needed. We don’t send a sales deck. Individual approval and contract decisions follow your own internal rules.
Before the steering meeting, write the one line on ownership →
References
The CEO as PM: What to hand over as a CEO who doubles as PM
Rollout order: Company-wide rollout starts with one department
External PMO: Three things to check before adding a seat
How to measure: The three generative-AI adoption metrics
Our service: Metamon (generative-AI usage diagnostic)
This article is a general framing, not legal, regulatory, or contractual advice.