ServiceNow Operating Model

[Scott Wallace1]

If you are wondering what an example of an organization ServiceNow operating model might look like, here is a good example. This model is designed to ensure the establishment of a best practice for building a cross functional organization to support the expansiveness of the ServiceNow platform. 

[Jon Miller1]

This is a very cool diagram, Scott. It could almost have been custom made for my organization and where we're heading.

But I am a little confused by the specific "ServiceNow" references (e.g. the evangelist under Innovation). Does this show how ServiceNow is organized? Or is it intended to show a best practice for us to specifically support the ServiceNow platform? Or is it intended to show how ServiceNow specifically can support the entire enterprise? Or is "ServiceNow" just used as an example of a "platform" and I can replace any occurrence of "ServiceNow" for "SAP" (for example)? If it's the latter than I like the diagram less as, for us, the COE and Steering Board are at the enterprise level (as I believe they should be), not per platform.

Also, is the diagram intended to show how an organization can be modeled in ServiceNow (a "digital twin" if you like) in the Rome release? We're only just onto Quebec and I've heard this capability is in Rome but not looked into it in any depth. This would be a powerful "sell" for me to show what will be available in later releases (we may skip Rome and go straight to San Diego next year).

Jon

[lneto]

Is it possible to have an editable version of it?