“Good.”
The owner added, “And employees.”
“Employees?”
“Yes.”
“Why?”
“Because they see the problem before the dashboard does.”
That became the second reform.
Employees received an independent channel for reporting concerns involving direct managers.
Reports could not be routed back to the same manager.
Retaliation patterns in scheduling would trigger automated review.
No system could eliminate fear.
But the owner wanted silence to become less expensive than speaking.
Then came loss prevention.
The security director reviewed the Seattle incident.
“Our officers handled it correctly.”
“They did.”
The owner nodded.
“But they hesitated.”
“They were under pressure from store management.”
“Exactly.”
He pointed toward the footage.
“I want policy language stronger.”
The director asked, “How strong?”
The owner answered.
“Suspicion must connect to behavior or evidence.”
“That is already implied.”
“I don’t want implied.”
The director nodded.
The owner continued.
“Customer appearance, confidence, clothing, payment method, or perceived status cannot independently justify detention.”
“That’s a long list.”
“Make it longer if necessary.”
The security director smiled.
“You really want this explicit.”
“Yes.”
“Why?”
The owner looked toward the paused footage.
The manager’s finger was frozen midair.
Because ambiguity protects bad instincts.
The next reform involved executive client profiles.
Ironically, the owner hated them.
His account had been coded as restricted because senior executives occasionally purchased gifts anonymously and because customer-facing systems were not supposed to expose sensitive corporate information.
That privacy protection had confused the Sales Associate.
The manager then weaponized the confusion.
The owner asked technology to redesign it.
“Why should the screen say executive access?”
The chief technology officer answered, “To stop employees from changing the record.”
“Then tell employees what action to take.”
The message changed.
Instead of mysterious language, the system displayed:
AUTHORIZED CLIENT. TRANSACTION MAY PROCEED. CONTACT CORPORATE SUPPORT ONLY IF TECHNICAL ASSISTANCE IS REQUIRED.
No status.
No mystery.
Just instructions.
The owner approved it.
“Good systems tell people what to do.”
The CTO smiled.
“Not who to fear?”
The owner looked at him.
“Exactly.”
The Sales Associate became unexpectedly important to the review.
She had considered quitting.
The owner asked to meet her.
Not in the executive office.
In a conference room at the Seattle store after reopening.
She entered nervously.
The owner stood.
“Sit.”
She sat.
He did too.
For a moment, neither spoke.
Then he asked, “Why did you stay?”
She looked confused.
“At the company?”
“Yes.”
She thought.
“I needed the job.”
“That’s the honest answer.”
She smiled faintly.
He continued.
“Do you want to stay now?”
The smile disappeared.
“I don’t know.”
“Good.”
She looked surprised.
“Good?”
“I don’t want gratitude to make your decision.”
She looked at him.
He continued.
“You did your job correctly.”
“Not completely.”
“Why?”
“I stopped talking.”
“After you tried several times.”
“I still stopped.”
The owner nodded.
“Yes.”
She stared at the table.