Tuesday afternoon I was in pre-op, getting ready for a minor procedure. My nurse was getting me set up, and I asked her what she thought about AI.

She got quiet for a second. Then she told me she had three kids — high school and college age — and she didn't know what kind of future they were going to inherit. What work would look like for them. Whether any of the things they were studying would still matter by the time they graduated. She wasn't hostile about it. She wasn't dramatic. She was just a parent doing the math, and the math was scaring her.

Coincidentally, I'd spent the morning writing an intelligence brief about OpenAI — nine hundred million weekly users, a company valued at three-quarters of a trillion dollars, an industry that didn't really exist five years ago and now can't be ignored by anyone. And sitting there in a hospital gown talking to someone with three kids and real concerns, I thought: this is the actual story. Not the valuation. This.

Because AI is coming whether we're ready or not. For the nurse. For her kids. For every employer in this valley deciding right now whether to get ahead of this or just wait and see.

Which brings me to today's conversation.

If you've been keeping track, you know that I've been scanning local job boards every week or so since January 11th. Indeed, LinkedIn, the usual. Looking for any Coachella Valley employer publicly posting a role that requires actual AI skills — not "proficiency in Microsoft Office," actual AI. For two and a half months: nothing.

Today that changed. Agua Caliente Resort and Casino posted an AI Product Manager role.

Now I want to be careful — I'm not hitting every employer in the valley, and I'm not claiming this is a comprehensive audit. But when Agua Caliente, one of the region's largest employers and a genuine training ground for the valley's hospitality workforce, puts something like this on the public internet, it matters. That's a signal. A real one.

So yeah. Hallelujah, and flowers to you. I mean it.

Being the AI nerd that I am, I decided to spend some time with the job description. I mean, why not? And based on the scope — lifecycle management, governance, vendor evaluation, risk assessment, data ownership — I sleuthed that this role likely came out of IT, maybe with some product or digital team influence. Generally, that's where most organizations start, and it makes sense. Agua Caliente isn't a tech company. They're a hospitality company, a gaming company, an employer of thousands of people who show up every day to serve guests. Of course IT is where this starts.

But here's the nuance I also uncovered: they're still figuring it out. And that's okay. Most organizations are. The job posting is a beginning, not an arrival. The question I have now is how they run this thing once they hire someone — and that's where I want to spend a minute.

Most AI rollouts that fail don't fail because of the technology. They fail because nobody built the conditions for the technology to actually land. And the conditions almost always break down in the same two places.

First: the workforce was never in the room.

AI sentiment nationally is trending negative right now. Almost 50% of those surveyed want very little do with it. That's not speculation — that's what the data shows.

Here's a reasonable assumption: at least half of Agua Caliente's workforce has some degree of concern about AI. Some are curious, sure. But a meaningful number are quietly worried — about their jobs, about being tracked, about being replaced by something they don't understand. And some are genuinely fearful. Not irrational fear. Real, grounded, human concern.

If you launch an AI initiative without creating space for that to be said out loud, you don't make the fear go away. You just make it go underground. And underground fear is far more destructive to adoption than open fear, because you can't address what nobody will say.

So before anything else — before the vendor evaluation, before the pilot, before the rollout plan — create safe spaces for the conversation. You don't need every employee in a room at once. You don't need a town hall. But you need spokespeople from every department at the table. Operations, F&B, gaming floor, housekeeping, HR, finance, guest services. Each of those departments has a culture, a set of concerns, and workers who will either carry this thing forward or quietly kill it. Give them a seat before you ask them to adopt anything.

That's not soft work. That's the hardest and most important work. And most organizations skip it entirely.

Second: the external-facing tools go live before the internal foundation is built.

This one I see constantly. The instinct is understandable — you want to show something, you want a win, you want to be able to point to AI in action. So you build a guest-facing chatbot, or an AI concierge, or an automated reservation tool. Something the customer sees.

And then it struggles. Not always because the technology is bad. Because the staff behind it doesn't trust it, wasn't trained on it, doesn't know how to handle edge cases, and in some cases was never told it was coming. The guest experience suffers. The employees feel undermined. And suddenly AI isn't a tool — it's the thing that created a problem.

The pattern is the same every time.

In my opinion, the better order is go internal first. Build tools that make your staff's jobs easier — scheduling, reporting, shift communication, internal knowledge bases, whatever your people actually need help with. Run small pilots. Let people get comfortable. Let them develop opinions about what works and what doesn't. Let them become the advocates, because they will be — if you give them the chance.

When you eventually do go external-facing, and you should, you'll have a team behind it that trusts the technology because they've used it, not because they were handed a training module and told to get on board.

If I were sitting across from the Agua Caliente leadership team right now, not that anyone's asking, here's where I'd start:

Do your employees feel safe using AI — or are they quietly ignoring it? There's a real difference between an organization that says it supports AI adoption and one that has actually created psychological safety around the conversation.

Do you have a real AI policy, or are you making it up as you go? Most teams are making it up as they go — that's not a dig, that's just where most organizations are in March 2026. Just keep in mind, "we'll figure it out" is not a strategy. It's a way to arrive at the same broken rollout faster.

And who owns this across the organization? If AI is owned only by IT, it will stay inside IT. The role needs authority that reaches across departments, or the person you hire will spend most of their time navigating internal politics instead of actually building anything.

Which is where I want to leave this.

The nurse in pre-op this morning wasn't asking about platform architecture or model benchmarks. She was asking whether her kids were going to be okay. That's the question underneath all of this, for almost everyone who isn't already inside the AI conversation.

For every employer in this valley making decisions about AI right now — and soon that will be all of you — the most important thing isn't the tool you pick or the hire you make. It's whether you've created a space where the people in your organization can ask that same kind of question honestly, without feeling like the answer is already decided.

AI can absolutely elevate and augment the humans around it. I believe that. But it doesn't happen automatically, and it doesn't happen fast, and it certainly doesn't happen when the rollout ignores the people it's supposed to help. The fear doesn't go away because you deployed something. It goes away because someone sat down and had the conversation.

That's the work. It's slower than a job posting. It's harder to put in a press release. And it's the only thing that actually sticks.

Congratulations, Agua Caliente. Now the real work begins.

Sat Singh hosts SunshineFM from Rancho Mirage. This morning he was in pre-op. This afternoon he was writing about AI. It's that kind of year. He's fine, by the way.

Until next time, wishing you blue skies and sunshine.

— Sat