Reflections on operational friction, risk, and how small inefficiencies quietly shape organizational exposure. There's a category of problems that never quite rises to the level of crisis.
Reflections on operational friction, risk, and how small inefficiencies quietly shape organizational exposure.
There's a category of problems that never quite rises to the level of crisis. The report that's always a little late. The workaround everyone uses but nobody owns.
These aren't emergencies. They're inconveniences.
Practitioner note: in live implementation work these sub-crisis problems are the ones clients apologise for raising, on the grounds that nothing has actually broken yet. That framing is precisely what allows them to persist.
They get absorbed into the rhythm of work, tolerated rather than addressed. People complain about them in the hallway, then go back to their desks and navigate around them.
But I've started paying closer attention to these small frictions. Not because they're urgent, but because of what they reveal. Each one is a signal. A place where the system and the work don't quite fit. A gap that someone is filling manually. A dependency that hasn't been examined.
Most of the time, these signals stay quiet. The friction is manageable. The workaround holds. But the signals don't go away. They accumulate. And they often point toward risks that will become much harder to manage later.
Across more than 600 NetSuite implementations delivered over 25 years, operational friction has proved a more reliable predictor of future incidents than any risk register we have been shown.
Operational friction is easy to dismiss because it doesn't announce itself. It's not a system failure. It's not a compliance breach. It's not a missed deadline, at least not yet. It's just extra effort, extra time, extra attention required to make things work.
But friction has a way of compounding. The manual step that takes an hour today will take longer as volume grows. The workaround that one person manages becomes a crisis when that person leaves. The data inconsistency that gets reconciled monthly becomes a material issue during an audit.
I've seen this pattern play out many times. The friction that everyone learned to live with eventually becomes the thing that breaks. Not because it got worse, but because the conditions around it changed. The organization grew. The regulatory environment tightened. A key person departed. Suddenly, the thing that was merely annoying became genuinely dangerous.
There's also a relationship between friction and fragility. The more workarounds you depend on, the more single points of failure you carry. The more manual steps in a process, the more opportunities for human error. The more reconciliation required, the longer it takes to know something is wrong. Each friction point adds a thread to the web of risk, and those threads are often invisible until one of them snaps.
Organizations often underestimate this accumulation because each individual friction seems small. But risk isn't just about individual probabilities. It's about the system as a whole. A dozen minor frictions can add up to a major vulnerability, especially when they're interconnected in ways nobody has mapped.
I wonder how different risk management would look if we paid more attention to operational friction. Not as a nuisance, but as a leading indicator. A way of seeing where the system is stressed before it fails.
The frictions are already there. People already know where they are. Ask anyone on the front lines what slows them down, what they wish worked better, what keeps them up at night. They'll tell you. The question is whether anyone is listening, and whether anyone is connecting those signals to the larger picture.
I wonder, too, about the cost of waiting. It's always easier to defer. There's always something more urgent. The friction is manageable today, so addressing it can wait until tomorrow. But tomorrow brings its own urgencies, and the friction remains. Until it doesn't.
There's a kind of strategic discipline in paying attention to small things. Not because they're the most important, but because they're often the most telling. The health of an operation shows up in the details. The gaps, the delays, the manual steps, the things that require heroic effort to work around. These are the seams. And seams are where things come apart.
Some organizations find value in periodically assessing their operational friction, not in response to a crisis, but in anticipation of one. To see where the effort is concentrating. To identify the dependencies that have grown quietly critical. To understand what today's inconveniences might become tomorrow's exposures.
That kind of assessment isn't about finding problems. It's about finding patterns. And patterns, once visible, can be addressed before they become emergencies.
The friction is already telling you something. The question is whether you're listening.
There's a category of problems that never quite rises to the level of crisis.
Operational friction is easy to dismiss because it doesn't announce itself.
I wonder how different risk management would look if we paid more attention to operational friction.
There's a category of problems that never quite rises to the level of crisis. The report that's always a little late. The workaround everyone uses but nobody owns.
Operational friction is easy to dismiss because it doesn't announce itself. It's not a missed deadline, at least not yet. It's just extra effort, extra time, extra attention required to make things work.
I wonder how different risk management would look if we paid more attention to operational friction. Not as a nuisance, but as a leading indicator. A way of seeing where the system is stressed before it fails.
These published sources cover the detail behind the points above:
Softype is an Oracle NetSuite solution provider with more than 25 years of experience and over 600 implementations. Our team sets NetSuite up around how your business already runs, then stays on to tune it as you grow. To see what that looks like for your own numbers, book a meeting with our team.
Document the workarounds rather than the complaints. A workaround constitutes demonstrable evidence that a process no longer performs according to its original specification, and it persists precisely because an individual has quietly absorbed the operational cost personally.
Subsequently establish how many colleagues depend upon each workaround. Friction affecting a single individual represents an inconvenience; friction that multiple colleagues have independently engineered around constitutes a structural deficiency in the underlying process.
Practitioner note: in live projects the workarounds nobody mentions are the informative ones, because they have been in place long enough to feel like the process itself.
Softype has delivered more than 600 NetSuite implementations over 25 years. If any of this describes your operation, book a meeting or contact us and we will talk it through.
Helping businesses thrive with integrated ERP solutions.
NetSuite
Service
Company
Contact Us
Copyright © 2026
