Fable
Both hands can write menus, but there is only one head chef in the kitchen
The kitchen management of an old established restaurant went through two stages. The first stage was writing all the master chef's recipes into standard operating cards: the grams of each ingredient, the cooking time, the plating method—all on paper. A new chef could reproduce the dishes from the cards, no longer relying on the master's word of mouth. This is turning intangible experience into tangible documents.
Then came the second-stage problem: operation cards were scattered in each chef's pocket. Someone changed the salt amount without telling others, someone had an old version of the card, someone made an improvement but other stations didn't know. The same sweet-and-sour fish tasted three different ways from three stoves. The operation cards were written, but the versions were a mess.
The head chef did one thing: he stored all the operation cards in a shared tin cabinet, and only he had the key. Anyone who wanted to change a recipe had to go through him—hand in the old card, explain the reason, and get a new card. The cards in the tin cabinet were the only trusted version; the kitchen cooked according to the cards in the cabinet and checked them once before starting work each day.
Half a year later, the head chef discovered that the central cabinet alone was not enough. Some people cooked according to the new cards, but the actual heat and timing of the finished dish did not exactly match the card—what the kitchen executed and what was written in the cabinet differed by an inspection step. He added a step: every day at noon, spot-check two dishes, compare the finished product against the operation card, and if a deviation is found, immediately trace whether the card was wrong or the person did not follow it.
This tin cabinet plus daily reconciliation is the second pitfall the kitchen hit after "writing it into files." Operation cards alone are infrastructure as code — turning configuration into readable, reproducible files. The tin cabinet plus a single key, version control and automated reconciliation is GitOps — using one central repository as the single source of truth, continuously verifying whether the actual state has drifted.
The restaurant's kitchen equipment procurement later followed the same path. Previously the procurement list was kept in the buyer's notebook, and switching to a shared document did make it clearer. But only when they set the shared document so that "only the kitchen supervisor can modify it, while the buyer can only read and place orders," and automatically reconciled it once a day, did the procurement deviation rate truly drop to zero.
At the kitchen debriefing, the head chef drew a line on the blackboard: on the left he wrote "written into a document so it can be passed on," on the right he wrote "lock the document into a single repository and verify it daily." He said each stage is worth a sum of money, but only the second stage is worth big money.