COLUMN
Don’t start generative AI
with the all-hands briefing
“How to use it” goes on the kickoff deck first. Attendance is high. A quarter later, “we heard about it” can still be standing in for “we’re using it.” What you decide first isn’t the date — it’s the one task where you can state who / for what / how often. No plan document needed.
Before the briefing, carve out one task →We separate the session people listen to from the task people use it for. No plan document, no sales deck after the call
Before the kickoff — don’t start with the briefing
IT schedules an all-employee briefing. Attendance is easy to get. A quarter later, there are logins. “We’re using it,” people say. The frequency column can stay blank.
The order in which seats are handed out is rollout order. Training for an in-house PMO is a separate topic. This article is about not starting generative AI with the briefing or the kickoff. It doesn’t dismiss briefings themselves. What you decide first isn’t who listens — it’s the one task where it gets used.
This is a way of splitting that fits your own rollout rules. We don’t make that decision on your behalf.
What tends to remain a quarter after starting with the briefing
| How it started | What tends to remain a quarter later |
|---|---|
| The all-employee briefing was called “rollout complete” | “We heard about it” stands in for “we’re using it” |
| Tool walkthroughs went out first | People know the buttons. For what / how often never lines up |
| A company-wide success-story session was held | Impressions come in. No task gets chosen to copy |
The first one weighs the most. “We heard about it” is a way of deferring the judgment that nobody is using it.
Before the briefing, carve out one task →No plan document, no sales deck after the call
Three things to decide before the briefing
| Target | Condition for inclusion |
|---|---|
| The one task to use it for first | Can state who / for what / how often on the spot. Brief this group only |
| Departments not to brief yet | Can’t state it. Don’t put them in the same kickoff audience |
| Departments to brief after the numbers | Look at them once the first task’s logs are in. Don’t run the sessions at the same time |
Don’t start with the largest audience. Headcount is a conversation for after the tool has been used.
For the kickoff deck, write department / one task / frequency. Example: Sales Planning | proposal drafts | weekly. The walkthrough comes after.
How to measure is in the three metrics; what to do after a success is in don’t make a pilot success the company-wide case. This article is about deciding, before either of those, how far the briefing reaches.
If you bring in an external assessment, “the one task to use it for first” is easier to run than “the all-hands briefing” (our Metamon works on the same premise). A first conversation starts from cutting the briefing scope. 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 kickoff — not a plan document
| Department | Use first / Not yet / After the numbers | The one line for the kickoff |
|---|---|---|
| Sales Planning | Use first | Generates proposal drafts weekly. The only briefing audience |
| Accounting | Not yet | Not in the all-hands kickoff audience |
| IT | After the numbers | Add the walkthrough after seeing the first task’s logs |
You don’t need a company-wide briefing plan. These three columns are what you can write in-house before the kickoff. When you contact us, no plan document or internal material is needed either. If you know things like the license unit price, the free-text field on the form is enough (leave it blank if not).
No need to hand over a company-wide sheet of impressions first. What the kickoff wants is the one task to use it for first.
Before the briefing, decide only the one task to use it for
Before briefing all employees, we separate the task to use it for first from the departments not to brief yet. No plan document needed. We don’t send a sales deck. Individual rollout, approval, and contract decisions follow your own internal rules.
Before the briefing, carve out one task →
References
Distribution order: Company-wide rollout starts with one department
After a success: Don’t make a pilot success the company-wide case
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.