← Back to Concept Contrast

Concept Contrast Fable

Prompt engineering and prompt management

Conclusion first:Prompt engineering is about "how to write a good prompt"; prompt management is about "how to keep a hundred prompts from causing chaos." The former cares about single-run effectiveness; the latter cares about versioning, testing, deployment, and rollback. An engineer can write a beautiful prompt, but if ten people on the team each make their own edits, no one runs regressions before release, and when something breaks no one knows which version was changed—even a beautiful prompt becomes a production incident.

Prompt engineering is about "how to write a good prompt"; prompt management is about "how to keep a hundred prompts from causing chaos." The former cares about single-run effectiveness; the latter cares about versioning, testing, deployment, and rollback. An engineer can write a beautiful prompt, but if ten people on the team each make their own edits, no one runs regressions before release, and when something breaks no one knows which version was changed—even a beautiful prompt becomes a production incident.

Fable

The cook and the kitchen rules

Old Zhao's restaurant had only one stove, and he was the only one there, pondering new dishes every day. He tried twenty ratios of sugar color for braised pork and adjusted eight doubanjiang blends for twice-cooked pork, keeping every seasoning formula in his head. Customers praised the food, and Old Zhao's reputation grew.

The restaurant expanded to five branches, and Old Zhao hired five stove chefs, printing his recipes into booklets and handing them out. The first two weeks were calm, but trouble started in the third week. Branch One's Kung Pao Chicken was too sweet, Branch Two's Mapo Tofu wasn't numbing, and Branch Three's Yuxiang Shredded Pork had turned into sweet-and-sour.

Old Zhao made the rounds of each shop's kitchen and found that every cook had a little notebook with his own notes. One said, I think it sells better with less sugar; another said, an old customer told me it was too spicy so I adjusted it. Everyone was changing the recipe, and no one told the others after changing it. Old Zhao didn't know which version he'd be tasting on any given day he came to inspect the dishes.

Old Zhao called the head chefs of the five stores back for a meeting and set three rules. First, recipes would be kept in unified custody; any change required submitting a modification request stating which parameter was changed and why. Second, every time a recipe was revised, three dishes had to be made with the same batch of ingredients, and the quality controllers from the three stores each had to taste a bite; only if the scores passed would it take effect. Third, all recipes would retain historical versions, so that if a customer said last month's fish-flavored shredded pork tasted better, the kitchen could immediately retrieve last month's version of the recipe.

When the rules were first introduced, the masters complained the process was too slow. Two months later, something happened: Store No. 3 received customer complaints for three consecutive days, saying the Kung Pao Chicken tasted wrong. Old Zhao opened the version book and found that a week earlier someone had swapped peanuts for cashews without going through the review process. Old Zhao directly rolled back to the previous version, and from discovering the problem to recovery took only five minutes.

From then on Old Zhao understood two kinds of work. The stove chef's job is to study how to make a dish delicious—how many grams of sugar, how many seconds of heat, the order of adding ingredients. The head chef's job is to manage the notebooks of all the stoves—who changed what, why they changed it, whether it was tested after the change, and whether a bad change can be reverted in one second. The stove chef relies on craft, the head chef on process.

Old Zhao later joked with peers: running one shop, the recipe can just live in your head. Running five shops together, the recipe has to go into a safe, the safe needs a password, and someone has to manage the password. The bigger your business, the less your skill is in cooking and the more it is in who is allowed to change the recipe, how to change it, and who is responsible after the change.

A restaurant consultant came to investigate and wrote one line: the bottleneck in dish quality is never the stove chef's skill, but whether the kitchen rules can keep up with the pace of expansion. Before the rules catch up, every new store is quietly modifying your signature dish, and by the time you notice, it has been changed beyond recognition.

Prompt engineering

The practice of designing and optimizing a single prompt to improve model output quality. It focuses on prompt structure, wording, example arrangement and chain-of-thought design, with the goal of achieving the best result in a single interaction.

Prompt management

The systems engineering practice of versioning, testing, deploying, rolling back and collaboratively managing prompts. It focuses on change traceability, quality gates and team collaboration, with the goal of systematically ensuring prompt quality and maintainability.

Story Mapping

  • Old Zhao studied the formula alone: prompt engineering—the polishing and tuning of a single prompt.
  • Five masters each change the recipe without saying a word: without prompt management, version chaos causes quality fluctuations.
  • Three rules—submit an application, review and test, retain versions: the core process of prompt management.
  • Rollback five minutes after peanuts were replaced with cashews: the practical value of version management and rapid rollback.
  • The division of labor between the stove cook and the head chef: prompt engineering focuses on single-item quality, prompt management focuses on system reliability.

In the project

Once prompt engineering reaches a passing grade, prompt management starts to deliver more value than continuing to optimize individual prompts. At minimum, do three things: put prompts into version control, route changes through review, and run regression tests before release. The larger the scale, the less you can rely on human memory—with ten prompts, chat history is fine; with a hundred prompts, you need tools. If you don't know which prompts need retesting after each model upgrade, your management isn't there yet.

京ICP备2026014272号