smon

Chương 8

“What does that mean?”

“When I arrived at Westbridge, everyone told me the same thing.”

“What?”

“That the company was successful because a few people worked harder than everyone else.”

He stopped.

“I thought that meant the people needed to change.”

“And?”

“And I missed that maybe the system around those people needed to change.”

I looked at the floor.

It was the closest thing to accountability I had heard from him.

Not an excuse.

Not a defense.

A realization.

The next morning, Rachel sent me a calendar invitation.

The subject was simple.

Emergency technical review.

The attendees included Westbridge leadership, legal representatives, and several engineers.

Including Evan.

I stared at his name for a while.

Because that meeting was not just about software.

It was about whether people who had stayed quiet were ready to speak.

And whether people who had made decisions were ready to listen.

And whether people who had made decisions were ready to listen.

The meeting started with twelve people in a conference room that suddenly felt too small.

I sat at the far end of the table.

Not because I wanted distance.

Because I needed it.

For years, I had sat in meetings like that as the person nobody noticed until something broke.

Now everyone was watching me before anyone had said a word.

Marcus sat across from me.

He looked uncomfortable in a way I had never seen before.

Not nervous.

Not angry.

Uncertain.

That was new.

The board representative, Karen Whitmore, opened the meeting.

She was the same person whose signature appeared on the agreement from years earlier.

I had never met her before.

That bothered me.

Not because she had done something wrong.

Because I had spent ten years inside Westbridge and never knew who approved the decisions affecting my work.

“Before we begin,” Karen said, “I want everyone to understand that this meeting is about facts.”

Nobody moved.

“No accusations.”

“No assumptions.”

“No decisions based on incomplete information.”

Her eyes moved around the room.

“That includes protecting the company from embarrassment.”

The sentence was directed at everyone.

Including herself.

Marcus spoke first.

“We have a critical systems issue.”

One of the engineering managers interrupted.

“Critical is a strong word.”

Marcus looked at him.

“Payments are failing.”

The manager shifted in his chair.

“Some payments are failing.”

Evan looked down.

I noticed the reaction.

Small.

Almost invisible.

But I knew that expression.

Someone had just said something technically correct while avoiding the actual problem.

I opened my notebook.

Not the old deployment notebook.

A new one.

A blank one.

I wanted to approach this differently.

“Can we start with what changed?” I asked.

Everyone looked at me.

A few people looked uncomfortable hearing my voice in that room again.

The engineering manager cleared his throat.

“When your access was removed, several automated processes began failing.”

“Which processes?”

He hesitated.

“That information is still being gathered.”

“By who?”

“Engineering.”

“Which team?”

Nobody answered immediately.

That silence told me more than a report would have.

Westbridge had spent years building systems nobody fully understood.

Now everyone was discovering the difference between ownership and familiarity.

“I need names,” I said.

The manager frowned.

“Excuse me?”

“I need to know who maintains each system.”

“That can be provided.”

“When?”

He looked toward Marcus.

Not at me.

That annoyed me more than I expected.

Because it meant even now people were looking for permission instead of answers.

“Today,” Marcus said.

The room became quiet again.

I opened my laptop.

The old one.

The one from my apartment.

Several people noticed.

I did not explain why I brought it.

I did not need to.

I connected the screen.

A diagram appeared.

Not a complicated one.

Just a map of systems and dependencies.

“The company believes this is a payment platform.”

I pointed to the center.

“It is not.”

Nobody spoke.

“It is a collection of systems built over years.”

I moved through the diagram.

“Authentication depends on this library.”

Click.

“Monitoring depends on this framework.”

Click.

“Deployment depends on these tools.”

Click.

“And several customer-facing services depend on the same components.”

A product executive leaned forward.

“Are you saying everything is connected?”

“No.”

I looked at him.

“I’m saying nobody knows exactly how connected everything is.”

That landed differently.

Because everyone in the room understood the difference.

A system that is complex can still be controlled.

A system nobody has mapped is a risk.

Marcus looked at the screen.

“Can it be stabilized?”

“Yes.”

“How long?”

I paused.

That was the moment where the old me would have made a promise.

The old me would have said whatever was needed to reduce panic.

Not anymore.

“I don’t know.”

The answer surprised them.

Even me.

“I can identify immediate failures.”

I continued.

“But a full stabilization plan requires information Westbridge should have collected years ago.”

Nobody liked hearing that.

Especially because nobody could argue.

Karen folded her hands.

“Lily, what would you need?”

“Access.”

Marcus nodded.

“Granted.”

“Not just access to systems.”

I looked around the room.

“I need access to people.”

The engineering manager frowned.

“Meaning?”

“I need engineers who worked on these systems.”

A few people exchanged looks.

“Some of those engineers are no longer with the company.”

“I know.”

“Some left years ago.”

“I know.”

The room went quiet.

Because everyone understood the implication.

Knowledge had left the building before anyone noticed.

After the meeting, Evan waited outside.

He looked exhausted.

“You okay?” I asked.

He shrugged.

“That depends.”

“On what?”

“On whether telling the truth gets people fired.”

I understood immediately.

He was afraid.

Not of me.

Of the company.

I leaned against the hallway wall.

“You did the right thing.”

He looked down.

“I should have said something earlier.”

“Yes.”

The answer surprised him.

I continued before he misunderstood.

“But you were twenty-three.”

He looked up.

“You were trying to keep your job.”

“That’s not an excuse.”

“No.”

I nodded.

“But it is a reason.”

May you like

Evan looked away.

“I thought you would be angry.”

Related Stories

Other posts