Why Good Companies Slowly Become Complicated

Most companies do not decide to become complicated. There is rarely a leadership meeting where someone deliberately proposes adding unnecessary approvals, creating overlapping processes or making simple decisions take twice as long. Complexity usually arrives much more quietly. A new process is introduced to prevent a mistake from happening again. Another meeting is added because communication has become difficult. A new tool solves one team’s immediate problem, while an additional approval is created because a decision once went wrong.

Individually, almost every addition can be justified. The problem becomes visible only after years of accumulation. Employees need permission from several people to make relatively small decisions. Customers are transferred between departments because ownership has become unclear. Teams spend increasing amounts of time coordinating work rather than doing it. Nobody can point to a single moment when the organisation became complicated because there was no single moment. Complexity accumulated one reasonable decision at a time.

As Pravin Chandan puts it, “Organisational complexity rarely arrives looking like complexity. It usually arrives disguised as a perfectly sensible solution to yesterday’s problem.”

The challenge for leaders is therefore not simply building processes that help a company grow. It is recognising that simplicity itself needs to be protected as the organisation becomes larger.

Growth Naturally Creates More Moving Parts

A small company can operate with remarkable informality. A few people sit close to one another, information travels quickly and many decisions can be made through a short conversation. Everyone understands roughly what everyone else is working on, and problems can often be resolved without formal processes.

Growth changes this.

More customers create more exceptions. More employees require clearer responsibilities. New markets introduce different regulations and expectations. Additional products create dependencies between teams. Finance, legal, security, human resources and other functions become increasingly important because the consequences of informal decision-making become larger.

Some complexity is therefore unavoidable. A company with thousands of employees cannot operate exactly like a company with ten.

The mistake is assuming that every layer of complexity created during growth must remain permanently. Organisations often become very good at adding processes when new problems appear and remarkably poor at removing them when circumstances change.

Pravin Chandan explains the imbalance clearly: “Companies have strong mechanisms for adding things and weak mechanisms for removing them. That is why complexity tends to compound.”

Without deliberate intervention, yesterday’s solutions become tomorrow’s organisational baggage.

Every Process Probably Made Sense Once

One of the most useful questions leaders can ask about an inefficient process is not, “Who created this?” but, “What problem was this originally designed to solve?”

The answer is often revealing.

Perhaps an approval was introduced after an expensive mistake. A weekly report may have been created because leadership once lacked visibility into an important project. A meeting may have begun during a crisis when daily coordination was genuinely necessary. A particular policy may have been designed around a customer or regulatory requirement that no longer exists.

The original reasoning can be completely valid while the current process has become unnecessary.

This distinction matters because employees often experience old processes as arbitrary bureaucracy. Understanding their history makes it easier to determine whether the underlying risk still exists and whether there is now a simpler way to address it.

Organisations should therefore periodically examine processes as assumptions rather than permanent infrastructure. The question should not simply be whether something once had a reason to exist. It should be whether that reason remains strong enough to justify the cost it creates today.

Exceptions Quietly Become Rules

Complexity also grows because organisations design processes around unusual events.

A customer finds an unexpected loophole, so a new verification step is introduced for every customer. One employee makes a poor decision, so an additional approval becomes mandatory for the entire team. A project exceeds its budget, so every future project receives another layer of reporting.

The organisation is trying to prevent a problem from recurring, which is understandable. But every preventive mechanism also creates a cost for all the situations in which the problem would never have occurred.

Over time, companies can end up designing the normal experience around exceptional failures.

Pravin Chandan puts it this way: “A business should be careful about making a thousand people perform an extra step forever because one person once made a mistake.”

This does not mean organisations should ignore risk. It means the response should be proportional to the likelihood and consequences of that risk. Sometimes better training, clearer accountability or improved technology can solve the underlying problem without permanently increasing friction for everyone else.

Meetings Multiply Because Ownership Becomes Unclear

Meetings are another place where organisational complexity becomes visible.

As companies grow, more people become involved in decisions. Cross-functional dependencies increase, and teams need mechanisms for sharing information. Meetings therefore become an understandable way to coordinate.

But meetings can also become substitutes for clear ownership.

When nobody knows who has authority to make a decision, more stakeholders are invited. When information is poorly documented, recurring meetings become necessary to keep everyone updated. When teams do not trust one another to make decisions independently, representatives from every department want to be present.

The calendar gradually fills with conversations that exist because the organisational structure has failed to make responsibility clear.

