One of the assumptions we rarely question is that businesses become easier to understand as they grow.
Larger organizations produce more information than smaller ones. They have dashboards, financial reports, customer analytics, departmental KPIs, operating reviews, and increasingly sophisticated reporting systems. From the outside, it seems reasonable to assume that more information should lead to greater clarity.
In practice, I have gradually come to believe the opposite.
As companies grow, they often become more difficult to understand. Not because information becomes scarce, but because it becomes increasingly filtered. Every additional management layer introduces another level of interpretation. By the time information reaches decision-makers, much of it has already been summarized, categorized, and separated from the circumstances that produced it.
Leadership receives a representation of the business rather than a direct view of how it operates.
That distinction matters more than it may initially appear.
When direct observation stops scaling
In a small company, a founder can observe much of the business directly. Customer complaints reach them. They know which employees are overloaded, which processes depend on informal arrangements, and where problems tend to emerge.
As the company grows, that visibility gradually disappears.
Departments become more specialized. Responsibilities are distributed. Managers begin reporting through other managers. Customer conversations, operational exceptions, financial performance, and project delivery are increasingly discussed in separate settings.
None of this is inherently problematic. Specialization and reporting structures are necessary for growth.
The difficulty begins when the information flowing upward no longer preserves enough context to explain what is happening across the organization.
Over time, a company can develop two different versions of itself.
The first is the operational company, where employees make daily decisions, solve customer problems, coordinate work, and deal with exceptions.
The second is the reported company, represented by dashboards, management presentations, financial statements, and departmental performance reviews.
Both are real in their own way. But they do not necessarily tell the same story.
How a company can look healthy while becoming harder to operate
Consider a growing B2B services company.
Sales reports increasing revenue and a healthy pipeline. The operations team reports that most projects are being delivered on time. Finance sees revenue growth broadly consistent with the company's targets.
Individually, these reports may all be accurate.
But suppose new customers are arriving with more complex requirements than the company previously handled. Sales continues closing deals, while operations increasingly relies on manual coordination and informal workarounds to deliver what was promised.
Projects still finish on time, but employees spend more time resolving exceptions. Experienced team members become involved in decisions that should have been routine. Customer requests pass through additional conversations, and a growing amount of work takes place outside the systems intended to manage it.
Finance may not immediately see the problem. Some of these costs are absorbed through existing salaries, managerial attention, and work that is never recorded as a separate expense.
The company continues to grow. Its reports remain largely positive. Yet the actual cost and difficulty of serving each customer may be increasing.
This is a hypothetical example, but the mechanism is common enough to be worth examining.
The problem is not necessarily that any department is reporting incorrectly. It is that each function describes a different part of the business, and nobody has fully reconciled those descriptions into an operating picture.
Sales sees commercial performance. Operations sees delivery. Finance sees financial results.
What may be missing is an understanding of how these outcomes depend on one another and whether the underlying system is becoming stronger or weaker.
What traditional reporting can miss
A dashboard is useful because it reduces complexity. Without that simplification, managing a growing organization would become impossible.
But simplification always involves choices about what to measure and what to leave out.
On-time delivery, for example, is an important indicator. It tells us whether commitments are being met. It does not necessarily tell us how much additional effort was required to meet them, how often managers had to intervene, or whether the same performance can be maintained as volume increases.
Employee productivity can improve on paper while coordination becomes more difficult. Revenue can increase while the organization accumulates operational obligations that have not yet appeared in its margins.
Even customer satisfaction may remain strong for a period because employees are compensating for weaknesses in the operating model.
I think this is one reason operational problems can remain invisible for surprisingly long periods. People inside the business often recognize the friction, but they encounter it as a series of local difficulties rather than as one company-wide problem.
A manager resolves an exception. Someone creates a spreadsheet because the existing system cannot handle a particular situation. A team introduces an additional meeting to coordinate work that previously moved without intervention.
Each adjustment may be reasonable. Some are necessary. But collectively they can change how the company operates without anyone explicitly deciding to make that change.
Eventually, the informal arrangements become part of the business.
The management reports may still describe the intended operating model, while employees are working within a different one.
Understanding the work behind the numbers
When this happens, I don't think the first response should necessarily be to introduce more KPIs or another reporting tool.
The more useful question is whether the existing information explains how work actually gets done.
For instance, if delivery performance remains strong while operational costs rise, it is worth examining what has changed beneath the reported results. Are projects becoming more complex? Are teams handling more exceptions? Has responsibility for certain decisions become unclear? Does routine work now require intervention from people who were not previously involved?
These questions require looking across departmental boundaries.
One practical approach is to follow a small number of actual transactions, customer requests, or projects from beginning to end. Not just through their recorded milestones, but through the decisions, handoffs, delays, and exceptions that shaped the outcome.
A customer order might appear straightforward in the CRM. But following it through fulfillment, delivery, invoicing, and customer support can reveal a very different process from the one management believes exists.
The purpose is not to inspect every employee's work or create another layer of oversight. It is to understand whether the company's formal description of its operations still corresponds to reality.
Sometimes the result confirms that the process is working well. Other times it reveals that a reported success depends on repeated manual intervention, unclear ownership, or arrangements that will be difficult to maintain at greater scale.
That distinction changes the decisions management needs to make.
The role of operational leadership
I see this as one of the more difficult responsibilities of a COO or anyone accountable for how a company runs.
Operational leadership is not only about making processes more efficient or ensuring that departments meet their targets. It also involves maintaining an accurate understanding of the organization as it changes.
That requires combining information that individual functions naturally view from different perspectives.
It also requires distinguishing between problems that can be solved locally and problems that indicate something more fundamental about the operating model.
A missed deadline may be a scheduling issue. Repeated missed deadlines across otherwise well-performing teams may indicate an underlying problem with capacity planning, decision ownership, or the way commitments are made.
The distinction is not always visible in a monthly operating review.
AI and automation may eventually make some of this work easier. Systems can increasingly connect information across tools, surface unusual patterns, and help identify inconsistencies that are difficult to recognize through manual reporting.
But technology does not eliminate the need to decide what those patterns mean.
An automated system may reveal that certain customer requests consistently require more intervention than others. Someone still needs to determine whether the cause lies in pricing, sales commitments, process design, product limitations, or something else.
Better information can support judgment. It cannot replace responsibility for understanding the business.
Keeping the reported company close to the real one
I have become less interested in how much information a company collects and more interested in whether its leadership can explain the relationships behind its results.
Can a company explain why delivery performance is improving? Does it understand what is happening to the effort required to produce that improvement? When customer demand changes, can management see how the change affects capacity, costs, and service quality?
These are not questions that one dashboard can answer on its own.
They require a view of the business that connects outcomes with the processes and decisions producing them.
The companies that handle growth well are not necessarily those with the most sophisticated reporting systems. They are the ones that continue finding ways to test their understanding against what is actually happening inside the organization.
Growth increases complexity, and complexity creates distance between management and day-to-day work. Some of that distance is unavoidable. The important question is whether the organization has developed ways to recognize when its understanding is becoming incomplete.
A company can be growing, meeting targets, and producing accurate reports while gradually losing visibility into how it achieves those results.
That is why I believe one of the most important responsibilities of operational leadership is not simply to keep the business running, but to ensure that the people responsible for it can still understand how it works.