A year after the Meridian incident, Mason became engineering reliability manager.
Richard told me before Mason did.
I said:
“Why are you telling me?”
“Thought you’d be proud.”
“I am.”
“Then call him.”
“No.”
Richard laughed.
“Why not?”
“Because it’s his news.”
Mason called that evening.
“I got it.”
“I heard.”
Silence.
“Richard told you?”
“Yes.”
“I was going to tell you.”
“You just did.”
He laughed.
Then asked:
“Do you think I’m ready?”
Dangerous question.
Mentors can become permanent judges.
I answered carefully.
“Yes.”
Then added:
“And my opinion should matter less now.”
He did not like that.
“You trained me.”
“Yes.”
“You know the job.”
“Yes.”
“So why less?”
“Because if you keep checking whether I approve, you’re still working under me emotionally.”
That landed.
Mason had grown through the crisis.
He built checklists.
Challenged Richard respectfully.
Worked with Tyler instead of treating him as permanently unsafe.
He deserved authority without me hovering.
Still, I struggled.
When he proposed a change to Horizon’s preventive-maintenance structure, I disagreed.
Strongly.
He listened.
Then did it his way.
My first reaction:
Mistake.
Three months later, data showed his version worked better.
That humbled me.
Experience can become its own trap.
The engineer who has solved many failures can start treating memory as law.
Mason brought newer analytical tools.
Different methods.
Good.
I called him.
“You were right.”
He laughed too long.
“Enjoy it.”
“I am.”
Mentorship should create people who eventually disagree with you intelligently.
Otherwise you created followers.
That became a Parker Precision principle too.
By then, I had hired my first employee.
Lena Ortiz.
Controls engineer.
Seven years experience.
Sharp.
Blunt.
She reviewed one of my standard diagnostic templates and said:
“This section is terrible.”
I almost defended eleven years of expertise.
Then asked why.
She showed me.
Too much narrative.
Not enough decision thresholds.
She was right.
We rewrote it.
Hiring changed the business.
Now I was management.
Dangerous.
I had spent years complaining about management assumptions.
Now I could create my own.
So I instituted practices I wished Horizon had used.
Document critical knowledge.
Cross-train.
No one employee owns an entire client relationship.
Emergency response rotates.
Overtime tracked.
People can say unavailable unless on contracted rotation.
No hero culture.
Easier written than practiced.
One night, a major client called me directly instead of the emergency number.
Old instinct:
I’ll handle it.
Then I stopped.
Lena was on rotation.
I redirected.
She solved it.
The next morning, part of me felt unnecessary.
Interesting.
I had built an identity around being the person called.
Giving that up was harder than I expected.
Horizon had relied on me.
I had also relied on being relied upon.
That insight made me a better manager.
I praised systems, not heroics.
When Lena fixed a midnight fault, we asked why midnight intervention was necessary and how to prevent recurrence.
No trophies for exhaustion.
No mythology around sacrifice.
That culture became one of Parker Precision’s strongest advantages.
It came directly from the morning I was fired.
My relationship with Mason changed again after his promotion because he became a client decision-maker.
That can be awkward.
Former mentee.
Now buyer.
I had to stop giving free advice casually.
At first, he would call:
“Quick question.”
There is no such thing as a quick question from a client when the answer carries liability.
I answered several anyway.
Old habit.
Then Denise caught unbilled time.
She asked why.
“It’s Mason.”
“So?”
“I trained him.”
“So?”
She was right.
Friendship and commercial work needed boundaries too.
I called Mason.
“If you want general advice as a friend, ask. If you want Parker Precision technical guidance for Horizon, route it through the contract.”
He laughed.
“You’ve become unbearable.”
“Yes.”
But he understood.
That boundary protected him too.
If he relied on casual advice and something failed, where did accountability sit?
Ambiguous.
Bad.
So we separated.
Friend conversation:
Career.
People.
General ideas.
Contract work:
Machine specifics.
Settings.
Formal recommendations.
Documentation.
This made the relationship cleaner.
Mason also learned management pressure firsthand.
One quarter, Horizon executives wanted downtime reduced while cutting maintenance overtime.
He complained to me.
“Impossible.”
“Maybe.”
“You’re supposed to agree.”
“No.”
I asked what data showed.
He brought it.
We reviewed.
Some overtime came from preventable callouts.
Some from scheduled work poorly planned.
The target was aggressive but not impossible.
He hated that answer.
Then improved scheduling.
Management was partly right.
That humbled him.
Later he said:
“I understand Richard more now.”
Same.
Responsibility changes perspective.
Not every unpopular decision is stupid.
Not every cost target is disrespect.
The challenge is understanding what the number actually buys or risks.
That was what Horizon had failed to do when eliminating my role.
Mason became better at translating technical risk into business language.
Not:
We need Ethan.
Instead:
This process has a single qualified recovery path. Estimated downtime exposure is X. Cross-training costs Y. Recommended mitigation is Z.
That is stronger than hero dependence.
I was proud.
Then caught myself.
He no longer needed my approval.
Still proud.
Both can coexist.
Mason’s promotion also forced him to learn something I had never taught well:
how to say no upward.
Technical engineers often become managers and discover expertise does not automatically create influence.
Executives ask for faster output.
Lower cost.
Less downtime.
Mason initially responded with technical explanations so detailed nobody listened.
I told him:
“Translate risk.”
He hated that phrase.
Then learned.
Instead of:
We need three days to validate servo changes because thermal compensation may shift.
He said:
“If we compress validation to one day, we increase the chance of an undetected stability problem during production. Here is the estimated downtime exposure.”
Same engineering.
Different language.
Executives listened.
That skill made him far more effective than simply knowing the machine.
I realized I had lacked it at Horizon too.
I knew risk.
I did not always communicate it in business terms.
That gap contributed to how replaceable my role looked on paper.
Technical people should not need to become salesmen for truth.
But we do need to make consequences understandable to decision-makers.
Mason also made one mistake after promotion that reminded both of us titles do not create instant wisdom.
He approved a weekend maintenance window without checking one supplier dependency.
The plant lost six extra hours.
No catastrophe.
Still expensive.
He called me furious at himself.
“I should’ve known.”
“Maybe.”
“You would have.”
“Maybe.”
I refused to become the imaginary perfect predecessor.
Experience remembers successes more vividly than near misses.
I had made scheduling mistakes too.
He documented the gap, changed the planning checklist, and moved on.
That was the healthier response.
Managers need room to make survivable mistakes or they never truly own the role.
Click here to continue reading: PART 11: Parker Precision Grew Fast Enough to Tempt Me Into Becoming the Kind of Boss I Once Resented, and Lena Called Me Out Before I Did
Five Minutes After Horizon Fired Me, Its Most Important Machine Failed and My Former Boss Learned Exactly What My Expertise Cost Outside Payroll
Part 10 of 16
