Older sailboats carry their history in plain sight. A new instrument appears beside the original one. A second pump is installed without removing the first. Wires disappear behind panels, cross through lockers, and reconnect somewhere no drawing records. Labels fade, switches lose their purpose, and equipment remains aboard because no one is completely certain whether it is still needed.

Most additions were sensible when they were made. A previous owner solved a problem, improved safety, added comfort, or adapted the boat for a particular voyage. The difficulty emerges years later, after many individually reasonable decisions have accumulated. The boat becomes heavier, harder to understand, and more difficult to maintain.

Organizations grow in much the same way. Every new application, policy, report, approval, committee, interface, and spreadsheet probably addressed a genuine need. Few were introduced with the intention of creating unnecessary complexity. Yet the combined result can become a vessel carrying far more than anyone deliberately chose.

Bandages Become Architecture

When an organizational process breaks, the fastest response is often a workaround. Someone creates a spreadsheet to reconcile two systems. Another person adds a manual review because the source information cannot be trusted. A manager introduces a meeting to coordinate work that the formal process no longer handles. A shared mailbox becomes the unofficial workflow, and an experienced employee becomes the human connection between several disconnected systems.

These responses are usually practical. Work must continue, customers must be served, permits must be issued, equipment must operate, and deadlines must be met. The people creating the workaround are often doing exactly what the organization needs at that moment.

The problem begins when the temporary solution becomes permanent. The original weakness remains, but the organization learns to work around it. Over time, another layer is added to manage the first workaround, followed by another control to manage the risks introduced by the second. What began as a bandage gradually becomes part of the architecture.

Organizations rarely remove a broken component when they can build a working path around it.

Addition Feels Safer Than Subtraction

Adding something creates visible evidence of action. A new system can be purchased. A committee can be formed. A report can be delivered. A policy can be approved. Each provides a tangible response to a recognized problem.

Removal is less comfortable. Eliminating a report requires confidence that no one still depends on it. Retiring an application means understanding every process, interface, and spreadsheet connected to it. Simplifying an approval path requires someone to accept responsibility for the risk the approval was intended to control. Subtraction demands a level of organizational understanding that addition often does not.

This is why complexity can continue even when almost everyone agrees that the environment has become too complicated. No single addition seems responsible for the problem, and no individual component feels safe to remove. The weight belongs to the whole collection.

The Cost Is More Than Technology

The obvious costs of accumulated complexity are licenses, infrastructure, support contracts, integrations, and maintenance. The less visible costs are often greater. Staff spend time reconciling systems, translating definitions, repeating data entry, preparing reports, attending coordination meetings, and explaining why one source differs from another.

Experienced employees become essential because they understand the informal routes through the organization. They know which spreadsheet is current, which report is misleading, who must be consulted before a change is made, and which written procedure no longer reflects how the work is actually done. Their knowledge keeps the vessel moving, but it also hides how dependent the organization has become on individual memory.

Eventually, complexity begins to shape the work itself. A decision that should take minutes requires several meetings. A simple question crosses multiple systems. A new employee needs months to understand procedures that no one intentionally designed. The organization may appear stable, but much of that stability depends on people continuously compensating for the weight it carries.

New Technology Can Add Another Layer

Artificial intelligence offers a powerful way to search, summarize, and interpret fragmented information. It may help people find their way through an environment that has become difficult to navigate. That is valuable, but it does not necessarily make the underlying environment simpler.

An intelligent assistant can locate five conflicting procedures and explain their differences. It cannot decide which four should be retired unless the organization is willing to make that decision. It can help reconcile data from overlapping systems, but it does not eliminate the need to determine whether all of those systems should continue to exist. It can make complexity easier to navigate while quietly allowing the complexity itself to survive.

This is one of the risks of every successful new technology. It can become another highly capable layer placed over the accumulated layers that came before. The immediate experience improves, but the boat continues to gain weight.

Refitting Requires Judgment

Simplifying an older sailboat is not a matter of removing everything unfamiliar. Some redundancy is deliberate. Some old equipment remains reliable. Some awkward-looking arrangement reflects a lesson learned in difficult conditions. A thoughtful refit begins by understanding what each component does, what depends on it, and whether it still supports the way the boat is now used.

Organizational simplification requires the same care. The goal is not minimalism for its own sake. It is to distinguish useful capability from accumulated burden. That means tracing dependencies, understanding the original purpose of controls, asking who still uses each output, and examining whether a workaround has outlived the problem it once solved.

It also means considering the crew. Removing a tool without understanding how people rely on it can make their work harder. Preserving every tool because someone may rely on it guarantees that the environment will never become clearer. Good subtraction is neither reckless nor timid. It is informed.

A Regular Lightening of Ship

Complexity is not a one-time problem that can be solved through a major cleanup and forgotten. Every functioning organization will continue to adapt, improvise, and add new capabilities. Some of those additions will eventually become obsolete, even when they remain technically operational.

A healthy organization periodically asks what can be retired, combined, simplified, or returned to its original purpose. Which reports are no longer read? Which approvals no longer control a meaningful risk? Which systems duplicate one another? Which meetings exist to compensate for an unclear process? Which skilled people are performing work that should be automated, reassigned, or stopped?

Every boat gets heavier. The question is whether anyone regularly notices, understands the load, and has the confidence to remove what no longer belongs aboard.

Next Bearing

Accumulated complexity becomes most visible when someone asks a simple question and discovers that the answer is distributed across systems, documents, definitions, and individual memory. The next Bearing considers why organizations with abundant information can still find straightforward questions surprisingly difficult to answer.