The first time Sterling asked me to eliminate positions, I understood how easy it had been for Marcus to reduce a person to a number.
Not because I agreed with him.
Because the spreadsheet was frighteningly clean.
Revenue had softened across two divisions.
A planned acquisition had been delayed.
Operating costs were above target.
The executive team needed to remove nearly six percent of corporate overhead before the next fiscal year.
My organization had to contribute.
Lena, now chief operating officer, called me into her office with the finance lead and HR.
A table appeared on the screen.
Role.
Salary.
Tenure.
Performance rating.
Estimated severance cost.
Savings.
People became rows before anyone said their names aloud.
I hated it.
But hating it did not make the financial problem disappear.
“We need four positions from your group,” finance said.
I looked at the list.
One name stopped me.
Nora Patel.
My deputy.
The woman who had covered my work while I helped my mother after surgery.
Her salary was high.
Her role overlapped with mine on paper.
The spreadsheet labeled that overlap “consolidation opportunity.”
I felt physically sick.
The finance lead pointed at the row.
“If you take Patel plus three manager roles, you reach the target with fewer total terminations.”
I heard an echo from years earlier.
You were expensive.
Jessica was cheaper.
I pushed my chair back.
“I need time to review the actual work.”
“We have to submit names by Friday.”
“It’s Tuesday.”
“Correct.”
“Then I have three days.”
HR looked at Lena.
Lena looked at me.
“You have until Thursday afternoon,” she said.
I left with the spreadsheet but did not start by protecting Nora.
That mattered.
If I simply saved the person I liked and sacrificed four others, I would be making the same kind of emotional decision from the opposite direction.
I mapped responsibilities.
Programs.
Client dependencies.
Regulatory obligations.
Who knew what.
Who could absorb what.
Which work could stop entirely.
That last question changed the exercise.
Finance had assumed every current activity needed to continue after fewer people remained.
It did not.
We were running two internal reporting processes that had grown over years but no longer served a clear decision.
We had a governance coordinator role created for a merger that was now complete.
We had three layers of project review on programs that needed two.
By Thursday morning, I had a different proposal.
Eliminate two vacant positions permanently.
Stop one low-value reporting process.
Combine a completed integration office into enterprise operations.
Remove two occupied roles whose work could genuinely be absorbed after those changes.
It still meant two people would lose their jobs.
There was no version where nobody got hurt.
Finance frowned.
“The savings are slightly below target.”
“By two hundred and ten thousand.”
“Correct.”
“I can close that through contractor reductions and travel.”
“That takes longer to realize.”
“Three months.”
The CFO joined the discussion.
“Why not eliminate Patel? It gets you there immediately.”
I took a breath.
“Because Nora owns continuity for three enterprise programs and is the designated backup for me. If we eliminate her because her salary is high, we create the exact single-point dependency our governance model is designed to prevent.”
The CFO looked at Lena.
Lena said nothing.
He looked back at me.
“Are you arguing she is untouchable?”
“No. I’m arguing her work exists and has to go somewhere. If we remove it, show me who owns it.”
That changed the conversation.
We spent forty minutes on the work instead of the salary.
In the end, the executive team accepted my plan with one adjustment.
The contractor reductions had to happen within sixty days, not ninety.
I agreed.
Then came the part I dreaded.
The two occupied roles belonged to people I knew.
One was a program coordinator named Brian who had been with Sterling seven years.
The other was a reporting manager named Mei whose team’s work was being automated and combined with finance.
Neither had done anything wrong.
That made the conversations harder, not easier.
HR offered to deliver the messages while I sat in.
“No,” I said. “I’ll speak first.”
Brian joined the video call from home.
He smiled when he saw me.
“Hey, Chloe. What’s up?”
I hated that sentence.
I did not read a long preamble.
“Brian, I have difficult news. Sterling is reducing corporate costs, and your position is being eliminated.”
His smile disappeared.
I explained the effective date.
The severance.
Benefits.
The transition period.
Then I stopped talking.
He stared at the screen.
“Is this performance?”
“No.”
“Did I do something?”
“No.”
“Then why me?”
That was the question every spreadsheet avoided.
I answered it as specifically as I could.
The governance structure had changed.
The work he coordinated would be split between two existing program offices.
His position would no longer exist.
He looked angry.
He had every right to.
“So all that stuff about people mattering only matters until finance wants a number?”
I did not defend Sterling with a slogan.
“This decision hurts you. I understand why it may feel exactly that way.”
He shook his head.
“Do you?”
“Yes.”
I did not tell my story.
This was his meeting.
But he knew enough about my history to understand the answer.
Afterward, HR told me I had handled it well.
I did not feel like I had.
There was no good version of telling a capable person his job was gone.
There were only ways to make it less disrespectful.
Mei’s conversation was quieter.
She asked practical questions.
Then one that caught me off guard.
“Was the decision made before today?”
“Yes.”
“How long ago?”
“Final approval was yesterday.”
“Thank you for telling me.”
She nodded slowly.
“My husband’s company laid people off last year. They had them working on a launch all week, then fired them Friday morning. I kept wondering if that was happening here.”
My throat tightened.
“No,” I said. “Once the decision became final, we scheduled this conversation before asking you to do additional transition work.”
She looked relieved, which felt awful in its own way.
The next two weeks were difficult.
We offered both employees paid transition time.
They could document their work without being expected to perform normal workloads.
Neither was asked to train an unofficial replacement under the fiction that nothing had changed.
Brian chose to leave immediately and take the severance.
Mei stayed through the transition period because she wanted time to interview internally.
She eventually accepted a finance analytics role in another division.
That outcome was good for her.
It did not make the original termination painless.
A month later, I sat with Nora after a leadership meeting.
She had heard enough about the cost reduction to know her name must have appeared somewhere.
“Was I on the list?” she asked.
I could not discuss confidential deliberations in detail.
But I could answer honestly.
“Your role was reviewed, like every senior role in my group.”
“And you kept it.”
“The work justified it.”
She watched me carefully.
“Would you tell me if it didn’t?”
That was the real question.
“Yes.”
She nodded.
“Okay.”
Then she asked, “Did this whole process mess you up because of what happened at your old company?”
I laughed without humor.
“Yes.”
“Good.”
I raised an eyebrow.
“Good?”
“It should bother you.”
She leaned back.
“I don’t want a boss who enjoys layoffs.”
Neither did I.
That night, I found the old severance agreement from years before in a locked folder on my personal computer.
I read the first page.
Then I closed it.
I did not need to revisit every sentence.
What mattered was what I had done differently when the decision belonged to me.
I had not saved everyone.
I had not turned a business constraint into a morality play.
I had forced us to understand the work before choosing the names.
I had told people promptly once the decision was final.
I had not asked them to rescue the company after removing their authority.
It was not redemption.
It was management.
Maybe that was enough.
The cost-reduction process also forced me to change one policy in my own organization.
Before the layoffs, managers were allowed to submit position-elimination recommendations with a short business rationale and a budget impact.
Afterward, I required three additional questions.
What work stops if this role disappears?
What work moves, and to whom?
What external commitments depend materially on this person during the next thirty days?
Finance complained that the form became longer.
I told them that was the point.
A week later, one director tried to submit a termination recommendation for a senior analyst named Luis.
His rationale said the team could “absorb responsibilities.”
I sent it back.
Who absorbs which responsibilities?
The revised answer named two people.
One was already at full capacity.
The other did not have access to a regulatory reporting system Luis administered.
The proposed savings were real.
So was the hidden risk.
The director withdrew the recommendation and found a different cost reduction.
Luis never knew how close his role came to being cut.
That felt strange.
Leadership decisions changed lives in rooms the affected people never entered.
There was no way around that completely.
But we could at least make the rooms more rigorous.
At the next executive meeting, the CFO joked, “Chloe has turned a layoff form into a dissertation.”
I replied, “Cheaper than losing a major client because nobody asked what the person actually does.”
The room went quiet for half a second.
Then Lena laughed.
“Point to Chloe.”
The CFO raised both hands.
“Fine. Keep the form.”
It stayed.
Years later, I would see similar questions added to Sterling’s enterprise workforce process.
Not because my story was special.
Because the principle was useful.
That mattered more.
Click here to continue reading: PART 14: A Call From Brenda Finally Filled In the Last Missing Piece of That Afternoon
The Layoff Call Came Five Miles Before the Biggest Pitch of My Career
Part 13 of 16
