Backend vs Frontend Taxonomy

[drosenst2]

In your experience, how do you all differentiate the browsing/filtering structure for the backend vs. the frontend taxonomy for knowledge articles? Is it exactly the same or different? Do you match that structure in other HR/IT applications across the board outside of SNOW? 

Also, do you see a big difference categorizing every article to help with Now Assist/Chatbots/AI in general?

I have a lot of thoughts and experience doing this, but don't want to bias the conversation. Any feedback is greatly appreciated.

[David Kay]

Ideally, all the taxonomies in your enterprise will map to one another.  That is, they need not be identical, but each one should be a subset of the others.  For example, the product taxonomy on a case or an incident might need to be three layers deep.  If the taxo used in knowledge is only two layers deep, it should map to the top layers of the incident taxonomy.  In fact, I'd do my best to avoid separate front-end and back-end taxonomies.

I recently lead a taxonomy workshop that included the CFO, because he wisely wanted to make sure that his reports aligned with how the rest of the business talked about product lines and products.

Here are some more detailed thoughts, one of a three-part series: https://www.dbkay.com/knowledge-representation/what-makes-a-good-taxonomy