I Delayed a Product Recall to Hit Quarterly Numbers

Engineering found a defect that could cause minor injuries. Probability was low, maybe 1 in 5,000 units. Recall would cost $2.3 million and blow our quarter. I waited three weeks to report it upward.

The Beginner Calculation

New managers often think they're paid to balance competing interests. Risk versus cost. Impact versus probability. I ran the numbers: expected liability seemed lower than recall costs. Legal said we were probably fine waiting for more data.

Those three weeks felt reasonable. We needed more testing anyway, right? I told myself I was being prudent, not reckless. The truth is I was scared of missing targets and looking incompetent.

What Experience Should Teach You

Seasoned managers know there's no calculation that makes customer safety negotiable. You find the money. You miss the quarter. You recall the product. The math always works out worse when you wait.

A kid got hurt. Not severely, thankfully, but enough for stitches and a lot of pain. The family's lawyer had our internal emails, including mine discussing the delay. Settlement cost four times the original recall estimate.

What I Live With

We recalled everything, obviously. Implemented new protocols where safety concerns go straight to the C-suite, no filtering. I still have the photo of that kid's injury in my desk drawer.

I'm better at my job now, but that doesn't erase the decision. Sometimes the lesson is that you don't get a do-over. You just have to be the person who doesn't make that mistake again and won't let others make it either.