On the morning of 15 December 1967, the Silver Bridge looked normal.
It crossed the Ohio River between Point Pleasant, West Virginia, and Kanauga, Ohio. Traffic used it as usual. From the road, there was no obvious sign that anything was about to happen.
Later that day, during the evening rush hour, the bridge "collapsed without warning" — the phrase used in the ASCE account, The Silver Bridge Collapse Recounted.
Investigators later traced the collapse to a fracture in a single eyebar in the suspension chain.
The weakness was not created in that final moment. A hidden flaw had been sitting inside the structure and developing over a long time before the collapse became visible.
The final crossing was not the whole story. It was the moment the hidden strain showed itself.
Businesses have their own Silver Bridge moments.
The system looks like it is still working. Work keeps coming in. Customers keep getting served. The team keeps finding a way.
But underneath, strain is accumulating.
More work comes in, and at first the team absorbs it.
People stay later. Internal work gets pushed back. Someone covers the gap. Small corners get cut. Nothing obvious breaks.
Then delivery starts to slow. Replies take longer. Turnaround times stretch. Updates become reactive. No single delay looks dramatic, but the service feels less controlled.
Then quality begins to slip. A check gets missed. A handover is weaker. A detail is misunderstood. A customer has to chase. The business is still delivering, but it takes more effort to hold the standard.
Extra work often looks manageable because the strain is absorbed before it is visible.
Then comes the people impact.
The strongest people start carrying the system. They fix the gaps. They reassure clients. They cover weak processes. They take on the exceptions.
They may not complain. But they feel the load first.
The people most able to carry overload are often the people you can least afford to lose.
Then the work starts leaving mess behind.
Rework increases. Customers ask for corrections. Invoices get queried. Payment slows down. Disputes appear. The team spends more time fixing yesterday's work than finishing today's.
That is your crack becoming a problem.
The question is not only: Can we take this work?
When taking on additional work, ask: What is already under strain, and what will this work add to it?
Before accepting the work, check the status of your bridge.
Look for the cracks — where delivery is already slowing, where rework is increasing, which internal work keeps being delayed, who keeps rescuing the system, which jobs are leaving mess behind.
The work may still be worth accepting. But not before the business knows what it will put under pressure.
If the structure underneath is already carrying too much, one more piece of work can be where the damage becomes visible.
What will this work damage if the business cannot absorb it?
If this feels familiar, start here:
👉 Run the Second Look Decision Diagnostic to see what’s missing before you decide
👉See related business decision
👉 📖 Read more on Second Look blog
You can continue with making the decision afterwwards.