The real test came when one of my engineers made a mistake that cost our company almost forty thousand dollars.
Priya.
Same engineer who challenged the fatigue-driving policy.
Smart.
Careful.
Not perfect.
She configured a controller revision using an outdated customer specification.
The error made it through review.
Equipment shipped.
A site team discovered incompatibility.
Rush replacement.
Overtime.
Freight.
Forty thousand.
My director called.
“What happened?”
“We used the wrong revision.”
“Who?”
“Priya configured. I approved team release structure. Quality review also missed it.”
He asked:
“Is this a performance issue?”
I felt the old Hartwell language.
Accountability.
Loss.
Ownership.
I said:
“It’s an incident. We need root cause before personnel conclusion.”
Good.
We investigated.
Why was the old specification active?
Customer document portal had two files with similar names.
Our internal system copied the earlier file into the project folder.
Priya missed the revision number.
Review checklist did not require explicit revision verification at release.
Quality reviewer focused on electrical compliance, not customer document revision.
Multiple layers.
Priya made an error.
System allowed it.
I called her in.
She looked terrified.
“How much did it cost?”
“A lot.”
“Am I getting fired?”
“No decision like that is being made today.”
She swallowed.
“Are they taking my bonus?”
“I don’t know. Bonus decisions follow written policy. Nobody is inventing a charge.”
She looked at me.
I knew what that sentence meant to me.
Maybe not to her.
We reviewed.
Priya accepted her part immediately.
“I should have checked.”
“Yes.”
“I thought the project folder was controlled.”
“Reasonable assumption. Still, revision verification belongs in your technical process too.”
She nodded.
We changed the checklist.
Updated document controls.
Added automated alerts for duplicate customer specs.
Priya received coaching and a documented performance note because the error was significant.
She did not lose base pay.
Her annual bonus was affected only according to the existing team and individual performance formula.
No forty-thousand-dollar invoice to her.
No “cheap lesson.”
The company absorbed the business loss.
That is part of employing people.
Months later, Priya told me:
“I thought you were going to make an example of me.”
“Why?”
“Forty grand.”
“Would fear make you better at revision control?”
She laughed.
“No.”
“Then we need a better system.”
Accountability still existed.
She had to improve.
We had to improve.
The company paid.
That incident resolved something in me.
For years, I had defined myself against Hartwell.
I would not be like Derek.
I would not build like Grant.
But negative identity is incomplete.
You eventually need your own philosophy.
Mine became:
Make responsibility specific.
Separate error from character.
Fix systems where systems contributed.
Use discipline where behavior requires it.
Never make financial punishment a substitute for analysis.
That was broader than payroll.
It became how I parented too.
When Mia damaged our car backing out after she started driving, my first reaction was anger.
Repair estimate: $1,700.
She cried.
“I’m sorry.”
I wanted to say:
You’re paying all of it.
Cheap lesson.
The phrase appeared in my head.
I stopped.
We discussed.
She had been careless.
We made her contribute part from savings and summer work.
Not the full repair.
Why?
Because we had given her access to the family car.
We carried insurance.
We accepted some risk.
Responsibility shared.
She lost driving privileges temporarily.
Practiced.
Returned.
No humiliation.
Laura noticed.
“You were thinking about Derek.”
“Yes.”
She smiled.
“Growth.”
I hated that word.
Still.
She was right.
The most important test of a principle comes when abandoning it would benefit you emotionally.
It is easy to oppose arbitrary punishment when you are punished.
Harder when you hold authority.
That is where the lesson became mine.
Priya’s mistake also changed our team culture because she talked about it openly afterward.
Not as confession.
As training.
She showed the wrong spec.
The file naming problem.
The missed revision check.
The corrected process.
New hires learned from a real incident without learning that mistakes end careers automatically.
That balance matters.
If organizations hide mistakes to protect reputation, people repeat them.
If organizations publicly shame individuals, people hide future mistakes.
We wanted neither.
Priya later became one of the most careful reviewers on the team.
Not because fear made her obsessive.
Because she understood why the control existed.
She eventually became a manager herself.
Years later, she told me:
“The forty-thousand-dollar mistake was the best training I never wanted.”
I laughed.
“Expensive.”
“For the company.”
Exactly.
Employment means the company bears business risk within the law and policy.
Employees bear responsibility through performance systems, coaching, advancement consequences, and discipline when appropriate.
Confusing business risk with personal debt is what had gone wrong at Hartwell.
When I considered the Midwest service manager role, Laura asked the most important question.
“Why do you want it?”
“More influence.”
“That sounds dangerous.”
I laughed.
“More ability to fix scheduling and training.”
“Better.”
“More pay.”
“Honest.”
“Less field travel eventually.”
“Best answer.”
Then she said:
“Do not take it to prove Grant was wrong about managers.”
I stared.
She knew me.
There was a part of me that wanted to become the kind of manager Hartwell should have had.
That can be noble.
It can also become another way the old job controls your future.
So I waited a week.
Asked myself whether I would want the role if Hartwell had never happened.
The answer was still yes.
That gave me confidence.
I took the position.
On my first quarterly review, one of my metrics showed labor utilization below target.
The easiest response would have been to push technicians harder.
Instead, we looked deeper.
Too much unpaid waiting at customer sites? No—employees were paid.
Too much travel between distant calls? Yes.
Scheduling design.
We redrew territories.
Utilization improved without telling workers to “own” the inefficiency.
That felt satisfying.
Not because I beat Hartwell.
Because I applied the lesson where it actually belonged.
Managers should look upstream before charging downstream people for system design.
After Priya’s incident, we also calculated the cost of the corrective controls. Extra review time. Software changes. Training. Someone asked whether spending that much to prevent another forty-thousand-dollar mistake was worth it. Good question. We did not implement every imaginable control. That would create bureaucracy worse than the original risk. We targeted the highest-leverage points: revision verification and document control. Accountability is not only about adding rules after failure. It is about deciding which rules actually reduce recurrence without making competent work impossible.
Click here to continue reading: PART 13: Mia’s first job brought the old Hartwell story back into our kitchen, and I realized the lesson mattered only if the next generation learned to ask questions before silence became normal
I expected my resignation meeting to last ten minutes, but one pay stub forced the CEO to confront a system her own brother had built
Part 12 of 16
