Underwriters don’t care whether friction is removed by a person, a process, or a platform. Here’s how to identify where it sits and what actually removes it in specialty insurance operations.

Underwriters don’t care whether friction is removed by a person, a process, or a platform. Here’s how to identify where it sits and what actually removes it in specialty insurance operations.
Most discussions about operational improvement in specialty insurance happen at the executive level. They focus on implementation timelines, platform capabilities, vendor evaluation, and the technology roadmap.
The people actually doing the work have a far simpler question.
Does that make my day any easier or any harder?
That question ultimately tells you whether any investment in people, process redesign, automation, or technology has delivered on its promise. A platform that scores very well in the demo but actually adds more steps to the underwriter's day isn't an improvement. A process change that reduces complexity for the leadership team but creates new friction on the desk doesn't solve the problem.
The measure of any operational investment is not whether it's been implemented. It's whether it's taken the friction out of the work that people do.
OIP Insurtech has spent 14 years mapping that friction inside specialty insurance operations. Here is what we have learned about where it lives and what actually removes it.
Workflow debt and operational inefficiency are 'leadership' concepts. The underwriters experience them in their own way.
Friction is the submission that arrives without the information to quote it (a broker call is required before anything else can happen). It is the document that has to be opened, read, and manually compared against three others before a decision can be made. It is the system that requires data to be rekeyed because it already exists somewhere else in a format the next system doesn't accept.
The compliance step gets pushed to the end of the day because there was no time earlier, and then it gets rushed at the end because there's no time then either. It has to go to a senior colleague because the process was never documented, and the answer lives in someone's head.
None of it is a line item. Tuesday is harder than it needs to be, Wednesday is the same, and the submission that should have taken an hour takes most of the afternoon.
This reality underpins every discussion about AI readiness, workflow efficiency, and technology spend. Before any of those discussions can be of real value, it's useful to clearly understand what the friction is and where it resides.
The article's most important reframing is also the simplest.
Underwriters don't care whether a person, a process, or a platform removes the friction. They just care that it is removed.
If the trained support person eliminates the 30 minutes of manual pre-processing per submission, that's a win. If redesigning the triage process means submissions arrive pre-sorted and pre-prioritized rather than in arrival order, that's a win. If automating document extraction means the underwriter opens a file that's already been extracted and is ready to review, that's a win.
The error most specialist insurers make is treating staffing, workflow redesign, and technology as mutually exclusive approaches. They aren't. They're all ways of dealing with different types of friction at different points in the workflow. The organizations that reduce friction most are the ones that match the right intervention to the right problem, rather than choosing one type of solution and applying it everywhere.
This is the key difference. It changes the way decisions are made. If you start with "we need to automate," you're going to look for automation. If you start with "where is our underwriting capacity being consumed by work that doesn't in any way require underwriting judgment," you're going to find the right answer. That answer may well be automation, or it may be staffing, or it may be process change, or it may be some combination of all three.
The starting point dictates the outcome.
Friction in specialty insurance operations centers on three intervention points. Each of these responds to a different type of solution.
Some friction is best dealt with by putting the right person in the right place in the workflow. Having trained underwriting support handle the administrative execution before the file reaches the underwriter means the underwriter opens something ready for a decision, rather than a file that still needs to go through the process.
Inspection review expertise,, which reads the report, identifies material findings, and writes the recommendation letter, means the underwriter reviews a conclusion rather than developing one from scratch. Account management support, which handles broker liaison and documentation, frees the underwriter to focus on risk assessment rather than account management.
The common thread is that skilled, expensive judgment is freed from work it doesn't need to do.
Some of the friction is a process issue. The workflow was designed for a smaller book, or perhaps never designed at all, and as the book has grown, so have the steps and workarounds that have built up at each stage.
Separating the speed work from the judgment work at intake is what makes the difference in what actually reaches the underwriter. Standardized SOPs replace informal judgment calls that slow everything down, and every deviation from the norm becomes a training issue. Triage systems that route work by complexity rather than time of arrival mean underwriters spend their time on the accounts that need it.
Some of the friction is absolutely a technology issue: the manual work is repetitive, rules-based, and high-volume enough that automation can produce reliable results at scale.
Document extraction removes the need for manual rekeying across systems that were never built to talk to each other. Automated policy checking flags any variances between the quote, binder, and issued policy without requiring a manual clause-by-clause check. Inspection review automation flags the material findings and drafts the recommendation letter before the underwriter even opens the file.
The key caveat is that technology reliably removes friction only where the process it applies to is standardized. With a broken process, automation will create friction faster than it removes it.
Most operational improvement programs measure the wrong thing.
Implementation milestones answer whether the solution was actually deployed. They don't answer whether the friction has gone away. You can have a platform that goes live on time and still add steps to the underwriter's day. It's been implemented, and it's a complete operational failure. Those are two very different outcomes,, and that's precisely how organizations end up with technology spend and no productivity improvement whatsoever.
The metrics that reveal whether friction has actually been removed are business outcome metrics, not implementation metrics:
These figures directly answer the underwriter's question. If time-to-quote hasn't improved, friction remains. If the proportion of underwriter time spent on admin work hasn't changed, then the intervention hasn't worked. If error rates further down the chain haven't changed, then the problem hasn't been solved where it was intended to be solved.
To measure those numbers, you need a baseline. You can't know whether an operation has improved without knowing where it was before the intervention. That baseline also makes the investment defensible when leadership comes and asks, "Was it worth it?"
The underwriter's question is a useful filter for every operational decision that a specialty insurer makes.
Does that make my day any easier or any harder?
The organizations getting the most out of their operational spend start with that question and work backward to the solution. The intervention itself matters less than whether it removes the right friction at the right point in the process.
That sequencing requires knowing where the friction actually sits before deciding how to address it. OIP Insurtech's Workflow Intelligence Diagnostic maps real workflows, quantifies where underwriting capacity is consumed by work it shouldn't require, and identifies where people, process, or technology will have the greatest impact.