Maybe your organization is the problem

When responsibilities overlap, decisions stall and routine processes consume the workday, leaders should examine the system employees are being asked to navigate.

Maybe your organization is the problem

Employees are working harder while decisions slow, responsibilities overlap and routine processes consume more time. Before treating the symptoms as performance problems, leaders should examine whether the organization itself is making the work unnecessarily difficult.

Spot complexity hiding inside improvement

Organizational complexity rarely begins with one obviously bad decision. It grows as leaders add processes intended to improve accountability, communication or quality.

A new approval step reduces risk. Another report gives leadership more information. A committee brings additional perspectives into the conversation, while a recurring meeting keeps more people informed. Each addition appears reasonable on its own.

Together, they can create a system that takes longer to navigate than the work it was designed to support.

Throughout my career, I have seen this pattern in health care systems, nonprofits, schools, businesses and community organizations. Talented people work harder while decisions slow, responsibilities overlap and employees spend more time managing processes than advancing the mission.

Leaders may interpret the resulting delays as performance problems. They ask employees to communicate more, manage their time better or demonstrate greater accountability. Those expectations cannot correct a system built around unnecessary meetings, duplicated reports and approval processes that no longer reflect the actual risk.

Sometimes the employee is not the problem. The organization has accumulated more complexity than anyone intended.

Follow the work from beginning to end

The cost of complexity becomes easier to see when leaders examine how work actually moves through the organization.

A 30-minute meeting may appear insignificant until it involves 12 employees every week. A short report becomes more expensive when several departments gather the same information in different formats. An additional approval may seem prudent until every project begins waiting for someone whose authority is not needed.

Employees must stop what they are doing, gather information, wait for responses and recover their concentration before returning to the original work. The burden appears through delayed decisions, repeated conversations and fragmented attention.

In my work, I often ask employees to walk me through a real decision, request or project. Where did it begin? Who needed to respond? Where did it slow down? Which steps improved the result, and which existed because they had always been there?

Those conversations frequently reveal workarounds leaders never intended. Employees maintain private tracking systems because the official one does not provide what they need. Departments hold preliminary meetings to prepare for the meeting where a decision is supposed to occur. Managers seek informal approval before beginning the formal approval process.

These workarounds show where the system no longer matches the work.

Some requirements remain essential because they protect safety, quality, legal compliance or financial accountability. Leaders need to distinguish those safeguards from accumulated habits that consume time without improving the outcome.

Remove friction before adding more

When performance slows, organizations frequently respond by adding another process, meeting or layer of oversight. The new structure is visible, which can make it feel like progress. It may instead add more weight to the problem leaders are trying to solve.

Before introducing another requirement, leaders should examine what already exists. Can an approval be matched more closely to the level of risk? Can overlapping reports be combined? Does a recurring meeting still produce information or decisions people use?

Every process should have a clear purpose and someone responsible for determining whether it continues to serve that purpose. A meeting should help people coordinate. A report should provide information someone uses. An approval should protect the organization or improve the decision.

“We have always done it” explains a process’s history. It does not establish its present value.

Subtraction can be tested as thoughtfully as addition. Leaders might simplify one approval path, combine two reports or suspend a recurring meeting for a defined period. They can then determine whether work moves more efficiently and whether anything important has been lost.

Growth will naturally introduce more employees, services, stakeholders and decisions. Some additional structure will be necessary. Strong leadership includes reviewing that structure as circumstances change and ending requirements that no longer contribute to the mission.

Before asking employees to work harder, follow one real assignment from request to completion: How much of its time is spent producing the result, and how much is spent navigating the organization?