US Insurance — Redesigning the NOD Process Before Automating It

1. The situation

A large US insurance enterprise had a Notice of Determination (NOD) process in which upstream friction and downstream processing effort were creating avoidable delay and inefficiency.

The documented transformation combined process streamlining upstream with AI-enabled automation downstream. The result was a 10% turnaround-time improvement, approximately 20% efficiency improvement, and about $1.5M in annual savings.

2. The transformation question

The central question was: How can an organization reduce processing time and cost without automating unnecessary complexity?

This is one of the most reusable questions in process transformation. Teams often begin with “What can we automate?” when the better starting point is “Why does this work exist, where does it slow down, and which steps should disappear before technology is introduced?”

3. Why the obvious answer can be wrong

If a downstream team is overloaded, automation appears to be the natural response. But downstream workload can be a symptom of upstream design: incomplete inputs, unnecessary handoffs, rework, inconsistent decisions or poorly structured information.

4. How to structure the diagnosis

A strong diagnostic separates the process into four lenses:

• Demand: what events create work?
• Flow: where do handoffs, waits and rework occur?
• Decision: which judgments are rule-based and which require expertise?
• Execution: which remaining steps are good candidates for automation?

The source evidence confirms process assessment, upstream redesign and downstream AI/automation. The four-lens model is a reusable practitioner framework for understanding that logic.

5. Transformation approach

The engagement improved the process in two complementary ways. First, upstream activities were streamlined to reduce unnecessary friction. Second, suitable downstream work was automated using AI-enabled intervention.

That sequencing is important. Process redesign improves the quality of work entering the downstream process; automation then removes manual effort from the work that legitimately remains.

6. Building the value case

The evidence is unusually useful because it shows value through three different lenses:

• Speed: 10% improvement in turnaround time.
• Productivity: approximately 20% improvement in efficiency.
• Economics: approximately $1.5M in annual savings.

Together, these measures demonstrate why transformation business cases should not rely on one headline metric. A process can be faster without becoming cheaper, or cheaper without improving customer or operational responsiveness.

7. Outcomes and evidence

The engagement delivered all three documented outcomes: 10% turnaround-time improvement, ~20% efficiency improvement, and ~$1.5M annual savings.

For practitioners, the more important lesson is the causal chain: upstream redesign reduced friction; downstream automation addressed remaining manual work; and the business case was measured across time, productivity and cost.

8. What could have gone wrong

• Automating downstream steps before fixing upstream defects.
• Using only labor reduction as the value metric.
• Automating decisions that still required human judgment.
• Failing to redesign exception handling.
• Reporting automation throughput while turnaround time remained unchanged.