How’s it going for everyone for CRs and incidents?
17 replies (most recent on top)
With the hard cutover to Workday in January, I imagine ServiceNow is soon going to get a lot of use.
The best part of Pac was that pretty much everything you needed to copy and paste was on one page. With SN, you have to click a hundred times to find what you want.
I agree with the post that brought up the rollout. If there is a horrible way to do a rollout, that will be Wells Fargo’s strategy. There is no in depth training. We are missing templates, approval groups, roles, etc. They did the migration and are so busy patting each other on the back, that they don’t see the complete mess this has caused. It will be a much better tool than p2k once we all learn how to use it and figure out ways to get what we need from it despite the sloppy deployment. Because the approval process is so jacked up and has the wrong people as approvers, I can’t wait to see the knee jerk reaction around the first CR that blows stuff up because it didn’t go through the proper approval channels. Sigh.
The vpn people shouldn’t exist either. There’s no reason that we couldn’t automate that to take 24 hrs or less.
PAC was bad.
The lion king group mentioned below shouldn’t even exist. All of that work should be done the rest of the way everyone else does it.
Not sure who PE is.
Change is inevitable.
We have several groups with JIRAs now. Our VPN people have one along with their web form, PE has one, the former wholesale group that switched to a lion king name has one, and many more are coming. It may work for field teams, techs, or call centers but it won’t be a good solution for everyone unless it can be customized to meet the exact needs of each group.
Anyone who likes PAC better has been here too long. Time to move along with your obsolete skills
The tool itself may be an improvement. I’m not going to challenge that. My issue is the abysmal rollout of it. That is was is preventing my team from doing work. We all knew it was coming, but didn’t get training until 4 weeks out and only on some of the high level processes. Integration with tools was not tested. In a month we will have adapted. But the whole “we are going to give you a little bit of orientation, then rollout the tool and expect that you don’t miss a deliverable” approach annoys me. We had ZERO time to test and modify processes from P2K to SN. This the worst rollout of a major application I have ever seen.
@1lzr I was in no way offering glowing praise of PAC.
I'm sure if you're interested in metrics, reporting, and ITIL it's the greatest thing you've ever encountered.
SN is vastly superior to Pac. Much more intuitive, can look up on google how to use various functions and learn best practices. All the information regarding apps/servers/relationships all in one interface without having to jump to 2-3 other apps. Within 3 days most of our team can see great benefits after we become fully acclimated to the software.
The only ones resisting SN in our area are the boomers who know nothing except Pac and refuse to learn new tools. Same people show this behavior when asked to use Teams and will likely be the same when Workday comes out and they have to lose TimeTracker.
"Just because something is new, doesn't necessarily mean it's better"
Well obviously. That's why it's good WF moved to an industry standard like SN, which 5 mins of use proves it far superior than pac2k or even some contemporary options.
I know a lot of people are set in their ways and afraid of any change whatsoever, but luckily SN transition is going smoothly and the response has been overwhelmingly positive. People absolutely hated pac, and are happy to be done with it.
@soj+1dKm1gI0
"Teams are actively avoiding SN. No one likes it. It takes much longer to do anything than our previous procedures - sometimes 3x-5x longer. Multiple teams in my group are switching to JIRA sites instead. Others are setting up their own Sharepoint repositories or using alternate methods to get work done. It will not work without extensive customization so it can be tailored to each group, but management keeps saying there will be no customizations, so its being avoided like a disease."
Those of us who work in platform governance aren't excited to hear this.
Just because something is new, doesn't necessarily mean it's better.
Mainframe computing is back.
It's nice to be using a modern system rather than the shitshow that was pac2000.
Worlds better. Hopefully WF continues to find ways to not be two decades behind the rest of the world
Start calling it "SNOW". They don't like it called that.
Teams are actively avoiding SN. No one likes it. It takes much longer to do anything than our previous procedures - sometimes 3x-5x longer. Multiple teams in my group are switching to JIRA sites instead. Others are setting up their own Sharepoint repositories or using alternate methods to get work done. It will not work without extensive customization so it can be tailored to each group, but management keeps saying there will be no customizations, so its being avoided like a disease.
IME teams that submit work through SNow are avoiding it like the plague.
They all rushed to get CR's into PAC before the cutoff date with the hopes that they could accomplish EOY stuff in PAC and not have to worry about SNow until after EOY freeze.
So it's basically sit and look at it, learn a little, then wait for the actual work to show up.