Organizing Knowledge Articles - Best Practices

[yundlu316]

Hi Experts, I'm seeking some advice on how to organize a potentially massive amount of knowledge articles.   This is a hypothetical example, but will hopefully help inform our team the best way to organize them.   Suppose we have a bunch of different job titles that are in every US capital:

For each of these combinations there is a unique New Hire document we want to serve up.   So for example, an Analyst I in Carson City will have a different New Hire document compared to an Analyst I in Washington DC, who will also have a different document than a Manager I in Washington DC, etc.   With such a massive combination, what is the best way to organize these documents so that the correct document can be read by the right person?

Does it make sense to have a different Knowledge Base for every combination of these titles/locations?  

Thanks for any suggestions.

[HugoFirst]

Hello David,

You do indeed have a challenging situation here.   I'm sure that there are many options available to you and each will have advantages and drawbacks.   While you have given us a pretty good description of what you're trying to do, before you make your decision, here's some things to think about:

1. How are the authors and maintainers of the documents organized?       Is there one group who does it all?   Or is there a group for each location?

2. How will the users access the articles?   Will they always be interested in only those articles for their location?   Or might they sometimes refer to documents in another location?

3. Will any documents be shared across the locations?   Or does each location contain its own unique set of documents?