Most operational friction exists for a reason—and that reason is almost never a good one anymore.
You have a three-step approval workflow for expense reports. Why? Probably because in 1987, your company was smaller, and the CFO needed visibility into cash outflows. Then the company grew. The policy stayed. Someone added another step in 2003 because of a compliance change. Nobody removed the first step. Now you have a three-step process that takes six days and catches approximately zero fraud.
You have a data silo between sales and fulfillment. Why? Because they started as separate systems. They grew separately. Now sales doesn't know what's in inventory until fulfillment tells them. Fulfillment doesn't know what they just promised until sales escalates a problem. Information flows in one direction, with a lag, creating chaos that you've solved with personnel—an operations coordinator whose entire job is bridging a gap that shouldn't exist.
You have a manual reconciliation process that two accountants spend 40 hours on every month. Why? Because the systems that generate the data don't talk to the systems that consume it. That's been true for four years. You've hired consultants. They've recommended integrations. You've evaluated solutions. The problem is still there. And now nobody even questions it anymore. It's just "how we do things."
This is friction becoming business model. Not by design. By inertia.
Friction Hides Inefficiency
Here's what makes this insidious: friction hides inefficiency so completely that you stop seeing it as a problem.
You've adapted around the friction. Your team knows the workarounds. Your processes have evolved to accommodate the delays. The approval workflow is slow, so sales has learned to batch requests. The data silo is messy, so you've hired a coordinator. The reconciliation is manual, so you've scheduled it every quarter and everyone blocks the time.
These workarounds work. And because they work, the underlying friction becomes invisible. It's not a problem to fix—it's how things are done.
Except it's costing you millions.
A manufacturing company had a four-step approvals process for capital equipment purchases under $50,000. Finance, operations, safety, and executive sign-off. The process took an average of 34 days. The company was doing approximately 200 purchases per year under that threshold.
When we mapped it, that process was tied up 11,200 days of attention annually—from four different departments. Multiply by fully-loaded cost of that attention, and the process had an implicit cost of $1.84 million annually. In salary time spent on approvals.
And here's the kicker: the process was designed to catch fraud. The company had zero purchase-order fraud in their 15-year history.
They'd built a $1.84 million fraud-prevention system for a fraud rate that had never exceeded zero.
When they implemented agentic review—which applied consistent rules, caught the actual edge cases that might matter, and escalated genuine risks to humans—the approval cycle compressed to 3.2 days. Same rigor. 91% less time.
Friction Compounds Through Your Organization
The real cost of friction isn't local. It's compound.
One slow approval process creates a bottleneck. The bottleneck creates backlog. The backlog creates delay downstream. The delay creates risk. The risk requires mitigation—maybe you hire someone to manage the queue, or you build a workaround, or you add a software layer to track things that the process should have tracked automatically.
Each layer makes the original friction harder to see and harder to fix. You've optimized around it. Now fixing it would disrupt everything that depends on it.
A financial services firm had a customer onboarding process that took 18 days. It should have taken 4. The extra 14 days came from scattered friction points: document collection required email and manual organizing (2 days), compliance review was a manual checklist (2 days), risk scoring pulled from three different systems manually (1.5 days), account setup required separate entries in credit, product, and customer profile systems (1 day, three different people), verification required a phone call scheduled around availability (1 day), and final sign-off took another half day.
Total: 18 days. Twelve separate handoff points. One bad email and the entire process stalls.
They'd hired a customer success person whose entire job was herding this process forward—following up when things got stuck, escalating when timelines slipped, problem-solving around bottlenecks. Her salary was $85,000 per year.
When they automated the friction—document collection through agentic intake, compliance review through rules, risk scoring through integrated data pull, account setup through orchestrated system APIs, verification through background checks API—the process became 4 days. Automated end-to-end.
They didn't reduce headcount, but they redirected 60% of that person's time from friction management to customer success strategy. Value went up. Cost didn't.
The Friction Audit
Most organizations have never actually mapped their friction. You know where the big delays are, but you don't have a systematic inventory of where time is actually being spent.
Here's how to audit your friction:
Identify the slow processes. These are your candidates. Anything that takes longer than it should. Approvals. Onboarding. Claims processing. Data transitions. Customer handoffs.
Map the actual steps. Not the documented process. The real process, including the workarounds, the back-and-forth, the informal conversations that make things move.
Quantify the human time. How many people touch it? How long does each person spend? What's the fully-loaded cost of that time?
Identify the friction points. Where do things slow down? Where do humans wait? Where is information not available? Where do systems not talk to each other? Where do humans have to re-enter data?
Assess the root cause. Is this friction from genuine business logic (we need multiple perspectives)? Or is it from technical constraints (systems don't integrate)? Or is it from historical accident (we've always done it this way)?
Calculate the cost of friction. Not just the direct cost, but the ripple effects. Does this process create bottlenecks downstream? Does it require mitigation—extra hires, duplicate systems, workarounds? Those costs count too.
The ROI of Removing Friction
Here's what most organizations discover when they do this audit: their biggest opportunities aren't about automating complex work. They're about removing friction that shouldn't exist.
Removing friction is high-ROI because the upside is immediate and measurable. If the process takes 18 days and should take 4 days, removing friction cuts 14 days. You can measure that. You can quantify the impact on customer experience, operational efficiency, everything downstream.
It's low-risk. You're not replacing judgment. You're removing unnecessary steps. The downside is minimal—you stop doing something you shouldn't have been doing in the first place.
It compounds. A 14-day reduction in a 400-customer annual process isn't just 5,600 days of time saved. It's improved cash flow. It's customers who deploy faster, who are happier, who are less likely to churn.
It makes space for judgment. Once you remove the friction, the humans working on the process can focus on edge cases, complex situations, relationships—the work that actually requires human intelligence.
Where To Start
Most organizations have 3-5 processes that account for 50% of their operational friction. These are your candidates: multi-step approvals that could be rule-based, data entry that gets re-entered elsewhere, manual reconciliation between systems, customer onboarding sequences with excessive handoffs, claims processing or fulfillment with multiple review cycles, and reporting that requires manual data gathering.
Pick one. Map it. Quantify the friction. Build a business case around removing it. Automate the boring parts. Keep the judgment. Measure the result.
Your competitors probably have the same friction. The difference is whether you see it clearly enough to fix it.