Don’t count the company-wide weekly
as the start of generative AI adoption

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 how to set up a weekly, and it applies equally to another provider’s assessment or an in-house exercise.

Before the meeting — don’t count the weekly as the start

The company-wide briefing or kickoff is a separate article. So is training for an in-house PMO. This article is only about not counting the weekly or the adoption meeting as the start.

NG (counting the meeting as the start)

The company-wide generative AI weekly is counted as the start of adoption

Invites can go out. Attendance is recorded. The weekly itself isn’t the problem. What you cut first is counting it as the start.

OK (not counted as the start)

The company-wide generative AI weekly is not counted as the start of adoption

If there is a meeting worth keeping, it’s fifteen minutes for the one department that can write down its task. Don’t build a company-wide agenda.

This is a split that fits your own meeting structure. We don’t make that decision on your behalf.

What tends to remain a quarter after scheduling the weekly first

What was scheduled first	What tends to remain at the next meeting
The company-wide weekly was called the start of adoption	Attendance stays. No one line for the meeting worth keeping
Progress sharing became the purpose of the weekly	More slides. No single task can be named
Recordings were circulated to absentees	Views are recorded. The meetings counted as “the start” don’t shrink

The first one weighs the most. Attendance is the meeting organizer’s job, and it’s fine there. The start of adoption isn’t the weekly.

Before scheduling it, separate the weekly from the one meeting worth keeping →Please don’t send the company-wide agenda. The form only needs the one line for the meeting you keep (or just the department name). Our diagnostic (Metamon) starts from that line. No plan document

The meeting to keep, and the standing meeting not to schedule

Target	Treatment
The meeting to keep	Fifteen minutes for the one department that can write down its task. Not a company-wide weekly
The standing meeting not to schedule	The company-wide generative AI weekly. Doesn’t go in the “adoption started” column
What to add later	Once the kept meeting’s one line is backed by a log or an owner’s confirmation, add time for that same department only

Don’t fold the company-wide weekly and the fifteen-minute department meeting into the same invite. Folding defers the blank at the next meeting.

Where the AI lead sits is a separate article (whose column it goes in). This article is about not counting the weekly as the start.

If you bring in an external assessment, “the one line for the meeting you keep” is easier to work with than a company-wide weekly (our Metamon works on the same premise). A first conversation starts from that one line. Whether to order an assessment or sign anything can wait until you have seen the result of the cut.

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

Department	Category	The one line for the meeting you keep
Production Control	Keep	Fifteen minutes where shift-report drafts get written. Not a company-wide weekly
HR	Don’t schedule	— (in neither the company-wide weekly nor a kept meeting)
IT	Later	— (not invited until the kept meeting’s one line is in place)

The one line for the kept meeting 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 whether to schedule a weekly. 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 kept meeting’s line” (e.g. Production Control | shift reports | 15 min / no company-wide weekly) or the name of a department not to schedule (leave it blank if unsure).

No need to hand over the company-wide weekly agenda first. What the meeting wants is the one line for the meeting you keep.

---

References
Briefing: Don’t start with the kickoff
Training: The order of in-house PMO training
Our service: Metamon (generative-AI usage diagnostic)

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