A KCS adoption happens in waves; the number of waves depends on the size of the organization. The first wave is the pilot and is necessary to create internal referenceability and excitement about the program.
At the completion of the KCS Design Session, we create the Adoption Strategy and Road Map. This exercise will help us select an initial group of 20-40 Analysts (Pilot Team) to incorporate the design deliverables into their jobs. Once the pilot is complete, the following responsibilities must be added to the job descriptions for the support organization.
The roles defined by the KCS Practices Guide are:
Successful adoptions have a formal licensing or certification process for the KCS roles. Until recently those programs had to be developed by each company. The KCS Academy (www.thekcsacademy.net ) now offers rigorous certification programs developed by the Consortium members. Industry level certification programs include:
The KCS Coach’s responsibility is to assist in the development of the skills of the Pilot Team members. The Support Analysts in the pilot who demonstrate good coaching skills (patience, constructive feedback, interest in the development of others) are good candidates to coach their peers in the subsequent waves of adoption.
There are a few different approaches to coaching for the Pilot Team:
Before beginning wave 1, the Adoption Team members who created the Performance Assessment Model in the Design Session should establish baseline metrics. This is necessary to track progress. The metrics may be different for each organization but typically include:
The Performance Assessment Model created during the KCS Design Session defines the specific measures that will be used by the organization. This is easy to do for the metrics that are known. For the unknown measures, a baseline must be estimated. How the baseline is estimated is not important as long as the way it is measured is consistent throughout the adoption.
For more information about recommended measures, see the Measurement Matters paper.