Having worked at a company with a ServiceNow implementation, I think I'd summarize my experience as: ServiceNow can be transformative when implemented by a comp

Having worked at a company with a ServiceNow implementation, I think I'd summarize my experience as: ServiceNow can be transformative when implemented by a competent team, or utterly useless when not managed well or left as-is upon deployment. Orgs get in trouble by trying to solve internal process inefficiencies and related people problems by throwing ServiceNow at it. The "digital" version of a shitty process is still a shitty process. > But I've never heard a single soul have anything favorable to say about SNOW I've been to the conferences, and there are plenty of folks who love the technology stack, and can do powerful things with it. But I suspect that most people experience the product as an end-user, and that experience is 100% dependent on the team that owns/implements the platform. There's a big difference between "We have a center of excellence for automating manual processes, and ServiceNow is part of that solution" and "We brought ServiceNow in to solve world hunger" .... ("is this thing on??...")