We often talk about how customers want to know what we in support know, as soon as we know it. Publishing knowledge to requestors quickly is one of the benefits of having responders create knowledge in the workflow! However, we recently got a question about how that plays out in practice. Should we really publish … Continue reading Should Not Validated Articles Be Visible Externally?
We always stress the importance of ensuring KCS articles are written in the customer context and are problem-centric rather than solution-centric. We might capture and publish an article on "How to Change a Battery," but if the customer is searching for “my car won’t start,” the likelihood they will find the appropriate article and resolve … Continue reading Context is More Important Than Content for Executive Buy-In
I often think about how the people-side of KCS® is what makes it special. When you read how to implement a KCS program in the Adoption Guide or you reference how to start the Solve Loop in the KCS v6 Practices guide, it doesn’t talk about the relationships you build when you go through a … Continue reading KCS with Friends
The KCS Academy hosted a KCS in Action web session on September 25 about how to improve collaboration between groups who contribute differently to essential knowledge capture in organizations. Watch the recording here (YouTube). With well over 100 attendees tuned in live, the chat window was full of valuable insights and conversation. It’s no surprise … Continue reading Tech Writers and KCS
Vocabulary is important! I propose there are three words we should eliminate from our service and support vocabulary: deflection, avoidance, and consumption. These three concepts are very self-centered; they reflect a vendor-centric perspective, not a customer-centric view. "Deflect" and "avoid" are often used when discussing the value of self-service, as if deflecting and avoiding our … Continue reading Vocabulary is Important
How do we deal with very generic issues or problems that have multiple possible causes? There are two ways to approach this: a master article or a resolution path. While the structure of these types of articles is the same, the intent is different. As a general rule of thumb, we want to have … Continue reading Master Article or Resolution Path?
We always caution KCS design efforts to not “over engineer” the process or the content standard. This is particularly true when it comes to article templates. People often ask, "how many templates should we have?” The answer is ONE… keep it simple! Because many of the KM tools offer us the capability to create different … Continue reading How Many Article Templates Should We Have?
KCS is a significant culture change for most organizations. We are attempting to shift the culture away from recognizing people for what they know, and toward recognizing people for their ability to learn, collaborate, and share. KCS Coaches play an integral role in making this shift, both by helping knowledge workers integrate the new KCS … Continue reading Coaching and Motivation
Big news from the Consortium for Service Innovation: Arnfinn Austefjord joins the staff as the Global Head of the KCS Academy on June 3, 2019. The KCS Academy continues to nurture and support the ever-growing number of KCS practitioners, Certified Trainers, and KCS Verified and Aligned partners, and Arnfinn’s focused leadership will facilitate the growth of this expanding network. … Continue reading Welcome Arnfinn Austefjord, Global Head of the KCS Academy
There are a few important reasons to use the "Work in Progress" (WIP) status in a KCS implementation. First is to preserve the customer context across the life of the case. If the issue takes some time to resolve, as is often the case in moderate to complex support environments, or if we have to … Continue reading Why do we need a WIP?