An employee could ask a passenger to cooperate. That did not mean the passenger was obligated to surrender a confirmed seat for someone else's convenience.
The discussion continued for two hours.
Employees examined examples involving delayed flights, passengers with accessibility needs, conflicting reservations, and requests from high-status customers.
Denise insisted that the class identify the relevant facts before choosing a response.
If a passenger needed assistance, what assistance was required?
If a seat had been incorrectly assigned, what did the reservation system show?
If the aircraft configuration had changed, what operational constraint existed?
If a passenger refused a voluntary change, what rule permitted further intervention?
The questions were repetitive by design.
The goal was to establish a habit of reasoning that would remain available when the cabin was crowded, the boarding clock was running, and a dissatisfied customer was demanding an immediate answer.
Near the end of the session, Denise returned to the first scenario.
A passenger had purchased a premium seat.
Another passenger preferred it.
The second passenger had a high loyalty status.
The first passenger declined to move.
"What should the employee do?" she asked again.
This time, the answer came from several people at once.
"Respect the confirmed assignment."
Denise nodded.
"Good. And if the second passenger complains?"
"Explain the policy and offer whatever legitimate alternatives are available."
"And if the passenger threatens to complain to senior management?"
"Follow the policy anyway."
Denise smiled faintly.
"That's the answer."
Emily wrote the final sentence in her notebook.
She did not know whether the lesson would make her a better flight attendant.
She knew it had forced her to reconsider a belief she had once held without examining it.
She had thought that good service meant preventing the most influential customer from becoming unhappy.
Now she understood that good service sometimes meant allowing a customer to be unhappy because the alternative would be to treat someone else unfairly.
That was a more difficult kind of professionalism.
It was also a more honest one.
Meanwhile, Whitmore Systems was changing the way it handled client requests.
The new policy was introduced at a company-wide meeting.
Nathan stood at the front of the main conference room while employees joined remotely from offices across the country.
Behind him, a slide displayed three categories.
Contracted work.
Authorized additional work.
Discretionary assistance.
He explained that all three could be legitimate.
Contracted work was the service the client had purchased.
Authorized additional work was work the client had agreed to buy through a separate approval.
Discretionary assistance was work the company chose to provide as a courtesy.
The problem had arisen when the categories became indistinguishable.
"When an engineer receives an additional request," Nathan said, "the engineer should not have to guess whether refusing it will damage the client relationship. The account manager should not have to guess whether the work is included. And the client should not have to guess what will happen when it requests something outside the agreement."
He paused.
"We are not eliminating generosity. We are eliminating the expectation that generosity must remain invisible."
A few people nodded.
Others watched the screen in silence.
Nathan understood why some employees were concerned.
They had built careers on being the people who could solve difficult problems quickly. They took pride in responding when others could not.
The new policy might appear to challenge that identity.
Nathan wanted them to understand that it did not.
"We will still respond to emergencies," he continued. "We will still help clients solve difficult problems. We will still make reasonable accommodations when circumstances justify them. But we will document the decisions, account for the resources, and make sure the people performing the work are not left to absorb the consequences without support."
He glanced toward Daniel.
"That includes me. If I request work outside the established process, the request will be documented just like anyone else's."
After the meeting, an engineer named Samuel Ortiz approached him.
Samuel had worked at Whitmore for eight years. He was one of the employees who had handled a large share of Blue Ridge's informal requests.
"Can I ask you something?" Samuel said.
"Of course."
"Will this make us less responsive?"
"It might make some requests take longer to approve."
Samuel nodded.
"That's what I'm worried about."
"Then help us make the approval process efficient."
"But the point is to stop people from asking for exceptions."
"No," Nathan said. "The point is to stop exceptions from becoming invisible."
Samuel looked thoughtful.
Nathan continued.