Fable
The shipyard and the caravan drew the blueprints all the way to the dock
The shipyard built a new fast ship, claiming it could sail all routes. When the merchant caravan came to try it, the ship was indeed fast, but it could not hold the clay jars they often transported, nor was it suitable for docking in shallow waters.
The shipyard initially wanted to revise the brochure, emphasizing speed, materials, and beautiful cabins. The caravan nodded after listening, but did not place an order, because what they were buying was not the ship's advantages but whether the cargo could arrive on time.
The craftsman then proposed making several custom parts. Today add guardrails, tomorrow modify the warehouse boards, the day after change the cables. Changes multiplied, yet no one redefined what this route was actually meant to solve.
On a trial voyage, the fast ship ran aground in shallow water. The shipyard blamed the caravan for stowing cargo incorrectly; the caravan blamed the shipyard for not understanding the wharf. Neither side was wrong, but the plan had not been designed together.
Later, the shipyard sent craftsmen, accountants, and captains to stay at the caravan dock for half a month. The caravan also opened its cargo list, loading and unloading process, customer commitments, and loss records.
They began revising the blueprints from how this route made money, where losses were greatest, and who was responsible for acceptance. The new ship did not satisfy everyone, but it was very suitable for this type of caravan. The value could also be stated clearly: less damage, less port delay, more stable delivery.
The shipyard also set boundaries. Every request from the caravan had to map to route revenue, loss or acceptance; a fast ship could not be turned into a jack-of-all-trades just because some captain liked it.
The caravan no longer treated the shipyard as a free carpenter. It had to hand over real constraints and bear trade-offs. What the two sides designed together was not a ship that satisfied every imagination, but a solution that could make money on a specific route. Later, when newcomers were onboarding, the old master no longer started with abstract categories, but had them review that failure: where they had originally relied on intuition, why the first patch was not enough, and how the new arrangement kept risk in a place that could be checked. Only when they could explain these details clearly, and also point out when to keep using it and when to upgrade it, were they considered to truly understand this approach. Later they also had newcomers practice with this approach: first have newcomers do it the old way and see how errors appeared; then redo it under the new rules and see which step was blocked in advance and which step left evidence. If newcomers could only recite names, they would still misuse it in similar scenarios; only those who could state the applicable boundaries, costs, and remedies after failure were allowed to take work independently.