A new leader can walk into a room with an impressive plan and still miss the most important information in it. The schedule may look sensible. The organizational chart may be accurate. The strategy deck may even be beautiful. But none of those things tells you what people have learned to work around, which promises they trust, or why a reasonable policy is difficult to use on a Saturday afternoon.
That is why my advice to a leader entering a new team is simple: before you announce how the culture will change, learn how the culture actually works.
This is not an argument for waiting forever or avoiding difficult decisions. It is an argument for making better ones. Across hospitality, attractions, entertainment, and communications, a leader inherits more than a set of goals. They inherit relationships, habits, frustrations, talents, and the memory of promises that were either kept or forgotten.
Do not mistake the organization chart for the organization
An organizational chart tells you who reports to whom. The daily operation tells you who people actually turn to when something goes sideways. Sometimes those are the same people. Sometimes they are not.
There may be a frontline employee who quietly teaches new hires how to navigate a complicated process. There may be a supervisor who knows how to calm a tense situation without making a guest feel like a problem. There may also be an invisible rule that nobody questions because, three leaders ago, someone got criticized for doing things differently.
Those are not side stories. They are clues about your real operating system. If you introduce a new standard without understanding the informal one, you may accidentally remove the very thing keeping the experience together.
Listen in three directions, not just upward
New leaders naturally spend time with the people who hired them. They should. Expectations, budgets, and strategic priorities matter. But that is only one part of the picture.
Listen upward to understand what the organization is trying to accomplish and which decisions cannot wait. Ask how success will be measured and where leaders believe the greatest risks sit.
Listen across to find the moments where one department’s success depends on another department’s work. Ask what information arrives late, which approvals routinely stall, and what coordination looks like when the schedule is full.
Listen close to the work by hearing from the people serving guests, answering phones, maintaining spaces, opening doors, managing queues, or resolving issues. Ask what makes a great shift possible and what repeatedly gets in the way.
People closest to the experience often have the clearest view of friction, although not always the authority to remove it. Leadership should change that equation.
Look for the difference between a preference and a pattern
Not every frustration requires a new policy. Not every request should become a priority. An effective listening tour is not a suggestion box that automatically turns into a to-do list.
Instead, look for repetition. If one person says a handoff is confusing, investigate. If several roles describe the same missing information at the same point in the day, you may have found an operating problem. If new employees consistently ask the same question, the training might not be doing its job.
Pair conversations with evidence. Review guest comments, employee feedback, staffing realities, training materials, existing standards, and the decisions leaders are asked to make over and over. Some problems look like attitude until you examine the process that produced them.
And remember that a beautiful solution nobody can execute is still a problem. A new form, dashboard, or approval process can create extra work if it does not address the real bottleneck. The goal is not to prove you can introduce something new. The goal is to make the work clearer and the experience better.
A practical first-30-days approach
Days 1–10: Observe with intention. Meet people in different functions and on different shifts. Study the guest journey and the employee journey. Learn the existing language of the operation. Write down patterns without rushing to assign blame. Be clear about which urgent safety, compliance, or service issues you will address immediately.
Days 11–20: Test what you think you heard. Bring the recurring themes back to the people doing the work. Ask whether you understood the problem correctly. Separate improvements you can make quickly from decisions that need resources or broader agreement. This step matters because leaders can turn a single memorable conversation into a false generalization.
Days 21–30: Choose a few visible commitments. Identify one friction point you can responsibly remove, one existing strength you can protect, and one larger issue that requires a plan. Name an owner, explain the next action, and set a date for an update. Then actually provide the update.
Thirty days will not reveal everything. It can, however, establish whether your leadership means another round of announcements or a more dependable way of working.
Trust is built by what happens after the conversation
Here is where many well-intended listening efforts stall: people share useful information, leadership thanks them, and nothing visible follows. Eventually employees stop believing the invitation to speak is worth the effort.
Not every idea can be adopted. Sometimes the answer is no. Sometimes a constraint is real, a budget is not available, or a change would create a bigger problem elsewhere. Explain that. A respectful explanation is more useful than a warm promise that disappears.
Closing the loop sounds straightforward: Here is what we heard. Here is what we can do. Here is what we cannot do yet. Here is when you will hear from us again. But it requires consistency, especially when the answer is not exciting.
For leaders who want to earn credibility, follow-through is not a communications accessory. It is the work.
Protect what is already good
One of the quickest ways to lose a capable team is to treat everything you inherited as evidence that the previous leadership failed. Sometimes a team has built a remarkable experience despite limited resources. Sometimes a tradition matters because it makes employees feel connected. Sometimes the unofficial workaround is a signal of ingenuity, not resistance.
Ask what should not change. Recognize the people already making the organization better. Give credit before claiming credit. Then invite those people into the improvements that genuinely need to happen.
I write in Chasing Magic: How Experience Changes Lives and Shapes Leaders about the relationship between feeling seen and creating meaningful experiences. That belief belongs in the first days of leadership as much as it belongs in daily operations. People are more likely to help build a stronger future when they know the work they have already done matters.
For more practical thinking, explore Chasing Magic Insights, discover my approach to consulting and workshops, or learn about Chasing Magic.
The strongest opening move is not to arrive with every answer. It is to create enough trust, curiosity, and clarity that the best answers can finally surface.
Leadership gets practical when the idea can survive the next shift.
Explore more essays on guest experience, operations leadership, employee experience, and the everyday decisions that shape how people feel.
Browse all Insights