You Don’t Have to Do Everything

[jasminecole]

One of the most important shifts in navigating the ServiceNow ecosystem is realizing that no single person is meant to do everything. This week, we’re focusing on understanding how roles interact across the ecosystem to build clarity around collaboration, expectations, and growth.

The platform spans multiple products, capabilities, and specializations. Admins, developers, architects, business analysts, platform owners, and others all contribute differently. The work becomes much clearer when you understand who is responsible for what and where those boundaries exist.

A helpful starting point is @Uncle Rob 's article, Beginner’s Guide to Understanding ServiceNow Job Roles, a library of insightful podcasts outlining common ServiceNow roles and what their work usually entails.

If your understanding of your role has evolved over time, or if you’ve had to clarify boundaries of your function on a project, feel free to share your experience. Clarity around responsibilities often makes for smoother collaboration and stronger outcomes. 

[Uncle Rob]

If you're trying to break into ServiceNow, you'll have a strong instinct to go wide:
"I'll learn to be a BA,  a PM, a pure dev, an admin, and <insert whatever other 4 process certs"

The problem is you seldom don't realize just how long it takes to learn each of these domains.  
Years ago a customer asked me to do an SPM implementation.  They knew it wasn't a product I specialized in... but they wanted me anyway for other reasons.  It was a solid year of nearly exclusive SPM implementation before I felt *comfortable* with the app. 

You don't have the YEARS necessary to master a wide path just for better odds to START something.

You're far better off aiming at ONE thing, and going DEEP enough on that thing to be marketable.
If you've got more certs than years of experience on the platform, that's a sure fire sign that you know the doctrine, but not the practice.

I'd go one step further than the title of this thread. 
You don't have to do everything?
You MUST NOT do everything!

Consider:  Wide vs Deep

BUT UNCLE ROB, if I'm supposed to go deep, which thing is the best to go deep on for the next X years.  Glad you asked, here's a video I did a few years ago.  And guess what, since that time the ecosystem has shifted radically into things I didn't even know about at the time.  You can NOT predict the future.