COLUMN
Generative AI success stories aren’t
measured by case-study PDF views
Compiling other departments’ success stories into a PDF doesn’t give your own department one task to keep. Views are a communications number. They don’t go in the adoption column. No plan document needed for the form.
Separate the case-study collection from the one line of work to keep →Please don’t send the case-study PDF. 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 case-study PDF doesn’t go in the adoption column
Not counting a distributed prompt library as adoption is a separate article. So is issuing a guideline. So is not writing “people found it useful” in the impact section. This article is only about one thing: don’t measure by case-study PDF views.
- NG (counting PDF views as adoption)
- The view count of the company-wide generative AI success-story collection is listed as an adoption KPI
The collection can be published later. Views aren’t adoption.
- OK (views go in the communications column)
- What’s kept as a success story is one line from a department that can name one task. Case-study PDF views go in the communications column
If there’s work to keep, it’s one line from a department that can name one task. Once that line exists, publishing the collection is fine. Circulating other departments’ success stories first doesn’t produce one task.
The line of work to keep and the timing of the collection are kept separate. No case-study PDF is needed on the form.
What tends to remain a quarter after counting the PDF as adoption
| What was kept first | What tends to remain at the next meeting |
|---|---|
| The case-study PDF was counted as adoption | Views remain. There’s no line of work to keep |
| Other departments’ success stories were circulated first | The stories remain. Nobody can name one task |
| PDF views were written as an adoption KPI | Views remain. The lines of work to keep don’t increase |
The first one weighs the most. The observation is that view counts tend to remain. It isn’t the collection that counts views as adoption. Once the line exists, publishing is fine.
Separate the case-study collection from the one line of work to keep →Please don’t send the case-study PDF. 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 communications number, and the PDF not listed under adoption
| Target | Treatment |
|---|---|
| Communications number | Case-study PDF views. Not listed in the adoption column |
| Document not listed under adoption | The success-story collection. Not counted as adoption until the line of work to keep exists. Publishing it afterwards is fine |
| Published later | Put the line of work to keep first (just the department name if unsure). After that, publishing the collection is fine |
Putting the collection 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 communications copy.
The one line of work to keep is the entry point for our diagnostic (Metamon). The split starts from that line (just the department name if unsure).
The one line to write on the form — not a case-study PDF
| Department | Category | The one line of work to keep |
|---|---|---|
| Reservations | Keep | One line: cancellation-notice drafts can be written. Not listed in the adoption column |
| Success-story collection | Not counted as adoption | — (the collection isn’t listed under adoption; the form takes the one line of work to keep — just the department name if unsure) |
| Membership | Later | — (the next line isn’t written until Reservations’ line can be put on the form; 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 on the form. Just the department name is enough if unsure.
You don’t need a plan document to decide whether to publish the collection. The form only needs the one line of work to keep (e.g. Reservations | cancellation-notice drafts; just the department name if unsure). No plan document or internal material is required.
No need to hand over the case-study PDF first. What the meeting wants is the one line of work to keep.
Separate the work to keep from the case-study collection
Whether the collection is already out or still to come, 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 case-study PDF. No plan document needed.
Separate the case-study collection from the one line of work to keep →
References
Prompt libraries: Distribution doesn’t count as adoption
Guidelines: Issuing one 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.