chapter eleven

11 Managing prompts in production

 

This chapter covers

  • Diagnosing where your team sits on the prompt management maturity curve and the next practical step
  • Moving prompts through a structured lifecycle: draft, test, approve, deploy, observe, improve, retire
  • Designing lightweight governance for a shared library: ownership, access, and approval without the friction
  • Reading the signals a well-run process produces to decide which prompts need attention
  • Recognizing the 10 most common prompt management failures and the targeted fixes for each

In chapter 5, you built prompt templates, reusable blueprints that separate stable instructions from variable inputs, making prompts easier to maintain and share. In chapter 10, you learned that a well-crafted, precisely constrained prompt is a harder target for adversarial manipulation. Both chapters shared an underlying principle: prompts are artifacts worth designing carefully, not just strings to write once and forget. Chapter 11 follows that principle to its practical conclusion. A well-engineered prompt is still fragile if it has no owner, no version history, and no process for changing it safely. This chapter is about what happens after the prompt is written.

11.1 Why prompt management matters

11.1.1 The six pillars of prompt management

11.1.2 Build vs. buy

11.1.3 Practical example 1: The support bot audit

11.2 The maturity journey

11.2.1 Stage 1: Inline prompts

11.2.2 Practical example: The weekend hack that shipped

11.2.3 Stage 2: Config files and version control

11.2.4 Practical example: The product manager problem

11.2.5 Stage 3: Prompt store

11.2.6 Practical example: The stale prompt discovery

11.2.7 Stage 4: Dedicated prompt management system

11.2.8 Practical example: The promotion without an approval record

11.3 The prompt lifecycle

11.3.1 Draft

11.3.2 Practical example: The underspecified draft

11.3.3 Test

11.3.4 Practical example: The invisible regression

11.3.5 Approve

Summary