Managing Friction: Removing the Hidden Barriers to Organizational Performance

🧭 Dojo Compass

Module: Entrepreneurship, Market Execution and Scaling

Focus Area: Operations and Supply Chains

Key Article Point

Strong organizations do not merely manage conflict. They manage friction.

Conflict is visible. It attracts attention, generates meetings, and often triggers formal intervention. Friction is different. It is quieter, more persistent, and often far more pervasive.

A project waits three days for an approval. An employee does not know who has authority to make a decision. A sales proposal moves back and forth between departments because expectations were never clear. A customer invoice requires three additional approvals. Two teams have different priorities and therefore continually slow each other down.

None of these situations may constitute a serious conflict. Yet together, they can consume enormous amounts of organizational time and energy.

For SMEs in particular, this matters. A large company may be able to absorb some organizational friction because it has excess personnel, financial resources, and administrative capacity. A small company usually cannot. When ten people spend an extra hour navigating an unnecessary process, the opportunity cost can be significant.

The objective, therefore, should not be to eliminate friction entirely. Some friction is valuable. The objective is to distinguish productive friction from unnecessary friction and systematically reduce the latter.

🎯 The Challenge

Friction is any recurring feature of organizational interaction that makes it more difficult, slower, or more expensive to accomplish an otherwise legitimate objective.

It can arise from many sources:

• Channeling problems — ideas or projects have difficulty reaching the appropriate decision-maker.
• Communication delays — information does not move quickly enough between people or departments.
• Unclear decision rights — employees do not know who has authority to decide.
• Rework — work must be repeated because expectations were ambiguous.
• Excessive processes — completing a relatively simple task requires unnecessary steps.
• Different priorities — departments optimize for different objectives.
• Competing incentives — one department benefits from behavior that creates costs elsewhere.
• Personality differences — individuals have different working styles that create recurring but manageable difficulties.

The important point is that friction does not necessarily result from bad people.

A highly competent sales team and highly competent legal team can create friction simply because their objectives differ. Sales wants to close a transaction quickly. Legal wants to reduce legal risk. Both objectives may be legitimate.

The problem arises when the organization has no effective mechanism for reconciling these objectives.

🥋 Dojo Solution

The first step in managing friction is to recognize it as an organizational phenomenon rather than as an occasional interpersonal problem.

If an employee repeatedly has difficulty obtaining approval from another department, the natural reaction may be to focus on the individuals involved.

But a better question is:

Why does this interaction repeatedly produce this result?

Perhaps the approval authority is unclear. Perhaps the information required for approval is not standardized. Perhaps the person responsible for approval has too many other responsibilities. Perhaps the technology system makes the process unnecessarily complicated.

The distinction matters.

If friction is treated as an individual problem, the organization may attempt to correct individual behavior.

If friction is treated as a system problem, the organization can redesign the system.

This does not mean individuals are never responsible. It means that recurring friction should first be investigated as a pattern.

1. Map the Sources of Friction

Organizations should periodically identify where friction occurs.

This can be done through relatively simple questions:

Where do projects slow down?

Where do employees repeatedly have to ask for clarification?

Where does work frequently return to an earlier stage?

Where do decisions remain unresolved?

Where do departments regularly complain about one another?

Where do customers experience unnecessary delays?

These questions can reveal friction that may otherwise remain invisible.

One useful approach is to map important organizational processes from beginning to end.

Consider a sales transaction:

Lead → Qualification → Proposal → Legal Review → Negotiation → Approval → Contract → Invoice → Payment.

At each stage, ask:

• Who owns the process?
• Who must provide information?
• Who makes the decision?
• How long does the stage normally take?
• What causes delays?
• How often is work sent backward?
• What happens when something goes wrong?

The objective is not to create bureaucracy around process analysis. It is to identify where the organization is losing time and energy.

2. Measure Friction

Once friction has been identified, it should be quantified whenever reasonably possible.

Measurement changes the discussion.

Instead of saying:

“Legal takes too long to review contracts.”

the organization can ask:

“What is the average time from submission of a contract to legal approval?”

Instead of:

“Management takes forever to make decisions.”

ask:

“How many days does it take, on average, to resolve a decision requiring executive approval?”

Potential measures might include:

• Average contract review time
• Average project approval time
• Average invoice-processing time
• Number of times work is returned for revision
• Number of days required to resolve internal questions
• Number of approvals required for common activities
• Average customer response time
• Percentage of projects delayed by internal dependencies

The objective is not measurement for its own sake.

The objective is to establish a friction baseline.

Once the baseline exists, the organization can determine whether interventions are actually working.

3. Separate Productive Friction from Wasteful Friction

Not all friction should be removed.

A company with no friction whatsoever could be a company with no controls.

A legal review may slow a transaction, but it may prevent a major liability. A financial approval may delay spending, but it may prevent waste. A technical review may create additional work, but it may prevent a product failure.

This suggests an important distinction:

Productive friction

Friction that produces a benefit greater than its cost.

Examples include:

• Quality-control checks
• Financial controls
• Safety reviews
• Legal review of material risks
• Strategic debate before major decisions

Wasteful friction

Friction that consumes resources without producing a proportionate benefit.

Examples include:

• Multiple approvals that add little additional scrutiny
• Repeated requests for information already available
• Meetings held because nobody knows who can make a decision
• Rework caused by unclear instructions
• Manual processes that could easily be automated
• Departments optimizing their own objectives at the expense of the company

