PM-201c · Module 3

Org-Wide Prompt Governance

3 min read

At organizational scale, prompt quality is not just a technical problem — it is a governance problem. Who owns each prompt determines who is accountable when it underperforms. Who can change a prompt determines how fast it can be updated and what oversight exists. How changes are reviewed determines whether the testing discipline holds under deadline pressure. Without explicit governance, the system defaults to whoever edits the file last — which is not a governance model.

  1. Define ownership Every production prompt has one owner — a named individual or role who is accountable for its performance. Ownership includes: maintaining the prompt, reviewing change requests, running regression tests before promotion, and responding to production incidents. Shared ownership without a primary is no ownership.
  2. Define change authority Who can modify a production prompt? Who must approve modifications before they are promoted? PATCH changes may require only the owner's approval. MINOR changes may require owner plus one reviewer. MAJOR changes may require team lead sign-off and mandatory golden dataset testing. Define the authority levels explicitly.
  3. Define the review process What steps must a prompt change go through before production promotion? Change request, review, golden dataset test, approval, changelog entry, deployment. The process should be light enough to allow necessary changes and robust enough to catch harmful ones. Write it down and enforce it consistently.
  4. Define the incident response When a production prompt failure is detected — error rate spikes, quality complaint received, A/B test shows regression — what happens? Who is notified? How fast must the owner respond? When does automatic rollback trigger? Incident response defined before the incident is resolved during it. Defined after is scrambling.

Do This

  • Assign a named owner to every production prompt — one person, not a team
  • Define change authority by version type: patch, minor, major
  • Require golden dataset testing before any production promotion
  • Write the governance process before the first production prompt is deployed

Avoid This

  • Do not let "everyone owns it" be the ownership model — it means no one does
  • Do not allow production changes without a documented review and approval step
  • Do not skip governance because the team is small — small teams grow, and governance is harder to add than to maintain
  • Do not define incident response during the incident — define it in advance

If it is not written down, it did not happen. If it is not governed, it will drift.

— FORGE