kellypuffs 06000168YK Visits (8373)
Tacit knowledge is the knowledge in your head. Knowledge you haven't shared. Explicit knowledge is knowledge written down and shared. Tacit knowledge is good, but explicit knowledge is better, particularly in a technical support context. In Rational Client Support, we've built a robust knowledge management program, based on knowledge-centered support best practices, aimed to equip the organization to capture knowledge effectively for reuse, not only internally, but outside the firewall as well.
The support engineer on the other end of the phone not only brings to bear his/her own expertise on an issue, but also has at hand our knowledge base built on the collective experiences of the organization and clients to date. We solve a problem once, and then reuse the solution, building upon it as experience dictates.
Capturing knowledge is not something we do in addition to solving problems....it is the way we solve problems.
Shared knowledge IS power.
image credit: (cc) KaCey97007
ASP Announces "Best Web Support" Winners for 2010 .... And IBM Support Portal Made The List!
Earlier this year IBM was nominated for the Association of Support Professionals annual "Ten Best Web Support Sites" award.
And the outstanding news is that we won!
Of course this all came about from concerted efforts across some major disciplines within IBM including our Support Portal Adoption team, as well as our entire support staff's driven work towards adopting a Knowledge Centered Support (KCS) model for ensuring high levels of content relevancy within our knowledge base. Teamwork is the name of the game here, and ASP has identified us at succeeding in working together to make our clients' lives easier when it comes to solving issues!
This is a coveted award in the web support industry and a very, very hard to get accolade- not only is this a major win for our Technical Support staff and Support Portal teams, but is A MAJOR WIN FOR IBM across the board!
So, take a gander at the ASP announcement here and join us in giving all the teams who have worked so hard on the IBM Support Portal to make it what it is today a hearty congratulations and job-well-done!
hat? What do you mean?
"Just in time, not "just in case" is a great catch-phrase that captures our knowledge management practices here in Rational Client Support. And we thought you might be interested in learning a little more about that.
We believe that knowledge base content (in a support context) is different and should be managed differently from other types of technical content, like documentation, white papers, or manuals. Technical Support content is dynamic and needs to be created, managed and delivered for "just in time" accuracy and freshness. A piece of support content is most valuable within the first 30 days of the problem being discovered. Unfortunately, many organizations take 60-90 days to document and release new solutions, which you can see from this graph is ... sub-optimal.
The Acme Co has started fielding support calls about the new bilateral destabilizer functionality, released last week. Sadly, a use case has emerged: if you plan on deploying the bilateral destabilizer underwater (like anyone would EVER do that), you need to make some adjustments in the motor housing.
Acme believes that getting this information out to their clients quickly is far more impactful than investing in a lengthy writing, editorial and review process while clients continue to struggle without this valuable knowledge nugget. Acme certainly doesn't want to continue to field calls about known issues. They want to get the knowledge as close to the clients as soon as possible, so their support engineers can be helping clients with new issues.
We believe the same is true for our business, and client surveys bear this out.
We want to fill knowledge gaps (yours and ours) as quickly as possible. We value accuracy and speed over presentation and format.
That is why we focus on "just in time", not "just in case". Content is created in the context of the issues a client is facing this minute - in the context of a PMR. We're not building an encyclopedia, we are providing solutions. And we create those solutions at the time they are being demanded. We recognize that knowledge is more accurately captured at the moment of using it, not in attempting to recollect it accurately later, which is why we ask our support engineers to capture their knowledge use in the PMR workflow. Capturing knowledge for reuse is not something we do afterwards, if we get a spare minute. It is an integral part of the core business.
Everyone in Rational Client Support is a knowledge worker. And you win.
kellypuffs 06000168YK Visits (3649)
So I was very thrilled to find a new IBM and KCS YouTube video that I just have to share with you.This new video from our friends at IBME
All NFRS blog posts tagged with "kcs".
kellypuffs 06000168YK Visits (2707)
Knowledge-Centered Support (KCS) in five minutes, using the Ignite format: 20 slides, 15 seconds each. Learn why KCS has emerged as the best practice for support knowledge, how it differs from conventional approaches, and how to get started.