Fable
A ship cannot have only a captain
On the long-voyage ship, the captain originally arranged everything alone. He could do a little of everything: read the stars, ration food, repair sails, keep accounts, negotiate prices. Short voyages could still hold up, and the crew was used to waiting for his orders.
Later the routes grew longer, the weather worsened, and there were more cargo owners. The captain worked from early morning to late at night every day, yet still missed tides, miscalculated provisions, or forgot to rotate the sailors' shifts.
The first mate suggested recruiting more people. Soon the ship had many capable sailors, but no fixed duties. Anyone could offer opinions, anyone could adjust the sails, and when something went wrong, no one could say who was responsible.
The captain first wrote a long list of commands. But conditions at sea changed too fast; before the list could be read out, the wind had already shifted. More people did not make the ship steadier, only the deck noisier.
The old navigator suggested organizing the crew into a team with roles. The navigator managed the route, the boatswain managed the deck, the accountant managed supplies, and the messenger managed port communications. Each person had goals, tools, and handoff methods.
They also defined the order of collaboration. When the navigator spotted a storm, he notified the boatswain to furl the sails; when the accountant found insufficient food, he had the captain adjust the port of call. Information flowed along responsibilities, rather than surging toward one person.
The first time they hit a storm, the crew did not wait for the captain to issue orders one by one. Each role acted within its boundaries, and key decisions were handed back to the captain. The ship was not noisier; it was steadier.
The captain finally stepped back from all the details and focused on judging the destination and risks. What truly improved the ship's sailing capability was not a few more clever helpers, but organizing the helpers into a crew with division of labor, processes, and shared goals. Later, when new roles were added to the ship, the first step was to clarify whose messages it received, to whom it handed results, and whether it could directly adjust the sails. The captain found that a crew's strength comes from clear boundaries, not from everyone rushing to show how clever they are. The farther the sea, the more valuable this order becomes. After the storm, during the debrief the crew no longer asked who was most capable, but which handoff was too slow, which boundary was vague, and which role lacked tools. The ship thus became steadier each time. Later, in the postmortem, everyone wrote this lesson into the daily rules: first see where on the ground the result actually changed, then decide what to keep, repair, or limit. If you look only at surface excitement, you will fall at the same place next time. This is more reliable than adding people temporarily.