This week’s discussion around responsibilities surfaced something that comes up a lot when people are navigating the ServiceNow ecosystem.
The instinct is to go wide. Learn to be an admin, a developer, a BA, a PM. Collect certifications. Cover as much ground as possible just to increase your odds.
But as @Uncle Rob shared, depth takes time. Real comfort in a product or specialization doesn’t happen in a few months. It happens through repetition, project work, and experience. Going wide might feel productive, but going deep is often what actually builds credibility.
That same tension shows up in how we distinguish between certain roles that are often mistaken for one another. In the Ask the Experts session Admins Are Not Developers, @Pranav Bhagat highlights how blurred expectations can create confusion, both on projects and in career paths. Understanding what each function is responsible for helps avoid misalignment and sets clearer growth trajectories,
In a couple of weeks, we’ll continue this conversation during an upcoming trainer-led office hours focused on navigating learning paths and entry points into the ecosystem. We’ll look at how others chose where to focus and how those decisions shaped their trajectory.
In the meantime, consider this: are you currently building depth in one area, or spreading yourself across too many at once?
