Picture a Tuesday staff meeting at a mid-sized DMO. Someone on the digital team pulls up an AI tool that just wrote a week's worth of social captions in four minutes, and they're genuinely thrilled. Two seats over, someone on the visitor services side is quiet, doing the math on what "four minutes instead of four hours" might mean for a role like theirs down the road. And in the back, the person who handles group sales is still writing follow-up emails exactly the way they did in 2019, because nobody's told them whether they're supposed to be doing anything differently.

Same building. Same organization. Three completely different relationships with AI, all happening at once, with no shared understanding of which one is "right."

That's not a broken organization. That's just what this moment looks like almost everywhere in tourism right now. Call it the messy middle: past the point where AI is a novelty, nowhere near the point where anyone has real policies, shared norms, or settled answers.

You're probably already in it. Here's how to tell.

The messy middle usually shows up as some combination of these:

Different people on your team are using AI tools in wildly different ways, with no shared standard for when it's appropriate or how the output gets checked. One staffer treats a chatbot's answer as a rough draft to edit hard. Another treats it as basically finished.

Leadership hasn't said out loud what's off-limits, what's encouraged, or what "good use" even looks like — so people are guessing, and guessing conservatively or recklessly depending on their personality, not on any actual guidance.

Somebody on your team is quietly worried about their job, and nobody has addressed it directly. Maybe it's the person who writes copy. Maybe it's the person who used to build itineraries by hand. That worry doesn't go away because leadership hasn't mentioned AI in a staff meeting — it just goes underground, where it does more damage.

A pilot project or two is running — a chatbot on the visitor website, an AI-assisted research tool — without anyone having agreed in advance what "this is working" would even look like.

If two or more of those are true for your organization, you're in the messy middle. And here's the part worth saying plainly: that's not a failure of leadership. It's what every organization looks like partway through a genuine shift in how work gets done. The failure is pretending you're further along than you are, or hoping the ambiguity resolves itself if nobody names it.

The fix isn't a policy document. It's a conversation.

It's tempting to think the way out of the messy middle is a finished AI policy — three pages, legal-reviewed, distributed by email, problem solved. Write one eventually, sure. But a policy written before your team has actually talked through what they're experiencing tends to answer questions nobody asked while missing the ones that actually keep people up at night.

The more useful first move is a real conversation, and it doesn't need to be complicated:

Name the moment out loud. Tell your team plainly that different people are probably using AI differently right now, that's expected, and you want to talk about it together rather than let everyone guess separately.

Ask what people are actually doing. Not in a compliance-audit way — in a curious way. What are you trying? What's working? What are you nervous about? You'll learn things leadership never sees from the top of the org chart, because your frontline staff, your reservations team, your visitor center volunteers are the ones actually touching these tools day to day.

Say the quiet part about jobs. If people are worried, a vague "we value our people" line doesn't touch that worry. Talk honestly about what you do and don't know about how roles might shift, and what the organization's actual stance is on using AI to augment work versus replace people.

Agree on two or three shared norms, not fifty. Something like: AI-generated visitor-facing copy always gets a human edit before it goes out; nobody feeds confidential partner or visitor data into a public tool; when in doubt, ask. You can build the fuller policy later. Right now, shared norms beat a perfect document nobody's read yet.

This is a training moment, not just a tech moment

Here's where this connects to something we believe deeply at Learn Tourism: this isn't fundamentally a technology rollout. It's a workforce development moment, and it deserves the same care you'd give any other significant change to how your team works.

That means treating it less like a memo and more like a learning experience — a real conversation where people can ask the question they're actually worried about, try something in a low-stakes way, and leave with a clearer sense of what's expected of them. A live session with your actual team, working through your actual tools and your actual anxieties, will do more for your organization's AI adoption than any policy document circulated cold.

Before your next AI conversation

Here's a five-minute exercise worth running with your leadership team this week: go around and have each person name, honestly, where they think the organization sits in the messy middle right now — further along than they expected, behind where they'd like to be, or somewhere in between. Then ask the harder question: has anyone actually said any of this out loud to the full team yet?

If the answer is no, that's your starting point. Not a policy. A conversation.

If you'd like help facilitating that conversation with your team — turning the messy middle into a shared, honest starting point instead of a source of quiet anxiety — that's exactly the kind of session we love building at Learn Tourism. Reach out and let's talk about what that could look like for your destination.