Why Shared Responsibility Often Means No Responsibility
When no one clearly owns the outcome, mature businesses pay for the delay in rework, missed follow-up, and decisions that keep circulating.
On August 11, 2020, Citibank meant to send Revlon’s lenders an interest payment.
The amount was about $7.8 million.
Instead, Citi sent the interest payment plus almost $900 million of its own money. The payments matched, down to the penny, the principal and interest Revlon owed on a 2016 loan.
This wasn’t one person casually clicking the wrong button in a corner of the bank.
The transaction went through Citi’s internal approval process. Three people reviewed it. One entered the transaction, one checked it, and one gave final approval.
The process had a name that sounded reassuring: the “six-eye” approval procedure.
Six eyes looked at the transaction.
The money still left the bank.
The Payment Was Supposed To Stay Inside Citi
The mistake came from a complicated loan transaction involving Revlon.
Some lenders were rolling their positions from one credit facility into another. To make that work inside Citi’s loan-processing software, the team had to enter the transaction as if the old loan were being paid off, then direct the principal portion to an internal Citi account.
That internal account was called a wash account. The point was to keep the principal from going out to Revlon’s lenders while the interest payment was processed.
The team understood the goal.
Interest would go to the lenders. Principal would stay inside Citi.
The problem sat inside the payment system. The software required more than one field to be set correctly to keep the principal from leaving the bank. The people involved believed setting the principal field to the wash account was enough.
It was not.
Hi there… I’m David Baer. I work with 7- and 8-figure businesses to streamline marketing, sales, and operations so revenue stops slipping through the cracks.
If you’re ready to create systems that drive real growth and reduce unnecessary expenses, grab 15 minutes on my calendar here to explore if I can help you.
Three People Reviewed The Same Mistake
The first person entered the transaction.
He selected the principal field and directed it to the wash account. But he didn’t set two other fields that also needed to point to the same internal account.
The second person reviewed the transaction and believed the principal was properly set to wash. He then sent it to the final approver.
The final approver also believed the setup was correct. He replied that it looked good and that principal was going to wash.
Then the transaction produced a warning. The system said the account used was a wire account and that funds would be sent out of the bank.
That warning sounds useful until you know what it left out.
It didn’t say whether the amount leaving the bank was the intended $7.8 million interest payment, the roughly $894 million principal amount, or both.
Since interest was supposed to go out, the warning didn’t necessarily signal a problem. The reviewer clicked yes.
Shortly after 6 p.m., the money went out.
The review process had three people in it, but all three shared the same wrong assumption about what the system was doing.
That is the part worth sitting with.
A Check Is Not The Same As Ownership
There is a reason companies add review steps.
A second person catches what the first person missed. A third person catches what the first two missed. At least, that’s the theory.
But review only works when each person knows what they own.
In Citi’s case, everyone knew the intended outcome at a high level: interest to lenders, principal to wash. But the actual control point was more specific. Someone had to know which fields controlled whether nearly $900 million stayed inside the bank.
That is where shared accountability gets thin.
The maker entered the transaction according to his understanding. The checker reviewed it according to the same understanding. The approver confirmed it according to that same understanding.
The process didn’t create three separate layers of protection. It passed the same misunderstanding through three chairs.
The Problem Showed Up The Next Morning
Citi found the error the next morning during normal reconciliation.
There were large cash breaks. Money that should have stayed inside the bank had gone to the lenders with the interest payment.
Citi sent recall notices asking for the principal portions back. Some recipients returned money. Others didn’t.
That led to litigation over whether the lenders could keep the funds. The legal fight matters, but the useful business lesson happened before the lawsuit.
A large institution had a process. The process had roles. The roles had labels. The labels created the appearance of control.
But when the moment came, no one in the chain owned the full question: will this setup actually send only the money we intend to send?
This Happens In Ordinary Companies Too
Most established businesses don’t have $900 million wire mistakes waiting inside their systems.
The pattern is smaller and more familiar.
A customer issue touches sales, service, billing, and operations. Everyone responds to their part, but no one owns the customer getting a final answer.
A vendor problem moves from accounting to operations to the manager who originally signed the agreement. Each person assumes someone else is deciding whether the vendor still makes sense.
A lead comes in through marketing, gets passed to sales, waits for technical input, then drifts because no one owns the handoff between interest and follow-up.
A contract renewal hits the inbox. Finance checks the payment. Operations checks whether the service is still being used. Nobody owns the decision to renegotiate, replace, or cancel it.
Nothing looks broken inside any single department.
That is why the problem survives.
Each team can truthfully say it handled its part. The business still loses money because the issue needed one owner, not several partial participants.
Shared Responsibility Dilutes The Decision
Shared responsibility sounds mature.
It feels collaborative. It gives everyone a voice. It reduces the chance that one person acts without input.
Those are real benefits.
But shared responsibility becomes expensive when it hides the decision owner.
A process can have many contributors. It still needs one person who owns the outcome.
Notice I didn’t say they need to own the task. I said they need to own the outcome.
That’s because owning a task means checking the invoice, sending the email, entering the data, reviewing the screen, or attending the meeting.
Owning the outcome means asking whether the right thing happened after all of those tasks were completed.
Did the customer get the answer?
Did the vendor cost get challenged?
Did the lead receive a real follow-up?
Did the renewal get evaluated before the business paid for another year?
Did the transaction do what everyone thought it did?
Without that outcome owner, a process can look controlled while the business bleeds time, money, and trust through the spaces between roles.
The Question Worth Asking Now
Citi’s mistake was unusually large, but the operating lesson is ordinary.
More reviewers don’t automatically create better control. More departments touching an issue don’t automatically create better follow-through.
Sometimes they create just enough shared involvement for everyone to believe someone else has the larger question covered.
So the useful question isn’t whether important work in your business has enough people involved.
The better question is: Where do too many people touch the work, but no one clearly owns whether the right outcome happened?
If this helped you, consider sharing The Systems Brief with another business owner who is ready to build a business that runs on systems, not hope.
When you’re ready, here are some of the ways I can help you:
→ Expense Reduction Consulting
Need help creating or improving your revenue systems?