Skip to main content
Apr 2, 2015 2:49 PM UTC
Question

Request for comment : Content Categories

Dear Champions,

Tech Support is currently working on an initiative aimed at improving customers’ experience with our Knowledge Base. One of the components of the initiative deals with how we can help customers finding the knowledge they need to do “the job they are trying to do”. As a consequence, we are planning to classify our knowledge base articles within the following categories (same categories across all product lines)

  • Install (Installation/Upgrade/Rehosting/Licensing)
  • Use (Usage and General Configuration)
  • Customize (Customization and APIs)
  • Improve Performance and Stability
  • Secure (Improve Security and Vulnerabilities)

We’re looking for some customer feedback on the approach and this is why I’m reaching out to you

  1. Is this breakdown meaningful for you ? Any missing/overlapping category ?
  2. Is this something you think we should also adopt in PTC Community ?

Thanks for your feedback/comments/questions

/Pierre

    9 replies

    Apr 2, 2015 3:04 PM UTC

    For Mathcad, I think there are really only two categories: Install (which I would call "installation and licensing", for clarity) and Usage. Customization and APIs are a subset of Usage. Improve performance and stability would be either part of usage, or part of installation, depending on the article (in Mathcad there are many ways to increase performance that just knowing how to use it better). Improving security and vulnerabilities could also fall under either usage Mathcad has ways to protect parts of the worksheet, and/or the worksheet as a whole from viewing or editing) or installation.

    I wouldn't want to change the current Mathcad sub-forums to the ones you list, but adding a new one for installation and licensing would be a good idea. It would make it much easier for people to find that information.

    Apr 2, 2015 3:22 PM UTC

    Just to be clear Richard, Pierre is talking about a new naming convention for the Technical Support Knowledge Base, and not the sub-communities within Mathcad on PTC Community.

    Apr 2, 2015 3:36 PM UTC

    Question 2 was about adopting this in the PTC community, so I thought he was referring to changing the names of the forums to the ones he lists.

    Apr 2, 2015 10:01 PM UTC

    The better system would be to publish a narrative for each feature - what it's for and why it's done that way against a wiki backdrop to link the descriptive segment of the narrative to the prescriptive description of how to use it as well as problems, corrections, and suggestions. This allows forward and backward links. Eg., items that are controlled in setup can be found by looking at links from the way a feature is used, a fairly common problem source where a feature fails to work because of some set up problem.

    The narratives should be readily available as they should be the controlling documents for software development, listing the initialization/selections required before a function can be performed, and a list of the resulting changes to the data structure as a result of the function. It would also be found in the feature proposal that was approved prior to creating the development spec.

    Pierre_MAuthor
    Apr 6, 2015 8:24 PM UTC

    David, thanks for the feedback. I like the approach and think it would make a lot of sense for product documentation. When it comes to KB articles, we don't really control how customers engage with us. They have a question or a problem and want to get it answered/solved. Some of the customers want to understand where the problem came fro, some want to prevent further problems, but the vast majority is just interested in getting rid of it to resume their work. That's why we are trying to help customers find the right relevant article as fast as possible, and then try to point from the article to the documentation where the narrative should happen.

    Apr 7, 2015 3:11 AM UTC

    You are right. Most people want answers, not explanations, and certainly not understanding. I feel sorry for them because they are very replaceable. If the job can be done via search results, it's not a stretch to replace the job holder with software. Give it 10-15 years and IBM's Watson system will replace most customer support workers and a little beyond that will replace the workers dependent on that support. I suspect it will be hosted on the Google Cloud.

    "Some people might be interested in just subscribing to discussions belonging to the "customization category"

    This could be handled by including a feature like Google does to follow keywords or searches. I am reminded that Yahoo!, Alta Vista, and others did manual rating and classification and the concept failed badly in comparison to link trace evaluation, which can't be applied to the KB, but could be done with a Wiki.

    tl;dr Sure, classify away, but the technique is being superseded by superior methods of information management.