Three weeks after Lily and I returned to Denver, I received a message from Lupita that contained only four sentences.
The new training schedule is posted. The complaint procedure is different. People are asking questions instead of pretending everything is fine. I think we are making progress, but I want to see what happens when the next difficult guest arrives.
I read the message twice.
Lupita had never been impressed by announcements, and I suspected she would remain unimpressed by mine. She wanted to see whether the changes survived an ordinary working day, when nobody from corporate was watching and the lobby was busy enough to make shortcuts tempting.
I replied that I agreed with her. Then I asked whether she would be willing to speak with me during my next visit, not as someone who had helped the owner, but as the new Housekeeping Training Lead responsible for evaluating whether our procedures worked.
Her answer came several minutes later.
Yes. But please don't schedule the meeting during room inspections. We already have enough meetings that could have been emails.
I laughed aloud in my office.
It was the first time since the incident that I had laughed about the Grand Regent without immediately thinking of Lily's frightened question at two in the morning.
The hotel was no longer an urgent crisis. Patrick's employment had ended after the formal investigation, Karl was completing his supervised shifts and retraining, and Robert was working under the ninety-day performance plan. The complaint-review changes were in place, and the housekeeping workload assessment was underway.
But the results remained uncertain.
David Mercer reminded me of that during our Monday operations meeting. The Grand Regent's first internal review showed that more complaints were being documented, while the number classified as fully resolved had temporarily fallen. One executive had already questioned whether the new process was making the hotel look worse.
I knew what he meant. Under the old system, a manager could close a complaint after offering a discount or arranging a late checkout. Under the revised process, that same manager needed to record what had happened, whether the guest's concern had been addressed, and what would prevent the problem from recurring.
The new figures were less flattering.
They were also more honest.
"Don't reward the property for making the numbers look good," I told David. "Reward it for finding the problems and correcting them."
He agreed, although he warned me that some managers would resist the additional work.
"They have already started asking whether every complaint needs to go through corporate."
"Not every complaint. Every complaint needs an appropriate response. Significant conduct issues and repeated failures need proper review."
"And if the number of unresolved cases rises?"
"Then we investigate why. We don't change the definition of resolved to make the number smaller."
David wrote that down.
I also asked him to ensure that the same standards were being applied across our other properties. The Grand Regent had exposed a weakness in the reporting process, but there was no reason to assume that the weakness existed only in Chicago. A system that rewarded quick closure could create the same problem anywhere, especially where managers were under pressure to meet financial targets.
We began a group-wide review of complaint handling, staff training, and employee reporting channels. Each property would be assessed according to its own circumstances, but the underlying questions would remain the same: Were complaints investigated properly? Could employees raise concerns without fear? Were managers evaluated on the quality of their decisions as well as the numbers they produced?
The review would take months, not days.
I wanted it to.
A rushed initiative might produce a new manual, a few presentations, and a set of signatures confirming that everyone had completed the required training. A meaningful change required us to discover where the old habits had taken root and why employees had found them easier to follow than the values printed in our handbooks.
Two days later, Robert called.
He sounded more subdued than he had during our first meeting in Chicago. He told me that the new complaint process had created some difficult conversations with department managers, particularly those who had grown accustomed to handling problems informally.
"One manager said the new system makes it harder to use common sense," he explained.
"What did you say?"
"I asked him to give me an example."
"And?"
"He couldn't identify a case where the process prevented a reasonable solution. He was frustrated because he had to explain his decisions."
I leaned back in my chair.
"That distinction matters. We don't want to eliminate judgment. We want managers to be able to explain it."
Robert agreed.
He also reported that the revised housekeeping schedule had reduced the pressure on employees to rush through rooms when unexpected guest requests arose. The first week had been untidy. Supervisors had struggled to redistribute assignments, and several employees had worried that the change would eventually be reversed.
Lupita had helped them identify where the scheduling assumptions were unrealistic. Rather than simply asking for fewer rooms per shift, she had mapped the tasks that routinely caused delays and suggested adjustments based on room type, occupancy, and additional requests.
The revised schedule was still being tested, but employees had begun to raise concerns earlier instead of waiting until the end of a shift.
"She has a good understanding of the operation," Robert said.
"She always did."
He was quiet for a moment.
"I should have listened before."
"Yes," I said. "You should have."
I did not soften the answer to spare him discomfort. Robert needed to recognize that the problem had not been his inability to understand a new policy. It had been his failure to question a system that appeared successful while employees and guests were absorbing the consequences.
He accepted that without defending himself.
Before we ended the call, he asked whether I intended to visit the property again.
"Yes."
"When?"
"You won't know in advance."
He gave a brief, uneasy laugh.
"Fair enough."
I did not tell him the date. Nor did I tell Lupita. If I wanted to see how the hotel behaved under ordinary conditions, I needed to avoid turning my arrival into another performance.
At home, Lily was preparing for a school assignment about family traditions. Her teacher had asked each child to bring a photograph or drawing of something their family did together. Lily had chosen the picture she made in Chicago, with Daniel, the vase of roses, and the enormous hotel windows.
She spread it across the kitchen table while I prepared dinner.
"Can I tell my class about flower day?" she asked.
"Of course."
"Do I have to say Daddy died?"
I put down the spoon.
"No. You can share as much or as little as you want."
She considered that.
"I want to tell them we buy roses because we miss him."
"That's a good way to explain it."
"And that he was bad at dancing."
I smiled. "That part is entirely up to you."
She giggled, then grew thoughtful.
"Will the hotel people be nice to the next little girl?"
I turned off the stove.
"I hope so."
"Do you know?"
"No, sweetheart. I don't know yet."
She looked disappointed.
I pulled out the chair beside her and sat down.
"Do you remember what we talked about in Chicago? About how we can't always know what people will do?"
She nodded.
"Sometimes people learn from their mistakes. Sometimes they need more help. And sometimes they don't change. We have to watch what they do, not just listen to what they say."
"Like when I say I'll clean my room?"
"Exactly like that."
She laughed.
"But you still make me clean it."
"Because I love you."
She gave me a skeptical look.
"That's a very strange way to show love."
I laughed with her, grateful for the ordinary conversation.
Later that evening, I returned to my office to review the first group-wide findings. One property had no significant concerns. Another had inconsistent documentation for reservation complaints. A third had a department manager who routinely closed cases after issuing compensation without checking whether the original problem had been corrected.
The details differed, but the underlying lesson was familiar. Our reporting systems had been designed to help us manage performance. In some places, they had become tools for making performance appear better than it was.
I added a new requirement to the review plan: each property would need to provide examples of complaints that had led to operational changes, not merely a list of complaints that had been closed.
The goal was not to produce a larger collection of paperwork. It was to make sure the company could demonstrate that it learned from what guests and employees told us.
The following morning, I received a message from Lupita with an attachment.
It was a draft of the new housekeeping training guide. The first page outlined the basic room-inspection procedure, but the next section dealt with situations employees might encounter outside their assigned tasks: a confused guest, a misplaced reservation, a family struggling with luggage, or a visitor who appeared distressed.
Lupita had included a clear instruction.
Help when you safely can. If the matter belongs to another department, contact that department and remain available until responsibility has been accepted. Never use departmental boundaries as a reason to abandon someone who needs assistance.
I read the sentence several times.
It was practical, specific, and difficult to misunderstand. It did not tell employees to ignore their responsibilities or attempt tasks beyond their training. It simply required them to treat a person's need as a problem worth solving rather than an inconvenience to be passed along.
I approved the guide for the pilot program, with one request: the reception and restaurant teams should help develop their own versions, using the same principle.
Then I sent Lupita a message.
This is good work. Please make sure the people using it have enough time and support to follow it.
Her reply arrived almost immediately.
That is the part I will be watching.
I smiled.
Three weeks earlier, she had been afraid that speaking up would cost her job. Now she was helping shape the procedures that governed the hotel, and she was already asking the questions management had failed to ask.
It was progress.
Not proof that everything had changed.
But progress.
Click here to continue reading: PART 10: When a Family Arrived With a Reservation the System Could Not Find, the Entire Hotel Had to Choose What It Had Learned
A Sleeping Child, a Crushed Bouquet, and the Receptionist Who Decided We Were Too Poor to Stay
Part 9 of 12
