If you haven't read article one The Hidden Cost of Operational Drag, in the Operational Drag series, you'll want to start there.
Operational drag is the gap between how fast your people work and how fast your business moves.
More precisely, operational drag is the accumulated friction of small inefficiencies—duplicate data entry, information searching, status meetings, slow approvals, tool switching—that consumes employee time and delays decisions without ever appearing on a financial statement.
It is not a failure. That distinction matters more than it sounds, and it's why most companies never fix it. Failures trip alarms. A crashed system, a missed shipment, a blown deadline—these get escalated, root-caused, and resolved. Drag trips nothing. It gets absorbed, normalized, and eventually mistaken for the nature of work itself.
The Defining Characteristics
Operational drag has four properties that separate it from ordinary inefficiency:
It's distributed. Drag almost never lives in one broken system or one bad process. It lives in the seams between systems and processes—the handoff from email to CRM, the gap between what the dashboard shows and what the meeting is called to clarify, the approval that sits in an inbox because no one owns its urgency. Because no single seam is anyone's responsibility, no one is accountable for the sum.
It's individually trivial. Each instance is too small to complain about. Re-entering a customer record takes ninety seconds. Pinging a colleague for a status update takes thirty. Finding the current version of the proposal takes four minutes. Nobody escalates a four-minute problem. But these events happen dozens of times per day, per person, across the organization—and together they become enormous.
It's invisible to leadership. Drag doesn't appear on dashboards because dashboards measure outputs, not friction. It doesn't appear on the P&L because payroll doesn't distinguish between an hour of skilled work and an hour of chasing approvals. Leadership experiences drag only indirectly: initiatives take longer than they should, decisions stall, and everyone seems maxed out despite headcount growth.
It compounds. The standard organizational response to slowness—another tool, another report, another oversight layer—adds coordination surface area. Each new system is one more place information must be updated, checked, and reconciled. Complexity layered on itself doesn't reduce friction; it institutionalizes it. This is why drag grows in successful, growing companies faster than almost anywhere else.
What Operational Drag Looks Like Day to Day
If you want to see operational drag in your organization, look for these patterns:
-
The same information entered more than once. A customer request arrives by email, gets entered into the CRM, copied into the project tracker, discussed in a standup, and summarized in a weekly report. Five touches. One unit of information.
-
Meetings that exist to transfer status. If the primary output of a recurring meeting is "everyone now knows where things stand," the meeting is compensating for a visibility problem somewhere else.
-
Approvals measured in days, judgment measured in minutes. The gap between how long an approval takes and how long the actual decision requires is pure drag.
-
The search tax. Employees search across email, chat, shared drives, and project tools for a document, a decision, or a thread they know exists. Research puts this at nearly an hour per day for the average knowledge worker.
-
Shadow workarounds. Private spreadsheets, side channels, and personal AI tools that employees maintain because the unofficial path is faster than the official one. Workarounds are your workforce's map of where the drag is—they've already found the friction and routed around it.
-
Busy All the Time. Moving Nowhere. Everyone is at capacity; the roadmap barely moves. When employees spend more time managing work than performing it, drag has taken hold.
What It Costs
Asana's Anatomy of Work Index, based on surveys of more than 10,000 knowledge workers, found that roughly 60% of the average workday goes to "work about work"—communicating about work, searching for information, switching between apps, managing shifting priorities, and chasing status—rather than the skilled or strategic work people were hired to do. Skilled work gets what's left. Strategy gets the leftovers.
Harvard Business Review research found the average digital worker toggles between applications nearly 1,200 times per day and spends about four hours per week simply reorienting after switches—roughly five working weeks per year lost to context changes alone. A joint Qatalog and Cornell study measured the recovery cost of each toggle at about 9.5 minutes to regain productive flow, and University of California, Irvine research puts full refocus after an interruption at around 23 minutes.
Run the numbers on even a mid-sized team and they stop being abstract. A 50-person company where drag consumes even half those losses is losing the equivalent of 10 to 15 full-time employees—headcount that shows up in payroll but not in output.
And the cost isn't only time. Drag also slows decisions (information arrives late or gets stuck), consistency (three people handle the same request three ways), and morale (few things burn people out faster than working hard on things that don't matter). Asana's research found the majority of workers report time-sensitive projects falling through the cracks because of task volume, not task difficulty.
What Operational Drag Is Not
The easiest way to define a term is to define what it isn't.
It's not laziness or underperformance. Drag afflicts hardworking teams most visibly—that's the paradox that makes it worth naming. The people experiencing the most drag are usually the most conscientious, because they're the ones dutifully updating every system and attending every status meeting.
It's not a technology deficit. Companies with the largest tool stacks often have the most drag, because every tool boundary is a seam where information must be manually carried across. Buying software to fix drag often adds another seam.
It's not the same as a bottleneck. A bottleneck is a single constraint that limits throughput; you can point at it. Drag is distributed friction across the whole system. Bottlenecks respond to targeted fixes. Drag responds only to deliberate operational design—mapping the friction, then removing, simplifying, and standardizing before automating anything.
It's not solved by AI—at least not first. This is one of the defining mistakes of the current moment. MIT research on enterprise AI found the overwhelming majority of pilots deliver no measurable financial return, largely because the technology gets pointed at processes nobody has mapped or simplified. Automating a slow process doesn't remove the drag. It accelerates it. AI belongs at the end of the fix, not the beginning.
The First Step: Make It Visible
Because operational drag is invisible by nature, the fix begins with deliberate diagnosis—an audit that maps where work slows down, where information gets stuck, and where skilled people repeatedly spend time on low-value tasks. The output isn't a tool recommendation; it's a friction map, ranked by cost and fixability.
Only with that map in hand does the question every leadership team is currently asking—where should we deploy AI?—become answerable. The friction points are the answer. They always were.
Download the Operational Drag Audit Checklist →
FAQ
What is operational drag in simple terms?Operational drag is all the small, invisible friction—duplicate data entry, searching for information, status meetings, slow approvals—that makes a business slower than the effort its people put in. It's the gap between how fast your people work and how fast your business moves.
What causes operational drag?Drag accumulates in the seams between systems, teams, and processes: handoffs that require re-entering information, tools that don't share data, approvals without owners, and coordination layered on top of coordination. Growth and new tools tend to increase it because each addition creates new seams.
How is operational drag different from inefficiency?Ordinary inefficiency is usually visible and localized—a slow machine or an understaffed team. Operational drag is distributed, individually trivial, and invisible on dashboards, which is why it persists in otherwise well-run companies.
How much does operational drag cost?Research from Asana across more than 10,000 knowledge workers found roughly 60% of the workday goes to coordination overhead rather than skilled work, and Harvard Business Review found workers lose about four hours per week simply reorienting between apps—roughly five working weeks per year, per employee.
Why is my team busy but nothing gets done?It's one of the clearest symptoms of operational drag. When skilled employees spend more time coordinating work than performing it, activity increases while strategic progress slows.
Can AI fix operational drag?Not by itself, and not first. AI applied to an unmapped, unsimplified process accelerates the drag rather than removing it. The sequence that works is: Remove. Simplify. Standardize. Automate.