Informa helps businesses and professionals in hundreds of ways.

Our international portfolio of live events, world-leading research publications, and innovative digital services provide specialists with the knowledge and connections they need to thrive.

HDI Service & Support World
April 25-29, 2027
Caesars PalaceLas Vegas, NV
6 Ways to Lead When Everything Is Changing

Service is changing at a frantic, dizzying pace. It can be hard to keep up. Not only that, but it’s keeping a lot of us up at night, as we collectively wonder at 3:17 a.m., “How are we going to lead our team through all these changes?”

During a panel discussion at HDI’s Service & Support World, Nate Brown of CX Accelerator, Lee Kemp of PCNA, Phil Verghis of The Verghis Group and Mary Cook, MBA of Slalom didn’t sugarcoat what’s happening in our industry. The change is real, it’s relentless and it’s not slowing down. But they had some hard-won, practical advice for anyone trying to lead through it.

Let’s take a look:


Redefine what “service” means

Before you can lead through convergence, you have to understand what you’re converging toward.

“Service is not just contact center, customer success or customer service,” Kemp says. “Service is how you deliver to your customer. When your organization embraces that, and sees the problems of the business as an entire customer experience challenge, you’re really able to dig into something.”

The org chart is slowly catching up to this reality. Departments that used to operate in silos (marketing, IT, operations, etc.) are being asked to work together in ways they never have. The customer has always seen one company. Now the company has to start acting like one.

“Departments are trying to figure out how to work better with each other,” Cook says. “Enterprise customers look at us and see one company. They don’t care that IT is separate from marketing. They don’t care that operations is separate from technology. The gap between those departments? Customers are feeling it.”


Stop doing two jobs

“Everyone has two jobs,” Verghis says. “The first job is what you’re paid for. The second job is that awful job of doing all the workarounds to make up for the fact that you don’t have the right things to do your first job.”

You know what he’s talking about: the overhead, the escalations, the handoffs that happen because systems don’t talk to each other and teams don’t share a common view of the customer. Good leadership, Verghis says, is about eliminating that second job entirely. Your role is to make it simple, even joyful, for your team to do the right thing the first time.

“When your work moves across streams, across another group, you silently hurt the customer,” Verghis says. “Helping the customer becomes difficult because you don’t have a common view of who they are. Every time you make a decision, look at it through the lens of customer effort. What are you doing and how does it impact the customer? Then, look at the employee effort. Are you making someone else’s life miserable just so your number looks right?”


Think of yourself as a Chief Growth Officer

Whatever your title says on LinkedIn, Kemp wants you to reframe it.

“Regardless of what your title is, regardless of what level you are, your job is to deliver growth,” Kemp says. “You have to have that mindset. It has got to be urgent.”

What does that urgency look like in practice? Kemp says stop waiting for the 12-, 24- or 36-month project to prove your value. Macroeconomic conditions change. Budgets shift. The next disruption is always around the corner.

“You’ve got to focus on ‘how do I deliver value now, so that I have the credibility to get the bigger things done later,’” Kemp says. “That’s how you earn the right to make change at scale.”

If you want to build the kind of team that can keep delivering value without you solving every problem, take a cue from Kemp. He spends 70% of his week in one-on-ones focused on people development.

“You need to free yourself from the burden of trying to fix everything yourself,” Kemp says. “Develop your future leaders so they’re making the decisions and not waiting on you to make them.”


Stop cutting the change management budget

Raise your hand if your organization has ever been through an ERP conversion. Now keep it up if change management was the first line item cut from that budget. Hand still up? We thought so.

“What’s the first thing you always cut when you’re going through a massive technical transformation?” Kemp asks. “Change management. ‘Oh, the leaders can handle that. They can write the communications.’ But they can’t. And it ends up costing you so much.”

The irony: The bigger the transformation, the more likely an organization is to skip what makes transformation stick. Kemp’s point is that when you’re thorough about change management, you can deliver a great outcome for the customer, despite the chaos underneath.


Build trust before you build anything with AI

“We need AI!” Cook hears it constantly from enterprise clients. And she’s not saying they’re wrong, but doesn’t think all of them are ready for it.

“If you don’t have governance in place first, you’re never going to make it,” Cook says. “You have to have the rails down before you send the train out.”

Before any AI implementation, Cook insists clients do two things: clean the data and update the knowledge base. Without those foundations, she says, AI doesn’t work in any meaningful way.


Listen to your team

Convergence starts with conversations, not PowerPoint presentations. It’s all about communicating with the people within your organization about what you are trying to change, what you are trying to lead and what you are trying to converge.

A practical tip from Cook: Befriend your CIO.

“Call your CIO before you need something and invite them out for coffee or lunch,” Cook says. “Build the relationship when the stakes are low, so you have credibility when they aren’t.”

And if you don’t know how to open any difficult cross-functional relationship, Kemp has four words that tend to work every time: How can I help?

“It changes the conversation,” Kemp says. “Even with the most difficult colleague, when you ask that question, you earn credibility. Then later, when you have to push for something they really don’t want to do, you’ve already built the trust to have that conversation.”

Related news

Bridging the Gap: 5 Tips for Cross-Functional Collaboration That Enables AI Transformation

Ask ten executives who owns AI at their company, and you’ll get ten different answers. IT says it’s not their call. Legal gets blamed for slowing everything down. HR figures it’s someone else’s department. Meanwhile, teams are buying tools nobody signed off on, duplicating work and hoping it all sorts itself out. Sound familiar?

