Organizations usually know when something is dramatically broken. A failed transformation, missed customer commitment, major talent loss, significant operational disruption, or sustained performance decline eventually demands attention. Organizational friction is harder to see because it rarely arrives as a single event. It accumulates through hundreds of smaller obstacles that individually appear manageable but collectively change how much effort the organization requires simply to operate.
A decision waits for another approval. A team prepares the same information for multiple leaders. Two functions maintain overlapping processes because ownership is unclear. Employees attend meetings because no one is certain who actually needs to be involved. A manager becomes the default escalation point for decisions that should occur elsewhere. Priorities are added without older priorities being removed. Teams create workarounds around technology that does not fit the work. Leaders spend increasing amounts of time coordinating across organizational boundaries that were intended to create clarity.
None of these conditions necessarily looks strategic in isolation. Most can be explained away as the normal inconvenience of working in a complex organization. The meeting took an hour. The approval required another day. The duplicate analysis consumed only a few additional hours. The employee eventually found the information. The customer issue was resolved after escalation. Work continues, so the organization appears to be functioning.
But work continuing is not the same as the organization working well. Every unnecessary organizational obstacle consumes something. It may consume time, attention, management capacity, decision speed, employee energy, or the ability to focus on higher-value work. Often the cost is absorbed rather than recorded. Employees stay later. Managers compensate. High performers navigate around broken processes. Teams build informal relationships to bypass formal structures. Leaders intervene personally to accelerate decisions. Additional people are added because existing capacity appears insufficient. The organization adapts to the friction, and that adaptation can make the underlying problem less visible.
This is one reason organizational friction can persist for years. Organizations are remarkably capable of compensating for their own design weaknesses. Talented employees find ways to make things work. Experienced leaders know whom to call. Long-tenured employees understand which process can be bypassed, which approval actually matters, and which stakeholder needs to be consulted even when the formal workflow says otherwise. Those behaviors keep the organization moving, but they can also create the illusion that the system is healthier than it is.
The cost becomes clearer when the organization changes. Growth increases the number of interactions required across functions. A transformation introduces new roles without fully retiring old ones. An acquisition connects operating models that were designed independently. New technology changes workflows without changing decision rights. Leaders add governance to control risk but rarely remove governance that has outlived its purpose. Strategies evolve faster than structures and processes. What employees once managed through relationships and institutional knowledge becomes increasingly difficult to navigate at scale.
At that point, friction begins to consume organizational capacity in ways leaders can feel but struggle to explain. Decisions seem slower. Managers appear overloaded. Employees report frustration. Functions blame one another for delays. Meetings multiply. Headcount requests increase. Execution becomes inconsistent. Leaders may respond to each symptom independently: improve collaboration, streamline a process, hire additional capacity, implement a new tool, clarify accountability, launch a culture initiative, or reorganize a team.
Any of those responses might be appropriate. The problem is that the symptoms may not be independent. A slow decision can originate in unclear decision rights, overlapping accountability, insufficient information, excessive governance, or leadership behavior. Cross-functional conflict can reflect incentives, organizational boundaries, competing priorities, capacity constraints, or poorly designed interfaces. Manager overload can reflect span of control, but it can also emerge because decisions that should occur elsewhere continuously escalate upward. Employees may appear resistant to change when they are actually navigating several competing systems that require incompatible behaviors.
This is where organizational friction becomes more than an efficiency problem. It becomes an organizational effectiveness problem because the organization's own operating conditions begin consuming the capacity required to execute its strategy.
The important distinction is not between organizations with friction and organizations without it. Every organization requires coordination, governance, controls, prioritization, and tradeoffs. Some friction is valuable. A second approval may reduce material risk. Deliberate challenge can improve a consequential decision. Regulatory controls can protect customers and the enterprise. Cross-functional consultation can prevent one function from optimizing at another's expense. Removing all friction would not create a high-performing organization. It could create a reckless one.
The executive challenge is to distinguish productive friction from organizational drag. Productive friction creates value greater than the effort it requires. It improves decisions, manages meaningful risk, protects important standards, or creates necessary coordination. Organizational drag consumes effort without creating equivalent value. It persists because of unclear authority, unnecessary complexity, duplicated work, conflicting priorities, poorly designed interfaces, outdated governance, fragmented systems, or organizational habits that no longer serve their original purpose.
That distinction changes the question leaders should ask. Instead of asking only whether employees are busy enough, whether processes are efficient enough, or whether individual teams are performing, leaders should ask: How much of our organization's capacity is being used to execute the work, and how much is being used to navigate the organization itself?
That question exposes a cost that rarely appears directly on a financial statement. The organization still pays for it though. It pays through slower execution, consumed management capacity, duplicated effort, delayed decisions, unnecessary coordination, employee exhaustion, missed opportunities, and the additional resources required to compensate for conditions the organization itself has created. Organizational friction is therefore not simply what makes work annoying. It is what the organization makes employees do in addition to the work just to get the work done.
Friction Accumulates Across the System
Organizational friction becomes expensive because it rarely stays contained inside the place where it begins. A poorly designed approval process does not only slow the decision being approved. It can force employees to create workarounds, increase the number of coordination meetings, generate additional status reporting, and push routine decisions upward to leaders who were never meant to make them. A single structural weakness can therefore create secondary work across multiple parts of the organization.
This accumulation is easy to miss because the organization usually sees the symptoms separately. Finance may see delayed approvals. Operations may see cycle-time problems. HR may see manager overload or declining engagement. Technology may see repeated requests for system customization. Business leaders may see inconsistent execution. Each function can respond rationally within its own domain while the underlying source of friction remains unchanged.
The result is a familiar pattern: the organization becomes increasingly busy solving problems created by the organization itself. That pattern often starts with ambiguity. When ownership is unclear, more people become involved. When decision rights are unclear, approvals multiply. When priorities compete, teams escalate tradeoffs upward. When roles overlap, coordination expands because people must continuously determine who should act. When systems are fragmented, employees manually reconcile information. When governance accumulates, employees spend additional time preparing material for reviews that may not meaningfully improve the decision.
Each additional coordination step can appear reasonable on its own. The problem is cumulative. One extra approval does not transform an organization. Neither does one recurring meeting, one duplicated report, one workaround, or one ambiguous interface. But when those conditions appear across hundreds of workflows and thousands of interactions, the organization begins converting productive capacity into navigation capacity.
This distinction matters because capacity is often discussed as though it were primarily a staffing problem. When teams feel overloaded, leaders naturally ask whether they have enough people. Sometimes they do not. But apparent capacity shortages can also reflect the amount of effort required to compensate for organizational friction. Adding headcount into a high-friction environment may increase total labor while leaving the underlying productivity constraint intact.
The same can happen with management capacity. Leaders may conclude that managers have too many direct reports when part of the overload actually comes from the amount of organizational mediation managers are required to perform. A manager who spends significant time resolving unclear priorities, escalating decisions, coordinating across poorly defined boundaries, interpreting conflicting messages, and navigating broken processes has less capacity to coach, develop, plan, and lead. The issue may involve span of control, but span alone does not explain how much organizational friction the manager is absorbing.
This is one reason friction can distort workforce decisions. Teams request additional resources because existing employees cannot keep up with the work. But some of that workload may consist of rework, coordination, duplicated analysis, unnecessary approval activity, manual reconciliation, or effort required to navigate unclear organizational interfaces. If leaders respond only by adding capacity, the organization can unintentionally institutionalize the friction rather than remove it.
The same dynamic affects decision speed. Slow decisions are often attributed to cautious leaders or bureaucratic culture, yet the problem may sit in the architecture surrounding the decision. Too many stakeholders may have implicit veto power. Decision authority may be distributed ambiguously. Information may live in different systems. Governance forums may overlap. Leaders may be reluctant to act because previous decisions were repeatedly reopened. The visible outcome is delay, but the mechanism is distributed across the system.
Cross-functional work is particularly vulnerable because friction tends to increase at organizational boundaries. Functions are usually designed around different expertise, goals, metrics, and operating rhythms. That differentiation is necessary. Problems emerge when the interfaces between those functions are poorly designed. One team's efficient process can become another team's bottleneck. One function's performance metric can create work for another. A handoff that appears clear in a process map may require repeated interpretation in practice.
As those boundary problems accumulate, organizations often respond by adding coordination. More meetings are created. Additional roles are introduced to connect functions. Project managers are added. Steering committees form. Escalation channels multiply. Shared trackers proliferate. These mechanisms can help, but they can also become compensating structures layered on top of unresolved design problems.
The organization then becomes more complex in order to manage the complexity it already created. Technology can accelerate the same cycle. A new platform may automate parts of a workflow while preserving an unnecessary process. Employees gain a faster way to complete steps that should not exist. Different functions implement tools independently, creating new integration problems. Manual workarounds move from spreadsheets into systems without changing the decision logic behind them. Technology improves local efficiency while increasing organizational fragmentation.
This is why friction should be examined as a system condition rather than as a collection of inconveniences. The relevant question is not simply, “Where is work slow?” It is, “What organizational conditions are repeatedly forcing employees to spend effort coordinating, clarifying, reconciling, escalating, duplicating, or compensating?”
That shift makes the cost more visible. Friction is expensive not only because individual tasks take longer. It is expensive because it multiplies activity around the work, consumes managerial attention, reduces available capacity, and creates new mechanisms whose purpose is to compensate for weaknesses elsewhere in the organization.
The more friction accumulates, the harder it becomes to distinguish the work required by the business from the work required by the organization.
And once that distinction becomes blurred, leaders can begin treating organizational drag as normal operating cost rather than as a condition that can be redesigned.
The Cost Rarely Appears Where the Friction Begins
One reason organizational friction survives is that its cost is rarely recorded at the point where it is created. An unnecessary approval does not appear on a financial statement as organizational friction. Neither does a duplicated report, a recurring coordination meeting, a delayed decision, or the hour an employee spends reconciling information across systems. Those costs are absorbed into payroll, management time, project timelines, operating expenses, and missed opportunities. The organization pays for them without necessarily knowing what it is paying for.
This creates a measurement problem. Traditional financial systems are designed to show what the organization spends, not how much effort was unnecessarily required to produce the outcome. Two teams may deliver the same result with similar headcount and budget while operating at very different levels of friction. One may spend most of its capacity creating value. The other may spend a significant portion of its capacity coordinating around unclear roles, navigating governance, correcting rework, and escalating decisions. The financial statements may look similar even though the organizational conditions are not.
Time is the most obvious cost, but it is only the beginning. Every hour spent navigating unnecessary organizational complexity is an hour unavailable for analysis, customer work, innovation, development, problem solving, or execution. At individual scale, that tradeoff may appear negligible. At enterprise scale, small amounts of recurring friction can consume substantial capacity because the cost multiplies across people, interactions, and time.
Management attention may be even more consequential. Senior leaders have finite cognitive and decision capacity. When that capacity is repeatedly consumed resolving issues that should have been settled lower in the organization, clarifying priorities that should already be coherent, or mediating across poorly designed boundaries, the cost is not simply the time spent in the meeting. It is the strategic work those leaders are not doing while they compensate for operating conditions elsewhere.
This is particularly important because organizations often respond to management overload by adding more management. Additional leadership layers, coordination roles, chiefs of staff, program offices, committees, and governance forums can all be appropriate. But if their primary purpose is to compensate for ambiguity or fragmentation, the organization may be increasing structural cost to manage friction created by the existing structure. What looks like additional capability can become another layer of organizational mediation.
Decision delay creates another form of cost that is easy to underestimate. A decision that takes two weeks instead of two days does not necessarily generate a visible expense, but the delay can affect customers, projects, hiring, capital allocation, product development, or competitive response. Teams may continue working under assumptions while waiting for direction. Others may pause. Some may hedge by pursuing multiple paths simultaneously. The direct cost of the delayed decision can therefore be much smaller than the activity generated while the organization waits for it.
Decision quality can also deteriorate. High-friction environments tend to generate more escalation, and escalation changes who is making the decision. Senior leaders may have broader organizational context, but they are often further removed from the work. When routine decisions repeatedly move upward because authority is unclear or people fear making the wrong call, the organization can create a paradox: decisions receive more senior attention while becoming less informed by local knowledge. The organization pays both through slower speed and weaker use of expertise.
Rework adds another layer. Conflicting priorities, incomplete handoffs, unclear ownership, changing expectations, and fragmented information can cause work to be revised or recreated after substantial effort has already been invested. Organizations frequently see the final deliverable but not the abandoned versions behind it. The cost is hidden because the employee was working the entire time. Utilization can remain high even while productive yield falls.
That distinction between activity and productive yield is important. A high-friction organization can look extremely productive from the inside because everyone is busy. Calendars are full. Teams are responsive. Managers are constantly solving problems. Employees work long hours. Leaders make frequent decisions. The intensity of activity can become evidence, in the organization's mind, that the business is demanding rather than that the operating environment is inefficient.
Over time, friction can even become culturally normalized. Employees learn that getting something done requires knowing the right person. Leaders accept that every significant decision will need escalation. Teams assume that several rounds of revision are inevitable. Meetings become the default mechanism for resolving ambiguity. Workarounds become institutional knowledge. New employees are taught how to navigate the system rather than questioning why the system requires so much navigation.
Once those behaviors become normal, removing friction can become surprisingly difficult because the compensating behaviors have acquired value of their own. The experienced employee who knows how to bypass a broken process may become indispensable. The manager who resolves every cross-functional conflict may be viewed as a strong leader. The executive who personally accelerates stalled decisions may gain a reputation for decisiveness. Each person is creating real value in the moment, but some of that value exists because the organization has created conditions that require heroic intervention.
This is where organizational friction begins to distort talent signals. Employees who navigate complexity well may appear more capable than those who simply perform the underlying work well. Managers who compensate for structural weaknesses may be rewarded for solving problems the system continually recreates. Teams with strong informal networks may outperform others not because their formal design is stronger, but because they have developed better ways to work around it. Performance becomes partly a measure of who can overcome the organization.
The cost can also surface through employee experience. Constant friction increases the effort required to accomplish ordinary work. Employees may describe the result as burnout, frustration, lack of empowerment, poor collaboration, or ineffective leadership. Those experiences are real, but addressing only the sentiment can miss what is generating it. A resilience program does not remove unnecessary approvals. A collaboration workshop does not reconcile competing goals. Better communication does not repair unclear decision authority. Employee experience can therefore become one of the places where organizational friction becomes visible, even when the source sits elsewhere.
Customers may experience the cost as well. Internal friction can become slower response times, inconsistent answers, delayed commitments, repeated handoffs, or an inability to resolve issues at the point of contact. What begins as an internal organizational design problem can eventually become a customer experience problem. The customer does not see the approval chain, matrix complexity, conflicting metrics, or fragmented systems. They experience the consequence.
The most significant cost may ultimately be opportunity cost. Organizations have limited capacity to pursue strategic priorities. When substantial effort is consumed managing internal complexity, less capacity remains for adaptation, innovation, growth, capability building, and strategic change. Friction does not have to stop execution entirely to be strategically important. It only has to make the organization consistently slower, more expensive, or more difficult to change than it needs to be.
This suggests that leaders should think about organizational friction as a form of capacity leakage. The organization invests in talent, leadership, technology, and structure to create productive capability, but some portion of that capability is lost to the effort required to navigate the organization itself. The exact amount may be difficult to reduce to a single number, and pretending otherwise can create false precision. But difficulty of measurement does not make the cost imaginary.
The more important task is to identify where capacity is repeatedly being consumed without creating proportional value. Where do decisions wait? Where does work bounce between teams? Where are employees reconciling information manually? Where do managers repeatedly intervene? Where does governance add review without improving the outcome? Where are people compensating for unclear roles, conflicting priorities, or poorly designed interfaces?
Those patterns reveal where the organization may be paying for friction even when no accounting category carries its name. The strategic question is not whether every inefficiency can be eliminated. It is whether the organization is knowingly investing its scarce capacity in the friction it chooses to keep, or unknowingly spending it on friction it has simply learned to tolerate.
Friction Is Usually Produced by the Organization, Not the Employee
When organizational friction becomes visible, the first response is often behavioral. Leaders may conclude that people are not collaborating well enough, managers are not communicating clearly enough, employees are resisting change, or teams are failing to take ownership. Those explanations can sometimes be correct, but they can also place responsibility on individuals for conditions the organization has designed.
Behavior does not occur in a vacuum. Employees respond to structures, incentives, decision rights, workload, information flows, leadership expectations, systems, and the consequences attached to different choices. When those conditions conflict, employees often adapt in ways that appear inefficient from a distance but make sense locally.
Consider a team that repeatedly escalates decisions. Leaders may describe the behavior as risk aversion or lack of empowerment. But if decision authority is ambiguous, prior decisions have been overturned, mistakes are punished inconsistently, or several stakeholders can challenge the outcome after the fact, escalation may be a rational response. Employees are not necessarily unwilling to decide. They may have learned that the safest way to operate is to transfer the risk upward.
The same dynamic can appear as poor collaboration. Two functions may struggle to work together because they have different objectives, conflicting measures, incompatible timelines, or unclear ownership of the work between them. Leaders may respond with relationship-building sessions or collaboration expectations. Those interventions may help, but they cannot fully compensate for a system that rewards each function for optimizing against the other.
This is why recurring friction deserves different treatment from isolated breakdowns. A single misunderstanding may be interpersonal. The same misunderstanding repeated across teams may indicate unclear organizational interfaces. One manager hoarding decisions may be a leadership issue. Similar escalation patterns across an enterprise may point to decision architecture. One employee struggling with a system may require training. Hundreds of employees maintaining parallel spreadsheets around the same system may indicate that the system does not fit the work.
The pattern matters because repetition changes the level of explanation. Organizations often underdiagnose friction by treating systemic patterns as collections of individual problems. Each issue is addressed close to where it appears. A manager receives coaching. A team gets a new process. Employees attend training. A communication plan is launched. Another governance forum is created. These responses may improve the local symptom while leaving the organizational condition that repeatedly produces it intact. The deeper causes often sit across several dimensions at once.
Structure can create friction when responsibilities overlap, interfaces are poorly defined, spans create excessive dependence, or work is separated in ways that require constant reintegration.
Decision architecture can create friction when authority is unclear, too many stakeholders have approval rights, decisions repeatedly escalate, or accountability is assigned without corresponding control.
Priorities can create friction when leaders continually add work without removing it, strategic priorities compete across functions, or teams receive incompatible signals about what matters most.
Processes and governance can create friction when controls accumulate over time, reviews duplicate one another, exceptions become routine, or mechanisms designed for earlier conditions remain after the business has changed.
Technology and information can create friction when systems fragment the workflow, information must be reconciled manually, data ownership is unclear, or employees have to move between tools to complete what should be a coherent process.
Leadership behavior can create friction when leaders routinely reopen decisions, bypass governance selectively, create competing commitments, tolerate ambiguity, or solve systemic problems through personal intervention rather than redesign.
Talent and capability can create friction when the organization lacks the skills or experience required for the work, but capability gaps can also be created by the system itself. An employee may have the necessary expertise but be unable to apply it because decision authority, workload, role design, or organizational interfaces prevent effective use.
These sources rarely operate independently. A structural ambiguity can generate decision problems. Decision problems create additional governance. Additional governance slows work. Slow work generates escalation. Escalation consumes leadership capacity. Leaders become bottlenecks, which encourages teams to create informal workarounds. Workarounds reduce consistency, so the organization adds more controls. The attempt to manage friction can therefore create additional friction.
That reinforcing cycle is one of the reasons organizational complexity is difficult to unwind. The mechanisms that appear to provide stability may have been created as responses to weaknesses elsewhere. Removing one without understanding what it compensates for can expose the original problem. Leaders then restore the mechanism or add a new one, concluding that simplification does not work.
Reducing organizational friction therefore requires more than deleting steps or layers. The objective is not simply to make the organization lighter. It is to understand why the friction exists, what function it currently serves, and whether that function can be achieved with less organizational cost.
An approval may exist because accountability is unclear. A recurring meeting may compensate for weak information flows. A coordination role may exist because two functions have poorly designed interfaces. A management layer may be absorbing decisions that the organization has never successfully distributed. A manual report may exist because leaders do not trust the underlying data. Removing the visible mechanism without addressing the condition beneath it can make execution worse rather than better.
This distinction separates simplification from redesign. Simplification asks what can be removed.
Redesign asks what the organization is trying to accomplish, why the current system requires so much effort to accomplish it, and what conditions would allow the same or better outcome with less friction.
That is a more demanding question because some of the friction leaders experience is produced by choices they have made elsewhere. More control creates additional review. More specialization creates additional interfaces. More customization creates additional complexity. More priorities create more coordination. More layers can create greater oversight while increasing decision distance. None of these choices is inherently wrong. The cost emerges when the organization accumulates them without continuing to evaluate whether the value they create still exceeds the friction they impose.
This is also why friction tends to increase gradually rather than through one obvious design decision. Organizations rarely choose complexity for its own sake. They add structures, processes, controls, systems, and roles in response to legitimate needs. A new customer segment requires specialization. A regulatory event requires additional controls. Growth requires more management. An acquisition introduces another system. A transformation creates temporary governance. Each choice is rational in context.
The problem is that organizations are often better at adding mechanisms than retiring them. Temporary processes become permanent. Exceptions become standard practice. Additional approvals survive the risk that originally justified them. Teams reorganize while old forums remain. New technology is layered onto existing workflows. Accountability changes but reporting requirements do not. The organization gradually accumulates operational sediment from earlier strategies, leaders, structures, and problems.
Employees encounter all of it at once. From their perspective, friction is not historical. They simply experience the current organization as it exists. They must navigate the layers regardless of why those layers were created. This is why long-tenured leaders can underestimate organizational friction. Each addition may have made sense when introduced, and familiarity reduces the perceived effort required to navigate it. New employees, cross-functional teams, and people moving into different parts of the enterprise often see the accumulated complexity more clearly because they have not yet learned to treat it as normal.
That perspective can be valuable. Questions such as “Why does this require three approvals?” or “Why do both teams produce this report?” can sound naïve inside an established organization, yet they may reveal exactly where historical complexity has become detached from current value.
The challenge for leaders is to resist explaining every recurring difficulty as a people problem before examining the conditions surrounding the work. If capable employees repeatedly struggle in the same places, if different leaders encounter similar bottlenecks, or if workarounds persist despite repeated attempts to eliminate them, the organization may be looking at evidence about its own design.
Organizational friction becomes actionable when leaders stop asking only, “Why aren't people working differently?” and begin asking, “What is the organization making difficult that should be easier?” That question does not remove accountability from employees or leaders. It places accountability at the correct level. People are responsible for how they perform within the organization. Leaders are also responsible for the organization within which people are being asked to perform.
What Great Organizations Do Differently
Great organizations do not assume that friction is simply the unavoidable price of complexity. They accept that large organizations will always require coordination, governance, specialization, controls, and tradeoffs, but they are more deliberate about distinguishing the complexity the business actually requires from the complexity the organization has accumulated around it. Their objective is not frictionless work. It is to ensure that the effort required to navigate the organization remains proportionate to the value that effort creates.
They pay particular attention to recurring points of organizational effort. When the same decisions repeatedly escalate, the same teams continually negotiate ownership, or the same processes generate workarounds, stronger organizations treat the repetition as evidence. They do not assume that every occurrence is an isolated execution failure. They ask what underlying condition is capable of producing the same behavior across different people, teams, or situations.
That distinction changes how problems are diagnosed. A single missed handoff may require coaching. Repeated handoff failures across a workflow may require redesign. One leader creating a bottleneck may require a leadership intervention. Similar bottlenecks appearing across several functions may indicate that decision authority is concentrated too high in the organization. One team struggling with workload may have a staffing problem. Multiple teams adding capacity while spending substantial time on rework, coordination, and escalation may be experiencing something different.
Great organizations therefore look for patterns before prescribing solutions. They also make organizational interfaces more explicit. Much of the work in modern organizations happens across boundaries rather than entirely within a single function. Strategy moves across functions. Customer outcomes depend on multiple teams. Transformation work crosses existing reporting lines. Decisions require information from different disciplines. The quality of these interfaces can therefore matter as much as the quality of the individual functions themselves.
When interfaces are poorly designed, employees become the integration mechanism. They determine who should participate, reconcile competing priorities, interpret ownership, locate information, and negotiate decisions informally. Strong performers can make this arrangement work, but the organization becomes dependent on individual navigation capability rather than organizational clarity.
Great organizations reduce that dependency. They clarify where responsibilities intersect, who has authority over consequential decisions, what information must move across boundaries, which outcomes require shared accountability, and where escalation should occur. They do not attempt to eliminate collaboration. They design the conditions that allow collaboration to produce work rather than merely consume time.
They are similarly disciplined about governance. Governance is treated as an investment rather than a default response to uncertainty. Every approval, review forum, committee, control, and reporting requirement consumes organizational capacity. Stronger organizations therefore ask what risk or decision the mechanism exists to manage and whether it continues to do so effectively.
That question becomes particularly important because governance tends to accumulate. A failure produces an additional control. A transformation creates a steering committee. A new leader requests another report. A regulatory requirement adds another review. An acquisition brings its own processes. Individually, each mechanism may have a defensible origin. Collectively, they can create an operating environment in which decisions require substantially more organizational effort than leaders realize.
Great organizations periodically challenge that accumulation. They ask whether a control still addresses a material risk, whether two forums serve overlapping purposes, whether information is being requested because it is used or because it has always been requested, and whether a decision could be made safely closer to the work. Governance remains where it creates value. It is redesigned or retired where it has become organizational drag.
They also recognize that priorities are part of organizational design. Leaders frequently discuss prioritization as an individual capability, but employees cannot personally resolve enterprise contradictions. If multiple senior leaders each declare different work critical, if new initiatives are continually added without corresponding tradeoffs, or if functional goals compete with enterprise priorities, employees are forced to perform the prioritization the leadership system has not completed.
The resulting friction appears as overload, shifting focus, excessive meetings, delayed delivery, and repeated escalation. Leaders may then ask teams to become more disciplined about priorities even though the organization continues generating more commitments than available capacity can support.
Great organizations make the tradeoffs more explicit. Adding meaningful work creates a corresponding question about what will stop, slow, receive fewer resources, or become less important. Capacity is treated as finite. Strategic priorities are translated into organizational choices rather than simply added to existing commitments. This does not eliminate competing demands, but it reduces the amount of unresolved strategic conflict pushed downward into the organization.
They also examine management workload differently. A manager's calendar can reveal more than individual time-management habits. If managers spend a disproportionate amount of time escalating routine decisions, translating conflicting priorities, manually coordinating work across functions, resolving unclear accountability, or compensating for broken processes, that activity may reveal organizational friction being absorbed by the management layer.
Stronger organizations do not automatically conclude that the answer is fewer meetings, greater delegation, or additional managers. They investigate why the management work exists. Some of it will be essential leadership. Some will be the unavoidable coordination required by the business. But some may be organizational repair work generated by conditions that could be changed.
That distinction matters because managers often become shock absorbers for weak organizational design. They reconcile contradictions before employees experience them. They personally connect functions whose interfaces do not work. They interpret strategies that have not been translated clearly. They negotiate resources because priorities exceed capacity. They repeatedly intervene so customers do not feel internal breakdowns.
Good managers should solve problems, but an organization should not depend on managers continually compensating for the same structural weaknesses. When the same repair work becomes a permanent part of leadership, great organizations investigate what needs to change upstream.
They approach technology with similar caution. Digitizing a process is not automatically the same as improving it. Automating unnecessary steps can make organizational friction faster without making it smaller. A workflow that requires five approvals remains a five-approval workflow when the approvals move into software. A fragmented information architecture remains fragmented when employees use newer systems to reconcile it.
Great organizations therefore examine the work before assuming technology is the answer. They ask what information is actually needed, which decisions the process should support, where ownership belongs, and which steps exist because of historical constraints rather than current necessity. Technology can then reinforce a better operating model rather than hardening an inefficient one.
Perhaps most importantly, great organizations are willing to question successful workarounds. Workarounds often contain valuable intelligence. Employees create them because the formal organization is not enabling the work effectively. A spreadsheet may reveal missing system functionality. An informal meeting may reveal a broken interface. A personal relationship between two leaders may be compensating for unclear governance. A shadow process may exist because the official process cannot accommodate the actual work.
The instinct is often to eliminate these behaviors in the name of standardization. Stronger organizations first ask what problem the workaround is solving. The workaround itself may not be desirable, but the need it addresses can reveal where the formal organization and actual work have diverged.
This is one of the clearest differences between organizations that merely manage friction and organizations that learn from it. The first tries to make people better at navigating the current system. The second uses recurring navigation effort as evidence about where the system may need to change.
The same principle applies to employee feedback. Complaints about bureaucracy, meetings, unclear ownership, slow decisions, poor collaboration, or constant reprioritization can easily be dismissed as dissatisfaction with the unavoidable realities of organizational life. Not every complaint warrants redesign, and reducing friction cannot mean responding to every preference. But repeated themes across levels, functions, or workflows deserve investigation because employees experience the organization at the points where its design meets the work.
Great organizations therefore do not ask employees only whether they are satisfied with the organization. They pay attention to where employees consistently have to compensate for it.
This creates a different standard for organizational effectiveness. The objective is not simply to have the right structure, the right processes, the right technology, or capable people. Each of those elements can appear reasonable independently while their interaction creates substantial friction. What matters is whether the system allows people to convert capability into execution without requiring excessive organizational navigation in between.
That is why stronger organizations continually examine the relationship between value-producing work and navigation work. They want coordination where coordination protects outcomes. They want challenge where challenge improves decisions. They want controls where controls manage meaningful risk. They want management where management adds judgment, direction, and capability.
What they try to reduce is organizational effort that exists primarily because another part of the organization is unclear, fragmented, duplicated, or poorly aligned. They do not pursue simplicity for its own sake. They pursue an organization in which complexity earns its cost.
1. Where are we asking people to spend effort navigating the organization instead of executing the work?
Every organization requires coordination, but leaders should distinguish between coordination that creates value and coordination that exists because the organization has become difficult to navigate. Repeated status meetings, duplicated reports, manual reconciliation, unclear handoffs, unnecessary approvals, and constant escalation can all consume capacity without improving the underlying outcome. The question is not whether employees are busy. It is whether the work surrounding the work is proportionate to the value it creates.
2. Which recurring problems are we still treating as isolated events?
A one-time breakdown may be local. A repeated pattern is different. When the same decisions escalate, the same teams struggle across boundaries, or the same processes require workarounds, leaders should ask what organizational condition is capable of producing the pattern. Repetition can indicate unclear authority, conflicting priorities, weak interfaces, duplicated governance, or another systemic source of friction. Treating each occurrence independently can keep the organization busy solving symptoms while preserving the condition that recreates them.
3. Where are managers compensating for organizational design weaknesses?
Managers often become the point where organizational contradictions are absorbed. They translate competing priorities, resolve unclear ownership, connect functions whose interfaces do not work, accelerate stalled decisions, and shield employees from broken processes. Some of that is legitimate leadership. The risk emerges when the same compensating activity becomes routine. Leaders should examine whether management capacity is being used to lead the business or repeatedly repair the conditions under which the business is being asked to operate.
4. Which complexity in our organization still earns its cost?
Not all friction should be removed. Governance, controls, specialization, review, and deliberate challenge can create significant value. The stronger question is whether the value continues to justify the organizational effort required. Processes and structures often outlive the conditions that created them. Leaders should be able to explain why important approvals, forums, layers, reports, and coordination mechanisms still exist and what material outcome they protect or improve. Complexity that cannot answer that question deserves closer examination.
5. What would become easier if we fixed the organization instead of asking people to work harder within it?
Organizations are often exceptionally good at compensating. Employees work longer, managers intervene, teams create informal workarounds, additional resources are added, and leaders personally accelerate important decisions. Those behaviors can sustain performance for a time, but they can also obscure the organizational conditions creating the extra effort. Leaders should identify where performance depends disproportionately on persistence, relationships, escalation, or heroic intervention. Those areas may reveal where the organization itself has become part of the execution problem.
Taken together, these questions shift the conversation away from whether employees are working hard enough and toward whether the organization is converting that effort into productive capacity effectively. They also create a more disciplined way to distinguish necessary complexity from avoidable organizational drag.
The objective is not to make work effortless. Complex strategy will still require difficult decisions, coordination, judgment, and tradeoffs. The objective is to ensure that the difficulty employees experience comes primarily from solving the problems the business needs solved, not from overcoming obstacles the organization has unnecessarily placed in their path.
Organizational friction is not simply a collection of annoyances. It is a signal about the relationship between the work an organization is trying to accomplish and the conditions it has created for accomplishing it. When structures, decisions, processes, systems, priorities, and leadership practices align reasonably well, employees can direct more of their capacity toward execution. When those elements conflict, organizational effort shifts toward coordination, clarification, escalation, reconciliation, and compensation.
That distinction matters because leaders can easily mistake sustained effort for healthy performance. A team that repeatedly works around broken processes may still deliver. A manager who resolves constant cross-functional conflict may still be viewed as effective. An executive who personally accelerates decisions may still produce results. But when performance depends on people continually overcoming the organization, the organization is consuming part of the capability it hired those people to provide.
The cost is rarely confined to efficiency. Friction affects how quickly decisions move, how consistently work crosses boundaries, how much capacity managers have available to lead, how employees experience the organization, and how effectively talent can apply its capability. Over time, those effects can influence customer outcomes, transformation capacity, workforce requirements, and the organization's ability to respond when strategy changes.
This is why organizational friction should not be approached as a campaign to remove bureaucracy or simplify everything. Some organizational friction is deliberate and valuable. Controls can protect the enterprise. Challenge can improve judgment. Specialization can increase expertise. Governance can prevent local decisions from creating broader risk. The relevant question is whether the organizational cost remains proportionate to the value being created.
That requires leaders to understand the purpose behind the complexity they inherit. A process may look inefficient but protect an important risk. A meeting may appear unnecessary but compensate for information that does not flow elsewhere. A management layer may seem excessive but currently hold together an interface the formal design has never resolved. Removing those mechanisms without understanding their function can transfer friction rather than reduce it.
The stronger approach is to examine where the organization repeatedly requires additional effort and determine what that effort is accomplishing. If the effort creates meaningful value, it may be worth preserving. If it exists primarily because another part of the system is unclear, duplicated, fragmented, or outdated, the organization has an opportunity to recover capacity rather than simply demand more of it.
This makes friction diagnostically useful. Repeated escalation can reveal decision ambiguity. Constant reprioritization can reveal unresolved strategic tradeoffs. Workarounds can reveal a gap between formal process and actual work. Management overload can reveal that leaders are serving as organizational integration mechanisms. Cross-functional conflict can reveal misaligned objectives or poorly designed interfaces. Employee frustration can reveal operating conditions that make routine execution harder than leaders realize.
The important move is to trace the friction back to the condition producing it rather than treating the visible behavior as the cause.
That also changes how leaders should think about organizational capacity. Capacity is not only the number of people available or the number of hours they can work. It is the amount of organizational capability that remains available after the requirements of navigating the organization have been satisfied. An enterprise can therefore have substantial talent and still experience constrained capacity if too much of that talent is being consumed by internal friction.
Growth makes this particularly consequential. Workarounds that function at smaller scale often become expensive as the number of employees, customers, products, geographies, or organizational interfaces increases. Informal coordination becomes harder. Leaders can no longer personally resolve every ambiguity. Additional structure is introduced to create control, but each addition can create new interfaces of its own. Unless the organization deliberately examines how work moves through the system, growth can scale friction alongside revenue and headcount.
Transformation can expose the same problem even more quickly. New strategies usually require the organization to make different decisions, coordinate in different ways, develop new capabilities, and shift resources. Existing friction consumes the very capacity required to make those changes. The organization may therefore struggle not because the transformation itself is poorly conceived, but because too much organizational energy is already committed to maintaining the current system.
This is why friction can become strategically important before it becomes operationally catastrophic. An organization does not need to be broken for friction to matter. It only needs to be using more capacity than necessary to produce the outcomes its strategy requires.
The most effective organizations will never eliminate friction entirely, nor should they try. They will instead become more deliberate about where friction is worth paying for and less tolerant of friction that exists only because the organization has learned to work around itself.
Organizational effectiveness improves when the difficulty of execution comes from the complexity of the work, not from unnecessary complexity in the organization required to perform it.
Supporting Research
- Bakker, A. B., & Demerouti, E. (2007). The job demands-resources model: State of the art. Journal of Managerial Psychology, 22(3), 309–328.
- Burton, R. M., & Obel, B. (2018). The science of organizational design: Fit between structure and coordination. Journal of Organization Design, 7, Article 5.
- Galbraith, J. R. (1974). Organization design: An information processing view. Interfaces, 4(3), 28–36.
- George, B., Pandey, S. K., Steijn, B., Decramer, A., & Audenaert, M. (2021). Red tape, organizational performance, and employee outcomes: Meta-analysis, meta-regression, and research agenda. Public Administration Review, 81(4), 638–651.
- Puranam, P. (2018). The microstructure of organizations. Oxford University Press.
- Soda, G., & Zaheer, A. (2012). A network perspective on organizational architecture: Performance effects of the interplay of formal and informal organization. Strategic Management Journal, 33(6), 751–771.
