Prompts as Team Assets
One Person's Good Prompt Is Everyone's
In most teams, prompting knowledge is invisible. One person has quietly worked out a genuinely good prompt for meeting notes; everyone else is still writing "summarise this" and being unimpressed. Nobody is hiding anything — it simply never occurs to people that a prompt is a shareable artefact rather than something you type and discard. Making them shared changes the economics: the twenty minutes one person spends refining a prompt pays off across everyone who uses it, and the improvements compound because more people hit more edge cases. The bar is low. A shared document with a handful of good prompts, each with a note on what it is for, beats nothing by a very large margin.
- Prompting skill spreads through sharing artefacts, not through training sessions
- A shared doc with ten good prompts is enough to start — do not over-engineer it
- Label each prompt with what it is for and what it is not for
- The refinement cost is paid once and the benefit is spread across the team
Version Them Like Anything Else You Rely On
Once several people depend on a prompt, it needs the ordinary discipline of a shared asset. Keep the current version in one place rather than in five copies drifting apart in different inboxes. Note when it changed and why, because "we changed the output format in March" explains a lot of confusion later. Keep the old version until the new one has been used in anger. And name an owner — shared assets with no owner decay quietly, and prompts decay in a particularly hard-to-notice way, because the output keeps looking fine while slowly drifting from what anyone actually wanted. None of this needs tooling. A dated document and a named person is genuinely sufficient for most teams.
- One canonical copy — forked copies drift and nobody knows which is current
- Record what changed and why; output changes confuse people who missed the update
- Name an owner, or the library rots while still looking healthy
- A dated shared document is enough; the discipline matters more than the tooling
Document the Judgement, Not Just the Text
The most valuable thing to write down alongside a shared prompt is not the prompt. It is what someone learned using it. Which cases it handles badly. What to check in the output before sending it. Which correction people keep having to make. Whether the thing it produces is a final draft or a starting point. A prompt with three lines of honest usage notes is far more useful than a prompt on its own, because it transfers the judgement rather than just the words — and judgement is the part that takes weeks to acquire and thirty seconds to write down once someone has it.
- Note the known failure cases — that is the expensive knowledge
- State what to check before the output is used or sent
- Say plainly whether the result is a draft or something near-final
- Three lines of usage notes double the value of any shared prompt
Prefer slides, quizzes, and saved progress? Read this lesson in the library — free, no sign-up.