The closest I ever came to reliving Project Titan happened seven years after the layoff.
Sterling was negotiating a major partnership with a software provider called Norwell Systems.
The value was smaller than Titan but still significant.
More importantly, the implementation touched almost every operating division.
Nora led the internal work.
By then, she had been promoted to vice president and reported to me.
She knew the program better than anyone.
The final executive workshop was scheduled for a Wednesday morning.
On Monday afternoon, HR called me.
One of the roles selected in a separate organizational redesign sat inside Nora’s program team.
The employee was Calvin Moore, a senior integration architect.
His position was being eliminated because Sterling had decided to move that capability into a central technology group.
The decision was final.
The planned notification time was Tuesday at 4 p.m.
I looked at Calvin’s calendar.
Wednesday, 9 a.m.
Norwell executive workshop.
Presenter: Calvin Moore — integration architecture and migration controls.
For a second, I was back in my car.
Five miles from Salesforce Tower.
Brenda’s voice.
Effective immediately.
I called Nora.
“Where are you?”
“My office.”
“I’m coming down.”
She looked up when I walked in.
“What happened?”
I closed the door.
“I need to discuss a confidential personnel issue. Calvin’s current role is being eliminated as part of the technology redesign.”
Her face changed.
“When?”
“Final approval today. Notification currently scheduled for tomorrow afternoon.”
She stared at me.
“The Norwell workshop is Wednesday.”
“I know.”
“Chloe.”
“I know.”
For a moment, neither of us spoke.
Then Nora said, “We can move the notification until Thursday.”
My stomach tightened.
That sounded kinder on the surface.
It also meant knowingly asking Calvin to prepare and deliver a critical presentation after leadership had already decided his job was gone.
I had hated that idea when it happened to others.
“I don’t want to do that,” I said.
“Then we tell him tomorrow and ask him to present anyway?”
“No.”
“What’s left?”
“Transition the presentation.”
Nora looked at the agenda.
“Calvin has the most knowledge.”
“Then we should have built a backup before now.”
“We have one. Priyank can cover most of it.”
“Most?”
“He hasn’t led the migration-control section.”
“Can you?”
“Yes.”
“Then you and Priyank present.”
Nora sat back.
“The client will notice Calvin disappeared.”
“Yes.”
“What do we tell them?”
“The truth we are allowed to tell. The team structure has changed, and you are taking executive ownership of the integration discussion.”
She looked at me carefully.
“Not ‘pulled into another strategic priority.’”
I smiled despite the tension.
“Absolutely not.”
We called HR back.
The notification remained Tuesday afternoon.
But before that happened, we removed Calvin from the Wednesday preparation workload.
We did not tell him why until the termination conversation.
At 4 p.m. Tuesday, his manager, HR, and I met with him.
I explained the role elimination.
Calvin went completely still.
Then he looked at me.
“What about Norwell tomorrow?”
“Nora and Priyank are covering it.”
He blinked.
“You already moved it?”
“Yes.”
“So you knew before today.”
“The final decision was approved yesterday.”
He looked down.
“I’ve spent six months on that workshop.”
“I know.”
“Do they know I’m gone?”
“Not yet. They’ll be told the team changed.”
He rubbed his face.
“Do you want me to brief Priyank tonight?”
There it was.
The offer I had once been pressured to make in reverse.
“No,” I said.
Calvin looked up.
“We already transitioned enough knowledge through the program files and team structure. If Priyank has questions about your work during your paid transition period, he can send them through HR-approved channels. You are not expected to work tonight.”
He stared at me.
“Seriously?”
“Yes.”
His eyes filled, which made him angry.
He looked away.
“Sorry.”
“You don’t need to apologize.”
He took a minute.
Then he asked about severance.
Benefits.
Internal openings.
The conversation became practical.
Afterward, I went to Nora’s office.
She was surrounded by architecture diagrams.
“How bad?” I asked.
She looked at me.
“The presentation?”
“Yes.”
“Manageable.”
“Are you sure?”
“No.”
That made me laugh.
“Good answer.”
We spent thirty minutes clarifying what she needed from other teams.
Then I left.
I did not take the deck home.
I did not rewrite Calvin’s slides.
I did not become the emergency presenter.
Wednesday morning, I attended the Norwell workshop as executive sponsor.
Nora opened.
“Before we begin, I want to note a change in our team. Calvin Moore is no longer serving in the integration role. I will own that work with Priyank Desai going forward.”
The Norwell executive asked, “Was this expected?”
Nora looked at me briefly.
Then she answered.
“It resulted from an internal organizational redesign completed this week. We recognized the timing created continuity risk, so we adjusted the agenda rather than pretend nothing changed.”
The room stayed quiet for a second.
Then the executive nodded.
“Thank you for being direct.”
That was it.
No collapse.
No panic.
No champagne before signatures.
The workshop continued.
Priyank stumbled on one answer.
Nora stepped in.
On another question, neither of them knew.
Nora said, “We’ll confirm and come back by tomorrow.”
No bluffing.
No invented promise.
They delivered the answer the next day.
Three weeks later, Sterling and Norwell signed the agreement.
The signing itself was almost boring.
Legal circulated final documents electronically.
Finance confirmed approval.
Procurement logged the executed version.
Someone brought cupcakes to the office.
Nora held one up.
“Should I get champagne?”
I pointed at her.
“Do not test me.”
She laughed.
Then her expression softened.
“You know what’s strange?”
“What?”
“We did the exact opposite of what happened to you.”
I thought about it.
Not exact opposite.
Calvin still lost his job.
He still went home on a Tuesday with a future he had not planned.
But the company did not use him after making the decision.
It did not conceal his departure from the client with a fake story.
It did not depend on one person so completely that removing him broke the work.
“We did better,” I said.
Nora nodded.
“Yeah.”
Better was enough.
A month later, Calvin emailed me.
He had accepted a role at a cybersecurity company.
He wrote only three sentences.
Thanks for not making me present after you knew. I was furious that day, but I understand now how easily that could have happened. I still wish I hadn’t been laid off, but I appreciate that part.
I read the message twice.
Then I saved it.
Not as proof that I was a good person.
As proof that process mattered most when it could not make the outcome painless.
The Norwell workshop became a reference point inside Sterling, though I tried to stop people from turning it into a heroic story.
A month later, one executive said during a leadership meeting, “Chloe saved us from another Titan.”
I corrected him immediately.
“No. Nora and Priyank delivered the workshop. HR coordinated the timing. Calvin’s documentation was current. We had enough redundancy to adjust.”
He waved a hand.
“You know what I mean.”
“I do. I still want the wording right.”
Lena glanced at me and smiled.
After the meeting she said, “You really hate being called indispensable now.”
“I hate what it encourages.”
“Which is?”
“Organizations stop building systems when they believe a person is the system.”
She nodded.
“That should probably be on a wall somewhere.”
“Please don’t.”
“I’m ordering a plaque.”
She did not.
But the operations team did something better.
They added a continuity review to all major external negotiations.
Every critical meeting had a primary owner and a backup.
Every major commitment had at least two people who understood the assumptions behind it.
If someone left, the process did not pretend nothing had happened.
The client was told what changed when appropriate, and responsibility was reassigned visibly.
It sounded bureaucratic.
It was.
Good bureaucracy is often just memory converted into a checklist.
I learned to appreciate that.
Click here to continue reading: PART 16: Years After the U-Turn, I Finally Knew What the $800 Million Deal Had Cost and Given Me
The Layoff Call Came Five Miles Before the Biggest Pitch of My Career
Part 15 of 16
