Article 08: Why Leadership Teams Misread Operational Performance
The dashboard showed green across every key indicator. Revenue was tracking to plan. Customer satisfaction scores were within the acceptable range. Employe...
Get started
The project had a clear objective. The team assigned to it was capable. The timeline was reasonable. Resources had been allocated. Leadership had communicated its importance.
Six months later, the project was behind schedule, over budget, and producing outputs that did not fully meet the original requirements. When the post-mortem was conducted, the causes were familiar. Dependencies on other teams that had not been honored on schedule. Decisions that had been escalated and not returned in time to keep the work moving. Specifications that had been revised multiple times because the original requirements had not been sufficiently clarified. Communication between contributors that had been inconsistent and incomplete.
No single failure had derailed the project. It had been slowed by the cumulative effect of dozens of small frictions, each individually manageable, collectively sufficient to significantly degrade the outcome.
Organizational friction is the resistance that work encounters as it moves through an organization. It is created by unclear ownership, competing priorities, approval requirements, communication gaps, and the coordination overhead of managing dependencies between teams and functions.
Friction is not the same as difficulty. Some work is genuinely difficult and requires time and effort proportional to its complexity. Friction is the additional resistance the organization adds to work through its structure, processes, and governance that is not intrinsic to the work itself. It is the organizational tax on execution.
This distinction matters because it changes the nature of the improvement opportunity. Difficult work requires investment in capability and capacity. Friction reduction requires investment in organizational design. The two interventions are different in character, different in cost, and different in the results they produce.
Friction lives in the white spaces of organizational charts. It accumulates where responsibilities are unclear, where teams must coordinate without clear protocols, where decisions require input from multiple stakeholders with different priorities, and where information must cross organizational boundaries to reach the people who need it. None of these friction points are typically mapped or measured. They are experienced by the people working within them and absorbed as the cost of doing business inside a complex organization.
Not all friction is equally costly. Four types consistently produce the most significant performance drag across organizational settings.
Ownership ambiguity is one of the most pervasive. When it is unclear who is responsible for a decision or an output, work either stalls while responsibility is negotiated or gets duplicated as multiple parties each take partial ownership. Either outcome degrades execution speed and output quality. Ownership ambiguity is particularly common at the boundaries between functions, where work does not fit cleanly within any single team’s mandate and where the question of who is responsible is genuinely contested.
Approval chain length is a second. Many organizations have approval processes that require sign-off from multiple levels or multiple functions before work can proceed. Each approval step adds time to the execution cycle. When approvers are overloaded, unavailable, or have different priorities than the teams seeking approval, the time cost of each step multiplies. Long approval chains are often a legacy of risk events that occurred years earlier and that the current organization may no longer face to the same degree.
Cross-functional dependency management is a third. Work that requires contributions from multiple teams moves at the speed of the slowest contributor. When teams have different priorities, different resource levels, and different definitions of what constitutes a satisfactory contribution, the management of cross-functional dependencies becomes a significant source of friction. The teams are not failing to perform. They are each responding rationally to their own priority context. The friction is a structural consequence of organizing work across functional boundaries without sufficient coordination mechanisms.
Information asymmetry is a fourth. Work proceeds most efficiently when the people performing it have access to the information they need when they need it. When information is controlled by other teams, embedded in systems that are difficult to access, or simply not shared because no clear protocol for sharing it exists, workers must spend time seeking information rather than using it. This seeking activity is pure friction. It adds no value to the output. It consumes time that could have been applied to productive work.
“When we finally mapped where our projects were losing time, we found that the majority of the delay was not in the work itself. It was in the transitions between work steps. The friction was in the handoffs, the approvals, and the waiting for information. The actual work was moving at roughly the speed it should.”
Individual friction points are easy to dismiss as minor inefficiencies. The cumulative economic cost of friction across an organization is rarely minor.
Consider an organization of two thousand employees in which each employee loses an average of one hour per day to friction-related activities. Waiting for approvals, seeking information, attending coordination meetings that exist to manage organizational complexity rather than to produce outputs, managing dependencies that could be handled through clearer protocols. One hour per day per person is two hundred and fifty thousand hours per year across the organization. At a fully-loaded labor cost of seventy-five dollars per hour, that is eighteen million dollars per year in labor investment consuming friction rather than producing output.
This calculation is illustrative rather than precise. The actual distribution of friction across organizations varies. But the magnitude is consistently larger than leadership intuition suggests because friction is distributed across thousands of small events rather than concentrated in visible inefficiencies.
Friction is not a soft organizational problem. It has a hard economic cost, and how internal friction connects to cost structure and performance is one of the most underexamined relationships in corporate financial management.
Friction reduction requires a different organizational posture than most improvement initiatives adopt. Most initiatives target specific problems or specific teams. Friction reduction requires examining the organizational system through which work moves and identifying the structural conditions that create resistance throughout that system.
This means mapping actual work flows rather than designed work flows. It means identifying where ownership boundaries are unclear and making them explicit. It means examining approval chains for their current relevance and removing or streamlining the ones that are operating on historical rather than current risk logic. It means improving information flow between teams so that seeking time is minimized and working time is maximized.
Organizations that reduce friction effectively do not do so through a single initiative. They build it as an ongoing discipline, regularly examining where resistance is building in their operating processes and addressing it before it becomes embedded as an accepted feature of organizational life.
“The most expensive thing in our organization was not any specific cost line. It was the friction between teams that slowed everything we tried to do. When we reduced it, the improvement showed up everywhere simultaneously.”
Friction is the invisible tax on organizational performance. Reducing it does not require more investment. It requires examining how the existing investment in people and processes is being consumed and redesigning the organizational structures that are converting productive capacity into coordination overhead.
The dashboard showed green across every key indicator. Revenue was tracking to plan. Customer satisfaction scores were within the acceptable range. Employe...
Get started
The growth was real. New customers were coming in faster than the pipeline had projected. Revenue was tracking significantly above plan. The commercial tea...
Get started