This is why simply declaring that a company should have fewer meetings rarely solves the problem. If the underlying ambiguity remains, the coordination requirement will reappear somewhere else.

Pravin Chandan observes, “A crowded calendar is sometimes a symptom of a deeper organisational problem. When ownership is unclear, meetings become the place where responsibility goes to hide.”

Reducing unnecessary meetings therefore often begins with making it obvious who owns decisions, who needs to provide input and who merely needs to be informed.

More Tools Can Create Less Productivity

Technology is supposed to simplify work, but organisations can accumulate software in exactly the same way they accumulate processes.

One team adopts a project management platform. Another uses a different system because it better suits its workflow. Communication happens across email, chat applications and comments inside documents. Customer information exists in one platform, financial information in another and reporting requires data from several more.

Each tool may solve a legitimate problem, yet the combined experience becomes increasingly fragmented.

Employees spend time moving information between systems, searching for the latest version of a document and remembering where a particular conversation happened. New employees need to learn not only how the business works but also an entire ecosystem of tools that evolved gradually over several years.

AI may make this problem even more interesting. Organisations are rapidly adopting new AI tools because individual teams can immediately see productivity benefits. Without thoughtful governance, however, companies may soon discover that they have added another large layer of fragmented technology rather than simplifying the existing one.

Technology creates leverage when it reduces work. It creates complexity when managing the technology becomes another category of work.

Approval Layers Grow Faster Than Decision Quality

Approvals are particularly attractive because they create the appearance of control.

If a decision carries risk, adding another reviewer feels safer. If something goes wrong, leaders may conclude that more senior oversight would have prevented it. Over time, decisions that were once made by one person require three or four signatures.

The cost is rarely calculated.

Every approval adds waiting time. Senior employees spend time reviewing decisions that could have been made elsewhere. Junior employees learn that exercising judgment is less important than obtaining permission. Responsibility becomes blurred because several people technically approved the outcome.

Eventually, the organisation can reach a strange situation in which nobody feels truly empowered even though many people are involved.

As Pravin Chandan puts it, “More people approving a decision does not automatically make it a better decision. Sometimes it simply makes responsibility harder to locate.”

Good governance should concentrate scrutiny where the consequences genuinely justify it. Routine, reversible and low-risk decisions should usually move much faster than decisions with serious financial, legal or reputational consequences.

Treating every decision as though it carries the same level of risk is one of the fastest ways to make an organisation slow.

Complexity Is Expensive Even When It Does Not Appear on a Budget

One reason complexity survives is that much of its cost is invisible.

A company can easily calculate the salary of an additional employee or the subscription cost of a new piece of software. It is much harder to calculate the cumulative cost of thousands of employees spending twenty extra minutes every week navigating an unnecessary process.

The same is true of slow decisions.

An approval that takes four days instead of four hours may not appear as an expense anywhere in the financial statements. Yet repeated across hundreds of decisions, the organisation loses enormous amounts of momentum.

Complexity also creates cognitive cost. Employees need to remember more rules, navigate more systems and understand more exceptions before completing basic work. The mental energy spent navigating the organisation is energy that cannot be spent solving customer problems or creating something new.

Pravin Chandan describes this as “the tax nobody invoices you for: the time and attention employees spend dealing with the company itself instead of doing the work the company exists to do.”

That tax becomes larger as organisations grow unless someone actively measures and challenges it.

Complexity Eventually Reaches the Customer

Internal complexity rarely remains entirely internal.

A company with unclear ownership may transfer customers between departments. A business with multiple approval layers may take days to respond to a request that should require minutes. Fragmented technology can force customers to provide the same information repeatedly because different teams cannot see what has already been shared.

From inside the organisation, every step may have an explanation. From the customer’s perspective, the experience simply feels difficult.

This is an important distinction because companies often design experiences around their organisational structure rather than around the customer’s objective. Customers are expected to understand which department handles which problem, which form belongs to which process and which internal policy prevents an employee from resolving an issue immediately.

The customer should not need to understand how complicated the company has become.

The strongest organisations absorb complexity internally while presenting simplicity externally. That requires significant effort because it is always easier to pass organisational complexity directly to the customer.

Simplicity Is Not the Same as Removing Structure

There is a danger in treating simplicity as a fashionable excuse to eliminate processes indiscriminately.

Some processes exist because the consequences of failure are serious. Financial controls, security requirements, quality standards and legal reviews may introduce friction while protecting the organisation from much larger risks. A business that removes every control in pursuit of speed may become simple right up until something goes catastrophically wrong.

