Looking for Advice: How to Store Product Owner Information for Knowledge Transfer

[Ashby0003]

Hi, 

We're looking to improve our process/product owners and I'm curious how people document information a product owner would need to be effective.

Has anyone done a Product owner knowledge base?

[Sean Walters]

Hi Ashby, 

I wouldn't say I have created a product owner knowledge base in my time however what I have done in the past is have a folder structure (within the company's Sharepoint and visible to the necessary people) for the following that helped me with defining best practices on the ServiceNow Platform. 

- Strategy (This folder could have your roadmap and demand process)
- Design (This folder could have your processes for workshops / POC processes)
- Implementation (Development process docs / Ways of working )
- Testing (Ways of working / Process)
- Deployment (Process for deploying standard sprints as well as projects etc)

I hope that helps and this is just one way to structure it , I'm sure there are many other ways to go about it. 

Please mark my answer correct and helpful if this resolves your issue.

[Harneet Sital]

Hi @Ashby0003 

Adding to what Sean posted, the way we did for our customers was we created knowledge articles visible only to product owners and they had it either bookmarked or searched it through the portal. This was all under a knowledge base called ServiceNow and the knowledge base was restricted to publishing known errors from upgrades, and notes for Product Owners, and Developers. 

So think about it from a broader perspective if you are thinking to go via creating a new Knowledge base. 

Thanks
-Harneet Sital (ServiceNow Certified Technical Architect)
Request you to please mark my answer as helpful or correct based on the impact
Find all my ServiceNow articles here

[jodgreen]

I feel like this is similar to figuring out where to store all the non-technical 'tribal knowledge' information about each of our enterprise applications (e.g. IT app owner, business app owner, vendor/rep contact info, licensing renewal dates, .....do you create a knowledge base for that? CI's in CMDB? is this part of the SAM module? We'd like this info to be linked to CMDB data, and real-time licensing information as well, if possible......