“That’s the danger,” I told her. “When operational work is done well, leadership starts thinking the absence of failure means the work is easy.”
She wrote that down.
“You’re seriously taking notes while I’m driving?”
“That sounded expensive.”
I smiled.
Something else was changing at headquarters.
Employees began forwarding me internal messages—not confidential documents, just comments.
Facilities-redundancy review.
Key-person risk assessment.
Operational dependency audit.
Termination checklist update.
Apparently, the board had ordered a company-wide examination of jobs that controlled functions executives barely understood.
I should have felt vindicated.
Mostly, I felt tired.
Then Elaine asked me to attend another board meeting.
This time Graham wasn’t present when the call began.
Elaine spoke alone for the first minute.
“We completed an internal review of your termination.”
I said nothing.
“We found several process failures.”
“Okay.”
“Your position was selected partly because the new vendor represented that your responsibilities could be absorbed.”
“I assumed that.”
“The vendor’s scope did not include several functions your team performs.”
I waited.
Elaine looked directly at the camera.
“And your transition-risk memo was summarized incorrectly before reaching the executive committee.”
That was new.
“Incorrectly how?”
“The recommendation changed.”
My fingers stopped above my keyboard.
“What did my memo say?”
“‘Do not deactivate current facilities authorization until secondary representatives are validated at all active sites.’”
“Yes.”
Elaine’s mouth tightened.
“The executive briefing stated, ‘Facilities authorization transition may be completed after restructuring.’”
For several seconds, I thought I had misheard her.
Those two sentences did not mean remotely the same thing.
“Who changed it?”
“We’re determining that.”
I leaned back.
Suddenly, the story was different.
Graham had ignored warnings, yes.
But someone between my report and his restructuring packet had turned a mandatory sequence into an optional cleanup task.
“Was it accidental?” I asked.
Elaine didn’t answer directly.
“We found tracked changes.”
That evening, Graham called me again.
This time he didn’t ask about a building.
“Mara,” he said, “I need to tell you something before the board does.”
His voice sounded worse than it had on the day North Side locked him out.
“They found out who altered your memo.”
### Part 6
The person who changed my memo was Halcyon’s chief operating officer, Victor Lang. I had worked with Victor for four years and never particularly liked him, but disliking someone is not evidence of anything. He was efficient, polished, relentlessly focused on cost reduction, and capable of making a twenty-minute conversation feel like an interrogation conducted entirely with spreadsheets.
Graham told me the board had already placed him on administrative leave.
“Why would he change it?” I asked.
“We’re still reviewing communications.”
“That means you know something.”
Graham sighed.
“He had committed to the board that his restructuring plan would save nine million dollars annually.”
I understood immediately.
My department was part of the savings.
“So my transition requirement threatened his timeline.”
“Apparently.”
“Apparently?”
“We found emails between his office and the facilities vendor.”
I waited.
“The vendor warned that they couldn’t assume landlord authorization immediately.”
My jaw tightened.
“When?”
“Before you were terminated.”
The room around me seemed to go very still.
Graham continued.
“Victor replied that internal personnel changes wouldn’t affect facility rights.”
I almost laughed.
That was exactly the assumption my memo had corrected.
“So they knew.”
“Victor knew there was a concern.”
“That’s not what I said.”
Graham didn’t answer.
I stood from my kitchen chair and walked toward the window.
Below me, headlights moved along wet streets.
“This wasn’t just carelessness.”
“No.”
“Did he think I would stay through a transition?”
“We believe he expected HR to negotiate a short-term extension after termination.”
I closed my eyes.
“They fired me effective immediately.”
“I know.”
“He told HR to remove me immediately and planned to ask me to keep working?”
“There’s an email discussing ‘post-separation knowledge transfer.’”
I stared out the window.
For years, I had watched executives use phrases like knowledge transfer as though knowledge were a box someone could place on a loading dock.
“So I was supposed to be disposable and available at the same time.”
Graham did not defend it.
“No.”
Something in me changed during that conversation.
Until then, I had been willing to view my firing as a stupid corporate decision made by people who didn’t understand infrastructure.
Now I knew at least one person had understood enough to manipulate the information.
Not because he wanted to destroy Halcyon.
Because he wanted his savings target.
That somehow made it worse.
There was no grand conspiracy.
Just ambition, shortcuts, and an assumption that if I became inconvenient, I would still help afterward.
“I’m sorry,” Graham said.
It was the first time he had used those words.
I turned away from the window.
“For which part?”
The question came out colder than I intended.
He accepted it.
Popular Posts
→- 1
- 2
- 3
- 4
Recently Viewed
Stories you read recently will appear here.