The objective is therefore not minimal process. It is appropriate process.

Pravin Chandan explains the difference well: “Simplicity is not the absence of structure. It is the absence of structure that no longer earns the effort it demands.”

Every recurring process should be able to justify itself through the value, coordination or risk reduction it provides. When the cost begins exceeding that value, leaders should be willing to redesign or remove it.

This makes simplicity a management discipline rather than an aesthetic preference.

Leaders Need to Create Permission to Question the System

Employees often know exactly where unnecessary complexity exists.

They experience the redundant approvals, duplicate reporting and confusing systems every day. They know which meetings consistently produce nothing and which policies everyone quietly works around to get things done.

Yet they may assume these things are untouchable.

A process created by senior leadership can acquire an almost permanent status even when the leaders who created it have left the company. Employees learn to adapt around inefficiency rather than question whether it should continue to exist.

Leaders therefore need to create explicit permission for people to challenge how work gets done.

This does not mean every employee should ignore processes they dislike. It means organisations should create mechanisms for identifying friction and evaluating whether it remains necessary.

A useful cultural question is simple: “If we were designing this company today, would we create this process exactly this way?”

If the answer is consistently no, history may be the only reason the process survives.

Simplicity Requires Periodic Organisational Cleaning

Homes accumulate objects. Computers accumulate files. Organisations accumulate processes.

All three require occasional cleaning.

Companies frequently conduct strategic planning exercises in which they decide what to add during the coming year. New initiatives are launched, new technologies are adopted and new priorities are introduced. Far fewer organisations conduct equally serious exercises focused on what should disappear.

This creates an asymmetry. Every planning cycle makes the company slightly larger in terms of commitments, even when headcount remains unchanged.

Pravin Chandan argues, “Every annual planning exercise should contain two lists: what the organisation will start doing and what it will deliberately stop doing.”

The second list may ultimately be more important.

Leaders can examine recurring meetings, reports, approvals, tools, policies and initiatives and ask whether each one still deserves organisational attention. Removing even a small percentage of low-value activity can return significant time to the business.

More importantly, it signals that processes are not permanent simply because they have become familiar.

AI Should Remove Complexity, Not Automate It

The rise of AI creates a particularly important opportunity for organisations to reconsider how work is structured.

The easiest approach is to take an existing complicated process and use AI to complete parts of it faster. That can certainly improve productivity, but it may also preserve unnecessary work.

If employees spend hours producing a report nobody genuinely needs, generating the report with AI in five minutes is an improvement. Eliminating the report entirely may be a much larger one.

This distinction matters because technology often encourages organisations to automate before questioning.

Pravin Chandan puts it clearly: “Before asking how AI can perform a process faster, leaders should ask whether the process deserves to exist at all.”

AI can create extraordinary efficiencies, but its greatest organisational value may come from allowing companies to redesign work rather than merely accelerating inherited workflows.

The opportunity is not simply faster complexity. It is simpler work.

Good Companies Become Complicated Because They Care

There is an important irony behind organisational complexity: much of it begins with good intentions.

Companies add controls because they want to prevent mistakes. They add meetings because they want better communication. They introduce processes because they want consistency. They adopt tools because they want employees to work more effectively.

Complexity is therefore not necessarily evidence of poor management. It can be the accumulated consequence of years of people trying to solve real problems.

The leadership challenge is recognising that solutions have life cycles too.

A process that helped a company move from fifty employees to five hundred may become an obstacle at five thousand. A policy created for one market may not work in another. A meeting that was essential during a difficult quarter may become unnecessary once the crisis has passed.

As Pravin Chandan puts it, “Organisations become complicated when yesterday’s solutions are allowed to become tomorrow’s assumptions.”

Protecting simplicity therefore requires constant attention. Leaders need to ask whether the organisation is becoming easier or harder to navigate, whether employees can make decisions at the appropriate level and whether customers are experiencing internal complexity that should never have reached them.

Growth will always create some complexity. The objective is not to eliminate it completely.

It is to ensure that complexity earns its place.

Because the most effective organisations are not necessarily those with the fewest processes, meetings or systems. They are the ones in which every layer has a clear reason to exist, and where leaders remain willing to remove it when that reason disappears.

Building complexity happens naturally.

Protecting simplicity requires leadership.

www.pravinchandan.in

#pravinchandan #pravin #chandan #marketing #leadership #ai

You May Also Like