The Green Status That Was Quietly Red

A hotel technology program manager reflects on how optimistic status reporting masks real risks, and shares practical methods to surface problems while corrective action is still affordable.

December 24, late at night, I was on a call rolling one tower back to the old network. We were replacing the network platform at two large resorts while the hotels stayed open, and the in room entertainment system, the one system a guest touches all night, was failing on the new platform. The program had reported green, leaning red, for months. The legacy systems in the rooms were the known unknown: nobody could say how they would behave on the new network until they met it in the production, and everyone on the program knew that risk was sitting there. The calendar offered no room for honesty about it. It was year end, and the date was not moving. So the uncertainty waited, and it picked the worst night of the year to introduce itself.

I have seen some version of that story on almost every large hotel technology program I have worked on. The weekly deck says green, the milestones say on track, and steering ends early. Then, a few weeks before the date, everything shows up at once: interfaces not certified, trainings not done, the vendor three builds behind.

Nobody lied. That's the uncomfortable part. The status was optimistic, rounded up, and a few weeks stale. By the time it turned red, the cheap options were gone.

Why good people report green

Status reporting is a social act first. Green buys a team time and quiet. Red buys scrutiny, extra meetings, and sometimes blame. People learn that early, so they wait a week to see if the problem closes on its own. Often it does, and that's exactly how waiting becomes the culture.

The rounding does the rest. A workstream can sit at 90 percent for six weeks, because the last 10 percent is integration, data cleanup, and property acceptance. The engineer says mostly done, the lead hears on track, the summary prints green. Nobody decided to mislead anyone. The rounding did it for them.

Hotels add pressure of their own. Our dates are tied to openings and brand commitments, and the team receiving the work is running a hotel at the same time. Admitting a slip feels like letting down people you know by name, so teams protect each other with optimism. It's a decent instinct, and it still costs the program its reaction time.

Where the red actually shows up

The warning is almost always there weeks ahead. It just isn't in the status column.

Start with the float. The end date stays put while the plan quietly absorbs a small delay every week. That's margin being spent and reported as progress.

The risk log tells you a lot too. If the same risks show up every week with the same wording, no owner, and no decision date, nobody is managing them.

Then look at what gets squeezed. Testing, training, and cutover rehearsal shrink to make room for delays that happened upstream. On a hotel program that's the worst place to find time, because it depends of property staff who already have a full operation to run.

And listen to the hallway. When someone says "we're fine, as long as," count the conditions. Each one is a red flag that hasn't made it into the report yet.

What I do about it

Asking for honesty louder doesn't work. What works is making the truth cheaper to tell early.

I ask for evidence over confidence: rooms wired and tested, interfaces certified, staff trained and signed off, defects closed. A status that has to point at finished work is hard to round up.

In every review I ask one question: what would turn this red? A fast, specific answer tells me the team is watching the right things. If the room goes quiet, I start asking more questions.

The first early red matters most. Teams calibrate to how the leader reacts the first time. If the first person to raise a flag gets interrogated, the next flag shows up on the last possible moment as a crisis. If they get help, decisions, and cover, the flags start coming while they're still cheap. After the December rollback we moved the program to yellow and kept it there, because the risk had been there the whole time. It was the most honest status we reported on the whole rollout.

I also try to stay close to the work. That means sitting in on working sessions and not just steering meetings, and walking the property during the install. A walk down a guest floor usually tells me more than the deck does.

Every risk gets a name and a decision date, and I review the oldest ones first. Once a risk has an owner and a date, it gets worked like a task. Without them it just sits there.

The color says something about the culture

A program that punishes red stays green until the week it fails. Then it fails late, at the property, in front of guests and owners. A program that rewards early honesty hears bad news while it still costs days instead of months.

My job isn't to demand the truth in the meeting where the date finally slips. It's to make the truth the easiest thing to say in every meeting before that one.

Operations & Strategy Project Management Risk Management Technology Implementation Status Reporting

Federico Grandoso is Senior Manager of IT Portfolio and Program Management at Sonesta International Hotels, based in Las Vegas. He has spent more than fifteen years running hotel technology programs, including roles at MGM Resorts, Marriott, and Starwood, where he opened the first Aloft in Costa Rica.

Comments

Comments for this content

0 comments available
Loading comments...