Claims Value Stream at Meridian Mutual
Meridian Mutual processes auto-glass claims through 18 steps across three departments. A recent value stream map shows 11 calendar days from claim receipt to payment, with only 3.2 hours of value-added work. First-pass yield is 68%; 22% of claims are reworked because the estimate and photos do not match, and 10% are pended for missing information. Claims move in batches of 40 between the intake, adjuster, and payment teams. Customers call for status updates 1,900 times per month. The VP of operations wants a future-state map with a 'one-day turnaround' target and has scheduled a two-day workshop. The claims manager fears the target is unrealistic because adjusters already handle 75 claims per day each and overtime is 12%. The company has no plan to add adjusters.
1. Calculate the value-added ratio using stated assumptions. What does it reveal, and what is the most important future-state design issue?
Read the worked answer
Value-added ratio = 3.2 hours / (11 days × 8 hours) = 3.2 / 88 = 3.6%. If the operation runs 24 hours, the ratio is 1.2%. Either way, less than 4% of lead time is value added. The ratio does not say adjusters are slow; it says claims wait, are handed off, or are reworked.
The most important future-state issue is first-pass yield and complete information at intake, because 22% rework plus 10% pends create most of the waiting. Batching 40 adds queue time between departments. The future state should design flow and pull around complete, correct claims, not simply compress the 18 steps. The one-day target must be tested against demand, adjuster capacity, and rework; with 75 claims per day and 12% overtime, capacity is tight, so reducing rework is the capacity release.
2. Propose the future-state changes you would prioritize and explain how you would sequence them. What should the VP not do in the two-day workshop?
Read the worked answer
Prioritize: (1) intake quality standard work - required fields, photo checklist, error-proofing, and fast feedback; (2) reduce batching and handoffs - process claims in smaller lots, co-locate or create a cross-functional cell for complex claims; (3) standard work and visual management for adjusters; (4) pull and status visibility to cut the 1,900 status calls; (5) kaizen on the 22% mismatch rework.
Sequence stabilization before flow: if you flow bad claims faster, you create bad payments faster. In the two-day workshop, do not design a future state from opinion or set a one-day target without capacity and quality data. Do not map every exception at once; use data to select one claim family. Do not treat the map as the deliverable; assign owners, dates, and measures for each improvement loop.