In which industries are you seeing the level of interest growing for KCS? What is driving it?
KCS had its start in high-tech, and (after 15 years) has clearly crossed into a mainstream practice in tech support–especially high complexity tech support. We’re seeing interest from early adopters in other knowledge intensive businesses, such as insurance underwriting and telecommunications, but little mainstream adoption. Clearly, in regulated fields, KCS has to be implemented differently from enterprise high-tech, but the core principles work well. Across industries, some service desks or help desks are implementing KCS as well.
As things keep getting more complex, I think we’ll see an increasing number of business areas where KCS makes sense. For example, one of my KCS customers manufactures truck transmissions! It sounds surprising, but these components are very complex, and their support operation doesn’t feel that different from a standard technology support center.
For companies that are implementing KCS, what do you see as the biggest challenge(s)? How are companies mitigating the risks?
If you look at any organizational transformation like KCS, the biggest risk is the set of “people” issues–perceived as politics, ineffective middle management, or stubborn end-users. The antidote is leadership–aligning people with a common organizational vision. As one of my customers told me, “people want to do the right thing for the team–they just often don’t know what that is.” Absent Dilbertesque dysfunctions that get in the way of doing the right thing, I think that’s true.
There are many common-sense tools that leaders can use to create alignment–coaching, appealing to people’s motivations, dealing forthrightly with objections, creating a healthy context for measurement and deploying transformational metrics–but the cornerstone has to be clear and honest communication about not just the what, but the why.
What do you see as the key Return on Investment (ROI) that KCS implementators are receiving?
Scale! Every one of my customers is under incredible pressure to do more with less. More customers, more complex products, higher expectations, managed services and on-demand offerings, value-added support…oh, and by the way, your budget is the same as last year’s. If you’re lucky.
For some, the key driver of scale is internal support center efficiencies. Treating more problems as known, or reducing rediscovery, saves significant time every time it happens. Capturing, modifying, and reusing content within the support process greatly increases the capacity of a support team.
For others, self-service takes center stage. Especially if self-service isn’t especially effective today, there’s a tremendous opportunity to not only deflect calls with knowledge, but to deliver far more support than you ever knew people wanted.
But it all comes down to doing more with the same people, or slowing the pace of headcount growth, which is frighteningly unsustainable for some of my more successful customers. So it’s all about leverage.
If you were to look into your crystal ball, what changes do you think we will see to KCS over the next three or four years?
The first area is making collaboration an explicit part of the process. KCS is tightly wedded to case management, and case management applications have traditionally been anti-collaborative: analysts own cases, then they escalate cases, or they requeue cases, but it’s not generally easy just to work together on the cases that most interest you. Support communities are just the opposite, and they seem to do a better job of allocating work. So we need to figure that out.
Of course, collaboration doesn’t end inside the support center. Whether you like the buzzword or not, Web 2.0 works. Why shouldn’t customers participate in the knowledge management process? For example, treating self-service and support communities as two separate things doesn’t make any sense.
The second area is the one I mentioned before: adapting KCS practices to work in regulated, generally lower-complexity environments like financial services.
Finally, I think we’re going to get a lot better at modeling the problem-solving process. A number of my customers are implementing Kepner-Tregoe, for example, and whether it’s K-T or something else, I think we’re going to need to provide more help and structure for problem-solving.
Of course, the great thing about working on a practice as rich and dynamic as KCS is that, three years from now, we’ll have learned a bunch about things we’re not even thinking about now.
Are there any other comments you would like to make about KCS?
The final point I’d like to leave people with is this: done right, knowledge management is the best thing a support leader can do for his or her employees. First, it can relieve some of the unremitting stress they’re under. Second, it can open new opportunities for doing interesting work, like creating revenue-bearing value-added support offerings. Third, it provides recognition for knowledge sharing–something that’s really hard to track without something like KCS. Finally, it moves them up the value-chain, reducing possible concerns about outsourcing or layoffs. So, don’t be concerned about asking them to take on another project; be happy that you’re doing something transformational and wonderful for your team.
You can follow any responses to this entry through the RSS 2.0 feed.
You can skip to the end and leave a response. Pinging is currently not allowed.