A few years ago, I was working at a large e-commerce company — you know the one, with the smiley arrow. My job was building automations. Workflows, scripts, scheduled jobs — the usual stuff that keeps operations from falling apart.
I was good at it. Or at least I thought I was, until the quarterly review meetings.
"So, how many automations are running right now?" Uh... a lot?
"What's the business value of what your team built last quarter?" Straight face.
"Who requested this automation and why?" I got an email from someone in business ops. We had an internal discussion. I built it.
That was genuinely my answer. Not because I didn't care, but because nobody had set up the infrastructure to track any of this. My job was to develop, not to play accountant. I'd monitor health once a month — sometimes. I'd forget to check on things — often. And when leadership asked me to quantify the value of my work, I had nothing. Just a straight face and a vague sense that things were running fine, probably.
If you've been in that meeting, you already know the feeling.
Here's the thing about enterprise automation that nobody warns you about: the hard part isn't building automations. It's everything that comes after.
Organizations are scrambling to automate. And honestly, the math makes sense — rising operational costs, pressure to move faster, do more with less. So teams build. And build. And build some more.
But here's where it gets messy.
Your finance operations team builds invoice matching automations. Your vendor management team builds automations to add, update, and (hopefully not) delete vendors from ERP systems. Your IT team automates data migrations between systems. Each Center of Excellence operates in its own silo, on its own tech stack, with its own way of doing things.
Nobody's asking "how do we manage all of this?"
And by "manage," I don't just mean keeping the lights on. I mean the full lifecycle — figuring out what to build next and how to prioritize it, actually building it with some discipline, monitoring health once it's live, and ultimately proving that the whole exercise was worth it.
That last part? That's where most organizations completely fall apart. Executive leaders want to know the "worth" of the automation team. What are you bringing to the table? Tech leads scramble to cobble together Excel spreadsheets, periodic email updates, fragmented dashboards — all of which get stale within a week and lost within a month.
What if there was a way to know, every single time an automation runs successfully, exactly how much time and cost it saved? And what if that data just... rolled up automatically?
Turns out, there is. And it's free.
But first — what even is an automation?
I know, I know. If you're reading this, you probably don't need this explained. But I've learned the hard way that people use this word to mean wildly different things, so let me level-set.
An automation is a piece of code that executes itself to reduce manual work. That's it. It encapsulates business logic — "when X happens, do Y" — so a human doesn't have to.
Every time this piece of code runs, it creates an execution record. Think of it as a receipt. It tells you when the execution started, when it ended, and what happened — success, failed, in progress, in queue, not started. Simple concept. The complexity comes when you have hundreds or thousands of these running across your organization, and someone asks, "so... how's it all going?"
That's the question Automation Center was built to answer.
Enter Automation Center
Automation Center is a free product from ServiceNow — yes, free, I'll say it again because people don't believe me the first time — and it fundamentally changes how automation teams work.
Think of it as a command center for your CoE. One place to manage the full lifecycle of every automation in your organization, regardless of how many you have. One of our customers — a large consulting and systems integration company — manages over 6,000 automations across multiple platforms using Automation Center. They're not just users; they're advocates. When a customer starts evangelizing your product unprompted, you know you've hit a nerve.
So what does it actually do? Let me walk you through the five big things.
- Pipeline Management — "Help me, I have an idea"
Here's a scenario. You're in the finance operations team. Every day, you and your team manually match invoices. It's stressful, error-prone, and business-critical. You know this could be automated, but you have no idea how to ask for it or where to go.
With Automation Center, anyone in the organization who has access to ServiceNow can simply log in and raise an Automation Request. Think of it as a "help me!" button with structure.
The requester describes what their process is about, how many people are impacted, and fills in some basic time-and-motion details — takes about 2 to 5 minutes. That's it. No back-channel emails, no hallway conversations that get forgotten, no sticky notes on someone's monitor.
Whether you're in finance doing invoice matching, vendor management updating ERP systems, or any team moving data from one system to another — the entry point is the same. And every request that comes in creates a pipeline. A visible, trackable, prioritizable pipeline.
- Visibility & Prioritization — "What should we build next?"
Now here's where it gets interesting. Once a request is submitted, the system doesn't just dump it into a backlog and wish you luck. It scores the request automatically. The higher the score, the greater the potential impact of that automation.
Your CoE team can now look at a two-dimensional Kanban board and immediately see all incoming requests, their scores, their current status, and associated tasks. No more guessing which automation to pick up next. No more squeaky-wheel-gets-the-grease prioritization where the loudest stakeholder wins.
The highest-scored requests float to the top. Your team reviews, evaluates, and moves cards across the board as work progresses. Every task tied to a request has its own status, so you always know where things stand — not just at the request level, but at the individual work-item level.
Real talk: if you've ever tried to run a CoE off emails and spreadsheets, this alone will change your week.
- Promotion to Production — "Are we actually ready to go live?"
This one came directly from customer conversations, and it's one of those features that sounds boring until you realize how much pain it eliminates.
When we talked to customers, a recurring theme was this: there's no easy, clear way to determine what needs to happen before moving code from a lower environment to production. Teams would forget steps, skip reviews, or deploy without sign-off — not out of malice, just because there was no checklist forcing the discipline.
So now, each Automation Request has a built-in promotion checklist. It gives full visibility into what tasks need to be completed before the request can be marked as published, who owns each task, and what the timelines look like.
It's not glamorous. It's a checklist. But it's the kind of checklist that prevents the 2 AM "why is production broken" phone call.
- Monitoring — "Is everything still alive?"
Automations are built. They're in production. Now what?
Now you need to watch them. And not the way I used to — checking once a month, sometimes forgetting entirely, hoping for the best.
Automation Center gives you a consolidated view of every automation in the system. How many are running, what types they are, what's their health. You can drill into insights and alerts, catch failures before they snowball, and actually understand the state of your automation estate at a glance.
The word "estate" sounds fancy, but when you have hundreds or thousands of automations, that's exactly what it is — a portfolio that needs active management. This is the dashboard that lets you do it without losing sleep.
5. Value Realization — The star of the show
Remember my straight face in those quarterly review meetings? This is the feature that would have saved me.
The Value Dashboard takes every successful execution of every automation and calculates the time saved and cost saved — automatically. No Excel sheets. No manual calculations. No "let me get back to you on that."
Every time an automation runs successfully, the system knows how long it took, what it replaced, and what that means in real terms. And it rolls everything up cumulatively, so when your VP walks in and asks "what has your team delivered this quarter?" — you don't freeze. You pull up a dashboard and show them.
I always hear a cheer from customers when I walk them through this. Not a polite nod — an actual cheer. Because every automation leader has been in that meeting where they couldn't justify their team's existence with data. This fixes that.
Pro tip: If you're pitching Automation Center internally, lead with this feature. Decision-makers care about value realization more than anything else. Show them the dashboard first, and the rest of the conversation gets a lot easier.
"But we don't build everything in ServiceNow"
I hear this in almost every conversation. And it's a fair point.
Most enterprise CoEs don't operate on a single platform. You've got automations built in ServiceNow, sure. But you've also got RPA bots from other vendors, scripts running on legacy platforms, integrations stitched together across tools that were never designed to talk to each other. The reality of enterprise automation is messy, multi-platform, and sprawling.
If Automation Center only managed ServiceNow-native automations, it would solve half the problem. The other half — the half that keeps CoE leaders up at night — is the stuff running everywhere else.
This is where the features I haven't talked about yet come in. And honestly, for teams operating across multiple platforms, these might be the most important capabilities in the entire product.
Connection Manager lets you bring in data from third-party automation platforms directly into Automation Center. Your RPA bots, your external orchestrators, your custom-built frameworks — you can ingest execution data from all of them into one place. Same pipeline view. Same monitoring. Same value calculations. One pane of glass, regardless of where the automation was built or where it runs.
This isn't just about visibility, though. Once that data is inside Automation Center, you can act on it. You can track health, flag failures, measure value — all the things we talked about in the five features above — but now applied to your entire automation estate, not just the ServiceNow slice.
And then there's Recommendations. This one is quietly powerful. Based on what you're trying to automate, the system can recommend which ServiceNow capability is the best fit for the job. Should this be a Flow? An Integration Hub spoke? A scheduled script? Instead of relying on tribal knowledge or whoever happens to be in the Slack channel when the question gets asked, you get a data-informed nudge in the right direction.
For CoE teams managing hundreds of automations across a mixed technology landscape, this combination — ingest from anywhere, monitor everything centrally, get recommendations on what to use — turns Automation Center from a ServiceNow management tool into an enterprise automation management platform. That distinction matters.
And because this is ServiceNow, everything is configurable and customizable. You can tailor workflows, adjust scoring models, build custom dashboards. Though if you're thinking about heavy customization — talk to me first. I've seen what happens when teams go overboard, and it's not pretty. A conversation upfront saves a rewrite later.
The bits they don't put in the product demo
Automation Center does a lot. But I'd be a lousy PM if I only told you the shiny parts.
While talking to customers, I've heard genuine cheers when walking through these features. I've also heard concerns — particularly around the manual effort involved in getting started. If you already have hundreds of automations scattered across systems, discovering all of them and assigning value to each one is real work. Nobody's pretending otherwise.
And there's a broader truth here that I keep coming back to: managing automations — the full 360 — should not be an afterthought. It should be baked in from day one. But let's be honest, most customers are already deep into automation development. They've been building for years. They don't need a lecture about what they should have done; they need a way to get a handle on what they've already done. Automation Center meets you where you are, including retroactive data ingestion so you can surface value from work that's already been completed. All's well that ends well.
But the manual discovery problem? That one stuck with me.
"It is not working!"
This is a story I keep going back to, and not because it's about automation.
Years ago, at the same e-commerce company, I used to sit with the helpdesk team — they were my internal customers. I'd show up early, understand their pain points, figure out what needed automating. I had the luxury of being physically close to the people I was building for.
One morning I was alone in the office. An employee walked in, visibly frustrated, and said: "It is not working!"
That was it. The full problem statement.
My brain went into overdrive trying to figure out what "it" was. The employee kept rambling about how this was impacting his work, how urgent it was, how nothing was functioning — but never once specified what "it" actually referred to.
Turned out to be his email client.
I go back to this memory a lot — not as a funny anecdote (though it is), but as a reminder. Customers aren't always articulate about their problems. Sometimes they know something is broken but can't name it. Sometimes the frustration is real but the root cause is buried three layers deep. The only way to get to it is to sit with them, listen longer than feels comfortable, and keep asking until the actual problem surfaces.
That's how most of Automation Center's features came to be. Not from a product roadmap brainstorm in a conference room. From sitting with customers and hearing the same unnamed frustration over and over until it had a shape.
What's next: the part where AI stops being a buzzword
So the manual discovery problem — the one customers kept flagging. The "I have 800 automations and I don't even know where half of them live" problem.
What if AI could crawl through your ServiceNow instance, discover every automation that exists, classify them, and quantify their value — in about 30 minutes?
Not 30 days. Not a consulting engagement. Thirty minutes.
That's not hypothetical. That's already live. And it's what I'll be writing about in my next post. How a focused, practical implementation of AI helps customers save a tremendous amount of time and cognitive load — not by replacing their judgment, but by doing the grunt work of finding and cataloguing what's already there so they can focus on the decisions that actually matter.
No "AI will revolutionize everything" hand-waving. Just a very specific problem, solved in a very specific way.
Stay tuned.
— Your friendly neighbourhood PM
