"You realize most founders spend years trying to make their ideas untouchable."
"Most founders are exhausting."
He looked at her sideways.
"You are a founder."
"I included myself."
The conversation stayed with her.
The original incident had begun with a young manager confusing authority with correctness. Amelia understood that the same mistake could happen at the top of an organization just as easily as at a branch desk.
She had more authority than Webb ever possessed.
That made skepticism around her more important, not less.
At the next executive meeting, she added a standing agenda item: Challenge the Protocol.
Every quarter, one leader had to present evidence that a policy component was ineffective, burdensome, unfair, or producing unintended consequences. The purpose was not to dismantle reform. It was to make sure reform remained open to evidence.
The first presentation focused on training fatigue.
Employees were receiving too many short modules from different departments. Compliance training, cybersecurity training, workplace conduct training, anti-fraud training, service-equity training. Completion rates were high, but retention was dropping.
Lisa Chen proposed consolidating several topics into scenario-based workshops built around real branch decisions.
"People don't experience risk in categories," she said. "A customer interaction can involve fraud concerns, disability accommodation, bias, privacy, and safety at the same time. Training those separately makes the real world look simpler than it is."
The redesign reduced total training hours while improving assessment performance.
Amelia approved it immediately.
The second challenge concerned the customer complaint portal.
Usage had grown so quickly that response times were beginning to slip. The very success of making complaints easier had created an operational problem. Customers were sometimes receiving automated acknowledgments followed by silence for several days.
"A visible complaint channel that feels like a black hole is worse than a hidden one," Amelia said.
The bank added staff and published response-time standards.
The third challenge was more personal.
An anonymous employee survey found that some managers felt employees could invoke "bias" during ordinary performance disagreements as a way to make supervisors afraid of giving feedback.
Some executives wanted to dismiss the complaint as resistance.
Amelia refused.
"If people believe the system can be misused, we investigate that too. Fair process has to protect the accused as well as the complainant."
HR reviewed several cases.
Most concerns reflected confusion rather than abuse. In one instance, however, an employee repeatedly accused supervisors of discrimination whenever his documented sales deficiencies were discussed, despite independent review finding consistent standards across the team.
The bank supported the manager's legitimate performance action while separately preserving the employee's right to raise future concerns.
That case became part of manager training.
"Bias prevention is not immunity from standards," Lisa told a class. "It is a requirement that standards be explainable, consistent, and supported by evidence."
Amelia watched from the back of the room.
She remembered the first week, when some employees had predicted the protocol would make everyone afraid to enforce rules.
The mature version of the system was proving something more difficult and more important: fairness required both protection from arbitrary power and protection of legitimate authority exercised transparently.
The distinction was less emotionally satisfying than slogans.
It was also how institutions actually worked.
Around the same time, Sarah Martinez published a video critical of Metropolitan Trust.