Handing out a prompt library
doesn’t count as 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 which prompts to keep, and it applies equally to another provider’s assessment or an in-house exercise.

Before distribution — don’t count handing out as adoption

The company-wide kickoff and briefing session is a separate article. So is in-house PMO training. This article is only about one thing: publishing a prompt library, templates, or an internal GPT landing page doesn’t count as adoption.

NG (counting distribution as adoption)

The company-wide prompt library is published on SharePoint, and “distribution complete” is recorded as adoption

The page can be published. It can be searched. It stays up. None of that is a criticism of the library. What you keep first is three prompts used in one task.

OK (the three prompts to keep, by name)

For proposal writing in Sales, keep three: “differences vs. three competitors”, “extract the conditions”, and “anticipated Q&A”. Nothing else goes in the company-wide folder

The 200-prompt catalogue can be added after those three have been used. Don’t rely on self-reporting alone — attach a log or a confirmation from the owner.

The split follows wherever your company keeps shared files. We don’t make that decision on your behalf. Nothing here recommends buying or not buying any particular prompt product.

What tends to remain a quarter after distributing the library first

What was distributed first	What tends to remain at the next meeting
A company-wide prompt library was published	Page views exist. Nobody can say which three were kept
“Please use this” was placed on the internal GPT landing page	The entry point remains. Nobody can say which three were kept
Each department was asked to add more templates	The count grows. It never narrows to one task actually using them

The first one weighs the most. Publishing is an information-sharing job, and it’s fine as that. Naming the three prompts is something only the task that used them can do.

Before you distribute the library, confirm the three prompts to keep →We confirm one line: the three prompts used in one task, and what isn’t distributed yet. Our Metamon diagnostic starts from those three. No plan document

The three to keep, and what isn’t distributed yet

Target	Treatment
The three to keep first	The names of three prompts used in one task can be stated on the spot. Only these go at the top of the catalogue
Not distributed yet	Not placed in the company-wide folder. Even if requests come in, nothing is added until the first three are in use
Added after measurement	Once logs confirm the three were used, a fourth and beyond for the same task can be added

Don’t publish all 200 at once. Publishing everything at once defers the blank at the next meeting.

The one line in the impact section is a separate article (what goes in the report). This article comes before that: cutting the catalogue you distribute down to three.

If you bring in an external assessment, “the names of the three to keep” is easier to work with than a company-wide catalogue (our Metamon works on the same premise). A first conversation starts from those three. Whether to order an assessment or sign anything can wait until you have seen the split.

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

Department	Category	The one line: three to keep
Sales	Keep first	Proposal writing. Keep three: “differences vs. three competitors”, “extract the conditions”, “anticipated Q&A”
HR	Not distributed yet	— (no HR templates in the company-wide folder)
IT	After measurement	— (the catalogue isn’t expanded until the scope of chat-log retention is settled under internal policy)

The three to keep 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 the scope of a prompt library. 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 three to keep” line (e.g. Sales | proposals | differences / conditions / Q&A) or the name of a department not distributed to yet (leave it blank if unsure).

No need to hand over the company-wide template list first. What the meeting wants is the one line naming the three to keep.

---

References
Briefing sessions: Don’t start with a kickoff
Training: The order of in-house PMO training
The impact line: Don’t write “people found it useful”
Ownership: Don’t leave generative AI ownership to IT alone
Our service: Metamon (generative-AI usage diagnostic)

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