The Compliance Constraint and the Parked Spreadsheet
At a regional insurer, 18 operations specialists process policy amendments. Every amendment must pass a mandatory compliance review before release. The board shows Intake, Preparation, Compliance Review (WIP 5), Release and Done. Compliance reviewers are a separate team of two and are not on the board. Preparation has no WIP limit. About 30% of amendments are blocked waiting for missing customer documents, but blocked items are moved to a 'parked' spreadsheet so the board stays clean. Release happens in a monthly batch. Average lead time is 45 days; value-added work is estimated at six days. Throughput is 40 amendments per week, and average WIP is 360. The compliance team says its WIP limit of five is always met because it only counts reviews actively being read. The operations manager wants to remove the compliance WIP limit to improve throughput.
1. Calculate flow efficiency and explain what it suggests about where to improve. What likely causes the gap?
Read the worked answer
Flow efficiency = value-added time / total lead time = 6 / 45 = 0.133, or about 13%. That means roughly 87% of the lead time is waiting, not value-adding work. The team should focus on wait states, not on making specialists work faster. Likely causes are visible in the setup: a mandatory compliance review with a WIP limit that counts only active reading, so its queue is invisible; preparation with no WIP limit; 30% of items blocked for missing customer documents but moved to a parked spreadsheet; and a monthly release batch that holds completed work. The average WIP of 360 and throughput of 40 per week give a Little's Law lead time of 9 weeks, or 45 days, which matches. That consistency suggests the system is stable, not that it is healthy. Improving flow efficiency means reducing the time items spend waiting for compliance, documents and release. The highest-leverage targets are the hidden compliance queue and the parked blocked items, because both are invisible and both inflate WIP. Measuring touch time alone would miss the real delay.
2. Evaluate the proposal to remove the compliance WIP limit and propose a better policy for compliance review and blocked items.
Read the worked answer
Removing the compliance WIP limit would likely increase WIP at the constraint, lengthen the compliance queue and increase overall lead time, because throughput at compliance is fixed by two reviewers. The existing limit is also flawed: it counts only reviews actively being read, so waiting reviews are not controlled. The better policy is to make compliance review a visible state with a WIP limit that includes both active and waiting reviews, and to manage the queue explicitly. If compliance is the constraint, protect it from interruptions and give it a clear pull policy. Blocked items should stay on the board in a visible blocked state, with an aging policy, an owner and an escalation path; they should not be parked in a spreadsheet to make the board look clean. Blocked items still consume WIP and should be counted. For missing documents, define a standard checklist and a policy for when an item returns to the queue. Consider a small expedite class for genuinely urgent amendments, but cap it. Review the compliance limit regularly with data on queue time and aging, not by removing the limit.
3. How should the monthly release batch and blocked-document policy be changed, and what feedback loop would you use?
Read the worked answer
Reduce the release batch size and increase release frequency if the compliance and operations systems allow it. A monthly batch holds completed work for up to a month, which directly adds to lead time and delays customer feedback. A smaller, more frequent cadence, such as weekly or twice-weekly, should reduce the wait after completion and make problems visible sooner. For blocked documents, define a standard missing-information checklist at intake, set a policy for how long an item waits before it is returned or escalated, and keep it visible on the board. Do not let blocked items disappear into a spreadsheet. Use a service delivery review or operations review to examine lead time, flow efficiency, blocked aging and release cadence, and a risk review for compliance exposure. Track the percentage of items blocked and the time to resolve missing documents. If the release batch cannot change because of regulatory constraints, make that policy explicit and measure the waiting it creates. The feedback loop should test whether smaller batches reduce lead time without increasing compliance risk.