Insights
The Operational Friction Score™
The suppression fix took eleven minutes.
Finding the right tab took thirty-four.
Explaining the same context to a second operator took eighteen.
The work was straightforward.
The path to the work was not.
The Problem
Most organizations know they have inefficiencies.
Very few can measure them.
Operational friction is the drag between knowing what to do and doing it. It hides in handoffs, duplicate tabs, unclear ownership, and approval chains that add steps without adding clarity.
Teams feel busy without feeling effective.
Headcount increases while throughput stays flat.
Leadership sees activity without seeing acceleration.
The Operational Friction Score™ is a framework for identifying and quantifying that drag. Five categories. One diagnostic lens. Repeatable across workflows, teams, and quarters.
Use it to find where work gets harder than it should before buying another tool or hiring another operator.
Most organizations dramatically underestimate how much time friction consumes.
Why Friction Stays Invisible
Major problems get attention.
Small daily drag does not.
Each friction event feels minor in isolation.
Searching for a file. Updating a spreadsheet. Waiting on approval. Rebuilding context after a context switch.
Repeated across operators, SKUs, and weeks, friction compounds into a hidden tax on execution.
See The Cost of Operational Friction.
Teams often respond by adding people instead of removing drag.
That trade rarely scales.
See Why Operational Complexity Grows Faster Than Revenue.
Friction also hides behind heroics.
Strong operators compensate for broken workflows.
Leadership interprets compensation as capacity.
The underlying drag never gets scored.
When those operators leave, the drag reappears as a crisis.
That is not a talent problem.
It is a friction problem that was never measured.
The Operational Friction Score Framework
The framework scores friction across five categories.
Each category has a distinct signature.
Score each category from 1 (minimal drag) to 5 (severe drag) per workflow.
Multiply by frequency and operator count to estimate organizational cost.
Category 1: Information Friction
↓
Category 2: Workflow Friction
↓
Category 3: Decision Friction
↓
Category 4: System Friction
↓
Category 5: Ownership Friction
High scores in multiple categories usually indicate a workflow stuck below Level 3 on the Workflow Maturity Model™.
Low scores across categories with poor outcomes usually indicate a visibility or prioritization gap, not a friction gap.
See The Visibility-to-Execution Model™.
Category 1: Information Friction
Definition
Information friction is drag caused by missing, scattered, stale, or conflicting data required to do the work.
Symptoms
Operators search across multiple spreadsheets before acting.
Two teams maintain different versions of the same metric.
Status lives in Slack threads instead of a shared record.
Reporting requires manual reconciliation between systems.
Business impact
Time shifts from execution to information hunting.
Decisions delay while someone finds the right file.
Errors increase when operators act on stale numbers.
Revenue issues stay open while teams debate which tab is correct.
See The Hidden Cost of Spreadsheet-Based Operations.
Common causes
Spreadsheet sprawl without a source of truth.
Exports pasted into email instead of linked systems.
Metrics defined differently by channel or team.
No named owner for data freshness.
Information friction is often the first category to score high in marketplace operations.
Catalog, inventory, pricing, and case data rarely live in one place without intentional design.
Category 2: Workflow Friction
Definition
Workflow friction is drag caused by unnecessary steps, duplicate work, or broken handoffs in the path from trigger to completion.
Symptoms
The same update happens in three systems.
Operators copy data from one tool to another daily.
Handoffs require meetings instead of structured queues.
Work restarts when someone returns from PTO because context was not captured.
Business impact
Throughput drops while headcount rises.
Quality varies by operator because the path is not consistent.
Volume spikes create backlog faster than resolution capacity.
Automation attempts fail because the underlying path was never simplified.
See Context Switching Kills Operational Productivity.
Common causes
Legacy processes built for smaller catalogs.
Duplicate workflows across channels without shared logic.
Approval chains added after one mistake, never reviewed.
Tools purchased to patch steps instead of redesigning the path.
Workflow friction often appears as duplicate work.
The same suppression checked in Seller Central, a spreadsheet, and a case tool.
Each check feels small.
Across fifty ASINs daily, duplicate work becomes a full-time job disguised as operations.
Category 3: Decision Friction
Definition
Decision friction is drag caused by unclear criteria, missing authority, or too many decision points for routine work.
Symptoms
Standups re-debate the same priority order daily.
Operators escalate routine fixes because criteria are unclear.
Similar issues get different treatment depending on who is on shift.
Leadership meetings exist primarily to decide what should already be ranked.
Business impact
High-impact work waits while low-impact work gets attention.
Operator confidence drops when every decision feels political.
Resolution speed varies by escalation path, not by revenue impact.
See The Revenue-at-Risk Framework™.
Common causes
No explicit prioritization layers.
Decision rights undefined by issue type.
Metrics that describe activity instead of impact.
Fear of wrong prioritization leading to over-approval.
Decision friction connects directly to prioritization failure.
See Why Most Marketplace Teams Prioritize Work Incorrectly.
Scoring decision friction often reveals that the team does not lack effort.
It lacks a sort order.
Category 4: System Friction
Definition
System friction is drag caused by tools that slow work instead of accelerating it.
Slow loads, broken integrations, fragmented UIs, and reporting delays all qualify.
Symptoms
Operators maintain shadow spreadsheets because the official tool is unreliable.
Integrations break silently and exports become the workaround.
Reports arrive too late to drive daily action.
Login and navigation overhead consumes measurable minutes per task.
Business impact
Software investment produces activity without outcomes.
Teams distrust data from official systems and rebuild parallel processes.
Detection delays because alerts are noisy or late.
Execution delays because the tool fights the operator.
See Reporting vs Operational Intelligence.
Common causes
Tools selected for features instead of workflow fit.
Integrations treated as one-time projects instead of owned systems.
Dashboards built without connection to queues and ownership.
Reporting treated as a batch job instead of an operational input.
System friction is not the same as missing software.
Often the organization has tools.
The tools do not connect visibility to action.
See The Xylem Operational Intelligence Framework.
Category 5: Ownership Friction
Definition
Ownership friction is drag caused by unclear responsibility for detection, prioritization, resolution, or prevention.
Symptoms
Issues visible on a dashboard with no named owner.
Work bounces between teams with no resolution.
Preventive fixes never happen because nobody owns recurrence.
Escalation is the only path to assignment.
Business impact
Problems age in visible queues.
Repeat issues consume the same resolution capacity monthly.
Cross-functional work stalls at handoff boundaries.
Operator morale drops when effort does not connect to closure.
See Why Ownership Breaks Before Process.
Common causes
RACI documents that do not match daily reality.
Shared queues without individual accountability.
Ownership defined by org chart instead of workflow stage.
Prevention treated as optional when volume is high.
Ownership friction often explains why detection exists without resolution.
See The Detection → Prioritization → Resolution Framework™.
If work feels harder than it should, friction is usually hiding somewhere in the process.
Scoring in Practice
Pick one high-volume workflow this week.
Case management. Suppressions. Inventory exceptions. Weekly reporting.
For each of the five categories, score 1 to 5 based on operator interviews and time observation.
Document evidence.
A score without evidence is opinion.
Evidence without scoring is anecdote.
Combine both.
Example: Listing suppression workflow
Information friction (4): Suppression status checked in Seller Central, internal tracker, and Slack.
Workflow friction (4): Same ASIN updated in case tool and spreadsheet.
Decision friction (3): Priority debated daily without revenue-at-risk sort.
System friction (3): Alert email noisy; true suppressions buried.
Ownership friction (4): No named owner per open suppression row.
Total friction profile: high information, workflow, and ownership drag.
Investment order: define owner and source of truth before automation.
That sequence matches the framework principle.
Remove friction before adding capability.
Example: Weekly operational reporting
Information friction (5): Data pulled manually from five sources.
Workflow friction (5): Same report rebuilt with copy-paste steps.
Decision friction (2): Report consumed but rarely drives same-day action.
System friction (4): BI tool refresh delays push reporting to weekends.
Ownership friction (3): Report owner clear; action owners unclear.
Highest drag is information and workflow.
Fix: single source metrics and automated pull before new dashboard features.
See Most Dashboards Should Be Alert Systems.
Connecting scores to investment
High information friction: invest in source of truth and data ownership.
High workflow friction: simplify path and remove duplicate steps.
High decision friction: implement prioritization layers.
High system friction: fix integrations and queue connection before new tools.
High ownership friction: assign named owners per workflow stage.
Do not automate a workflow scoring 4 or 5 in workflow friction.
Automation encodes the broken path.
See The Journey From Prompt to Process to Software (And Why Most Teams Stop Too Early).
Friction Across Marketplace Operations
The framework applies across common ecommerce operational categories.
Spreadsheet sprawl
Usually scores high on information friction and workflow friction.
Symptoms include conflicting inventory numbers and manual catalog updates.
See Operational Problems Begin as Information Problems.
Reporting delays
Usually scores high on system friction and information friction.
Reports that arrive Friday cannot drive Monday action.
See The Visibility Gap.
Approval chains
Usually scores high on decision friction and workflow friction.
Extra approvers rarely prevent errors.
They often prevent speed.
Context switching
Usually scores high on workflow friction and system friction.
Operators lose minutes rebuilding mental model per switch.
Those minutes compound across a shift.
See Context Switching Kills Operational Productivity.
Missing ownership
Usually scores high on ownership friction and decision friction.
Visible problems with no owner age until escalation.
That pattern breaks the full lifecycle in the Detection → Prioritization → Resolution Framework.
From Score to Action
Friction scoring is not an annual audit.
It is a quarterly diagnostic per workflow.
Re-score after changes.
If scores drop and throughput rises, the investment worked.
If scores stay high after a tool purchase, the wrong category was treated.
Monthly leadership review question:
Which workflow carries the highest combined friction score multiplied by daily volume?
That workflow gets the next simplification sprint.
Not the loudest workflow.
The highest-drag workflow.
The best systems remove friction before adding automation.
Relationship to Other Xylem Frameworks
The Operational Friction Score complements frameworks that address adjacent problems.
Revenue-at-Risk Framework™
Sorts work by impact when decision friction is low enough to act.
See The Revenue-at-Risk Framework™.
Detection → Prioritization → Resolution Framework™
Maps lifecycle stages where ownership and system friction break execution.
See The Detection → Prioritization → Resolution Framework™.
Workflow Maturity Model™
Shows maturity stage where friction scoring should happen before software investment.
See The Workflow Maturity Model™.
Operational Debt Framework™
Explains why unscored friction compounds into debt over time.
See The Operational Debt Framework™.
When future Xylem content references friction, drag, duplicate work, or hidden operational cost, it refers back to these five categories.
Use this article as the canonical reference for measuring friction before building.
Conclusion
Most organizations know they have inefficiencies.
Very few can measure them.
The Operational Friction Score™ provides five categories:
Information Friction.
Workflow Friction.
Decision Friction.
System Friction.
Ownership Friction.
Score honestly per workflow.
Invest in the highest-drag categories first.
Remove friction before adding automation.
That is how operations stops feeling harder than it should.
Pick one workflow this week.
Score five categories.
Name the highest score.
Fix that category before buying another tool.
The framework proves itself when operators feel the path get shorter.
Measure that feeling with scores, not sentiment surveys.
That is how friction stops being invisible.
Reference this framework when evaluating headcount plans, software roadmaps, and process redesign.
Friction is measurable.
Measurement is the first step toward removal.
Start scoring.