| NowSpectrum | Issue #7 · Opinion |
Hey {{first_name}}, 👋
This week — a hot take. Most ServiceNow instances aren't badly built. They're badly maintained. Those are very different problems with very different fixes.
The take —
ServiceNow doesn't decay because the platform is weak. It decays because almost every company treats the implementation as a project with an end date, when the platform actually needs ongoing maintenance forever.
The Pattern We Keep Seeing
A company implements ITSM. It goes well. The vendor or consulting partner leaves. Everyone celebrates a successful go-live. Then, slowly, things start drifting:
| → | CMDB data goes stale because nobody owns keeping Discovery accurate |
| → | Catalog items rot — owners leave, nobody reviews if requests still even work |
| → | Business Rules accumulate with no one auditing what's actually still needed |
| → | Compliance evidence gets collected once before an audit, then forgotten until the next one |
None of these are technology failures. They're governance failures — and they all share the same root cause: nobody was assigned to keep the platform healthy after the project ended.
Why This Keeps Happening
Implementation budgets are large and visible. Maintenance budgets are small and invisible — until the year someone discovers the CMDB is 40% wrong, or an auditor asks for evidence nobody has been collecting, or a catalog item that's been broken for six months finally gets noticed.
By the time the rot is visible enough to fix, it's usually expensive enough that fixing it looks like a whole new project — which restarts the exact same cycle.
What Actually Works
The instances that stay healthy long-term all share one thing: someone owns ongoing governance as an actual job function, not a side task. That usually looks like:
| ✓ | A scheduled, recurring review cycle for catalog items, not a one-time cleanup |
| ✓ | CMDB accuracy treated as a metric someone is accountable for, with a dashboard tracking it |
| ✓ | Compliance evidence collected continuously, not assembled in a panic before an audit |
| ✓ | A standing budget line for governance, separate from any new project's budget |
None of this is exciting. It doesn't make a good case study. But it's the actual difference between an instance that's still trustworthy in year five and one that everyone has quietly stopped believing.
| We go deeper on the governance side of ServiceNow — GRC, CMDB discipline, and what actually keeps an instance healthy — on nowspectrum.com | Read the GRC guide → |
— The NowSpectrum Team
| NowSpectrum | nowspectrum.com |