She would need testimony, records, and a careful reconstruction of the decisions.
The process would take time.
The people involved might resist it.
And the longer the investigation continued, the greater the pressure would become to produce a simple answer.
Victoria was determined not to let that pressure replace the truth.
At 2:20 p.m., she visited the engineering department.
The open-plan office occupied two floors and contained rows of workstations, collaboration rooms, and testing laboratories. Screens displayed code, product dashboards, and technical diagrams. Employees moved between desks carrying laptops and notebooks.
Unlike the executive floor, the engineering department felt busy rather than ceremonial.
Victoria was accompanied by Priya Shah and a department coordinator. She had asked that the visit remain informal, with no prepared presentation and no requirement for employees to attend.
She wanted to see how the work was done.
Near a glass meeting room, she noticed a young Black engineer explaining a technical problem to two colleagues. One of them interrupted repeatedly, finishing the engineer's sentences and redirecting the discussion toward a different solution.
The engineer stopped speaking.
The other man continued.
Victoria did not intervene.
She had seen only a few seconds of the exchange. It could have been a routine disagreement. She needed context before interpreting it.
A few minutes later, the engineer returned to his desk.
Victoria approached.
“Excuse me. May I ask you a question?”
He looked up.
“Sure.”
“My name is Victoria Matthews. I'm the new CEO.”
His expression changed.
“Oh. Right. Of course.”
“You don't need to stand up.”
He gave a nervous laugh.
“Sorry. I wasn't expecting to meet you today.”
“That's why I came without a formal presentation.”
She introduced Priya and explained that they were conducting an initial review of the company's working environment.
“We're interested in understanding how teams make decisions, how performance is evaluated, and whether employees have access to the resources they need.”
The engineer nodded cautiously.
“Okay.”
“What is your name?”
“David Carter.”
“How long have you worked here?”
“Three years.”
“What do you think Pinnacle does well?”
David appeared surprised by the question.
“Technically? We have good people. The products are complicated, but the engineers are capable. We solve difficult problems.”
“And what could we improve?”
He glanced toward a nearby meeting room.
“Communication.”
“In what way?”
“Sometimes the people who make decisions don't understand the work well enough to know what they're asking for.”
“Can you give me an example?”
David hesitated.
“It's not really my place to criticize leadership.”
“I'm not asking you to criticize anyone. I'm asking you to describe a process.”
He looked at Priya, then back at Victoria.
“Sometimes a technical recommendation gets made in a meeting, and then someone more senior repeats the same recommendation later. Suddenly, it's treated as a new idea.”
Victoria listened.
“Does that happen often?”
“Enough that people notice.”
“Have you raised the issue?”
David smiled faintly.
“With whom?”
“Your manager?”
“I tried. He told me that influence is part of leadership and that I should focus on delivering results.”
“What happened after that?”
“Nothing. I kept working.”
Victoria thanked him.
She did not ask him to identify the people involved. If he wished to provide a formal account, she wanted him to have access to an appropriate reporting channel.
As they continued through the department, Victoria noticed that employees were willing to discuss technical obstacles but became more cautious when asked about promotion decisions or management behavior.
One engineer told her that the company offered excellent training but that access to leadership-development programs depended heavily on manager recommendations.
Another said that promotion criteria were often described as flexible, although the flexibility seemed to benefit some employees more than others.
A third explained that employees who challenged a manager's decision could find themselves excluded from high-profile projects.
None of these conversations established misconduct.
But together, they suggested that Pinnacle's informal culture might matter as much as its written policies.
At 3:35 p.m., Victoria returned to her office.
An email from Miriam was waiting.
The technical team had recovered part of the missing audit history.
One of the compensation files had been accessed repeatedly in the days before the acquisition announcement. Several accesses were associated with accounts belonging to senior management.
The access records did not prove that anyone had altered or deleted evidence.
However, they established that the documents had received unusual attention during a period when the company knew leadership would change.
Miriam recommended that the review examine the associated correspondence and meeting records.
Victoria forwarded the recommendation to Mark and requested an urgent governance briefing.
Then she opened the note left anonymously that morning.
The numbers don't tell the whole story.
She had assumed the message referred to compensation disparities.
Now she wondered whether it referred to something else.
Perhaps the numbers had been adjusted.
Perhaps the executive summary had been deliberately narrowed.
Or perhaps someone simply knew that the official reports could not capture the full experience of the people whose careers were affected.
Victoria looked at the city beyond her windows.
The investigation was only beginning.
And somewhere inside Pinnacle Solutions, someone had reason to fear what the records might reveal.
At 4:05 p.m., Elena Brooks knocked on Victoria's office door.
“Come in.”
Elena entered carrying a printed email.
“I thought you should know about this.”
Victoria took the paper.