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
Making Knowledge a Force Multiplier in Service Operations

Shift left works when knowledge is part of how work gets done, not something added afterward. In our service desk, we learned this the hard way. When knowledge capture felt like extra work, especially when you are dependent on Tier 2 and Tier 3 teams, it slipped. When we embedded it into daily operations, took ownership instead of waiting, the results followed.

Today, knowledge is not perfect or fully standardized, but it is actively used and reinforced in ways that materially improve service outcomes.


Knowledge as a byproduct of solving

We do not treat knowledge creation as a separate task or a documentation project. Knowledge is created and improved as issues are resolved. In practice, that looks like this:

  • Analysts search the knowledge base early when working an issue
  • If an article helps, it gets linked to the ticket
  • If something is missing or unclear, the article is flagged with relevant notes to be updated
  • If no article exists, a draft or update is captured while the solution is fresh

This approach keeps content grounded in real demand. Articles change because they are used, not because someone scheduled time to clean them up. Over time, this has reduced repeat work and helped analysts resolve more issues without escalation.


How knowledge shows up in daily operations

We do not yet measure knowledge health through a dedicated scorecard. Instead, we see its impact through service outcomes we already track and review regularly.

  • First contact resolution stays consistently above target when knowledge is current and used
  • Customer satisfaction remains high because answers are consistent regardless of who takes the call
  • Resolution times improve when analysts can reuse known solutions instead of starting from scratch
  • New analysts ramp up faster because they rely on documented fixes rather than tribal knowledge
  • Self-service adoption increases as articles become clearer and more reliable

In our operational reviews, strong performance is often tied back to “knowledge discipline,” rather than any single tool or process change. When articles are flagged, updated, and reused, the metrics move in the right direction.


Coaching knowledge behaviors as they exist today

Knowledge behaviors are reinforced through regular coaching. Team leads regularly bring knowledge into their conversations with agents, especially when reviewing tickets or quality feedback.

Typical coaching prompts include:

  • Did you check the knowledge base before escalating?
  • If you used an article, did you link it to the ticket?
  • Was the article accurate or did it need an update?
  • If this was new, did we capture what we learned?

These conversations happen in 1:1’s, ticket reviews and informal follow-ups. Opportunities vary from time to time, but the expectation is clear: using and improving knowledge is part of doing the job well. Over time, this has helped shift the mindset from “close the ticket” to “leave the desk smarter than you found it.”


Where we are still uneven

It is important to be honest about maturity. We are not operating a fully institutionalized KCS model today.

  • Knowledge metrics are inferred from outcomes rather than tracked directly
  • Reuse and linking are encouraged but not yet measured consistently

Despite this, the behaviors are real and producing results. The lack of perfection has not stopped progress because knowledge is already embedded in the flow of work.


Conclusion

In our service desk, knowledge is a force multiplier because it is used, discussed and improved every day. We see its value through higher first contact resolution, strong customer satisfaction and faster analysts ramp up. While our practices are still evolving and uneven in places, knowledge is clearly part of how we operate.

For service desk leaders, the takeaway is simple: you do not need a perfect framework to get value from knowledge. You need to make it visible in daily work, where reuse drives continuous review. In KCS, knowledge improves through use, not through isolated perfection efforts.

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.