The foundation Now Platform product. VanPaulTek designs, architects, builds, implements, and supports every ITSM process — from a scratch install to a production platform running for years.
ITSM (IT Service Management) is where most ServiceNow journeys start. It's the foundation for how IT captures work, controls change, restores service, and communicates with the business.
Done well, ITSM is invisible — tickets flow, changes ship, SLAs are met. Done poorly, it becomes a ticketing system that nobody trusts and everyone routes around.
VanPaulTek's ITSM practice sits at the intersection of process design and platform engineering. Every consultant on our ITSM team has stood up production ITSM instances — we design what we can build, and we build what we designed.
The processes that make up a modern ITSM practice — configured, integrated, and supported by one team.
Detect, respond, restore service. The most-used process on the platform and the one users judge you on.
Move beyond ticket closure — find root cause, ship permanent fixes, track known errors.
Approvals and CAB workflows without becoming bureaucratic. Change safely — and quickly — at scale.
Service catalog design, request workflows, fulfillment automation. The self-service front door.
Article lifecycle, agent contribution, self-service deflection. The multiplier for every other process.
SLA / OLA / UC definition, tracking, breach management, executive reporting.
The consumer-grade catalog experience that drives adoption. Design, taxonomy, governance.
Configuration data foundation. Without a trusted CMDB, change and incident impact analysis fail.
Design, architect, develop, implement, and support — five phases, one accountable team.
Process and experience design — this is where value or waste is baked in.
Technical architecture that will scale for 5+ years without a re-platform.
Configuration + code, delivered in sprints with test coverage from day one.
Cutover with a real playbook — not hope and a Friday deploy.
Ongoing operation — because Day 2 is where most implementations fail.
Sample roadmap based on real implementations — adjustable to your scope, but grounded in what actually works. Not vendor marketing timelines.
Practical fixes that don't need a project charter. Ordered by timeframe and impact — the stuff experienced practitioners just do.
Grep system logs for repeating error patterns — often one broken Business Rule accounts for 30%+ of noise. Comment it out, root-cause later.
Simple SLA + workflow: incidents in Resolved state auto-close after 3 business days. Kills the 'incident zombies' problem no one wants to touch.
Identify your 5 most-common standard changes (server reboots, VLAN adds, cert renewals). Move to Standard Change template with auto-approval — saves ~20 hours/week of CAB time.
One config toggle. Agents get relevant articles inline — first-call resolution jumps 8–15% within 60 days.
If >5% of your tickets are categorized 'Other', reporting is meaningless. Force categorization on close; retire 'Other' after 30 days of guided taxonomy.
For P3+ incidents, Now Assist can generate a case summary paragraph in 2 seconds. Handoff quality goes up; L1→L2 friction drops.
Every stale Update Set is technical debt. Clean quarterly. Fewer surprises during family upgrades.
Find the notification group with 40+ people that no one actively reads. Break it into service-scoped lists. Everyone gets fewer, more relevant notifications.
Catalog governance dies from bloat. Retire the bottom 20% every quarter. Users find what they need.
Real KPIs and targets from mature implementations. Track these; if they trend the wrong way, something is off.
L1 resolves without escalation. Poor knowledge = poor FCR. Baseline first, then improve incrementally with knowledge investment.
P2 = business impact. If this drifts up, your routing, knowledge, or capacity has a problem.
Change success is where operational maturity shows. <90% = process too loose or too heavy.
Requests deflected via portal + Virtual Agent. Requires investment in knowledge + catalog UX.
SLA breaches signal misaligned expectations. Sometimes the fix is the SLA target, not the ops team.
Median beats average — a few very old tickets skew average and hide the healthy tail.
Health = discovered CIs / expected CIs, weighted by class importance. Trust = velocity.
The insurance policy for upgrades. Under 60% and every family upgrade is a coin flip.
Honest warnings from many deliveries — the mistakes that cost time, money, and adoption. These aren't in vendor guides.
Why it fails: Data migration cost scales exponentially with historical depth. Nobody actually queries 5-year-old incidents; the archived reports satisfy audit.
Do this instead: Migrate 6-12 months live; archive the rest to read-only reporting. Saves weeks of migration work and instance performance.
Why it fails: UI Actions look easy but break under multi-user race conditions, don't survive upgrades cleanly, and can't be tested via ATF.
Do this instead: Default to Flow Designer for any workflow logic. Reserve UI Actions for genuine UI-only interactions.
Why it fails: You won't. Every skipped test becomes a manual regression run before every upgrade — one Utah → Vancouver upgrade eats the time you 'saved'.
Do this instead: ATF coverage on every workflow, day one. Target 60% by go-live, 80% within 6 months.
Why it fails: Vendor demos are optimized for wow-factor, not your operational reality. Data model shortcuts they take will haunt you.
Do this instead: Design your data model in a fresh dev instance. Reference the demo for inspiration, not for copy-paste.
Why it fails: Every class you populate needs a data source, reconciliation strategy, and owner. Empty or stale classes destroy CMDB trust.
Do this instead: Start with 20-30 classes tied to real business services. Grow the model when demand and data both exist.
Why it fails: Users can't find anything; governance collapses; abandoned catalog items multiply. Big catalogs signal 'no owner'.
Do this instead: Launch with 20-30 most-requested items. Add via governance process. Retire yearly.
Why it fails: Every extra approval step delays value and gets rubber-stamped. Approval theater teaches users to route around the tool.
Do this instead: Reserve approvals for actual risk gates. Auto-approve where the risk is <1% and the value of speed is >10x.
Why it fails: Legacy integrations accumulate — each survives 'just in case' — and each is a maintenance liability during upgrades.
Do this instead: Quarterly integration health review. Retire anything with <10 messages/day and no owner.
Why it fails: You end up building processes no one respects — the shape of ITIL without the substance.
Do this instead: Use ITIL vocabulary; size the practice to your organization. What matters is that work flows, not that the process diagram is complete.
Stand up a new ServiceNow instance from scratch with Incident, Change, Request, Knowledge, SLM, and CMDB.
Migrate from Remedy, Cherwell, Service Manager, or homegrown tools — with data preserved.
Inherit an existing instance that's underperforming — stabilize, refactor, and get it healthy.
Redesign your Incident or Change practice to reduce MTTR and increase change velocity.
Rebuild a stale catalog with governance, taxonomy, and a modern Employee Center storefront.
Define real SLAs with measurable targets and executive reporting.
A focused ITSM foundation (Incident, Change, Request, Knowledge, basic CMDB) usually 3–5 months. Multi-module rollouts with heavy customization: 6–12 months. Everything scoped and phased.
As a guide, not a religion. We use ITIL vocabulary and practices as a starting point and size them to your organization's actual complexity.
Yes. Tool-to-tool migration is a common engagement — data mapping, workflow reproduction, historical preservation, cutover.
All currently-supported ServiceNow release families. We plan and execute family upgrades regularly (Utah, Vancouver, Washington, Xanadu…).
Yes. Employee Center is the modern replacement for the classic Service Portal for internal users, and we deliver it as part of most modern ITSM engagements.
Yes — Discovery for on-prem, Service Graph Connectors for cloud, custom integrations where needed. CMDB health is a core capability.
Reach out — we get back within 1 business day.
