Why doesn't this site offer a quick reference quide for new users for core ServiceNow processes

[bluera]

Why doesn't ServiceNow provide a quick reference guide for new users. I am looking for a quick reference quide to provide to new employees that are brought in once a new account is onboarded. They normally do not have an y experience with the tool, and they have to be up and productive two weeks after going live. Is there not a document that exists that provides high level instructions on:

Creating and managing an asset brought in or taking out of an environment

Creating and managing service request

Creating and managing change requests

Creating and managing incidents

Creating and managing problem records as a result of an incident

Creating and managing an asset brought in or taking out of an environment

I work on numerous accounts running service improvement projects and a majority of our technical vendors we use other than ServiceNow have those documents available for their customers, yet I have never seen the same from ServiceNow.

[Sandeep Rajput]

@bluera This can be attributed to varying nature of these processes from one organisation to other. For each of the processes you mentioned there could be some approvals involved in between or there are some custom workflows catering to customer specific processes.

Sometimes a generalised document may confuse a user more who is relatively new to the platform. Hence it is rather a best practice to prepare training manuals covering all the nuances of the process being followed by the organisation. A lot of cues for these processes can be taken from the existing ITSM fundamentals course offered by ServiceNow.

[bluera]

I disagree, when I first started using ServiceNow 15 years ago, we created a Quick reference guide to get the teams started. Very generic and walked them through common generic tasks for change mgmt, configuration mgnt, problem mgmt, Service mgmt and Problem mgmt. If that were the case you would not publish learning modules. This just seems to be laziness on the vendor side I will create my own. We pay so much for licenses and the added value is just not there.