Don’t create the generative AI
office first

Written by Kazuo Yutani, Representative of Metamorphose LLC. Observations from PMO work on what happens after generative AI goes live at financial institutions and corporate teams. Metamorphose offers the Metamon generative-AI usage diagnostic; this article is about not creating the office first, and it applies equally to another provider’s assessment or an in-house exercise.

Before the box — don’t create the office first

Not leaving ownership to IT alone is a separate article. So is not counting a company-wide weekly as a start. This article is only about one thing: don’t create the box called “AI promotion office” first.

NG (create it first)

Create the generative AI promotion office first

The office can be added later. It’s not the box to create first.

OK (don’t create it first)

The generative AI promotion office is not created first

If there’s work to keep, it’s one line from a department that can name one task. Once that line exists, adding the office is fine. Writing the office’s mission statement first doesn’t produce one task.

The split follows your own organisation. We don’t make that decision on your behalf.

What tends to remain a quarter after adding the office first

What was added first	What tends to remain at the next meeting
The promotion office was created first	The office name remains. There’s no line of work to keep
The office’s mission was written first	The policy remains. Nobody can name one task
Part-time members were gathered from other departments	The roster remains. The lines of work to keep don’t increase

The first one weighs the most. The observation is that the office name and the seats tend to remain. It’s not the box to create first.

Before creating the office, separate it from the one line of work to keep →Please don’t send an org-chart draft. The form only needs the one line of work to keep (just the department name if unsure). Our Metamon diagnostic starts from that line. No plan document

The work to keep, and the box not to create first

Target	Treatment
Work to keep	One line from a department that can name one task. Not listed under the promotion office
Box not created first	The generative AI promotion office. Not listed until the line of work to keep exists
Added later	Once the line of work to keep is confirmed by a log or the owner, decide whether to add the box (adding it is fine)

Putting the office and the work to keep on the same agenda tends to defer the blank at the next meeting — that’s an observation, not an instruction on how to structure approvals.

What a CEO who doubles as PM hands over is a separate article. This article is about not creating the promotion office first.

If you bring in an external assessment, “the one line of work to keep” is easier to work with than a promotion office (our Metamon works on the same premise). A first conversation starts from that line. Our Metamon diagnostic also uses that line as its entry point.

The note you can write in-house before the meeting — not a plan document

Department	Category	The one line of work to keep
Procurement	Keep	One line: the description field on purchase orders can be drafted. Not listed under the promotion office
Generative AI promotion office	Not created first	— (not listed until the line of work to keep exists; adding it afterwards is fine)
Corporate communications	Later	— (not listed under the office until Procurement’s line is confirmed by a log or the owner)

The line of work to keep shouldn’t rest on self-reporting alone. If a log or the owner can confirm it, that’s enough — no attachment is needed when you contact us.

You don’t need a plan document to decide whether to create the office first. 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 one line of work to keep (e.g. Procurement | purchase-order description; just the department name if unsure).

No need to hand over an org-chart draft first. What the meeting wants is the one line of work to keep.

---

References
Ownership: Don’t leave generative AI ownership to IT alone
Weekly meetings: Don’t count a company-wide weekly as a start
The CEO as PM: What to hand over as a CEO who doubles as PM
Our service: Metamon (generative-AI usage diagnostic)

This article is a general framing, not legal, regulatory, or contractual advice.