There were delays. Some employees complained that investigations took too long. A few managers struggled to adapt. One department experienced a temporary decline in productivity while responsibilities were reorganized.
Maya refused to hide those problems.
At the next town hall, she addressed them directly.
“We have made progress,” she said. “But progress does not mean we have solved everything.”
Employees watched from the auditorium and from offices connected through video.
“There will be days when our procedures are inconvenient. There will be cases where people disagree with the outcome. There will be mistakes. What matters is whether we are willing to examine those mistakes honestly and correct them.”
She paused.
“I also want you to understand that fairness does not mean everyone gets exactly what they want. A promotion will still depend on qualifications. A complaint will still require evidence. A business decision will still need to make sense. But the process must be honest, consistent, and respectful.”
A hand rose in the second row.
It belonged to Olivia Grant, who had returned to her project after the Chicago investigation.
“Ms. Bennett, what should employees do when the person they need to report is someone senior enough to influence the investigation?”
Maya looked at her.
“That is why the independent reporting channel exists. You should not have to report a concern to the person you are concerned about. You can contact the ethics committee directly, and the committee is required to review the matter without interference from the relevant management chain.”
Olivia nodded.
“And what if someone retaliates anyway?”
“Then retaliation becomes a separate violation. The employee can report it, and the committee can review the evidence independently.”
Maya paused.
“But I also want to say something important. You should not have to become an expert in company procedures just to feel safe at work. Our responsibility is to make the system understandable and accessible.”
A second employee raised a hand.
“Will there be a way to know whether these changes are actually working?”
“Yes,” Maya replied. “We will continue measuring employee trust, retention, promotion patterns, and complaint outcomes. The results will be reviewed independently and reported to the board.”
The meeting continued.
When it ended, several employees approached Maya.
Some thanked her.
Others offered suggestions.
One employee criticized the new scheduling system because it was difficult to use on older mobile devices. Another asked for clearer information about internal training opportunities.
Maya listened and took notes.
She did not promise that every suggestion would be adopted.
She promised that every suggestion would be considered.
It was a small distinction, but an important one.
Respect did not require agreement.
It required taking another person's concerns seriously.
That evening, Maya returned to her office and found Samuel waiting near the door.
He was holding a folder.
“Am I catching you at a bad time?” he asked.
“No. Come in.”
Samuel entered and sat down.
“I've been working on something with the maintenance team.”
Maya opened the folder.
Inside was a proposal for a practical training program designed to help entry-level maintenance employees develop technical skills and qualify for supervisory positions.
The program included equipment certification, safety training, communication workshops, and paid mentoring hours.
Maya studied the document.
“This is thorough.”
“We've got people who know how to do the work,” Samuel said. “But they don't always know how to show what they can do when a better position opens.”
“Who developed this?”
“Three technicians, two supervisors, and me. We asked the team what they needed.”
Maya smiled.
“You involved the people who would actually use the program.”
“Figured that might help.”
“It certainly does.”
Samuel shifted in his chair.
“There is one more thing.”
“Go ahead.”
“I want the younger technicians to lead some of the training sessions themselves. Not just listen to supervisors. Some of them have skills the rest of us can learn from.”
Maya looked at the proposal again.
“I like that.”
“Then can we try it?”
“Yes. Submit the final budget to Daniel. We'll fund a pilot program at headquarters and one regional office.”
Samuel's face brightened.
“Thank you.”
“You should be thanking your team. They did the work.”
“I will.”
He stood, then glanced at the wooden plaque behind her desk.
“You kept it.”
“Of course.”
Samuel smiled.
“Good.”
After he left, Maya returned to the proposal.
She remembered the man who had once been turned away from the building because someone assumed he was not important enough.
Now he was helping create opportunities for people who had spent years believing that advancement was reserved for someone else.
His influence had grown far beyond the maintenance department.
He had become the kind of leader who noticed people.
And that, Maya thought, was exactly what the company needed.
The training pilot began in June.
Twenty-four employees enrolled.
Some had worked in maintenance for more than a decade without receiving formal certification. Others were younger employees who had entered the company through temporary positions.
The program was practical and demanding.
Participants learned equipment diagnostics, workplace safety, documentation procedures, and basic team leadership. They also completed projects designed to improve the efficiency of the facilities department.
Samuel insisted that every participant receive constructive feedback.
He did not want the program to become a ceremonial exercise in encouragement.
“If someone needs to improve, tell them what they need to improve,” he explained during the first session. “But don't make them feel that a mistake means they don't belong here.”
One participant, a quiet technician named Luis Ramirez, struggled with the written assessments.
He was excellent at repairing mechanical equipment, but he had difficulty translating his knowledge into formal reports.
After the second assessment, he approached Samuel.
“I don't think I'm going to pass,” Luis said.
Samuel looked at the paper.
“Why do you think that?”
“My answers aren't good enough.”
“Are the repairs you perform good enough?”
Luis nodded.
“Then we have something to work with.”
Samuel sat beside him.
“Show me how you would explain this repair to another technician.”
Luis began describing the problem.
He explained the equipment failure, the signs he noticed, and the steps he took to fix it.
Samuel listened.
“That's a good explanation,” he said.
“But I can't write it like that.”
“Not yet.”
Samuel helped him organize the information into short sections.
They worked through the process one step at a time.
By the end of the week, Luis's reports had improved significantly.
He passed the next assessment.
Months later, he became one of the first employees in the program to qualify for a lead technician position.
When Maya visited the maintenance department, Samuel introduced them.
“This is Luis. He completed the program and is now supervising the evening repair team.”
Maya shook his hand.
“Congratulations.”
“Thank you, Ms. Bennett.”
“What was the most useful part of the program?”
Luis thought for a moment.
“Learning that I didn't have to pretend I knew everything.”
Maya smiled.
“What do you mean?”
“Before, I thought asking for help would make people think I wasn't qualified. Samuel taught us that a good supervisor needs to recognize what they don't know and find the right person to help.”
Samuel folded his arms.
“That's a lesson worth learning.”
Maya looked around the room.
Employees were working together, reviewing equipment, and discussing the next training schedule.