Defining governance in ServiceNow projects
I will tell you from the first one, like getting standards. We at Avalara, we firmly believe in using out-of-the-box functionality. And that’s what I’m talking with stakeholders about is that I want to make sure you’re willing to blow up your existing practices, and use the best practices that ServiceNow has identified in this domain to redo the way that you might be doing work today. That’s one of our tenants of governance is out-of-the-box But I will tell you, we do smart customization as well. It’s not a hard and fast, absolutely not every time, but the team has a discussion about it, and if it makes sense, we’ll do something in a customized way. That’s one part of governance. I’ll talk about the second one real quick. Who’s the ultimate decision-maker? Sean, with so many modules out here, I have so many stakeholders. I think I have about 15 of them. And of course, all of their work is number one on their list. But when they throw the list together, that list of 1 through 1,000, we have to draw a cut line somewhere within our quarterly commits. That’s where my amazing TPMs and also my boss and my boss’s boss are able to advocate for “This is our cut line for our capacity, and that’s what we’re going to deliver this quarter.” That to me, governs the two things. The standards you're going to follow, and the best practices, and also who’s the ultimate decision-maker.
https://www.youtube.com/watch?v=t-19GslAuZk