Lessons Learned and Ditches to Avoid
KCS is not something we do in addition to solving problems. It becomes the way we solve problems.
In order for organizations to leverage knowledge as a key asset, and deliver higher value to requestors and customers, we must focus on the source of value: people and knowledge. We must transition from a transaction-oriented model to a knowledge-centric, relationship-based model. We must recalibrate our measurement systems to measure the creation of value, not just activity. We must rethink the role of information, knowledge workers, managers, and requestors to take full advantage of the knowledge that emerges from the experience and interactions of the organization.
In this guide, we have attempted to capture the best we know to date on the techniques for embracing the core practices that make up KCS. These practices, organized in the individual-focused Solve Loop and the system-focused Evolve Loop, represent the essence of KCS.
The Solve Loop:
- Integrate the use, maintenance, and creation of knowledge into the problem solving process
- Make the knowledge “sufficient to solve”
- Let demand drive focus for what knowledge to improve and what knowledge to create
The Evolve Loop:
- Deliver knowledge through self-service
- Identify high value content based on article reuse
- Identify high impact opportunities for improvements (processes, policies, products, or services) based on requestor patterns and trends
These concepts are well established in academic work and research. Many of the concepts in KCS align with the quality concepts of Dr. Deming (see Deming’s 14 Principles). Nonaka and Takeuchi's book The Knowledge-Creating Company was a constant reference during the formative years of KCS.
Why then do organizations struggle with KCS adoption? Because a successful adoption of KCS requires that we rethink traditional processes, structures, measures, and management practices. Change management, and good judgment, is required.
Lessons Learned
Proven success factors make a difference in KCS adoption:
- A KCS Executive Sponsor needs to populate the impact map with goals that support the KCS workflow. They need to fund the infrastructure and resources and maintain support for the team while communicating (in a sustained way) the benefits, strategic impact, and progress of the KCS program. These communications, across their peers, upward to senior management, and downward to the team, provide leadership and motivate the team.
- Communication from executives and within the team should be part of a formal program to help each stakeholder group—the requestors, responders, and organization—understand and support the transition. Glitches and ditches are common, and communications help manage expectations, overcome objections, and deal with exceptions. Audience-appropriate messaging through multiple communication avenues will smooth adoption and help people understand, "What's in it for me?" Do not let the communications plan be too short or superficial—communications are central to change management and need to be both thoughtful and sustained to have a real impact.
- The coaching role, new to many teams, has an enormous effect. When the right people are selected (ideally, by their peers) and given the time and support to coach, KCS prospers. Coaches must have strong interpersonal and influence skills as well as an operational understanding of the KCS Practices.
- The right metrics are based on goals for the outcomes or results and enable trend analysis for the leading indicators or activities. Do not put goals on activities. Through the impact map, we empower and motivate knowledge workers (and managers) with a clear association of their individual activities to organizational goals. A balanced view of the metrics and trend analysis should enable continuous improvement and performance insight.
- Performance should focus on the creation of value by individuals and teams. It must consider both qualitative and quantitative measures and reinforce the transition from an activity-based model to a value-based model.
- The team and its enablers and stakeholders must see KCS as an organizational change, not just a tool. Knowledge management and KCS are about people, not technology. KCS can be assisted by (and assist!) technology, but success is dependent far more on the changes in organizational values, interactions, and processes. KCS offers a different way to think about and manage the value of knowledge.
Judgment is Required
The idea that a good knowledge base will allow the organization to deliver answers using lower skilled, lower cost resources is false. The Solve Loop practices of Reuse, Improve, and Create require people who consistently exercise good judgment. If, in the process of solving an issue, we find a KCS article we feel resolves the issue, we should review the article to ensure that it is relevant and accurate. We must exercise judgment, and we are responsible for the advice we give. If we are uncertain about a situation, we need to get a second opinion, just as we would before KCS. The knowledge base does not reduce the need for good judgment. In fact, the need for good judgment increases.
What did you learn from your KCS adoption?
Some thoughts from experienced KCS Program Managers.
- "The way it is sold to the knowledge workers is important. They need to understand the big picture as well as what’s in it for them."
- "Clear accountability – the managers have to own KCS success. It cannot be viewed as a staff function, or viewed as something extra or additional to handling incidents. KCS has to become a core competency, integral to the business.”
- "Wish we had a better understanding of what we needed for success before we went shopping for a tool.”
- "Understand engineer workflow before switching a new tool."
- "I'm glad we piloted the process and content standard with the tools we already had before purchasing a new tool."
- "Can’t sustain KCS without continuing change and improvement."
- "Have resources aligned. You can not over-communicate what KCS is about and why you are doing it.”
- "The biggest skeptics turned out to be our biggest evangelists...once they experienced the benefits."
- "Reuse counts helped us get the right information on the self-service website."
- "The KCS Practices Workshop was high impact and an important element in our success.”
Familiar “Ditches”
Following are the most common points of failure in KCS adoptions.
Lack of management ownership
- It is important to have a strong staff or KCS Council to support the KCS adoption. Ultimately, the ownership for KCS success must lie with the managers. As a domain moves from Adopting in Waves to Building Proficiency, there is a need to overtly shift the accountability for KCS success from the KCS Council to the managers. KCS is a bigger change for management than it is for the knowledge workers. Having a plan to coach the managers can be helpful in making this transition.
Ineffective coaching program
- An effective way to pick the right coaches is to survey the organization about who they trust. Coaches need to have a belief in KCS and strong influence and interpersonal skills. They don't necessarily need to be subject matter expert.
- Give the coaches time to coach! It is an investment that will pay off.
Not having the knowledge workers design the workflow and content standard
- Let the people doing the work (the knowledge workers) own the workflow and content standard, and keep both simple! While there should be management representation on the KCS Council, management should not be the owners of the workflow and content standards. When management owns those they often over-engineer them.
Not changing the metrics as we expand from Building Proficiency to Optimize and Innovate
- Once KCS has been implemented in an organization, that organization must transform its measurements from transaction-based to value-based. The health and contribution of the value being created can no longer be measured by the time and number of transactions processed. The value must be measured in terms of the effectiveness of the knowledge flow and collaboration that goes beyond the traditional boundaries of the organization, in all directions.
- Traditional support measures will show dramatic improvement in the early phases of adoption. As we start to deliver a high percentage of what we know through self-service, the traditional event-based measures will all go in the “wrong” direction. We must reset executive expectations and understanding of the traditional measures and introduce measures that include customer use and success with self-service.
It's a Matter of Balance
As we said in the introduction, the adoption of KCS represents a transformation. It requires a shift in the organization's culture, values, and focus. It requires a balance of:
Individual and Team
Activity and Outcome
Completion and Evolution
Content and Context
Knowing and Learning
Management and Leadership
We hope this guide has helped launch you your KCS journey. KCS adoption is not a trivial undertaking. It requires both patience and persistence; change is hard!
The KCS Practices Guide reflects the collective experience and thinking of the many dedicated individuals and organizations who make up the Consortium for Service Innovation, as well as the academic work reflected here. We continue to learn and evolve our understanding. The evolution is a function of our Members' courage to try new and therefore unproven ways to address the challenges of change. If you like what you see in the KCS Practices and would like to contribute to its ongoing evolution, please join us. The journey continues!
This guide comes from lessons learned through the collective experiences of Members of the Consortium for Service Innovation, who have also created a Field Guide for KCS Program Management (Member login required).
KCS continues to evolve. If you would like to be part of creating the next version of KCS, become a Member of the Consortium for Service Innovation.
Special Thanks
"The Why Behind Each Practice" was created in the spring of 2023 by a group of Consortium Members who were looking for a way to describe the essence of each Practice, for use as a communication plan to get buy-in and understanding and/or as a sanity-check while designing a KCS program for a specific environment.
It was born out of a Consortium Member session called "KCS with No Staff, No Funding, No Time, and Bad Tools" and reflects the collected experience of the following people. Thanks to each of them for their perspective and feedback!
- Tamara Amlung, pro accessio
- Arnfinn Austefjord, Consortium
- Denise Baldwin, SDL
- Jennifer Crippen, DB Kay & Associates
- Arun Daniel, Dell
- Judith de Jong, SDL
- Karen Eisen, Alida
- Sara Feldman, Consortium
- Victor Feyen, Topdesk
- David Hahn, Humana
- Bret Halford, SAP
- Jenna Hoffman, Intel
- Gerald Joiner, Humana
- Terry Kim, SDL
- Kelly Murray, Consortium
- Mitzi Newland, PAR
- Jason O'Donnell, Autodesk
- Nikki Peck, Humana
- Matt Seaman, Consortium
- Christian Tobbe, Humana
- Carla Verwijs, Sequal
- Jacob Watts, PAR
