COLUMN
Issuing a generative AI guideline
doesn’t count as adoption
A guideline can be issued. The read receipts will remain. Issuing it isn’t adoption. This article is only about not counting an issued guideline document as adoption. No plan document needed.
Separate the one line of work to keep from the guideline you issue later →Please don’t send a policy 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
Before the document — don’t count issuing as adoption
The company-wide kickoff and briefing session is a separate article. So is not counting a distributed prompt library as adoption. This article is only about one thing: issuing a guideline document doesn’t count as adoption.
- NG (counting the issued document as adoption)
- Issuing the generative AI guideline is counted as adoption
The document can be issued later. Issuing it isn’t adoption.
- OK (issuing isn’t counted as adoption)
- Issuing the generative AI guideline is not counted as adoption
If there’s work to keep, it’s one line from a department that can name one task. Once that line exists, issuing the document is fine. Circulating the prohibited-uses wording first doesn’t produce one task. Whether prohibitions are needed is outside this article’s scope.
The line of work to keep and the timing of the guideline are kept separate. No policy draft is needed. We don’t make that decision on your behalf.
What tends to remain a quarter after counting the guideline as adoption
| What was issued first | What tends to remain at the next meeting |
|---|---|
| Issuing the guideline was counted as adoption | Read receipts remain. There’s no line of work to keep |
| The prohibited-uses document was circulated first | The document remains. Nobody can name one task (whether prohibitions are needed is outside this article’s scope) |
| Read-receipt records were kept | Read receipts remain. The lines of work to keep don’t increase (whether the procedure is needed is outside this article’s scope) |
The first one weighs the most. The observation is that read receipts tend to remain as a matter of document administration. What counts as adoption isn’t the issued guideline.
Separate the one line of work to keep from the guideline you issue later →Please don’t send a policy 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 document not listed under adoption
| Target | Treatment |
|---|---|
| Work to keep | One line from a department that can name one task. Not listed in the adoption column |
| Document not listed under adoption | The generative AI guideline. Not counted as adoption until the line of work to keep exists. Issuing it afterwards is fine |
| Issued later | Once the line of work to keep is confirmed by a log or the owner, decide whether to issue the document (issuing it is fine) |
Putting the guideline 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 write internal policy.
Not writing “people found it useful” in the impact section is a separate article. This article is about not counting an issued guideline document as adoption.
The one line of work to keep is the entry point for our diagnostic (Metamon). A first conversation starts from that line (just the department name if unsure). The diagnostic doesn’t cover the wording of the guideline or HR procedures.
The one line to write in your enquiry — not a plan document
| Department | Category | The one line of work to keep |
|---|---|---|
| Logistics | Keep | One line: delivery-delay notices can be drafted. Not listed in the adoption column |
| Generative AI guideline | Not counted as adoption | — (not counted as adoption until the line of work to keep exists; issuing it afterwards is fine) |
| Product planning | Later | — (the next line isn’t written until Logistics’ line is confirmed by a log or the owner) |
The observation is that a line of work to keep tends not to stick when it rests 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 issue the guideline. Your enquiry only needs the one line of work to keep (e.g. Logistics | delivery-delay notices; just the department name if unsure). No plan document or internal material is required.
No need to hand over a policy draft first. What the meeting wants is the one line of work to keep.
Separate the one line of work to keep from the guideline you issue later
Once the line of work to keep exists, issuing the guideline is fine. Our Metamon diagnostic uses that line as its entry point. The form needs one line (just the department name if unsure). Please don’t send a policy draft. No plan document needed.
Separate the one line of work to keep from the guideline you issue later →
References
Briefing sessions: Don’t start with a kickoff
Prompt libraries: Distribution doesn’t count as adoption
The impact line: Don’t write “people found it useful”
Our service: Metamon (generative-AI usage diagnostic)
This article is a general framing, not legal, regulatory, or contractual advice.