"You're lost, unless you have a rutter."
The Dutch East India company built an empire on knowledge. So can you.
In Shogun, the Dutch ship pilots are the best in the world. Not just for being better sailors. Because they have better rutters. As James Clavell explains in the book:
A rutter was a small black book containing the detailed observation of a pilot who had been there before. It recorded magnetic compass courses between ports and capes, headlands and channels. It noted the sounding and depths and color of the water and the nature of the seabed. It set down the how we got there and how we got back.
But he adds something important to that description.
*But a rutter was only as good as the pilot who wrote it, the scribe who hand-copied it, the very rare printer who printed it, or the scholar who translated it. A rutter could therefore contain errors. Even deliberate ones. A pilot never knew for certain until he had been there himself. At least once.
The Dutch understood this. They built better rutters. And they kept them secret. A library of the best routes to India, China, Japan, and the East Indies.
Maps they denied existed.
In 1611, Hendrik Brouwer charted a route between the Cape of Good Hope and Java that cut the voyage from a year to six months.
Their rivals sailed the same oceans. The Dutch got there in half the time, carried twice the cargo. And nobody outside the Dutch East India company knew exactly how.
That’s more than navigation. That’s a competitive moat.
People are starting to realize that AI compounds what you feed it. Design systems, patterns, decisions - it produces at scale and speed that would have been inconceivable three years ago.
AI doesn’t know what context is worth compounding and what isn’t. Whatever you give it, it will amplify. Documented decisions and undocumented drift. Authoritative tokens, and a Figma file out of date with production. Enforced constraints, and those in one engineer’s institutional memory. All of it goes in.
Good context will compound into coherence at scale. Bad context into confident, fast-moving inconsistency. The AI isn’t lost, it’s just following charts that are wrong.
A rutter was only as good as the pilot who wrote it...
Most organizations haven’t verified theirs even once.
A rutter wasn’t a single source. Historical rutters were compiled from multiple voyages, multiple pilots. Sometimes conflicting observations.
The value wasn’t just having the information. It was knowing which accounts to trust when they disagreed. The 1589 observation or the 1612 one. The pilot who navigated this strait in summer, versus the one in winter. The hint that was a lie.
Your product context is the same problem. Design system, yes. But brand guidelines, Figma libraries, components, content strategy, regulatory environment. Institutional memory about why one pattern exists and what happens if you overlook it. And the sources don’t always agree, so how does the AI navigate?
Organizations that integrate, orchestrate, and prioritize those sources - they’re building rutters. Every decision made is another voyage in the record. Every conflict resolution is a note to avoid a reef. Generation cycles that feed back into the system to make the next one more reliable.
It’s compounding advantage. Your competitors all have access to the same models. For all their genius, they’re commodities. But accumulated product knowledge, integrated, adjudicated, tells AI what right looks like for you. It’s the rutter your organization built, deliberately or not, for as long as you’ve been making decisions and writing them down. Its compounding nature means the earlier you build it, the harder it is to catch up.
The Dutch didn’t win the spice trade because their ships were faster. They won by taking the navigational system they built into proprietary, compounding knowledge. Then they protected that fiercely.
Same ocean. Same models.
You know what the difference was.
Further reading:
Clavell, J. Shōgun. Hodder & Stoughton, 1975.
Bruijn, J. R. Between Batavia and the Cape: Shipping Patterns of the Dutch East India Company. Journal of South East Asian Studies, Sept 1980.
Article photo by Gene Brutty on Unsplash.