What are the roles of an ServiceNow Architect?

[Suggy]

What are the roles of a ServiceNow Architect? What does that person do in day-to-day life? 

How depth that person know about a particular product?

How many products knowledge should that person have (out of 100s of ServiceNow products......?)

PS - I am not looking for any official documentation. It would be great if you really give details of what you really do as part of day-to-day activities being a ServiceNow architect. 

[Sajilal]

1)

You are the bridge to take the customer requirement from a business perspective to implement the same in ServiceNow from a Functional/Technical perspective. You also govern, manage, administer the entire end to end instance of ServiceNow not only from the platform perspective with regards to its implementation and health but also the various integrations with external application. lastly you are the guardian of the implementation practices of your Instance. Again more or less is determined project to project and organization to organization!

2)

At least expecting a high overview about the products and its way of work plus usage and value to the customers instead of always bending towards custom scoped apps.

3)

Not necessary to know everything but you can also be an architect around the ITSM area/ITOM area and be a techincal/master architect around the topic 🙂

If this was helpful, do give a thumbs up/mark it as Correct to close the Thread, Thanks

[Suggy]

Thanks for the details 🙂

To me, there should be something like ITSM Architect, ITOM architect, HRSD architect etc and not "ServiceNow architect" because, to my knowledge there is no single person who can know every product out there.

I have seen several projects where customer may CSM, HRSD, GRC, ITOM, LSD etc and we had to pitch in multiple Architects based in the products requirements from customer.

Again, I would say it would still be better to call ITSM SME, ITOM SME, GRC SME etc rather then calling XXX Architects. 

Even if you talk about platform capabilities like IH-ETL, Encryption, Vault etc, not a single Architect knew all those products.

So these are just my thoughts based on my experience 🙂

[Fevzi Yerlikaya]

You need a solid grasp of key modules like ITSM and ITOM, but you don't have to know every product. Being familiar with about 5-10 areas is enough to guide the team effectively.

[Sohail Khilji]

Hi @Suggy ,

See the below attached doc,... that will give you a clarity of this question...