When Complexity Becomes Invisible 

How experienced teams can unintentionally hide operational risk 

Complexity doesn't always look complicated. 

Sometimes, it looks like an experienced employee who knows exactly which spreadsheet to open, which number needs

to be adjusted before a report goes to leadership, or which membership exception requires a manual correction.

The team gets the work done, so the process appears healthy. But a capable team can become so good at navigating

workarounds that the organization stops seeing the complexity underneath. 

A team being able to manage a complicated process does not mean the process is healthy. 

Experience Can Hide Process Problems 

Experienced employees are valuable because they know the history behind the systems. They remember exceptions,

recognize unusual situations, and know how to keep work moving. Over time, however, that knowledge can begin

compensating for weaknesses in the process itself. A manual reconciliation becomes routine. A separate spreadsheet

becomes essential. A system limitation becomes something everyone simply works around. 

The complexity hasn't disappeared. People have simply learned how to manage it. 

The New Employee Test 

One of the simplest ways to identify hidden complexity is to look at a routine process through the eyes of someone

who does not know it yet. Ask a newer employee to document the process from beginning to end without coaching

them through it. Then watch for four things: 

• Where they need an explanation to know what happens next. 
• Where they leave one system and open another. 
• Where they encounter an undocumented exception or manual correction. 
• Where someone says, “That is just how we usually handle it.” 

Follow the Complexity Across the Association 

In an association, invisible complexity rarely stays in one department. A membership exception may begin as a

manual correction in the AMS. That change can affect billing, require another adjustment during reconciliation,

and ultimately influence the report leadership sees. The final report may still be accurate, but only because several

people know which corrections have to happen behind the scenes. 

The report may be right. The process still may not be healthy. 

Institutional Knowledge vs. Institutional Dependency 

Institutional knowledge is an asset when people understand why processes exist and that knowledge can be transferred.

Institutional dependency is different. If a critical process works only because one person remembers the exceptions,

undocumented rules, or recurring adjustments, the organization carries more risk than the process may appear to have. 

When “It Works” Is Not Enough 

A process can work and still depend too heavily on one person. It can produce the right answer while requiring

unnecessary manual intervention. It can get the job done while becoming increasingly difficult to explain, transfer,

or scale. 

The better question is: Does this process work as clearly, accurately, and sustainably as it should? 

Make the Complexity Visible 

The goal is not to criticize the people who created workarounds. In many cases, they were solving real problems

with the tools available to them. The goal is to understand what those workarounds are compensating for, decide

which ones still serve a purpose, and simplify what no longer needs to be complicated. 

Periodically look at familiar processes through unfamiliar eyes. Follow the exceptions.

Question recurring manual corrections. Document what people know, but the system does not. 

Because making complexity visible is the first step toward deciding what should remain and what is ready to change.