Lisa Duerre spent the last year studying why that happens. As part of an applied research project for her leadership consulting collective, RLD Group, she studied where AI adoption breaks down inside organizations, and where it works. The findings from RLD Group’s research helped inform a collaboration on the CONVERSATIONS WORTH HAVING®: The Human Accelerator for Artificial Intelligence Quick Start Guide, which is available as a digital download.

Duerre views organizations through what she calls an I–WE–US leadership framework, defined like this:

  • I: individual judgment and accountability

  • WE: workflows and cross-functional coordination

  • US: governance, decision rights and organizational measures

“All three levels are contributing to the breakdown or the alignment, whether people realize it or not,” Duerre says. “AI is amplifying whatever’s already true in your system. The teams that were disconnected before AI showed up are more disconnected now. The ones that talked to each other are moving faster, together.”

If your company is ready to collaborate better with AI tools, Duerre shared the following tips. Take a look.

Form a cross-functional AI committee

Duerre’s background is in HR, and she says most HR leaders assume AI ownership belongs to IT. It doesn’t, at least not exclusively.

“Ownership needs to sit at the system level,” Duerre says. “Each function carries a piece of it, based on what they do, how well they understand that part of the business and how their work depends on everyone else’s. AI is flattening how we work. You can’t just keep it in your own business unit anymore. You have to look all around you.”

For starters, she suggests building a cross-functional AI committee instead of having one department make all the AI decisions. Legal, IT, cybersecurity and HR should be on the committee, Duerre says.

“If you have a C in front of your title, you should be on that committee,” Duerre says. “That’s how I look at it, because it’s a system-level solution.”

During these meetings, Duerre says you’ll find out that some departments are racing ahead with AI and others are holding back.

“Both sides need to name the trade-offs aloud,” Duerre says. “With teams moving too cautiously, you have to talk about the opportunity cost of falling behind. With teams sprinting ahead, you have to ask them what happens if they don’t bring everyone else along with them.”

Figure out how to use AI strategically

Most companies spent the past two years telling employees to use AI with anything, without much strategy behind it. Duerre says that’s starting to catch up with organizations as finance teams scrutinize the cost.

Her rule of thumb: if you can’t articulate the goal and how you’ll measure success, don’t roll it out yet.

“Teams that use AI well have a strategy behind it,” Duerre says. “They’ve kicked the tires on what they’re trying to solve it for. You need to ask yourself, ‘Which business outcome are we trying to improve, and what must be aligned for AI to create measurable value?’”

Here are a few examples of how to use AI strategically:

  • A company could select a workflow that regularly creates delays, redesign it with AI and test the new approach. Then, measure whether it improves time, cost, quality or capacity.

  • Use AI to support early sales outreach and qualification across markets and languages. AI can help a business reach and assess more potential opportunities, while people remain responsible for understanding the customer and building trust.

  • Flag patterns in customer complaints across multiple channels with AI, so leadership can see recurring problems before it shows up in satisfaction scores.

Check-in regularly during an AI rollout

Duerre recommends a minimum weekly check-in during any AI rollout, sometimes daily depending on complexity. But the format matters more than the frequency. Status updates don’t cut it.

“Ask, ‘What are we learning and what are we surprised by?’ That’s a question that helps you with your check-ins, versus, ‘It’s in three products now and we’ve tested six,’” Duerre says. “That doesn't help, because you’re having these meetings to figure out what’s working and why. If you ask more strategic questions, you can move even faster.”

Publish AI guardrails

Employees who don’t know what’s allowed with AI will either freeze or go around the system entirely, Duerre says. She recommends publishing clear, specific guardrails on what’s okay and what’s not. Come up with some real examples, and pair them with an intake process that doesn’t require writing a thesis to get an approval for using it.

"The approval path should be lightweight, not bureaucratic,” Duerre says. “Something like, ‘If you’re going to use AI, here’s the path. And if it needs approval, here’s three or four quick questions for you to answer.’”

Take employee anxiety about AI seriously

“AI is just a tool” is a phrase Duerre hears at nearly every conference she attends, but she doesn’t buy it.

“Saying it’s a tool is underselling what’s happening at companies right now,” Duerre says. “AI is changing how we work. It’s changing how we lead teams.”

Duerre wants leaders to remember that a lot of employees are fearful of AI. Pew Research Center found 52% of U.S. workers are worried about the future impact of AI in the workplace.

Employees who feel AI is being “done to them,” instead of built alongside them are especially anxious, she says.

“Leaders need to recognize that anxiety is contagious,” Duerre says. “As a leader, this is your opportunity to show up as the safe, steady person who is showing what you’re learning with AI. And don’t be afraid to show how you’ve failed using AI, too.”

Duerre asks every executive she works with: “Who am I with AI?” and encourages them to pass this mindset question along to their employees, too.

“AI is now your teammate,” Duerre says. “Phrasing it as, ‘who am I with AI?’ is different than, ‘what’s going to happen to me with AI?’ You really want your team to feel empowered with AI and show them how it can help accelerate their career.”

Put these ideas into action

Rewiring your organization for AI requires more than the right tools. It takes shared language, practical frameworks, and a willingness to keep learning. Here are a few resources to help you take the next step.

  • Enterprise AI Playbook: Practical frameworks and executive discussion questions to help IT, HR, and business leaders align around AI that delivers measurable value.

  • Work-First AI Use Case Assessment: Identify the workflows where AI can have the greatest impact before you invest in new tools.

  • The REWIRED Brief: Get weekly insights, real-world case studies, and practical advice on leading AI transformation.