Organisational friction: why positive conflict leads to successful business outcomes

Friction is often treated as one organisational defect: remove steps, resolve disagreement and make work feel smooth. That combines two very different conditions.

Some friction drains capacity without improving a decision. Other friction slows a team just enough to expose a weak assumption, conflicting duty or better option. Remove the first. Protect the second.

The distinction matters in digital work because a fast path from senior request to delivery can look efficient until clients, practitioners or specialists reveal what the request missed.

Identify draining friction

Draining friction adds effort without proportionate value. Examples include repeated data entry, unclear ownership, duplicated approval, inaccessible tools, standing meetings with no decisions and processes retained after the risk that created them has changed.

Do not label a control waste simply because it causes delay. Establish its purpose, authority, consequence and evidence. A security, regulatory or quality check may be essential and badly designed. The response is to make the control effective and usable, rather than remove it for speed.

Map an important task end to end. Record work time, wait, handoffs, rework, exceptions and decision authority. Ask the people doing it which steps protect value and which exist through habit. Validate their account with service and risk evidence.

Look for friction that transfers cost. A faster front-end process may create manual correction backstage. Removing a client question may increase professional risk. Improvement needs a whole-service view.

Recognise productive conflict

Productive friction is disagreement directed at the work. Somebody questions the deadline, challenges the evidence, presents an alternative or explains an impact the dominant group has missed.

It is useful when:

• the question is consequential;
• participants have relevant knowledge;
• evidence and assumptions are visible;
• people can disagree without personal penalty;
• somebody has authority to decide;
• the decision and dissent are recorded;
• the conversation ends in action or further evidence.

Conflict without these conditions can become politics, repetition or personal attack. Volume and seniority then determine the result rather than the quality of the argument.

Positive conflict does not require performative intensity. A considered written objection can be more useful than a heated meeting. Design several routes for challenge.

Understand why difficult information disappears

People adjust what they say to the likely consequence. If a realistic estimate is repeatedly punished while an optimistic estimate receives approval, planning will fill with optimism. The team may remain privately unsurprised when delivery slips.

This is not solved by asking everybody to be courageous. Leaders need to change the conditions around truth-telling.

Ask for a range, assumptions and confidence rather than one date. Separate estimation from commitment. Reward early risk disclosure through constructive response. Avoid using a red status as evidence of personal failure.

Senior leaders should state their view after asking for contrary evidence where practical. If the sponsor opens with a preferred answer, less powerful participants will interpret “challenge welcome” through that signal.

Watch whose disagreement is treated as expertise and whose is treated as attitude. Psychological safety must extend across role, discipline, location and personal characteristics.

Build challenge into decisions

Do not rely on an unusually confident person to raise the issue. Create a decision method.

For material choices, circulate a short paper stating the question, options, recommendation, evidence, assumptions, risks and latest safe decision date. Ask a named person or discipline to test the recommendation from a relevant perspective.

Useful techniques include:

• a premortem exploring how the decision could fail;
• independent technical or professional assurance;
• red-team review for security or high-consequence assumptions;
• user testing that lets behaviour challenge internal opinion;
• written input before a senior meeting;
• reversible pilots with success and stop conditions;
• a decision log preserving dissent and review triggers.

Choose the method in proportion to consequence. Requiring an adversarial review for every small content change creates the draining friction the organisation is trying to remove.

Give conflict a boundary

Endless debate is not better governance. Define what evidence is needed, who decides and when. Once the accountable person makes a reasoned decision within authority, the team should implement it while monitoring named risks.

Record material dissent because it may contain the condition that later triggers review. The record should support learning, not build a case against the person who challenged.

Reopen a decision when new evidence, a failed assumption or a pre-agreed threshold appears. Do not relitigate it merely because somebody remains unhappy.

Leaders must also intervene when behaviour becomes personal, discriminatory or unsafe. “Positive conflict” should never be used to excuse aggression or ignore unequal power.

Slow down where correction is expensive

Speed has value when it shortens learning and delivery. It destroys value when it removes the time needed to understand an irreversible or high-consequence choice.

Match pace to reversibility. A prototype can move quickly when no client relies on it and data is controlled. A production migration, automated professional decision or major supplier commitment deserves deeper assurance.

Sustained overload reduces capacity for challenge and thoughtful review. Plans should include the work of testing, documentation, recovery and decision-making. Treating these as optional overhead converts apparent speed into later defects and technical debt.

Rest and manageable work in progress are delivery conditions as well as wellbeing concerns. Avoid making a universal claim that longer hours always reduce productivity; measure the actual quality, throughput and rework in context.

Remove obsolete friction safely

Create an owner for each material process and a route to challenge it. Review the purpose, evidence, users and failure consequences. Test a simpler path with controls and rollback.

Remove duplicated decisions while keeping necessary perspectives. Automate a rule only after its exceptions and accountability are understood. Retire old forms, meetings and reports when the replacement is working, so the organisation does not operate both indefinitely.

Measure total task time, wait, error, rework, accessibility, risk and user effort. A local efficiency gain may conceal a worse service elsewhere.

Examine the culture through evidence

Ask when a material recommendation was last changed because somebody challenged it. Examine decision records, estimate ranges, risk timing and whether the same small group dominates discussion.

Interview people who participate less. Silence may mean agreement, lack of relevant knowledge, fatigue, fear or an inaccessible format. Do not diagnose culture from one meeting.

Distinction’s value “be reasonably unreasonable” expresses a willingness to challenge while remaining responsible for evidence and relationships. The word “reasonably” matters: challenge should sharpen the work and help a decision, not reward provocation for its own sake.

The practical goal is an organisation where unnecessary effort is questioned and necessary disagreement is usable. If nobody can remember a consequential challenge reaching a senior decision, leaders should investigate whether the smooth surface is hiding risk.

Distinction can help map where delivery friction drains capacity and where governance needs stronger challenge. A first conversation should identify the decision or service at issue, rather than promise that more conflict is inherently better.