The 1715 Treasure Fleet: A 300-Year-Old Lesson in Single Point of Failure in Business
- Maria Mor, CFE, MBA, PMP
- 4 hours ago
- 6 min read
On July 31, 1715, eleven Spanish ships loaded with years of accumulated gold and silver sailed straight into a hurricane off the Florida coast. Only one ship in the convoy survived. It was the one that had broken away from the group and taken its own route.
That wreck is the reason this stretch of Florida coastline earned the name Treasure Coast, two and a half centuries after the fact. Buried inside that story is a pattern I see constantly in growing companies. The moment everything of value gets loaded onto one system, one vendor, or one person, the business is one bad storm away from losing it.
Table of Contents
What Actually Happened in 1715
Two Spanish fleets combined into one convoy that summer: the Nueva España fleet and the Tierra Firme fleet, sailing together out of Havana toward Spain. Combining them made sense on paper. It concentrated years of New World silver and gold into a single, heavily guarded voyage instead of several smaller, riskier ones.
The Spanish crown wanted the voyage made regardless of the season. Hurricane risk was well known in late July, but the treasure had already been waiting, and the pressure to move it outweighed the pressure to wait. Eleven ships sailed together on the same route and the same timeline. A twelfth, a French frigate called Le Grifon, sailed separately because its captain did not know the Florida coastline well enough to trust the same path as the others.
Seven days later, the hurricane hit. Eleven ships went down in a matter of hours. Le Grifon made it home.
Single Point of Failure in Business: What the Storm Actually Exposed
The storm did not create the risk. The risk was already there the moment every asset the crown owned was loaded onto one convoy, following one route, on one timeline. The hurricane just made the risk visible.
This is the part that applies directly to a growing company today. Single point of failure in business rarely looks dangerous while things are calm. It looks efficient. One platform running everything. One employee who understands the full billing cycle. One client responsible for most of the revenue. One person approving every payment. Consolidation feels like progress right up until the one thing holding it together becomes unavailable.
According to McKinsey Global Institute research, disruptions lasting a month or longer now occur every 3.7 years on average, and cost the average company nearly 45 percent of a year's profits over the course of a decade. McKinsey's operations practice points to a specific cause: globally integrated asset networks and supply chains that are too tightly concentrated are the exact conditions that create single points of failure. The point is not to avoid growth or scale. It is to know where the concentration sits before something forces you to find out.
Why the Pressure to Sail Anyway Feels So Familiar
The most human part of the 1715 story is not the storm. It is the decision to sail into hurricane season because the treasure had already waited long enough.
Growing companies make a version of that decision constantly, usually without recognizing it as a decision at all. A single vendor becomes the default because switching feels disruptive. One person becomes the process owner because training a second person takes time nobody has. A concentrated client relationship becomes the backbone of the revenue because it is easier than building three smaller ones. None of these choices are wrong in the moment. They are the same trade the Spanish crown made: the near-term convenience of moving forward outweighs a risk that has not happened yet.
The gap almost never shows up as a competence problem. It shows up as a proximity problem. When you built the system and you live inside it every day, the concentration becomes invisible. You cannot see clearly what you built and rely on every day. That is not a failure of judgment. It is a structural limitation that applies to every business owner or leader running a company close enough to see the details and too close to see the shape.
There is a simple test underneath all of this: if one person, one vendor, or one client disappeared tomorrow, would the business still run next week? If the honest answer is no, that is a structural risk, not a staffing question and not a technology question.
Where This Risk Hides Inside a Growing Company
This kind of structural risk shows up in more places than most owners and leaders expect, and almost never with a warning label. A few of the most common places it hides:
One vendor or platform running a core function with no backup plan if access disappears
One employee holding the institutional knowledge for a critical process, with no way to transfer it and no backup
One client representing a disproportionate share of revenue
One person approving every payment or major decision, creating a bottleneck disguised as oversight
One bank account or cash position acting as the only signal of financial health
One system of record that nobody has stress-tested against a real disruption
None of these are inherently reckless decisions. Most of them were the fastest, most reasonable choice at the time they were made. The problem is not that the choice was made. The problem is that nobody went back to check whether it was still the right structure once the business had grown past the point where it was safe. The approval bottleneck is worth its own look, since when one person controls every financial checkpoint, the back office loses the safety net that would otherwise catch errors and fraud before they compound.
Why Outside Perspective Helps
Nobody on the 1715 voyage thought they were making a reckless decision. Every choice, from combining the fleets to sailing on schedule, looked reasonable from inside the moment it was made. That is exactly how this kind of structural risk develops. It is never one bad decision. It is a series of individually sensible ones that nobody re-evaluated as the business changed shape.
This pattern shows up across industries, not just in businesses with obvious risk exposure. Seeing it requires someone outside the day-to-day operation, because the owner or leader who built the structure is too close to the details to see where the whole thing rests on one point. A Process Health Check exists for exactly this reason: to look at where operations, revenue, and decisions currently rest, from outside the daily pressure of running the business.
Free Resource: 5 Steps to Streamline Your Business
If reading this made you mentally scan your own operation for the one vendor, one person, or one client holding more weight than they should, that instinct is worth following. The 5 Steps to Streamline Your Business guide walks through how to identify where structure is missing before adding more tools or systems on top of it.
Frequently Asked Questions
What is single point of failure in business and why does it matter?
This describes any part of an operation where the failure or unavailability of one vendor, one employee, one client, or one system would disrupt or halt the business. It matters because these points of concentration are usually invisible during normal operations and only become obvious once something forces the disruption to the surface.
How is this different from normal business risk?
Most business risk is diversified and expected, such as market shifts or seasonal demand changes. This kind of risk is structural instead. It exists because of how the operation was built, not because of external market conditions, which means it can often be identified and reduced before it causes a disruption.
What is the most common single point of failure in growing companies?
The most common pattern is institutional knowledge trapped in one employee, with no transfer plan and no backup, followed closely by revenue concentrated in one or two clients and core functions run through a single vendor or platform with no contingency plan.
Can a business fix this without stopping operations to do it?
Yes. Identifying where concentration exists does not require pausing the business. It requires a structured review of where operations, revenue, and decisions currently rest, followed by a deliberate plan to build redundancy in the highest-risk areas first.
Why do owners and leaders often miss this in their own business?
Business owners and leaders are inside the operation every day, which makes the concentration difficult to see. The proximity that comes from building and running a business daily is the same proximity that hides where the structure has become too dependent on one point. Outside perspective typically identifies it faster than an internal review can.
Ready to Find Where Your Structure Rests on One Point?
The 1715 fleet never asked where everything of value had quietly ended up in one place, until the storm asked for them. If your business is growing and you have not asked that question in a while, now is a reasonable time to ask it with someone outside the day-to-day operation.
The Back Office Brief
Get a weekly insight connecting back office operations to profit. Delivered every week, free.