The goal is therefore not zero friction.

It is optimal friction.

4. Clarify Decision Rights

One of the most common sources of organizational friction is uncertainty regarding who can decide.

When decision rights are unclear, several things can happen.

Employees may delay decisions because they fear exceeding their authority. Others may seek approval unnecessarily. Multiple people may become involved in decisions that require only one person. Alternatively, nobody may act because everyone assumes someone else has responsibility.

A simple decision-rights framework can dramatically reduce this problem.

For recurring decisions, organizations should identify:

Who recommends?

Who decides?

Who must be consulted?

Who must be informed?

The level of formality should depend on the size and complexity of the organization. An SME may not need a sophisticated governance system. It may simply need clear agreement regarding who has authority to make particular types of decisions.

Clarity itself is a friction-reduction tool.

5. Design Better Interfaces Between Departments

Friction frequently occurs not within departments but between them.

Sales and legal. Finance and operations. Product and marketing. Management and employees.

Each department may operate effectively in isolation while the interface between them performs poorly.

This suggests that organizational design should pay particular attention to interfaces.

For example, instead of simply telling sales and legal teams to “work together better,” the company might establish a standard process:

1. Sales provides a defined package of information.
2. Legal reviews against predetermined risk categories.
3. Standard terms are approved automatically.
4. Only exceptions require additional legal review.
5. Material deviations are escalated to a designated decision-maker.

The result is not merely better cooperation.

It is a better system of cooperation.

6. Create Friction-Reduction Incentives

Organizations sometimes unintentionally reward friction.

A department may be measured on its own risk reduction, regardless of the effect its processes have on the rest of the organization.

A finance team may be rewarded for controlling spending without considering whether excessive controls slow revenue generation. A legal team may be rewarded for identifying risks without considering whether its approach makes transactions commercially impractical.

The solution is to introduce incentives around organizational outcomes.

Suppose a company reduces the average time required to close a transaction from thirty days to fifteen days while maintaining appropriate legal and commercial protections.

The resulting improvement in cash flow and revenue generation is an organizational achievement.

It should therefore be possible for friction reduction to become part of performance objectives or bonus considerations.

This creates a powerful message:

The organization rewards not only doing one’s job, but making it easier for the organization to do its job.

7. Build a Friction Review Into Organizational Management

Friction should be monitored continuously rather than addressed only when it becomes severe.

A quarterly or semiannual friction review could ask:

• Where are our biggest recurring delays?
• Which processes generate the most rework?
• Where are decision rights unclear?
• Which interfaces between departments are creating problems?
• What friction have we removed?
• What new friction has emerged?
• Which friction is productive and should remain?
• Which friction should be redesigned?

This does not need to become another large corporate meeting.

For an SME, a short review of five or ten important organizational processes may be enough.

The key is persistence.

Friction tends to return because companies evolve. New employees join. New technologies are introduced. New customers create new requirements. New regulations appear. A process that worked when a company had ten employees may become inefficient when it has fifty.

Organizational friction is therefore dynamic.

⚙️ The Framework

🏗️ Putting It Into Practice

SMEs can establish a simple five-stage cycle:

1. Identify
Find recurring points where work becomes unnecessarily difficult or slow.

2. Measure
Establish a baseline for the time, cost, rework, or effort involved.

3. Diagnose
Determine whether the source is structural, technological, procedural, interpersonal, incentive-based, or some combination.

4. Redesign
Change the process, clarify authority, improve the interface, automate the task, or otherwise address the underlying cause.

5. Monitor
Measure the result and determine whether the change actually reduced friction without eliminating valuable controls.

This turns friction management from an informal complaint mechanism into an organizational capability.

📌 Key Takeaways

1. Conflict and friction are different. Conflict is often visible; friction is usually more pervasive.
2. Recurring friction is usually a system issue as well as a people issue.
3. Measure friction wherever possible. Time, delays and rework can often be quantified.
4. Do not eliminate productive friction. Controls, review and debate can create significant value.
5. Focus particularly on organizational interfaces. Many problems occur between departments rather than within them.
6. Clarify decision rights. Uncertainty about authority creates substantial organizational drag.
7. Align incentives with enterprise-wide outcomes. Reducing friction should create value for the people who help reduce it.
8. Review friction continuously. Organizational processes that work today may become inefficient tomorrow.

🌿 Reflection

A company can lose enormous amounts of value without experiencing a single major conflict.

A project can simply take too long. A customer can wait too long. An employee can spend an afternoon obtaining an approval that should have taken five minutes. A decision can remain unresolved while an opportunity disappears.

None of these events may look dramatic individually.

Together, however, they create organizational drag.

The most effective organizations are therefore not those in which every interaction is perfectly smooth. They are organizations that understand where friction is useful, where it is unavoidable, and where it is simply waste.

The objective is not to build a frictionless organization.

It is to build an organization in which every meaningful source of friction earns its place.

⚔️ Dojo Mission

Choose one important process in your company this week.

Map it from beginning to end.

Identify where it slows down, where work is repeated, where authority is unclear and where people must expend unnecessary effort.

Measure the biggest source of friction.

Then remove one unnecessary obstacle.

Do not attempt to redesign the entire organization.

Find one source of friction. Remove it. Measure the result. Then move to the next one.

Over time, small reductions in organizational friction can compound into a significant increase in speed, capacity and competitive performance.