COLUMN
Training completion rates don’t count
as generative AI adoption
Completion records will remain. The completion rate isn’t adoption. This article is only about not counting generative AI training completion rates as adoption. No plan document needed.
Before reporting it, separate the completion rate from the one line of work to keep →Please don’t send the attendance roster. 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 completion rate doesn’t go in the adoption column
The company-wide kickoff and briefing session is a separate article. So is the send-back decision in in-house PMO training. So is issuing a guideline. This article is only about one thing: generative AI training completion rates don’t count as adoption.
- NG (counting the completion rate as adoption)
- A 92% completion rate for company-wide generative AI training is listed as an adoption KPI
Training can be added later. Completion isn’t adoption.
- OK (the completion rate isn’t counted as adoption)
- The completion rate goes in the training-operations column. Not in the adoption column
If there’s work to keep, it’s one line from a department that can name one task. Once that line exists, adding training is fine. Collecting completion certificates first doesn’t produce one task. Whether certificates are needed is outside this article’s scope.
The line of work to keep and the timing of the completion rate are kept separate. No attendance roster is needed in your enquiry. We don’t make that decision on your behalf.
What tends to remain a quarter after counting the completion rate as adoption
| What was kept first | What tends to remain at the next meeting |
|---|---|
| The completion rate was counted as adoption | The completion percentage remains. There’s no line of work to keep |
| The completion rate was written in the adoption column of the board report | The percentage remains. There’s no line of work to keep |
| Test scores were kept | Scores remain. The lines of work to keep don’t increase (whether tests are needed is outside this article’s scope) |
The first one weighs the most. The observation is that the completion percentage tends to remain as a matter of training operations. What counts as adoption isn’t the completion rate.
Before reporting it, separate the completion rate from the one line of work to keep →Please don’t send the attendance roster. 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 completion rate 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 |
| Number not listed under adoption | The training completion rate. Not counted as adoption until the line of work to keep exists. Adding training afterwards is fine |
| Added later | Put the line of work to keep first (just the department name if unsure). After that, adding training is fine |
Putting the completion rate 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 a training curriculum.
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 training content or HR procedures.
The one line to write in your enquiry — not a completion-rate table
| Department | Category | The one line of work to keep |
|---|---|---|
| Facilities maintenance | Keep | One line: inspection-record drafts can be written. Not listed in the adoption column |
| Generative AI training | Not counted as adoption | — (the completion rate isn’t listed under adoption until the line of work to keep exists; adding training afterwards is fine) |
| Store development | Later | — (the next line isn’t written until Facilities’ line can be put in the enquiry; just the department name if unsure) |
The observation is that a line of work to keep tends not to stick when it rests on self-reporting alone. No attachment is needed when you contact us. Just the department name is enough if unsure.
You don’t need a plan document to decide whether to add training. Your enquiry only needs the one line of work to keep (e.g. Facilities maintenance | inspection-record drafts; just the department name if unsure). No plan document or internal material is required.
No need to hand over the attendance roster first. What the meeting wants is the one line of work to keep.
Before reporting it, separate the work to keep from the completion rate
Before reporting the completion rate, we start from the one line of work to keep. 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 the attendance roster. No plan document needed.
Before reporting it, separate the completion rate from the one line of work to keep →
References
Briefing sessions: Don’t start with a kickoff
Training: The send-back decision in in-house PMO training
Guidelines: Issuing one doesn’t count as adoption
Our service: Metamon (generative-AI usage diagnostic)
This article is a general framing, not legal, regulatory, or contractual advice.