What's your KnoweldgeBase creation policy?

[Mark Greenwood2]

I am looking to establish a policy for what conditions warrant creation of a new KnowledgeBase.  I am trying to balance accommodating the needs of the knowledge users with the concerns of having too many KnowledgeBases that it becomes counterproductive.  

Anyone have any best practices that have served them well?  Or perhaps cautionary tales on what to avoid?

[Michele27]

My suggestions:

1. Be clear about the content you want to store in ServiceNow > consider compliance to the organisation's policies around Records Management, Controlled Document Management and Risk Management.  
2. Take a minimalist approach > keep it simple.
3. Who is your target audience?  I have two knowledge bases (1) End User Content - pitched at everyone in the organisation and (2) Technical Content - pitched at our technicians.  Knowledge Blocks and the "Can Read/Cannot Read" checkbox on the article templates are used to further restrict whole or partial content, if required.